{"id":118,"date":"2025-02-10T15:15:08","date_gmt":"2025-02-10T20:15:08","guid":{"rendered":"https:\/\/sites.nd.edu\/businessanalysis\/?page_id=118"},"modified":"2025-03-07T21:00:42","modified_gmt":"2025-03-08T02:00:42","slug":"how-to-define-requirements","status":"publish","type":"page","link":"https:\/\/sites.nd.edu\/businessanalysis\/?page_id=118","title":{"rendered":"Requirements Elicitation"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Requirements elicitation is the process of gathering, identifying, and understanding stakeholder needs, expectations, and constraints to define clear and actionable requirements for a project or system. Effective elicitation helps bridge the gap between business goals and technical implementation, reducing the risk of misalignment and project failures.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is a Requirement?<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A requirement is something that is needed or wanted with regards to a future system, product, process or procedure.<\/li>\n\n\n\n<li>Effective requirements define a project&#8217;s real needs as well as the effective, clear solutions.<\/li>\n\n\n\n<li>A solution may require multiple <a href=\"https:\/\/sites.nd.edu\/businessanalysis\/?page_id=116\" data-type=\"link\" data-id=\"https:\/\/sites.nd.edu\/businessanalysis\/?page_id=116\">Requirement Levels and Types<\/a>.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Why Are Requirements Important?<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Vague or missing requirement specification is one of the highest causes of project failure. \n<ul class=\"wp-block-list\">\n<li>Research shows that more than 70% of failed projects miss the mark due to a lack of requirements gathering. <\/li>\n\n\n\n<li>Based on this statistic, you can assume that if you don\u2019t bother to gather requirements effectively, or at all, you\u2019re probably going to deliver a real mess!<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>If the requirements are insufficient (i.e., not clearly and comprehensively defined), the project may be considered a failure even if it is delivered on time and within budget.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"501\" height=\"424\" src=\"https:\/\/sites.nd.edu\/businessanalysis\/files\/2025\/02\/Both-Orig-1.jpg\" alt=\"\" class=\"wp-image-30\" style=\"width:435px;height:auto\" srcset=\"https:\/\/sites.nd.edu\/businessanalysis\/files\/2025\/02\/Both-Orig-1.jpg 501w, https:\/\/sites.nd.edu\/businessanalysis\/files\/2025\/02\/Both-Orig-1-300x254.jpg 300w\" sizes=\"auto, (max-width: 501px) 100vw, 501px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Without well-defined requirements prior to vendor selection, your team may become overwhelmed and \u201ccharmed\u201d by the sales pitch and select a product that will not meet their actual needs.<\/li>\n\n\n\n<li>Some of the most common reasons for insufficient requirements are:\n<ul class=\"wp-block-list\">\n<li>Incomplete list of stakeholders<\/li>\n\n\n\n<li>Poor stakeholder representation\/support<\/li>\n\n\n\n<li>Time\/schedule limitations<\/li>\n\n\n\n<li>Limited knowledge\/understanding of the business analysis process<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">1. Techniques<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requirements elicitation involves the application of various techniques to ensure that all relevant perspectives are considered. <\/li>\n\n\n\n<li>It typically involves talking with stakeholders directly, researching topics, and reviewing existing documentation.<\/li>\n\n\n\n<li>You can elicit requirements using any method <em>or combination of methods <\/em>that enables you to uncover detailed information related to the project objectives.<\/li>\n\n\n\n<li>Some of the most common requirements elicitation techniques include:\n<ul class=\"wp-block-list\">\n<li>Brainstorming<\/li>\n\n\n\n<li>Diagramming<\/li>\n\n\n\n<li>Document Analysis (reviewing existing documentation)<\/li>\n\n\n\n<li>Focus Groups<\/li>\n\n\n\n<li>Interface Analysis (reviewing existing interfaces)<\/li>\n\n\n\n<li>Interviews<\/li>\n\n\n\n<li>Observation<\/li>\n\n\n\n<li>Workshops<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>See <a href=\"https:\/\/sites.nd.edu\/businessanalysis\/?page_id=321\" data-type=\"page\" data-id=\"321\">Elicitation Techniques<\/a> for detailed information about the techniques specified above.<\/li>\n\n\n\n<li>The project&#8217;s stakeholders, complexity and timeline will dictate the best method or combination of methods for eliciting requirements.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">2. Documentation<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>As you identify the applicable requirements during elicitation, they should be documented.\n<ul class=\"wp-block-list\">\n<li>See <a href=\"https:\/\/sites.nd.edu\/businessanalysis\/?page_id=165\" data-type=\"page\" data-id=\"165\">Requirements Documentation<\/a> for detailed information about documenting requirements.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Requirements elicitation is the process of gathering, identifying, and understanding stakeholder needs, expectations, and constraints to define clear and actionable requirements for a project or system. Effective elicitation helps bridge the gap between business goals and technical implementation, reducing the risk of misalignment and project failures. What is a Requirement? Why Are Requirements Important? 1. [&hellip;]<\/p>\n","protected":false},"author":4975,"featured_media":0,"parent":38,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-118","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/pages\/118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/users\/4975"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=118"}],"version-history":[{"count":18,"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/pages\/118\/revisions"}],"predecessor-version":[{"id":356,"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/pages\/118\/revisions\/356"}],"up":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=\/wp\/v2\/pages\/38"}],"wp:attachment":[{"href":"https:\/\/sites.nd.edu\/businessanalysis\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}