<p>Enter Organization Name</p><p>Enter Project Name Requirements Definition Approval Signatures</p><p>Name: Name: Title: Title: </p><p>Name: Name: Title: Title: </p><p>Name: Name: Title: Title: </p><p>Name: Name: Title: Title: </p><p>Name: Name: Title: Title: </p><p>Prepared by: Version: Date:</p><p>Project Board: Sponsor: Customer Representative: Technical Representative: Enter Project Name Requirements Definition Enter Organization Name Document History</p><p>Reviewed By Organization Person</p><p>Copied To Organization Person</p><p>Revision Record Number Date and Sections Notes</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc iii 11/14/17 Acronyms</p><p>Acronym Description</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc iv 11/14/17 References</p><p>Document Title File Name</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc v 11/14/17 Table of Contents</p><p>1. INTRODUCTION 1</p><p>1.1 Document Purpose 1 1.2 Project Deliverable Roles 1 1.3 Related Documents 1</p><p>2. PROBLEM/REQUIREMENTS LIST 2</p><p>2.1 High Level Problem/Requirements 2 2.2 Detailed Requirements 2</p><p>3. DOMAIN KNOWLEDGE 2</p><p>3.1 Business Domain 2 3.1.1 Description 2 3.1.2 Key Terms 2 3.2 Technical Domain 3 3.2.1 High Level Decomposition/Structure 3 3.2.2 Common Problems/Pitfalls 3 3.2.3 Key Terms 3 3.2.4 Expert List 3 3.2.5 Key Reference Materials 3</p><p>4. HISTORICAL DATA (PREVIOUS CHANGE EFFORTS) 3</p><p>4.1 Description 3 4.2 Observations 3 4.3 Implications for the Present Rollout 4</p><p>5. WHOLE PRODUCT EXERCISE 4</p><p>5.1.1 Whole Product Wheel 4 5.1.2 Component Descriptions 4 5.1.3 Sequence Order 5 5.1.4 Whole Product Concerns 6</p><p>6. APPENDICES 6</p><p>6.1 Defined Processes/Model 7 6.2 Related Work Papers 8 6.3 REVISION HISTORY 8</p><p>7. GLOSSARY 8</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc vi 11/14/17 0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc vii 11/14/17 1. INTRODUCTION</p><p>1.1 Document Purpose The Requirements Definition Document is a compilation of the following products:  Problem/Requirement List  Domain Knowledge Notebook  Historical Data  Whole Product Exercise</p><p>1.2 Project Deliverable Roles The people listed below will receive a copy of the Requirements Definition deliverable. See the Project Plan for a description of the roles of the Creator, Reviewers, and Acceptor/Approvers.</p><p>This list is current as of November 14, 2017. </p><p>Creator Organization Name</p><p>Reviewers Organization Name</p><p>Acceptor/Approvers Organization Name</p><p>1.3 Related Documents</p><p>2. PROBLEM/REQUIREMENTS LIST</p><p>2.1 High Level Problem/Requirements</p><p>ID Priority Problem/Requirement Description Type Solution/Rationale Number (Mandatory, Reporting, Low, External)</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc 1 11/14/17 2.2 Detailed Requirements</p><p>Detailed Requirements for high level requirement: (ID #) ID Priority Description Supporting Number Activities</p><p>3. DOMAIN KNOWLEDGE</p><p>3.1 Business Domain</p><p>3.1.1 Description</p><p>3.1.2 Key Terms</p><p>3.2 Technical Domain</p><p>3.2.1 High Level Decomposition/Structure</p><p>3.2.2 Common Problems/Pitfalls</p><p>3.2.3 Key Terms</p><p>3.2.4 Expert List</p><p>3.2.5 Key Reference Materials</p><p>4. HISTORICAL DATA (PREVIOUS CHANGE EFFORTS)</p><p>4.1 Description</p><p>4.2 Observations</p><p>4.3 Implications for the Present Rollout</p><p>5. WHOLE PRODUCT EXERCISE</p><p>5.1.1 Whole Product Wheel</p><p>5.1.2 Component Descriptions</p><p>Component Purpose Users Priority Critical Issues</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc 2 11/14/17 Name</p><p>5.1.3 Sequence Order</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc 3 11/14/17 5.1.4 Whole Product Concerns Whole product concerns (for each product) are questions and considerations that need to be considered in sketching the whole product solution or strategic/tactical directions that should be represented in the same solution.</p><p>CONCERN DESCRIPTION AREA Social: How will the product be made known and made useable to its users? Marketing Communication Training & Coaching Internal User Support Organizational: How will the organization support and control the product? Procedures Policies Operating Standards System Administration Product Management Technical: How will the technology be deployed and supported over the life of the product? Support Technical Documentation Architectural: How will the product fit the application environment and technical infrastructure? Integration</p><p>6. APPENDICES</p><p>6.1 Defined Processes/Model</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc 4 11/14/17 6.2 Related Work Papers These work papers were used as inputs to this deliverable:</p><p>Work Paper/Products Location</p><p>6.3 REVISION HISTORY The following table shows the history of revisions that have been made to this document. </p><p>Date Description Person Responsible</p><p>7. GLOSSARY A standard glossary of terms, including the names of all Best Practices Process Library methodologies and stages, is included in the standard Glossary. This section defines additional terms, including those specific to this business or project. Term Definition</p><p>0a9ddc8be1f3f8e3e86af74a2be3dd4f.doc 5 11/14/17</p>