Changes

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.

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.

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.

Stakeholders:  Architecture Council, ESSARB, Enterprise Architecture Directorate, solution architects, service architects, project teams, service leads, service teams.

Related SSC processes:  PGoF, Service Management Framework.

Related SSC processes:  PGoF, Service Management Framework.

==== Logical/Physical Architecture Document ====

==== Logical/Physical Architecture Document ====

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

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

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.

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.

Related SSC processes:  PGoF, Service Management Framework.

==== IT Standard Document ====

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

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.