Use Case Realization-Object-Oriented Design-Lecture 19 Slides-Computer Engineering, Slides of Object Oriented Analysis and Design

Download Use Case Realization-Object-Oriented Design-Lecture 19 Slides-Computer Engineering and more Slides Object Oriented Analysis and Design in PDF only on Docsity!

Department of Computer Engineering

1 Sharif University of

Object-Oriented Design

Lecturer: Raman Ramsin

Lecture 19 :

Use Case Realization – Design

Department of Computer Engineering

Sharif University of Technology

Design Workflow: Design a Use Case  Place in the Design Workflow:  Architectural Design  Design a Use Case  Design a Class  Design a Subsystem  The activity Design a Use Case is concerned with finding the design classes, interfaces, and components that interact to provide the behavior specified by a use case.

Department of Computer Engineering

Sharif University of Technology

Interaction Diagrams: Example – Use Case

Department of Computer Engineering

Sharif University of Technology

Interaction Diagrams: Example – Analysis

Department of Computer Engineering

Sharif University of Technology

Modeling Concurrency  Use active classes and objects.  Sequence diagrams:  par - all operands execute in parallel;  critical - the operand executes atomically without interruption.  Communication diagrams:  postfix the sequence number with a label to indicate the thread of control.  Activity diagrams:  forks;  joins.

Department of Computer Engineering

Sharif University of Technology

Concurrency: Sample System – Use Case Diagram

Department of Computer Engineering

Sharif University of Technology

Concurrency: Active Classes

Department of Computer Engineering

Sharif University of Technology

Concurrency: Interaction Diagrams ( 1 )

Department of Computer Engineering

Sharif University of Technology

Concurrency: Communication Diagrams

Department of Computer Engineering

Sharif University of Technology

Subsystem Interaction Diagrams  Subsystem interaction diagrams show the interactions between the different parts of the system at a high level:  they may contain actors, subsystems, components, and classes;  you can show parts of the subsystem (e.g., provided interfaces) in boxes hanging down below the subsystem.

Department of Computer Engineering

Sharif University of Technology

Timing Diagrams: Notation

Department of Computer Engineering

Sharif University of Technology

Timing Diagrams: Compact Form  The compact form emphasizes relative time.

Department of Computer Engineering

Sharif University of Technology

Reference  Arlow, J., Neustadt, I., UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design, 2

nd

Ed. Addison-Wesley,