[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241969-105":53,"doc-detail-241969-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","requirements-elaboration-r03-u00-march-2010","Requirements Elaboration - R03-U00 - March 2010","","Requirements Elaboration defines three RQE activities—evaluate mandated requirements, document use case scenarios, and create requirements traceability matrix—supported by an RACI assignment across functional and program roles. The approach guides recipients to incorporate enterprise-level requirements from the Project Allocation Report into master requirements artifacts and to use the resulting use case models as inputs for analysis, design, and testing. Tools and artifacts are specified for each RQE step.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/requirements-elaboration-r03-u00-march-2010/241969/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/requirements-elaboration-r03-u00-march-2010/241969.png","ImageObject",442,249,{"name":88,"@type":89},"Olivia Brown","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-15","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":8},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of Requirements Elaboration in ProPath R03-U00?","Question",{"text":108,"@type":109},"It specifies activities extending beyond initial requirements gathering, including evaluation of enterprise-level requirements, documentation of use case scenarios, and ensuring requirements traceability.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What does RQE-1 cover and what output is produced?",{"text":113,"@type":109},"RQE-1 evaluates mandated requirements and is associated with creating the Project Allocation Report content as input for master requirements artifacts.",{"name":115,"@type":106,"acceptedAnswer":116},"How is requirements traceability ensured in RQE-3?",{"text":117,"@type":109},"RQE-3 creates the Requirements Traceability Matrix using IBM Rational RequisitePro® (or a provided template for teams without automated tools).","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},241969,1791717056,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":8,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":73},16904993612988,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","| Requirements Elaboration |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- |\n| Software Engineering Analyst | \u003Cbr>|  |  home |  goals |  raci |\n| Functional Analyst |  | \u003Cbr>|  |  |  |\n\nOED ProPath R03-U00 March 2010  \n\n| Requirements Elaboration |  |\n| --- | --- |\n|  |  home  process  raci\u003Cbr>Goals of Requirements Elaboration\u003Cbr>To specify a set of activities that extend beyond the initial requirements gathering process.\u003Cbr>Specific goals include:\u003Cbr>􀂟 Evaluate enterprise-level requirements for implementation\u003Cbr>􀂟 Document Use Case Scenarios\u003Cbr>􀂟 Ensure requirements traceability |\n\nOED ProPath R03-U00 March 2010  \nRequirements Elaboration RACI Chart-1  \nR = Responsible A = Accountable C = Consulted I = Informed home  process  goals  \n\n|  |  | Role |  |  |  |\n| --- | --- | --- | --- | --- | --- |\n|  |  | Functional Analyst | Software Engineering Analyst | Technical Project Manager | Standards Division Director |\n| RQE-1 | Evaluate Mandated Requirements |  | R |  | A |\n| RQE-2 | Document Use Case Scenarios | R |  | A |  |\n| RQE-3 | Create Requirements Traceability Matrix | R |  | A |  |\n\nOED ProPath R03-U00 March 2010  \n\n|  |  | Requirements Elaboration: RQE-1 Evaluate Mandated Requirements |  |  |  |\n| --- | --- | --- | --- | --- | --- |\n|  |  |  home |  process |  goals |  raci |\n| Description |  | The Project Allocation Report is a Microsoft Office ® Excel ® based report generated from the Enterprise Requirements Management Repository. The report contains a set of enterprise-level requirements and associated metadata that are determined to be applicable to a particular project iteration. A recipient project is expected to incorporate the requirements content of this report into their master requirements artifacts and subsequently implement them in the identified project iteration.\u003Cbr>Contact the Office of Enterprise Development (OED) -Standards Division\u003Cbr>Enterprise Requirements Management Team [email address: 'VA OIT OED SE Enterprise Requirements Management] . |  |  |  |\n| Artifacts\u003Cbr>Used |  | Enterprise RM Project Allocation Questionnaire Project Charter\u003Cbr>Project Management Plan Stakeholder Request |  |  |  |\n| Artifacts\u003Cbr>Created |  | Project Allocation Report |  |  |  |\n| Responsible Role |  | Software Engineering Analyst |  |  |  |\n| Tools |  | IBM Rational RequisitePro ® |  |  |  |\n| Standards |  |  |  |  |  |\n| More Info.... |  | Enterprise Requirements Repository |  |  |  |\n\nOED ProPath R03-U00 March 2010  \n\n|  |  | Requirements Elaboration: RQE-2 Document Use Case Scenarios |  |  |  |\n| --- | --- | --- | --- | --- | --- |\n|  |  |  home |  process |  goals |  raci |\n| Description |  | The Functional Analyst creates the Use Case Model and associated Use Cases, taking the Project Allocation Report into consideration. The Use Case Model, a high-level requirements document, (1) models the system's intended functions and its environment and (2) serves as a contract between the customer and the developers.\u003Cbr>Each Use Case specifies the actors and the sequence of activities performed by the actors interacting with the system. The Use Case Model and Use Cases serve as input for the analysis, design, and testing activities. |  |  |  |\n| Artifacts\u003Cbr>Used |  | Project Allocation Report Requirements Specification Document Stakeholder Request |  |  |  |\n| Artifacts\u003Cbr>Created | | Use Case Model\u003Cbr>Use Case Specifications |  |  |  |\n| Responsible Role |  | Functional Analyst |  |  |  |\n| Tools |  | IBM Rational RequisitePro ® |  |  |  |\n| Standards |  |  |  |  |  |\n| More Info.... |  |  |  |  |  |\n\nOED ProPath R03-U00 March 2010  \n\n|  |  | Requirements Elaboration: RQE-3 Create Requirements Traceability Matrix |  |  |  |\n| --- | --- | --- | --- | --- | --- |\n|  |  |  home |  process |  goals |  raci |\n| Description |  | The Functional Analyst generates the Requirements Traceability Matrix in the project's IBM Rational RequisitePro ® project. Development teams that do not have access to automated tools should use the ","cbCaigtwShtCtUsC","https://ap.wps.com/l/cbCaigtwShtCtUsC","pdf",139694,6,"English","# Requirements Elaboration\n## Goals of Requirements Elaboration\n## Requirements Elaboration - RQE-1 Evaluate Mandated Requirements\n## Requirements Elaboration - RQE-2 Document Use Case Scenarios\n## Requirements Elaboration - RQE-3 Create Requirements Traceability Matrix","[{\"question\":\"What is the purpose of Requirements Elaboration in ProPath R03-U00?\",\"answer\":\"It specifies activities extending beyond initial requirements gathering, including evaluation of enterprise-level requirements, documentation of use case scenarios, and ensuring requirements traceability.\"},{\"question\":\"What does RQE-1 cover and what output is produced?\",\"answer\":\"RQE-1 evaluates mandated requirements and is associated with creating the Project Allocation Report content as input for master requirements artifacts.\"},{\"question\":\"How is requirements traceability ensured in RQE-3?\",\"answer\":\"RQE-3 creates the Requirements Traceability Matrix using IBM Rational RequisitePro® (or a provided template for teams without automated tools).\"}]","Requirements Elaboration - R03-U00 - March 2010 | PDF",1789183941]