Statement of Understanding (SOU)

Statement of Understanding (SOU)

<p> AO</p><p>Statement of Understanding</p><p>This Statement of Understanding (SOU) is an agreement between the <<Office/Development Team>> team and the Architecture Office (AO) that describes specific expectations of the <<Name of Project>> project. It may include a description and rationale of the approach to be used, as well as details of expected deliverables for each point in the System Development Life Cycle (SDLC). This document can be referenced throughout the project and serve as a guide for decisions. </p><p>This document focuses on SDLC artifacts and does not cover all areas of documentation needed for the project. For example, C&A, DBMO, and Records Management are not addressed in this SOU and are still the responsibility of the development team. This document is valid for the initial project release or 12 months following initial approval. </p><p>Below is the list of deliverables for the project, their relationship to the SDLC, and any alternate deliverables and justifications that may be necessary to support the project’s needs.</p><p>SDLC High-Level Associated Yes/ Alternate Justification Phase Purpose Artifact No Deliverable R e q</p><p> u Vision i r . Unambiguous e m set of e n requirements: t Glossary s</p><p>& agreement </p><p>A between n</p><p> a stakeholders Business Rules l y and what s i s system should do Supplementary . Develop clear Specs understanding of requirements Use Case . Define Model boundaries . Provide Use Case Specs features</p><p>Navigation Map</p><p>D H Analysis Model e i g s h i g</p><p> n L . Allocate e v</p><p> e Functionality l</p><p>12/09/2014 Page 1 AO</p><p>SDLC High-Level Associated Yes/ Alternate Justification Phase Purpose Artifact No Deliverable . Understand the domain Navigation Map . Manage stakeholder expectations Test Strategy . Establish a test strategy Proof-of- Concept D e t a i l e . Builds on Design Model d</p><p>D existing design e</p><p> s . Ensures i g</p><p> n compliance with FSA Test Plan Reference Architecture Test Case</p><p>C . Transforms o n</p><p> s design into a t</p><p> r Source Code</p><p> u working c</p><p> t system, i o</p><p> n satisfying </p><p>& requirements</p><p>A . Develop s</p><p> s Developer e procedures for m Guide</p><p> b data conversion l y and/or warehousing I n d</p><p> e No standard p TCO will verify e artifacts exist n product meets d for this phase. e requirements n t</p><p>R . Support phase e l e . Discover No standard a s e possible defects artifacts exist </p><p>& . Perform Post for this phase. Release Assessment</p><p>12/09/2014 Page 2 AO</p><p>Agreement It is understood and agreed upon that this SOU may be adjusted as needed to ensure the success of the project.</p><p>Principal Contacts The principal contacts for this SOU Template are: . Cheryl Vukas, AO Chief, [email protected] . Inge Martens, AO SDLC Change Implementer, [email protected]</p><p>Signatures</p><p>______AO Chief</p><p>______ADC Architect</p><p>______PMO Chief</p><p>______Office Chief of the Requesting Office</p><p>*Please note - This document is not valid until proper approval signatures are obtained and the final document is submitted to the PMO office for filing.</p><p>12/09/2014 Page 3</p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    3 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us