Difference between revisions of "SSC Architecture Deliverables and Reports"

From wiki
Jump to navigation Jump to search
(Defined Conceptual, Logical/physical, and reference architecture documents, and IT Standard documents.)
m
Line 1: Line 1:
 +
[[File:EA Sticker.png|alt=SSC Enterprise Architecture|right|frameless|225x225px]]
 
Architecture deliverables consist of one or more architecture artifacts that are combined and formally reviewed, agreed, and signed off by stakeholders.
 
Architecture deliverables consist of one or more architecture artifacts that are combined and formally reviewed, agreed, and signed off by stakeholders.
  

Revision as of 09:25, 20 September 2019

SSC Enterprise Architecture

Architecture deliverables consist of one or more architecture artifacts that are combined and formally reviewed, agreed, and signed off by stakeholders.

Key SSC EA deliverables

Conceptual Architecture Document

Artifacts included: Solution requirements catalog (initial/high-level), solution motivation diagram, context diagram, conceptual architecture diagram.

Purpose: To provide a conceptual architecture at an early stage (ideally project ideation/definition), that identifies the key strategic outcomes/capabilities served/realized by the initiative, and generally what shall be done for whom, and how success will be measured/determined. It is a key deliverable in determining the initial architecture approval to proceed for all new/changing services, and projects at SSC.

Stakeholders: Architecture Council, ESSARB, Enterprise Architecture Directorate.

Related SSC processes: PGoF, Service Management Framework.

Author: Solution or Service Architect.

Logical/Physical Architecture Document

Artifacts included: Solution requirements catalog (detailed), solution motivation diagram,

Purpose: To provide a detailed logical/physical solution architecture, that identifies the complete business, information, application and technology needs of the initiative, their compliance with existing EA principles, enterprise, service, solution and reference architectures, alignment with SSC target architecture, and IT Standards. p

Stakeholders: Architecture Council, ESSARB, Enterprise Architecture Directorate.

Related SSC processes: PGoF, Service Management Framework.

Author: Solution or Service Architect

Reference Architecture Document

Artifacts included: Reference Architecture diagram(s).

Purpose: To identify, for a particular state, situations, conditions, circumstances, what architecture concerns, considerations and patterns should be applied in the development of new archtiectures.

IT Standard Document

Defined standards/norms that should be followed in the development of architecture, designs and IT implementations at SSC. As per SSC's IT Standards Framework.