Use case modeling

This section presents use case modeling for the CRS. As mentioned, you should spend most of your time getting the use case text right rather than the diagram. Figure 9.1 is a use case diagram for CRS. It is shown as an example and not meant to be complete. 

Please note that use case modeling is not associated with any development process. It is even independent of object-oriented technologies. It is a generic tool for capturing functional requirements. I have used use case specifications in ISIS PL projects, and it worked perfectly. 

Figure 9. Use Case Model of Trust Case Collaborative Development...

The result of a mediation from the respective use case models to the base vocabulary is illustrated in Fig. 14.14. As can be seen, attributes values are mediated to the common concept Constraint, which, in turn, can be either an EqualsCon-straint (attribute s value is specified to have a specific value), a LessThanConstraint (attribute s value is specified to be less than a specific value) and a GreaterThanCon-straint (attribute s value is specified to be greater than a specific value). By that, inconsistency rules can be formulated by referring to the concepts defined in the base vocabulary. 

Fig. 14.14 Result of mediating the use case models to the base vocabulary...

Figure 5-2 CAPE-ModE Functional Analysis using Use Case Modeling...

---