# Architecture principles whose category is Architecture Review / Evolution / Governance Artifacts

> 17 records

This index as JSON: https://banes-lab.com/json/api/facets/architecture/category/architecture-review-evolution-governance-artifacts

## Entries

- [Assessment](https://banes-lab.com/records/architecture/assessment.md): The activity of evaluating a codebase or architecture against stated criteria, using collected evidence.
- [Architecture Review](https://banes-lab.com/records/architecture/architecture-review.md): The activity of examining a structural change against the architecture's criteria and recorded decisions before it is accepted.
- [Design Review](https://banes-lab.com/records/architecture/design-review.md): The activity of checking a component or feature design for contracts, failure modes and testability before it is built.
- [Code Review](https://banes-lab.com/records/architecture/code-review.md): The activity of having a second party read a code change against review standards before it merges.
- [Impact Analysis](https://banes-lab.com/records/architecture/impact-analysis.md): The activity of tracing a change through the dependency graph to find every consumer it affects.
- [Gap Analysis](https://banes-lab.com/records/architecture/gap-analysis.md): The activity of comparing the current state of a system with its target state and listing each difference.
- [Fitness Functions](https://banes-lab.com/records/architecture/fitness-functions.md): A mechanism that turns an architecture rule into an executable check the pipeline runs on every change.
- [Quality Attributes](https://banes-lab.com/records/architecture/quality-attributes.md): A conceptual representation of the non-functional properties a system must meet, each stated as a measurable scenario.
- [Architecture Decision Records (ADR)](https://banes-lab.com/records/architecture/architecture-decision-records.md): A formal definition of one architecture decision, recording its context, the choice made and its consequences.
- [Evolutionary Architecture](https://banes-lab.com/records/architecture/evolutionary-architecture.md): An approach in which the architecture changes in small increments, each guarded by fitness functions.
- [Minimum Viable Architecture](https://banes-lab.com/records/architecture/minimum-viable-architecture.md): An approach in which a system starts with only the structure its current quality attributes require, and defers the rest until a force demands it.
- [Greenfield Development](https://banes-lab.com/records/architecture/greenfield-development.md): An abstraction of building a new system with no inherited code, so its boundaries are designed from the current forces.
- [First-Principles Design](https://banes-lab.com/records/architecture/first-principles-design.md): An approach in which a design is derived from the problem's forces and invariants before any known pattern is chosen.
- [Reference Architecture](https://banes-lab.com/records/architecture/reference-architecture.md): A formal definition of the modules, patterns and allowed dependencies that a family of systems instantiates.
- [Pattern Consistency](https://banes-lab.com/records/architecture/pattern-consistency.md): The degree to which one kind of problem is solved with the same pattern throughout a codebase.
- [Architectural Consistency](https://banes-lab.com/records/architecture/architectural-consistency.md): The degree to which the code follows the system's declared boundaries, layers and dependency rules.
- [Standardization](https://banes-lab.com/records/architecture/standardization.md): A design rule that one format, tool or pattern is chosen for each recurring concern and applied everywhere it occurs.