![](\"http:\/\/3.bp.blogspot.com\/-pf5CC5OuWAA\/V-DG3fwDEfI\/AAAAAAAAA7k\/NePcQ-pCRP0GkB0h0NGOARcrg0sUSv5rwCK4B\/s1600\/4325067780_c251777417_z.jpg\")
<\/a><\/td><\/tr>- Feasibility Study<\/u>: Knowing if what the client wants is possible, taking into account technical, economical, and organizational aspects. This stage outputs the feasibility study report.<\/li>
- Requirement Gathering<\/u>: Getting the expectations of what the software should do from the client and end-users. Requirements must be clear, correct, consistent, coherent, modifiable, verifiable, unambiguous, traceable, and from a credible source.<\/li>
- Software Requirement Specification<\/u>: After collecting information from all the people involved, an engineer creates the SRS, where the client's specifications are expressed in natural language, and all the technical aspects of the project are detailed in order for it to be useful for the development team, including pseudo code and GUI sketches.<\/li>
- Software Requirement Validation<\/u>: Between the developer and client, the specifications are reviewed to verify that they are correct, within scope, and achievable.<\/li>
<\/li><\/ol>REQUIREMENT ELICITATION<\/div>It is an organized process to gather requirements for the software, it has four steps.<\/div>
<\/div>![\"Requirement](\"https:\/\/www.tutorialspoint.com\/software_engineering\/images\/requirement_elicitation_process.png\")
<\/a><\/div>
<\/div>First the developer gets the requirements from the client, then they are prioritized and categorized, next they are reviewed with the stakeholders to remove any ambiguity or doubts about the requirements, finally, they are documented correctly for the next phases of development.<\/div>
<\/div>One or more of these methods can be in the elicitation phases, each one with its ups and downs:<\/div>- Interviews<\/li>
- Surveys<\/li>
- Questionnaires<\/li>
- Brainstorming<\/li>
- Prototyping<\/li>
- Observation<\/li><\/ul>Hope y'all learned something from this :)<\/div><\/div>
Sources:
Tutorialspoint: Software Requirements<\/a><\/div>","protected":false},"excerpt":{"rendered":"In order to define what a piece of software can do, you have to define clearly the functions and requirements that it must contain for the customer to be satisfied and your team to know what to do and how.The goal is to arrive at a Software Requirements Specification (SRS) Document, a spec sheet that … Continue reading Software Requirements<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":37540,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[173,162,276,278,174,279,54,60,25],"class_list":["post-37539","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","category-syndicated","tag-process","tag-development","tag-elicitation","tag-initiation","tag-methodology","tag-requirement","tag-software","tag-software-engineering","tag-tc1019"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37539","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=37539"}],"version-history":[{"count":1,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37539\/revisions"}],"predecessor-version":[{"id":37541,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37539\/revisions\/37541"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media\/37540"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=37539"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=37539"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=37539"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Requirement Gathering<\/u>: Getting the expectations of what the software should do from the client and end-users. Requirements must be clear, correct, consistent, coherent, modifiable, verifiable, unambiguous, traceable, and from a credible source.<\/li>