SSC Architecture Deliverables and Reports - Revision history

Logan.scott: Replaced content with "{{Delete|reason=Expired content.}}"

2024-10-28T13:41:13Z

Replaced content with "{{Delete|reason=Expired content.}}"

Logan.scott at 19:53, 24 October 2024

2024-10-24T19:53:17Z

Stephen.anthony at 18:54, 24 September 2019

2019-09-24T18:54:09Z

Stephen.anthony at 17:14, 24 September 2019

2019-09-24T17:14:22Z

Stephen.anthony: /* Logical/Physical Architecture Document */

2019-09-24T17:10:35Z

Logical/Physical Architecture Document

Stephen.anthony at 14:25, 20 September 2019

2019-09-20T14:25:47Z

Stephen.anthony: Defined Conceptual, Logical/physical, and reference architecture documents, and IT Standard documents.

2019-09-19T23:16:21Z

Defined Conceptual, Logical/physical, and reference architecture documents, and IT Standard documents.

Stephen.anthony: Started page and descriptions of deliverables.

2019-09-19T23:00:54Z

Started page and descriptions of deliverables.

New page

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:

Logical/Physical Architecture Document:

← Older revision		Revision as of 13:41, 28 October 2024
Line 1:		Line 1:
−	~~'''Please note that this page is no longer being updated and the information appearing on these pages is no longer current.'''~~	+	{{Delete\|reason=Expired content.}}
−
−	~~'''For information about SSC's Enterprise Architecture practice, please see: [[/163gc.sharepoint.com/sites/ACoE-CEA/SitePages/Home.aspx~~\|~~Architecture Centre of Excellence - Centre d'excellence en architecture - Home]]'''[[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.~~
−
−	~~=== 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, 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]]~~

← Older revision		Revision as of 19:53, 24 October 2024
Line 1:		Line 1:
−	[[File:EA Sticker.png\|alt=SSC Enterprise Architecture\|right\|frameless\|225x225px]]	+	'''Please note that this page is no longer being updated and the information appearing on these pages is no longer current.'''
		+
		+	'''For information about SSC's Enterprise Architecture practice, please see: [[/163gc.sharepoint.com/sites/ACoE-CEA/SitePages/Home.aspx\|Architecture Centre of Excellence - Centre d'excellence en architecture - Home]]'''[[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.

← Older revision		Revision as of 18:54, 24 September 2019
Line 43:		Line 43:

	==== Assessment (Logical/Physical) ====		==== Assessment (Logical/Physical) ====
		+
		+	[[Category:Architecture]]
		+	[[Category:Enterprise Architecture]]
		+	[[Category:Modeling]]

← Older revision		Revision as of 17:14, 24 September 2019
Line 33:		Line 33:
	==== 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.
		+
		+	==== EA Strategic Roadmap ====
		+
		+	==== Services Roadmap ====
		+
		+	==== Service Roadmap ====
		+
		+	==== Assessment (Idea/Concept) ====
		+
		+	==== Assessment (Logical/Physical) ====

@@ Line 9: / Line 9: @@
 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.
@@ Line 16: / Line 16: @@
 ==== 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.

← Older revision		Revision as of 14:25, 20 September 2019
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.

@@ Line 1: / Line 1: @@
 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 ====
-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.