This article would be quite helpful for folks in an Architect role, or somebody who is tasked to prepare a Solution Architecture document for their customers / implementation.

Background

Often working as a Platform Architect I am asked about preparing a SAD (Solution Architecture and Design document) for the Governance forums review.

These governance forums are usually Architecture Forums (AGF/GF) or so-called Technical Governance Forum (TGF) who are responsible for vetting the overall solution keeping in view the business objectives and limits of the technology in question. There are certain key elements around which these forums operate such as scrutinizing technical debt, business objectives met, resources required, understanding System Integration complexities and Roadmap. Often the stakeholders in these forums come from an Architecture background and are SME of their own domain (sometimes Enterprise Architects too)

To present this information to these stakeholders we need a document in proper format, and we may generally use this same format as an overall Solution Architecture & Design Document (SAD)

Here is a sample format that I’ve been following for our customers

===================================================================================

Context

Background

Security Regulatory Compliance

Guiding Principles

Business Function Impact

Scope & Requirements

In Scope

Out of Scope

Requirements

Solution Design

Current State Architecture

Future State Architecture

High level Solution Design

Conceptual Design

Data Sets

Data Model View – ServiceNow

Foundations Data

Impact on Existing Systems

Key design decisions

ServiceNow Components ( for e.g. Catalog, Plugins etc.)

Integrations In Scope

Integrations Conceptual View

Integration Details

Data Mapping

Mobile App

Details

Technology Impacts

Assumptions

Risk & Issues

Data Classifications

Data Sets (e.g. for IRM Entity, Risk Exposure, Framework , Risk Indicators etc. )

Data Archival

Data Anonymization

Data Normalization

Exemptions/Technical Debt

Glossary

References

===================================================================================

If you think we can add more stuff, then please add your comments on this article and I'll review and add.

This format is in general that I've used for my customers across the years