{"id":37988,"date":"2016-10-24T12:25:21","date_gmt":"2016-10-24T17:25:21","guid":{"rendered":"http:\/\/tc1019softwareengineering.wordpress.com\/?p=309"},"modified":"2016-10-24T12:25:21","modified_gmt":"2016-10-24T17:25:21","slug":"software-requirements-elicitation-and-specification-6","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/software-requirements-elicitation-and-specification-6\/","title":{"rendered":"Software requirements elicitation and specification"},"content":{"rendered":"<h3><img class=\"alignnone size-full wp-image-320\" src=\"https:\/\/tc1019softwareengineering.files.wordpress.com\/2016\/10\/slide_2.jpg?w=775\" alt=\"slide_2\" srcset=\"https:\/\/tc1019softwareengineering.files.wordpress.com\/2016\/10\/slide_2.jpg?w=775 775w, https:\/\/tc1019softwareengineering.files.wordpress.com\/2016\/10\/slide_2.jpg?w=150 150w, https:\/\/tc1019softwareengineering.files.wordpress.com\/2016\/10\/slide_2.jpg?w=300 300w, https:\/\/tc1019softwareengineering.files.wordpress.com\/2016\/10\/slide_2.jpg?w=768 768w, https:\/\/tc1019softwareengineering.files.wordpress.com\/2016\/10\/slide_2.jpg 960w\" sizes=\"(max-width: 775px) 100vw, 775px\"   \/><\/h3>\n<p>The software requirements are description of features and functionalities of the target system. Requirements convey the expectations of users from the software product. The requirements can be obvious or hidden, known or unknown, expected or unexpected from client\u2019s point of view.<\/p>\n<h2>Requirement<\/h2>\n<p>The process to gather the software requirements from client, analyze and document them is known as requirement engineering. The goal of requirement engineering is to develop and maintain sophisticated and descriptive \u2018System Requirements Specification\u2019 document.<\/p>\n<h2>Requirement Engineering Process<\/h2>\n<ul>\n<li>easibility Study<\/li>\n<li>Requirement Gathering<\/li>\n<li>Software Requirement Specification<\/li>\n<li>Software Requirement Validation<\/li>\n<\/ul>\n<h3>Feasibility study<\/h3>\n<p>When the client approaches the organization for getting the desired product developed, it comes up with rough idea about what all functions the software must perform and which all features are expected from the software.<\/p>\n<h3>Requirement Gathering<\/h3>\n<p>If the feasibility report is positive towards undertaking the project, next phase starts with gathering requirements from the user. Analysts and engineers communicate with the client and end-users to know their ideas on what the software should provide and which features they want the software to include.<\/p>\n<h3>Software Requirement Specification<\/h3>\n<p>SRS is a document created by system analyst after the requirements are collected from various stakeholders. SRS defines how the intended software will interact with hardware, external interfaces, speed of operation, response time of system, portability of software across various platforms, maintainability, speed of recovery after crashing, Security, Quality, Limitations etc.<\/p>\n<h3>Software Requirement Validation<\/h3>\n<p>After requirement specifications are developed, the requirements mentioned in this document are validated. User might ask for illegal, impractical solution or experts may interpret the requirements incorrectly. This results in huge increase in cost if not nipped in the bud. Requirements can be checked against following conditions &#8211;<\/p>\n<ul class=\"list\">\n<li>If they can be practically implemented<\/li>\n<li>If they are valid and as per functionality and domain of software<\/li>\n<li>If <div class=\"post-limited-image\"><img alt=\"\" border=\"0\" src=\"http:\/\/feeds.wordpress.com\/1.0\/comments\/tc1019softwareengineering.wordpress.com\/309\/\" \/><\/div>\n<div class=\"post-limited-image\"><img alt=\"\" border=\"0\" src=\"https:\/\/pixel.wp.com\/b.gif?host=tc1019softwareengineering.wordpress.com&#038;blog=115377093&%23038;post=309&%23038;subd=tc1019softwareengineering&%23038;ref=&%23038;feed=1\" width=\"1\" height=\"1\" \/><\/div><!--more--> are any ambiguities<\/li>\n<li>If they are complete<\/li>\n<li>If they can be demonstrated<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>info: <a href=\"https:\/\/www.tutorialspoint.com\/software_engineering\/software_requirements.htm\" rel=\"nofollow\">https:\/\/www.tutorialspoint.com\/software_engineering\/software_requirements.htm<\/a><\/p>\n<p>&nbsp;<\/p><br \/>  <a rel=\"nofollow\" href=\"http:\/\/feeds.wordpress.com\/1.0\/gocomments\/tc1019softwareengineering.wordpress.com\/309\/\"><img alt=\"\" border=\"0\" src=\"http:\/\/feeds.wordpress.com\/1.0\/comments\/tc1019softwareengineering.wordpress.com\/309\/\" \/><\/a> <img alt=\"\" border=\"0\" src=\"https:\/\/pixel.wp.com\/b.gif?host=tc1019softwareengineering.wordpress.com&#038;blog=115377093&%23038;post=309&%23038;subd=tc1019softwareengineering&%23038;ref=&%23038;feed=1\" width=\"1\" height=\"1\" \/>","protected":false},"excerpt":{"rendered":"<p>The software requirements are description of features and functionalities of the target system. Requirements convey the expectations of users from the software product. The requirements can be obvious or hidden, known or unknown, expected or unexpected from client\u2019s point of view. Requirement The process to gather the software requirements from client, analyze and document them &hellip; <a href=\"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/software-requirements-elicitation-and-specification-6\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Software requirements elicitation and specification<\/span><\/a><\/p>\n","protected":false},"author":32,"featured_media":320,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[347,69,44,25],"class_list":["post-37988","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","category-syndicated","tag-software-requirements-elicitation-and-specification","tag-softwareengineering","tag-sin-categoria","tag-tc1019"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37988","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\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=37988"}],"version-history":[{"count":2,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37988\/revisions"}],"predecessor-version":[{"id":37990,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37988\/revisions\/37990"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=37988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=37988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=37988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}