WicsaWikiWANParty:COPA
From WICSA Conference Wiki
Contents |
Overview
At Philips Research a system architecture approach is being developed under the name COPA: Component-Based Platform Architecting. It centers around the acronyms BAPO-CAFCR.
BAPO
BAPO expresses that the architecture is not determined in isolation, but should fit into a context:
- Business
- Architecture
- Process
- Organization
CAFCR
CAFCR summarizes the five main architectural views that bridge the gap between customer wishes and technical realization. Each view answers a specific question:
- Customer view
- What does the customer want?
- Application view
- How is the system used?
- Functional view
- What does the system offer?
- Conceptual view
- How does the system work?
- Realization view
- How is available technology used?
A very good description of the method is in the PhD thesis of Gerrit Muller. PhD: Faculty TPM Delft, June 7, 2004, Thesis: CAFCR: A Multi-view Method for Embedded Systems Architecting; Balancing Genericity and Specificity here is the thesis
Gaudi site gives many more references
Artifacts
These views are filled with artifacts (documents, models, etc), for example like in the following table:
| Customer | Application | Functional | Conceptual | Realization | |
| Variation | Variation models Scenarios |
Variation models Scenarios |
Variation models Scenarios |
Variation models Scenarios |
Variation models Scenarios |
| Functionality | Value proposition | User scenarios | Feature dictionary | System decomposition | Technology mapping |
| Qualities | Customer drivers | Quality requirements | Quality properties | Principles Mechanisms |
Mechanisms Conventions |
| Supporting artifacts | Context diagramTrend analysisCompetitor / complementer analysis |
System contextWorkflow contextDomain model |
Feature / value matrix | Collaborations Information models |
Collaboration estimations Supplier roadmaps |
The scenarios in this table are architecture scenarios, as defined with Scenario-Based Architecting.
