Architectural Decisions/Waivers

An Architectural Decision (AD) captures significant design decisions that concern the software system. An AD is used in the following scenarios:

supporting design decisions that are significant, but do not need sign-off

supporting design decisions that require a waiver

documenting the usage of software not currently part of the Technical Reference Model (used with a pilot)

The Architectural Decisions validate and document critical design decisions that denote long-term effects on the system, as opposed to decisions that render a short-term, immediate impact. Through prudent and reasonable judgment, the development team should consider what decisions may/may not require an AD.

SDLC Waiver

All system development is to be conducted in accordance with the SDLC. There are circumstances when it is appropriate to deviate from the SDLC and published standards. When this situation occurs the deviation must be accompanied by an SDLC Waiver. The Architecture Office (AO) can assist with waiver content and review before the waiver is submitted for approval, but the development team is responsible for:

completing the waiv er request

obtaining the appropriate signatures

delivering the original signed waiver to PMO for retention

The entire process is depicted in the Waiver Process diagram.

Use the current SDLC Waiver template to ensure the waiver includes all required information and signatures.

In the event of waiver disapproval, the requesting Office Chief may submit a Waiver Override for additional director review.

Use the SDLC Director Waiver Override template to ensure the override request includes all required information, attachments and signatures. Once signatures are obtained, deliver the original signed document, with all attachments, to PMO.

When submitting an SDLC Waiver, an Architectural Decision may be used by the development team to document these decisions.