SElec-4 UseCases (1)

SElec-4 UseCases (1) - LECTURE 4: Use Cases Ivan Marsic...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Ivan Marsic Rutgers University LECTURE 4: Use Cases
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Topics Actors, Goals Sketchy/Summary Use Cases Use Case Diagram System Boundary and Subsystems Detailed Use Case Specification Traceability Matrix System Sequence Diagrams Risk Analysis and Reduction
Background image of page 2
Use Cases For Functional Requirements Analysis and Specification use case  is a description of how a user will use the  system-to-be to accomplish business goals Detailed use cases are usually written as usage scenarios or scripts , listing a specific sequence of actions and interactions between the actors and the system
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Deriving Use Cases from System Requirements REQ1: Keep door locked and auto-lock REQ2: Lock when “LOCK” pressed REQ3: Unlock when valid key provided REQ4: Allow mistakes but prevent dictionary attacks REQ5: Maintain a history log REQ6: Adding/removing users at runtime REQ7: Configuring the device activation preferences REQ8: Inspecting the access history REQ9: Filing inquiries ( Actors already given if working from user stories instead of system requirements ) 1 2 3 4 5 X Y Actor Actor’s Goal (what the actor intends to accomplish) Use Case Name Landlord To  dis a rm  the  lo c k a nd e nte r, a nd g e t s pa c e  lig hte d up. Unlock (UC-1) Landlord To  lo c k the  do o r & s hut the  lig hts  (s o m e tim e s ? ). Lock (UC-2) Landlord To  c re a te  a  ne w us e r a c c o unt a nd a llo w a c c e s s  to  ho m e . AddUser (UC-3) Landlord To  re tire  a n e xis ting  us e r a c c o unt a nd dis a b le  a c c e s s . RemoveUser (UC-4) Tenant To   find  o ut  who   a c c e s s e d  the   ho m e   in  a   g ive n  inte rva l  o f  tim e   a nd po te ntia lly file  c o m pla ints . InspectAccessHistory (UC-5) Tenant Unlock (UC-1) Tenant To  lo c k the  do o r & s hut the  lig hts  (s o m e tim e s ? ). Lock (UC-2) Tenant To  c o nfig ure  the  de vic e  a c tiva tio n pre fe re nc e s . SetDevicePrefs (UC-6) LockDevice To  c o ntro l the  phys ic a l lo c k m e c ha nis m . UC-1, UC-2 LightSwitch To  c o ntro l the  lig htb ulb . UC-1, UC-2 [to be identified] To  a uto -lo c k the  do o r if it is  le ft unlo c ke d fo r a  g ive n inte rva l o f  tim e . AutoLock (UC-2)
Background image of page 4
Types of Actors Initiating actor  (also called primary actor or “user”):  initiates the use case to realize a goal Participating actor  (also called secondary actor):  participates in the use case but does not initiate it: Supporting actor : helps the system-to-be to complete the use case Offstage actor : passively participates in the use case, i.e., neither initiates nor helps complete the use case, but may be notified about some aspect of it (e.g., for keeping records)
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Use Case Diagram: Device Control UC1: Unlock UC2: Lock UC3: AddUser UC4: RemoveUser UC5: InspectAccessHistory UC6: SetDevicePrefs UC7: AuthenticateUser UC8: Login « p a r t ic ip e »
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 26

SElec-4 UseCases (1) - LECTURE 4: Use Cases Ivan Marsic...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online