Statement of Understanding (SOU)

Total Page:16

File Type:pdf, Size:1020Kb

Statement of Understanding (SOU)

AO

Statement of Understanding

This Statement of Understanding (SOU) is an agreement between the <> team and the Architecture Office (AO) that describes specific expectations of the <> 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.

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.

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.

SDLC High-Level Associated Yes/ Alternate Justification Phase Purpose Artifact No Deliverable R e q

u Vision i r . Unambiguous e m set of e n requirements: t Glossary s

& agreement

A between n

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

Navigation Map

D H Analysis Model e i g s h i g

n L . Allocate e v

e Functionality l

12/09/2014 Page 1 AO

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

D existing design e

s . Ensures i g

n compliance with FSA Test Plan Reference Architecture Test Case

C . Transforms o n

s design into a t

r Source Code

u working c

t system, i o

n satisfying

& requirements

A . Develop s

s Developer e procedures for m Guide

b data conversion l y and/or warehousing I n d

e No standard p TCO will verify e artifacts exist n product meets d for this phase. e requirements n t

R . Support phase e l e . Discover No standard a s e possible defects artifacts exist

& . Perform Post for this phase. Release Assessment

12/09/2014 Page 2 AO

Agreement It is understood and agreed upon that this SOU may be adjusted as needed to ensure the success of the project.

Principal Contacts The principal contacts for this SOU Template are: . Cheryl Vukas, AO Chief, [email protected] . Inge Martens, AO SDLC Change Implementer, [email protected]

Signatures

______AO Chief

______ADC Architect

______PMO Chief

______Office Chief of the Requesting Office

*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.

12/09/2014 Page 3

Recommended publications