Coherence home
Ethnography in systems design
Viewpoint oriented requirements
Use case and OO analysis
Coherence papers
Bibliography
Use cases and object oriented modelling in UML
Coherence has adopted use cases as a means of bridging the gap between the understandings of the social nature of work as described in the social viewpoints, and the models and descriptions of requirements in systems design. In particular, use cases offer a way of identifying, through the description of scenarios of system usage, the classes of objects, and their interactions, which must be modelled in the process of system design and development.Whilst use case analysis and Coherence may both provide useful information and focus for each other, Coherence in particular can act as a useful route into more detailed use case analysis. The focus on the social organization of the workplace leads naturally to consideration of interactions between actors and the system under consideration, which provides a link into the identification of use cases and the generation of use case models.
It should be noted that, whilst use cases are not tied to object oriented analysis and development, it is with this approach to systems design with which they are linked most strongly. Consequently, we have decided to link to object oriented development in Coherence, although this does not preclude linking through to structured analysis, or any other approach for that matter. In making this choice, Coherence must consequently address how to model the results of its social analysis in an object oriented manner. To do this, we have adopted UML (the Unified Modelling Language) as the notation which Coherence links to. UML, as its name suggests, is the coming together of a number of previously distinct modelling notations. It has been adopted as a standard by the OMG (Object Management Group) for the purpose of exchanging models, and is becoming widely used in industry.
|
|
