{"id":107,"date":"2022-01-26T19:38:11","date_gmt":"2022-01-26T19:38:11","guid":{"rendered":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/chapter\/4-3-requirements-traceability-matrix\/"},"modified":"2024-12-23T17:47:05","modified_gmt":"2024-12-23T17:47:05","slug":"4-3-requirements-traceability-matrix","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/chapter\/4-3-requirements-traceability-matrix\/","title":{"rendered":"4.3 Requirements Traceability Matrix"},"content":{"raw":"The project team should link the requirements to the activities and deliverables that satisfy them during the project. The requirements traceability matrix is a common structure used by project teams. It also shows each requirement\u2019s relationship to other requirements. Traceability is used to help ensure that the solution conforms to requirements and assists in scope, change, risk, time, cost, and communication management[footnote]International Institute of Business Analysis. (2015). A guide to the Business Analysis Body of Knowledge (BABOK Guide), version 3.0. Toronto, Ont: International Institute of Business Analysis.[\/footnote]. A formal traceability matrix is usually built hierarchically, starting with high-level requirements and filling in the details as the requirement is progressively elaborated. This hierarchy is similar to an outline filled in as more detail is known[footnote]Business Analysis for Practitioners: A Practice Guide (2015). Project Management Institute.[\/footnote].\r\n\r\nThis matrix can include the information regarding:\r\n<ul>\r\n \t<li>Requirement ID\r\n<ul>\r\n \t<li>A unique identifier<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Associate ID\r\n<ul>\r\n \t<li>A unique identifier for requirements associated with higher-level requirements<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Requirement category<\/li>\r\n \t<li>Requirement description\r\n<ul>\r\n \t<li>A textual description of the requirement<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Current status\r\n<ul>\r\n \t<li>E.g., active, canceled, deferred, added, approved, assigned, completed.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Status date<\/li>\r\n \t<li>Business needs, goals, and objectives\r\n<ul>\r\n \t<li>To address the rationale for inclusion<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Project objectives\r\n<ul>\r\n \t<li>To address the rationale for inclusion<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>WBS number\r\n<ul>\r\n \t<li>The relationship of the requirement with project activities and milestones<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Design ID\r\n<ul>\r\n \t<li>The relationship of the requirement with the design elements<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Build ID\r\n<ul>\r\n \t<li>The relationship of the requirement with the implementation of a specific feature<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li>Test strategy and test scenarios (e.g., technical\/system case tests, user\/acceptance case tests)\r\n<ul>\r\n \t<li>Test cases that will validate that the built features perform as required by the requirements.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\nLet\u2019s create a small version of the requirements traceability matrix for Grocery LLC\u2019s m-commerce project.\r\n<ul>\r\n \t<li>ID (1): Customers shall log in to the application using their usernames and passwords.<\/li>\r\n \t<li>ID (2): Customer profile information, including the name, shipping and billing addresses, and payment accounts, shall synchronize across all interfaces (mobile application, mobile website, and desktop website).<\/li>\r\n<\/ul>\r\n<div>\r\n<table class=\"grid\" style=\"border-collapse: collapse;width: 100%\" border=\"0\"><caption>Table 4.1: Requirements Traceability Matrix<\/caption>\r\n<tbody>\r\n<tr>\r\n<td style=\"width: 6.39313%\"><strong>ID<\/strong><\/td>\r\n<td style=\"width: 9.95544%\"><strong>Associate ID<\/strong><\/td>\r\n<td style=\"width: 34.0013%\"><strong>Requirements Description<\/strong><\/td>\r\n<td style=\"width: 12.7545%\"><strong>Current Status<\/strong><\/td>\r\n<td style=\"width: 9.31927%\"><strong>WBS<\/strong><\/td>\r\n<td style=\"width: 9.57387%\"><strong>Design ID<\/strong><\/td>\r\n<td style=\"width: 8.81044%\"><strong>Build ID<\/strong><\/td>\r\n<td style=\"width: 9.19211%\"><strong>Test case<\/strong><\/td>\r\n<\/tr>\r\n<tr>\r\n<td style=\"width: 6.39313%\" rowspan=\"2\">1<\/td>\r\n<td style=\"width: 9.95544%\">1.1<\/td>\r\n<td style=\"width: 34.0013%\">Customers shall receive a one-time password to their mobile phones.<\/td>\r\n<td style=\"width: 12.7545%\">Active<\/td>\r\n<td style=\"width: 9.31927%\">2.2\r\n\r\n3.2<\/td>\r\n<td style=\"width: 9.57387%\">D3\r\n\r\nD6<\/td>\r\n<td style=\"width: 8.81044%\">B3\r\n\r\nB8<\/td>\r\n<td style=\"width: 9.19211%\">Case 2<\/td>\r\n<\/tr>\r\n<tr>\r\n<td style=\"width: 9.95544%\">1.2<\/td>\r\n<td style=\"width: 34.0013%\">Customers shall be able to sign in to the mobile application by swiping their fingerprints on their smartphones.<\/td>\r\n<td style=\"width: 12.7545%\">Active<\/td>\r\n<td style=\"width: 9.31927%\">2.2\r\n\r\n3.2<\/td>\r\n<td style=\"width: 9.57387%\">D3\r\n\r\nD6<\/td>\r\n<td style=\"width: 8.81044%\">B3<\/td>\r\n<td style=\"width: 9.19211%\">Case 3<\/td>\r\n<\/tr>\r\n<tr>\r\n<td style=\"width: 6.39313%\" rowspan=\"2\">2<\/td>\r\n<td style=\"width: 9.95544%\">2.1<\/td>\r\n<td style=\"width: 34.0013%\">The profile page consists of the fields \u201cFirst Name\u201d, \u201cMiddle Name,\u201d \u201cLast Name,\u201d \u201cGender,\u201d \u201cStreet Address,\u201d \u201cApartment\/Suite Number,\u201d \u201cCity,\u201d \u201cState,\u201d \u201cZip Code,\u201d \u201cMobile Phone Number,\u201d \u201cOther Phone Number,\u201d \u201cDebit\/Credit Card Number,\u201d \u201cDebit\/Credit Card Expiration Date,\u201d and \u201cDebit\/Credit Card Security Code.\u201d<\/td>\r\n<td style=\"width: 12.7545%\">Active<\/td>\r\n<td style=\"width: 9.31927%\">2.2\r\n\r\n4.4\r\n\r\n5.2<\/td>\r\n<td style=\"width: 9.57387%\">D2<\/td>\r\n<td style=\"width: 8.81044%\">B2<\/td>\r\n<td style=\"width: 9.19211%\">Case 6<\/td>\r\n<\/tr>\r\n<tr>\r\n<td style=\"width: 9.95544%\">2.2<\/td>\r\n<td style=\"width: 34.0013%\">When customers type new information or edit existing information in their profile pages on only one of the interfaces, this information will be updated immediately on other interfaces.<\/td>\r\n<td style=\"width: 12.7545%\">Active<\/td>\r\n<td style=\"width: 9.31927%\">2.2\r\n\r\n4.4\r\n\r\n5.2<\/td>\r\n<td style=\"width: 9.57387%\">D2\r\n\r\nD9<\/td>\r\n<td style=\"width: 8.81044%\">B2<\/td>\r\n<td style=\"width: 9.19211%\">Case 7<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/div>","rendered":"<p>The project team should link the requirements to the activities and deliverables that satisfy them during the project. The requirements traceability matrix is a common structure used by project teams. It also shows each requirement\u2019s relationship to other requirements. Traceability is used to help ensure that the solution conforms to requirements and assists in scope, change, risk, time, cost, and communication management<a class=\"footnote\" title=\"International Institute of Business Analysis. (2015). A guide to the Business Analysis Body of Knowledge (BABOK Guide), version 3.0. Toronto, Ont: International Institute of Business Analysis.\" id=\"return-footnote-107-1\" href=\"#footnote-107-1\" aria-label=\"Footnote 1\"><sup class=\"footnote\">[1]<\/sup><\/a>. A formal traceability matrix is usually built hierarchically, starting with high-level requirements and filling in the details as the requirement is progressively elaborated. This hierarchy is similar to an outline filled in as more detail is known<a class=\"footnote\" title=\"Business Analysis for Practitioners: A Practice Guide (2015). Project Management Institute.\" id=\"return-footnote-107-2\" href=\"#footnote-107-2\" aria-label=\"Footnote 2\"><sup class=\"footnote\">[2]<\/sup><\/a>.<\/p>\n<p>This matrix can include the information regarding:<\/p>\n<ul>\n<li>Requirement ID\n<ul>\n<li>A unique identifier<\/li>\n<\/ul>\n<\/li>\n<li>Associate ID\n<ul>\n<li>A unique identifier for requirements associated with higher-level requirements<\/li>\n<\/ul>\n<\/li>\n<li>Requirement category<\/li>\n<li>Requirement description\n<ul>\n<li>A textual description of the requirement<\/li>\n<\/ul>\n<\/li>\n<li>Current status\n<ul>\n<li>E.g., active, canceled, deferred, added, approved, assigned, completed.<\/li>\n<\/ul>\n<\/li>\n<li>Status date<\/li>\n<li>Business needs, goals, and objectives\n<ul>\n<li>To address the rationale for inclusion<\/li>\n<\/ul>\n<\/li>\n<li>Project objectives\n<ul>\n<li>To address the rationale for inclusion<\/li>\n<\/ul>\n<\/li>\n<li>WBS number\n<ul>\n<li>The relationship of the requirement with project activities and milestones<\/li>\n<\/ul>\n<\/li>\n<li>Design ID\n<ul>\n<li>The relationship of the requirement with the design elements<\/li>\n<\/ul>\n<\/li>\n<li>Build ID\n<ul>\n<li>The relationship of the requirement with the implementation of a specific feature<\/li>\n<\/ul>\n<\/li>\n<li>Test strategy and test scenarios (e.g., technical\/system case tests, user\/acceptance case tests)\n<ul>\n<li>Test cases that will validate that the built features perform as required by the requirements.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Let\u2019s create a small version of the requirements traceability matrix for Grocery LLC\u2019s m-commerce project.<\/p>\n<ul>\n<li>ID (1): Customers shall log in to the application using their usernames and passwords.<\/li>\n<li>ID (2): Customer profile information, including the name, shipping and billing addresses, and payment accounts, shall synchronize across all interfaces (mobile application, mobile website, and desktop website).<\/li>\n<\/ul>\n<div>\n<table class=\"grid\" style=\"border-collapse: collapse;width: 100%\">\n<caption>Table 4.1: Requirements Traceability Matrix<\/caption>\n<tbody>\n<tr>\n<td style=\"width: 6.39313%\"><strong>ID<\/strong><\/td>\n<td style=\"width: 9.95544%\"><strong>Associate ID<\/strong><\/td>\n<td style=\"width: 34.0013%\"><strong>Requirements Description<\/strong><\/td>\n<td style=\"width: 12.7545%\"><strong>Current Status<\/strong><\/td>\n<td style=\"width: 9.31927%\"><strong>WBS<\/strong><\/td>\n<td style=\"width: 9.57387%\"><strong>Design ID<\/strong><\/td>\n<td style=\"width: 8.81044%\"><strong>Build ID<\/strong><\/td>\n<td style=\"width: 9.19211%\"><strong>Test case<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 6.39313%\" rowspan=\"2\">1<\/td>\n<td style=\"width: 9.95544%\">1.1<\/td>\n<td style=\"width: 34.0013%\">Customers shall receive a one-time password to their mobile phones.<\/td>\n<td style=\"width: 12.7545%\">Active<\/td>\n<td style=\"width: 9.31927%\">2.2<\/p>\n<p>3.2<\/td>\n<td style=\"width: 9.57387%\">D3<\/p>\n<p>D6<\/td>\n<td style=\"width: 8.81044%\">B3<\/p>\n<p>B8<\/td>\n<td style=\"width: 9.19211%\">Case 2<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 9.95544%\">1.2<\/td>\n<td style=\"width: 34.0013%\">Customers shall be able to sign in to the mobile application by swiping their fingerprints on their smartphones.<\/td>\n<td style=\"width: 12.7545%\">Active<\/td>\n<td style=\"width: 9.31927%\">2.2<\/p>\n<p>3.2<\/td>\n<td style=\"width: 9.57387%\">D3<\/p>\n<p>D6<\/td>\n<td style=\"width: 8.81044%\">B3<\/td>\n<td style=\"width: 9.19211%\">Case 3<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 6.39313%\" rowspan=\"2\">2<\/td>\n<td style=\"width: 9.95544%\">2.1<\/td>\n<td style=\"width: 34.0013%\">The profile page consists of the fields \u201cFirst Name\u201d, \u201cMiddle Name,\u201d \u201cLast Name,\u201d \u201cGender,\u201d \u201cStreet Address,\u201d \u201cApartment\/Suite Number,\u201d \u201cCity,\u201d \u201cState,\u201d \u201cZip Code,\u201d \u201cMobile Phone Number,\u201d \u201cOther Phone Number,\u201d \u201cDebit\/Credit Card Number,\u201d \u201cDebit\/Credit Card Expiration Date,\u201d and \u201cDebit\/Credit Card Security Code.\u201d<\/td>\n<td style=\"width: 12.7545%\">Active<\/td>\n<td style=\"width: 9.31927%\">2.2<\/p>\n<p>4.4<\/p>\n<p>5.2<\/td>\n<td style=\"width: 9.57387%\">D2<\/td>\n<td style=\"width: 8.81044%\">B2<\/td>\n<td style=\"width: 9.19211%\">Case 6<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 9.95544%\">2.2<\/td>\n<td style=\"width: 34.0013%\">When customers type new information or edit existing information in their profile pages on only one of the interfaces, this information will be updated immediately on other interfaces.<\/td>\n<td style=\"width: 12.7545%\">Active<\/td>\n<td style=\"width: 9.31927%\">2.2<\/p>\n<p>4.4<\/p>\n<p>5.2<\/td>\n<td style=\"width: 9.57387%\">D2<\/p>\n<p>D9<\/td>\n<td style=\"width: 8.81044%\">B2<\/td>\n<td style=\"width: 9.19211%\">Case 7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<hr class=\"before-footnotes clear\" \/><div class=\"footnotes\"><ol><li id=\"footnote-107-1\">International Institute of Business Analysis. (2015). A guide to the Business Analysis Body of Knowledge (BABOK Guide), version 3.0. Toronto, Ont: International Institute of Business Analysis. <a href=\"#return-footnote-107-1\" class=\"return-footnote\" aria-label=\"Return to footnote 1\">&crarr;<\/a><\/li><li id=\"footnote-107-2\">Business Analysis for Practitioners: A Practice Guide (2015). Project Management Institute. <a href=\"#return-footnote-107-2\" class=\"return-footnote\" aria-label=\"Return to footnote 2\">&crarr;<\/a><\/li><\/ol><\/div>","protected":false},"author":3,"menu_order":4,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-107","chapter","type-chapter","status-publish","hentry"],"part":99,"_links":{"self":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/107","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/users\/3"}],"version-history":[{"count":2,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/107\/revisions"}],"predecessor-version":[{"id":773,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/107\/revisions\/773"}],"part":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/parts\/99"}],"metadata":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/107\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/media?parent=107"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapter-type?post=107"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/contributor?post=107"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/license?post=107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}