Application Architecture
Application Architecture connects business capabilities, application systems and data. Teams can see which systems support an activity, where information appears across applications, and how services and interfaces connect them.
Manage the application portfolio
| Area | Question it answers |
|---|---|
| Application systems | What applications exist and what business responsibilities do they carry? |
| Application modules | Which parts of a system support each business area? |
| Application services | What reusable capabilities does an application offer? |
| Interfaces and integrations | How do systems exchange information and depend on one another? |
| Architecture coverage | Which applications support each capability and business object? |
Moving from the portfolio to services and integrations helps teams clarify system responsibilities, identify gaps and duplication, and understand critical dependencies.
Maintain application records
Application records describe system identity, business purpose, and relevant development and operational information. They provide a shared directory for enterprise architecture, IT and business teams.
Systems are maintained at enterprise scope. A system used by several domains has one shared record. Domain teams can consult and reference the directory within their permissions, including selecting a source system during table annotation.
Find data through applications
Collection and annotation in Projects connect applications to physical tables, the business objects they implement and the responsibility domains involved.
ERP and SRM, for example, may both handle supplier information. Linking their tables to the same Supplier business object lets teams examine both systems through a common business concept, compare their uses and coordinate definitions.
Application usage views reflect governance information as it changes and respect the user's access scope.
Work with the other modules
| Module | Connection to application architecture |
|---|---|
| Operating Model | Provides business capabilities and governance responsibilities |
| Data Architecture | Defines the business objects and information structures handled by applications |
| Standards | Provides definitions, codes and security requirements for application data |
| Projects | Supplies collected structures and annotations to examine actual data distribution |
| Datasets | Describes how governed data is delivered to consumers through shared contracts |
Common uses
- Clarify system responsibilities: identify applications supporting a business capability.
- Locate data sources: move from a business object to related applications and tables.
- Assess change impact: use service, integration and data relationships to identify collaborators.
- Align definitions across systems: discuss differences using shared objects and standards.
Data Architecture
Build a shared view of enterprise information through subject classification, business objects, logical models and physical mappings.
Standards
Align data definitions, controlled values, business measures and security requirements so teams and systems share understandable, reusable standards.