 |
Page History
| Anchor | ||||
|---|---|---|---|---|
|
A community model can be represented with different levels of detail to reflect different levels of detail in use cases, as shown in the Table 1 above. The greyed columns in the Table 1provide a mapping from the use case levels to community modelling concepts and the associated UML for ODP notation.
We illustrate these different levels of detail in community models using the simple Federated Repository example introduced in section 4.1.
Figure 13 can be considered a community model representation of the level 0 use case (summary use case) as it only identifies key roles in the community and the community objective. Note we also add a Policy package as a placeholder for future requirements.
This model can be further refined by adding the high-level interaction called Repository Access between the user and the system (level 2), as shown in Figure 15. This level can be further refined by adding detail to the interactions, specifying types of access to the Repository, namely Query, Identify and Aggregate Data (level 3). This is also depicted in the figure.
| Anchor | ||||
|---|---|---|---|---|
|
