 |
Page History
| Scrollbar |
|---|
| Note | ||
|---|---|---|
| ||
Formatting is in progress. |
...
The following suggestions provide some guidance for structuring the existing inventory of use cases using the ODP community concepts:
- Adopt use case levelling to organize use cases in categories and relate these categories to each other; a side effect of this is that re-usable sequences can be identified, thus removing duplication and promoting reuse of both requirements and solution approaches;.
- Map the levelled use cases to the respective community models; note that this is inevitably a human activity, guided by rules defined in the Table 3.1-1. This table can also be used when analysing narrative text of use cases to identify interactions between the User and the System role;.
- Analyse the actions and interactions associated with system roles in the community and map them to appropriate candidate Enterprise Services;.
- Analyse whether there are possible sub-communities and/or relationships with other communities.
...
