Friday, November 19, 2010

Use case maps: casual scenarios, architectural entities or behaviour patterns?

The basic idea of UCM is very simple and is captured by the phrase causal paths cutting across organizational structures. The realization of this idea produces a lightweight notation that scales up, while at the same time covering all of the foregoing complexity factors in an integrated and manageable fashion. The notation represents causal paths as sets of wiggly lines that enable a person to visualize scenarios threading through a system without the scenarios actually being specified in any detailed way (e.g. with messages). Compositions of wiggly lines (which may be called behavior structures) represent large-scale units of emergent behavior cutting across systems, such as network transactions, as first-class architectural entities that are above the level of details and independent of them (because they can be realized in different detailed ways).

  • Requirements engineering and design of:

    • Real-time systems
    • Object-oriented systems
    • Telecommunication systems
    • Distributed systems
    • Business processes
    • Multimedia systems
    • Agent systems
    • E-health systems
    • Aspected-oriented models


No comments: