LEARN. PRACTICE. GROW.Concept and mechanism
Architecture governance supports direction and oversight of design and evolution decisions. During implementation, compare delivery against approved requirements and guidance. A successful functional test demonstrates tested behavior but does not guarantee satisfaction of an isolation or resilience requirement. Retain that evidence’s value and record the specific gap. The architectural role includes impact analysis and treatment recommendations; accepting business risk depends on defined authority. Do not assume the architect, project manager, and technician executing the change all have the same decision rights.
Guided application
In an incident near cut-off, an authorized urgent path may exist. Use it with rationale, known impact, test limits, application conditions, rollback, and follow-up. A temporary exception needs ownership and review; otherwise deviation may become permanent without a conscious decision. Urgency does not establish approval by itself, but neither does it require ignoring an existing rapid-decision mechanism. If the proposal is unacceptable, present consequences of alternatives. These examples are fictional and do not describe BNP Paribas internal procedures. In actual work, confirm governance, standards, and responsibilities applicable to the entity.
A ticket identifies the request; the decision and conditions show how deviation was handled.
Common pitfalls
Urgency as authority; test as approval; implicit permanent exception; architect accepting risk without a mandate.
Related topics: Content, views, and traceability · Architecture connected to value and operations
Record who decided, using what evidence, and under which conditions.
Reference: How ArchiMate and TOGAF complement each other · OGEA-101, TOGAF Enterprise Architecture Foundation; body of knowledge drawn from TOGAF Standard, 10th Edition