The detail a decision needs
“Every active case has an owner” states an important idea. A transfer contract defines when that owner can change. The chosen procedures and any supporting software put that agreement into practice.
A Simple Architectural Framework (ASAF) distinguishes three levels of abstraction:
| Level | Description | Example |
|---|---|---|
| Conceptual | Communicate the important concepts and their relationships. | A case has a current owner; a receiving person accepts a transfer. |
| Logical | Describe the required relationships and behaviour without choosing implementation details. | Check that the transfer offer and case version are current, keep one owner, and record the accepted transfer. |
| Physical | Specify the actual arrangements that realise the design. | The implemented interfaces, storage, configuration and operating procedures. |
A proposed physical design identifies intended arrangements. It becomes an as-built description only when it accurately records what was implemented. The fictional worked example still has open implementation choices and unrun checks.
Across the architecture
These levels apply to all aspects. A logical organisation view may describe responsibilities and decision rights; a physical one can identify the actual team assignments and procedures. Information has concepts, logical records and implemented representations.
Level of abstraction and scope answer different questions. An enterprise view can contain detailed information, while a small component may first need a conceptual explanation. The process areas describe the work that develops and revisits those descriptions.
Methodology configuration
Your method may use different labels for overview, design and implementation records. Match their purpose and detail through Methodology configuration. Keep links between views so that a changed rule can be followed to the arrangements that realise it.