Categories: Architecture

After reading Secure Design Best Practices, architects who are part of a software development team may find this page useful as the weaknesses are addressed by known security tactics, helping the architect in embedding security throughout the initial design process.

"Architecture is the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution." [IEEE 1471]

This document provides a guideline for tracking dependencies between architecture activities. A dependency exists when a specific activity needs to be executed before another activity can be executed or even started.

Architecture description markdown templates.

This document provides a guideline for structuring architecture documentation in the PAPCP R&D environment.

Architecture review checklist for pull requests in Markdown.

Architecture Review Goals

Threat modeling is the process of analyzing various business and technical requirements of a system identifying the potential threats, the mitigations of these threats, and documenting the vulnerabilities these threats have on the system.

The purpose of this guide is to provide handson support to the roles involved in defining the system architecture influenced by requirements, captured in the system epics, epics, and features.

Product capabilities describe what the product “can do” for anyone who wants to understand its capabilities. They represent the product's property and are updated throughout its lifecycle through multiple releases.

Product capability markdown template for ADO.

Software architecture is not a static document, instead, it's a continuous iterative process throughout each increment. This guide serves as a reference for the roles providing and describing different levels of architecture.

This chapter gives some basic best practices for a secure software design. Assessing how security is addressed in the design of a product is one important step to ensure that the product meets the best security level and can be done at various points in a product lifecycle.

This guide describes what system interfaces are, how they are documented, and how they are managed.

This guide describes the what, why, and how related to the versioning of architecture documents.