Object Oriented Analysis Unified Modeling Language By Mary Biddle

Use Cases Use Case – a behaviorally related sequence of transactions that make up one standard use of the system being modeled. Use Cases are generated from requirements specifications and from interviews with users/clients. Why Use Cases? Customers can describe what they want the system to do better than the entities within the system.

Actors User cases are stimulated by actors. Actors are users outside the current system – Actors may be users that play a particular role – Actors may be other systems or devices that either stimulate the system or receive output from the system Use Cases describe the users view of the system.

SafeHome Use Case Activate Security HomeownerMotion Detector Intruder Detected Siren Activate Siren Notify Police Police Deactivate Security Deactivate Siren

Security Control Alarm Create Packages (Subsystems) Activate Security Motion Detector Intruder Detected Siren Activate Siren Notify Police Police Deactivate Security Deactivate Siren Sensors Homeowner

Packages Motion Detector Intruder Detected Sensors Door Open Detector Window Open Detector Pet Detected

Packages Security Control Alarm Activate Security Motion Detector Siren Police Deactivate Security Sensors

SafeHome State Security Off Alarm Security On Activate Security Intruder Detected Deactivate Security

Encapsulation Encapsulation – creating a high level of abstraction while hiding the detailed implementation Information Hiding – hide the implementation so when requirements change the impact to the design is minimized. Using these concepts when creating the objects will increase reuse and minimize the impact of change.

Key Classes from the Use Case Homeowner Password Activate_Security Deactivate_Security Motion Detector Movement_Detected Siren Activate_Siren Deactivate_Siren Police Notify

Key Classes after Analysis Security_Monitor State Activate_Security Deactivate_Security Fire Department Notify Sensor State Type Position Activated Police Notify Siren Activate_Siren Deactivate_Siren n 1..n

Define the Interfaces for the most dynamic areas Motion Detector Sensor State Type Position Activated Fire DetectorDoor Detector

Scenario Diagram Security_MonitorSensor Activate_Security Activated True GetType Fire Alarm Fire Department Notify Siren Activate Deactivate_Security Deactivate

Documentation Each Use Case will have a description. – The description will be using terms from the user’s/client’s language. Each State Diagram will have a description Each Class will have a description. – Each attribute will have a description. – Each function will have a description. Each Scenario Diagram will have a description.