Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.

Slides:



Advertisements
Similar presentations
UML (cont.) “The Unified Modeling Language User Guide” by G. Booch, J. Rumbaugh and I. Jacobson ● Classes ● Relationships ● Class diagrams ● Examples.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Unified Modeling Language
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
Object-Oriented Analysis and Design
Use-case Modeling.
Software Testing and Quality Assurance
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
UML – Class Diagrams.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
© Copyright Eliyahu Brutman Programming Techniques Course.
Use Case Analysis – continued
Team Members Rachid Alaoui Medarhri (Senior Student). Tarek Bougroug (Senior Student). Supervised By : Dr. Driss Kettani.
The Unified Modeling Language (UML) Class Diagrams.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
System models l Abstract descriptions of systems whose requirements are being analysed.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
CS /31 Illinois Institute of Technology CS487 Software Engineering OOA with UML David Lash.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
TAL7011 – Lecture 4 UML for Architecture Modeling.
Chapter 7 The Object-Oriented Approach to Requirements.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Design Jon Walker. More UML ● What is UML again?
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Design Model Lecture p6 T120B pavasario sem.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Introduction to OOAD and the UML
Software Engineering Lecture 8 Object-Oriented Analysis.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Introduction to UML Todd Bacastow Rational Unified Process A process for the effective implementation of key “Best Practices” Control Changes Manage.
Chapter 3: Introducing the UML
UML - Development Process 1 Software Development Process Using UML.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
ITEC0724 Modern Related Technology on Mobile Devices Lecture Notes #2 1.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Introduction to UML Hazleen Aris Software Eng. Dept., College of IT, UNITEN. …Unified Modeling Language.
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
1 Kyung Hee University Interaction Diagrams Spring 2001.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1 Use Case Analysis – Part 4 Analysis Mechanisms.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
CHAPTER
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Unified Modeling Language
Introduction to Unified Modeling Language (UML)
Unified Modeling Language
Uml diagrams In ooad.
Presentation transcript:

Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006

Sharif University of Technology2 Outline UML related issues.  Class Diagram.  Interaction Diagrams. Use-case Realization.  Use-Case Realization Report. An Example (Login) SEPID - Design

Sharif University of Technology3 UML related issues Class Diagram:  The diagrams describing the classes and relationships that participate in the realization of the use case. Interaction Diagrams:  The diagrams (sequence and collaboration diagrams) describing how the use case is realized in terms of collaborating objects.

Sharif University of Technology4 Class Diagrams A class diagram describes the types of objects in the system and the various kinds of relationships that exist among them. Class diagrams also show the attributes and operations of a class and the constraints that apply to the way objects are connected.

Sharif University of Technology5 Classes in UML

Sharif University of Technology6 Relationships (Dependency) A dependency is a using relationship that states that a change in specification of one thing may affect another thing that uses it, but not necessarily the reverse. Some source of dependency:  Using methods of other class  Using other class as argument of methods  Throwing exception

Sharif University of Technology7 Relationships (Generalization) one thing is-a-kind-of a more general thing. Generalization at the implementation perspective is associated with inheritance in programming languages.

Sharif University of Technology8 Relationships (Association ) An association is a structural relationship that specifies that objects of one thing are connected to objects of another. Association can have Multiplicity Types of association:  Aggregation  Composition

Sharif University of Technology9 Aggregation and Composition Aggregation is the part-of relationship. but the part object can exists alone. composition is also part of relationship, but the part object may belong to only one whole

Sharif University of Technology10 Interaction Diagrams Types of interaction diagrams: Sequence diagrams and collaboration diagrams. Sequence diagrams show the explicit sequence of messages and are better when it is important to visualize the time ordering of messages. Collaboration diagrams show the communication links between objects and are better for understanding all of the effects on a given object and for algorithm design.

Sharif University of Technology11 Sequence Diagram

Sharif University of Technology12 Collaboration Diagram

Sharif University of Technology13 Use-case Realization represents the design perspective of a use case. A use-case realization describes how a particular use case is realized within the design model, in terms of collaborating objects.

Sharif University of Technology14 Some Points Use case realization typically has two parts:  express the structure of the use case  express the behavior of the use case. In other words it shows the flow of events in a use case A use-case can be realized in different ways The use-case realization completely realizes the selected sub-flows of the use case; there is no missing behavior. All required behavior has been unambiguously distributed among the model elements participating in the use-case realization.

Sharif University of Technology15 Some Points (cont.) The Flow of Events Design should be readable and suit its purpose. The diagrams describing the use-case realization should be readable and suit their purpose. Where several diagrams illustrate the use- case realization, the role of each is clear, and the diagrams are consistent with one another. All exceptional cases to be considered in the current iteration have been handled.

Sharif University of Technology16 Use-Case Realization Report Brief Description  A Brief Description of the realized use case. Flow of Events Design  A Flow of Events Design of the use-case realization. Interaction Diagrams  Interaction Diagrams of the use-case realization. Participating Objects  Objects participating in interaction diagrams of the use-case realization. For each object, its class and brief description. Class Diagrams  Class Diagrams of the use-case realization. Derived Requirements  Derived Requirements of the use-case realization.

Sharif University of Technology17 An Example (Login) Consider we want to realize login use-case of a system. Login: User can enter to system after entering its username and password correctly. At first we try to specify the structure of Login Use-case.

Sharif University of Technology18 An Example (Cont.) Class diagram

Sharif University of Technology19 An Example (Cont.) Sequence diagram

Sharif University of Technology20 Thanks References: RUP documents, The UML User Guide, UML Distilled.