Bridging the Gap Between Requirements and Design with Use Case Maps Use Case …people.scs.carleton.ca/~sbtajali/4004/slides/4-1-UCM... · 2009-09-15 · Bridging the Gap Between
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Bridging the Gap Between Requirements and Design with Use Case Maps
Software Engineering Issues
u Requirements/analysis models need to support new types of dynamic systems– Run-time modification of system structure– Run-time modification of behaviour
u Need to go from a requirements/analysis model to design models in a seamless way
Bridging the Gap Between Requirements and Design with Use Case Maps
User Elevator Control System
inelevator
abovebelow
at requestedfloor
Arrival Sensor
approachingfloor
doorclosing-delay
add to list
[else]
no requests
[stationary]
[moving][not requested]
door closemotor up
motor down
moving
decide ondirection
motorstop
[requested]
dooropen
Select Destination
removefrom list
[more requests]
The elevator control system case study is adapted from Hassan Gomaa's Designing Concurrent, Distributed, And Real-Time Applications with UML (p459-462), copyright Hassan Gomaa 2001, published by Addison Wesley. Used with permission.
Bridging the Gap Between Requirements and Design with Use Case Maps
Complementary Yet Compatible!
Use Case MapsScenario notation, readable, abstract, scalable, loose, relatively effortless to learn
Use Case MapsScenario notation, readable, abstract, scalable, loose, relatively effortless to learn
LOTOSMature formal language, good theories and tools for V&V and completeness &consistency checking.
LOTOSMature formal language, good theories and tools for V&V and completeness &consistency checking.
BothFocus on ordering of actionsHave similar constructs à simpler mappingHandle specifications with or without componentsHave been used to describe dynamic systems in the pastHave been used to detect feature interactions in the past
BothFocus on ordering of actionsHave similar constructs à simpler mappingHandle specifications with or without componentsHave been used to describe dynamic systems in the pastHave been used to detect feature interactions in the past
Bridging the Gap Between Requirements and Design with Use Case Maps
Scenario Definitions
u Enhances the behavioural modeling capability of UCM paths and path elements
u Requires a path data model (for conditions at various points along the path)– Currently, global and modifiable Boolean variables
u Values may be assigned to variables along a path
– In future, …u Variables may possibly have different typesu Variables may be scoped to paths or componentsu Scenarios may be structured into sub-scenarios
Bridging the Gap Between Requirements and Design with Use Case Maps
Scenario Definitions
u Requires a more formal definition of some notational elements– Currently, logical expressions with global variables– Currently, OR forks, selection policies, start points,
waiting places, & timers covered (in future: loops)
u Scenario definitions consist of …– Name of scenario (scenarios may be grouped for
convenience)– Set of concurrent start points– Set of initial values assigned to global variables
Bridging the Gap Between Requirements and Design with Use Case Maps
!OnList
!Requested
ExampleUser
at floor
d own
elevator
approachingfloor
s top
-delay
d oor
r emovefrom list
Service Personnel
memory
[ else]
already on list
i n
m ovingm otor up
[ else]
d eci de ondi r ec t ion
i n-
door closem ovingm oving
approachingfloor
d oorclosing-delay
s top
[requested]
o pen
stationary-
[off] e xit
switch onabove
a pp. floor
s witch off
! OffOff
switch on
s wit ch off
Selected Contributionsu Amyot, D., Andrade, R., Logrippo, L., Sincennes, J., and Yi, Z. (1999) Formal Methods for Mobility
’99, Richardson, USA, D. and Andrade, R. (1999) Description of Wireless Intelligent Network Services with Use Ca
M aps. SBRC’99, Rio de Janeiro, Brazil, D., Buhr Gray, T., and , L. (1999) Use Case Maps for the Capture and Validation of
. ISRE'99, Limerick, Ireland, D. and Logrippo Use Case Maps and LOTO Sfor the Prototyping and Validation of a
. Computer Communication, 23(12)., D., Charfi Gray, T., , L., Sincennes Stepien, B., and Ware, T. (2000)
Feature description and feature interaction analysis with Use Case Maps and LO TOS. FI W'0 0, Sc otland.u Amyot, D. (2000), Use Case Maps as a Feature Description Notation. In: L ang uag e C onstruct s f o r
Designing Features, Gl asg ow, Sc otl and .u Amyot, D., and Logrippo, L. (2000) Structural Coverage for Lotos—A Probe Insertion Technique.
T est Co m ’2 000, Ottawa, Canada., D. and Mussbacher On the Extension of UML with Use Case Maps Concepts.
Y ork, UKu Amyot, D. and Eberlein, A. (2001) An Evaluation of Scenario Notations for Telecommunication Systems
. ICTS'01, Dallas, USAu Am yot, D. (2001) Specification and Validation of Telecommunications Systems with Use Case Maps and
LOTOS. Ph.D. thesis, University of Ottawa, Canadau Cameron, D. et al. (2001) Draft Specification of the User Requirements Notation, C ana dia n con t rib uti on to
-Tu Miga, A ., Amy ot, D., B ord ele au, F . , C am e ron, D ., and Wo odside, M . ( 200 1) Der ivi ng Mes sage S equ enc e
C har ts fro m U se Cas e M aps Sc enario Sp ec i fic ati ons . 10th S DL Forum, Co pen hag en, De nmarku Mussbacher, G. and Amyot, D. (2001) A Collection of Patterns for Use Case Maps,