Documents produced by IT Architects

This section discusses the key principle for any document produced by IT Architects.

This lecture describes the general purpose of the architecture documentation (not specific to individual documents).

This lecture provides a summary of the input documents required for the IT Architect to produce the architecture documents.

This lecture discusses the reason why the IT Architect should know well the content of the input documents.

This lecture discusses the Project Charter as an input document for architecture.

This section describes the requirements as input into the architecture documents.

This section discusses the functional requirements as input into architecture documents.

This section discusses the functional requirements sub-types and what is their value as input into architecture documents.

This section discusses the non-functional requirements as input into architecture documents.

This section discusses the business principles and drivers as inputs into architecture documents.

This section discusses change requests as input into architecture documents.

This section discusses the architecture frameworks and methodologies as input into architecture documents.

This section discusses the architectural capability assessment as input into architecture documents.

This section discusses the organizational model as input into architecture documents.

This lecture describes what is the purpose of the architecture document/blueprint.

This lecture describes what are the sections of the architecture document/blueprint and what is their content.

This lecture provides an extensive list of viewpoints the IT Architect can choose from the illustrate the architecture solution.

This section includes examples of the diagrams usually included in an architecture document/blueprint.

This lecture discusses in detail the architecture risks, what is their purpose and how they can be used as an effective tool to document the risks and their mitigation.

This lecture describes how to document the architecture decisions addressed during the creation and implementation of the solution as well as gaps in between the target state and what was actually implemented.

This lecture describes how to document the architecture future improvements that will be  addressed during future implementation phases. 

This lecture provides a real life example of a solution architecture for a mortgage calculator application. The pdf version of this has also been provided for your convenience.

This lecture describes what is the architecture decision document and what is its purpose as a IT Architect produced document.

This lecture describes what are the sections of the architecture decision document and what is their content.

This section provides an example of criteria that can be used for a complex architecture decision document.

This lecture describes what are the key activities in order to produce the architecture decision document.

This lecture provides an example of an architecture decision summary.

This lecture describes what is the implementation strategy document and what is its purpose as a IT Architect produced document.

This lecture describes what are the sections of the implementation strategy document and what is their content.

This lecture describes how the infrastructure strategy document applies to different architecture levels.

This lecture describes what is the purpose of the Request for Proposal (RFP)/Request for information (RFI) documents.

This lecture describes what are the key activities in order to produce the Request for Proposal (RFP)/Request for information (RFI) documents.

This lecture describes what is the purpose of the Architecture Proof of Concept (PoC).

This lecture describes what are the sections of the PoC report.

This lecture describes what are the key activities in order to produce the Architecture Proof of Concept (PoC) report.

This lecture describes what is the Business Technology Roadmap deck/ document and what is its purpose as a IT Architect produced document.

This lecture describes what is the purpose of the Business Technology Roadmap deck/document.

This section provides an example of a typical business technology roadmap.

Provide detailed information of why it is so much better to use AI to create the architecture documentation.

What are the prerequisites in order to use AI for the generation of the architecture documentation.