251
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + − + − + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SSC Architecture Deliverables and Reports (view source)
Revision as of 14:54, 24 September 2019
, 14:54, 24 September 2019no edit summary
[[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.
Key SSC EA deliverables
=== Key SSC EA deliverables ===
Conceptual Architecture Document:
==== Conceptual Architecture Document ====
Artifacts included: Solution requirements catalog (initial/high-level), solution motivation diagram, context diagram, conceptual architecture diagram.
Logical/Physical Architecture Document:
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, solution architects, service architects, project teams, service leads, service teams.
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, context diagram, conceptual architecture diagram, business process cooperation diagram (for the project/service), implementation and deployment diagram (optional), application cooperation diagram (optional), technology usage diagram, technology 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.
Stakeholders: Architecture Council, ESSARB, Enterprise Architecture Directorate, service architect, solution architects, designers/engineers, project teams, service leads, service teams.
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.
==== EA Strategic Roadmap ====
==== Services Roadmap ====
==== Service Roadmap ====
==== Assessment (Idea/Concept) ====
==== Assessment (Logical/Physical) ====
[[Category:Architecture]]
[[Category:Enterprise Architecture]]
[[Category:Modeling]]
