Session 5 Object Model Development. OOAD with UML / Session 5 / 2 of 19 Review A class icon is a rectangle with three sections within it An object is.

Slides:



Advertisements
Similar presentations
Use Case & Use Case Diagram
Advertisements

Use Case Model. C-S 5462 Use case model describes what the user expects the system to do –functional requirements may describe only the functionalities.
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Assignment I, part 1. Groups of three students. Specify one as group leader. group names to TA and me. Create an object-oriented conceptualization.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
CS3773 Software Engineering Lecture 03 UML Use Cases.
Tutorial 2. What is a UML Use Case Diagram? Use case diagrams model the functionality of a system using actors and use cases. Use cases are services or.
Interaction Diagrams Activity Diagram State Machine Diagram
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
Object Oriented Analysis Process
COMP1007 Intro to Systems Requirements © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Intro to System Requirements Lecture 2 Use-Cases.
A use case describes one “case” of how a user can use the system.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
Requirements Analysis 4. 1 Use Case I b504.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Use-Cases.
System Analysis and Design
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 6 - Use cases and activity diagrams Dr.
Use Case Diagram.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
Chapter 7: The Object-Oriented Approach to Requirements
2005/05/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
1.  Modeling the context of a system  Modeling the requirements of a system 2.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Rational Unified Process (Part 1) CS3300 Fall 2015.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
CS 360 Lecture 6.  A model is a simplification of reality  We build models to better understand the system being developed.  We build models of complex.
Requirements Determining the requirements of software involves determining the needs of the users of the software. Determining the requirements of software.
1 Object-Oriented Analysis Use Case Driven. 2 The outline method for OOA 1.Identify object classes within the problem domain 2.Define the behaviour of.
Faculty of Computer & Information Software Engineering Third year
Chapter 6 A Use-Case-Driven Process. 2 Definitions The choice of models and the choice of techniques used to express them have a significant impact on.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Systems Analysis and Design in a Changing World, 3rd Edition
Developed by Reneta Barneva, SUNY Fredonia for CSIT 425 Requirements Modeling.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
Introduction to Unified Modeling Language (UML) By Rick Mercer with help from The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, Ivar.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
Systems Analysis and Design in a Changing World, 6th Edition
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.
The Unified Modeling Language (UML)
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Week IV in SOS  Tuesday Project Time -- 4:15pm-5pm URL for project(s) due to Judy by Friday 5pm  Friday Paper  OOAD Handouts thru last Thursday (see.
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
 What to do if you want to build a new house? › Buy a bunch of wood and nails and start immediately. › Or, put some blueprints to follow, and plan of.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
OO DomainModeling With UML Class Diagrams and CRC Cards Chapter 6 Princess Nourah bint Abdulrahman University College of Computer and Information Sciences.
ISMT221 Information Systems Analysis and Design Use case diagram Lab 4 Tony Tam.
UML Fundamental Elements. Structural Elements Represent abstractions in our system. Elements that encapsulate the system's set of behaviors. Structural.
Chapter 3: Software Design –Use case Diagram Nouf Alghanmi.
Introduction to Unified Modeling Language (UML) By Rick Mercer with help from The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, Ivar.
Developing Business Processes Developing an activity diagram of the business processes can provide us with an overall view of the system.
Systems Analysis and Design in a Changing World, Fourth Edition
Use Case Model.
Introduction to Unified Modeling Language (UML)
OO Domain Modeling With UML Class Diagrams and CRC Cards
Concepts, Specifications, and Diagrams
Introduction to Unified Modeling Language (UML)
General Workflow of Use-Case Driven Development
Presentation transcript:

Session 5 Object Model Development

OOAD with UML / Session 5 / 2 of 19 Review A class icon is a rectangle with three sections within it An object is represented as a rectangle with an underlined name Constraints are represented as strings enclosed in braces and placed near the element the constraint applies to A comment is a graphical symbol containing information Relationships provide a pathway for communication between objects

OOAD with UML / Session 5 / 3 of 19 Objectives Explain use case and use case diagram Explain the three key elements of use case diagram Elaborate the relationship amongst use cases Define the role of use case diagram in software development Explain the use case model with examples

OOAD with UML / Session 5 / 4 of 19 What is Use Case?-1 Use Case diagrams help to Focus on possible users of the system Find out the roles that users are going to play while interacting with the system Find out what fundamental services (use cases) the users in respective roles, expect from the system Depict the interactions between each user or role and the services it expects from the system

OOAD with UML / Session 5 / 5 of 19 What is Use Case?-2 A Use Case is a sequence of actions a system performs that yield an observable result of value to a particular actor

OOAD with UML / Session 5 / 6 of 19 What is Use Case?-2 Uses Cases represent the specified requirements as a series of interactions between the system and one or more actors. The interactions help in describing the proposed functionality of the system to the users. In the case of a complex system, use cases also provide a starting point for the analysis of the system in terms of what needs to be built. The use cases provide a source for services provided by the system and help to determine the classes that the system must implement.

OOAD with UML / Session 5 / 7 of 19 Use Case Diagram-1 > Actor Name Actor System Boundary Actor Class

OOAD with UML / Session 5 / 8 of 19 Use Case Diagram-2 USE CASE Name > Stereotypes Use Case

OOAD with UML / Session 5 / 9 of 19 Use Case Diagram-3

OOAD with UML / Session 5 / 10 of 19 Use Case Diagram

OOAD with UML / Session 5 / 11 of 19 Relationship amongst Use cases-1 Extends

OOAD with UML / Session 5 / 12 of 19 Relationship amongst Use cases-2 Extends

OOAD with UML / Session 5 / 13 of 19 Relationship amongst Use cases-3 Use

OOAD with UML / Session 5 / 14 of 19 Role of Use Case Diagram during development Requirements workflow Analysis and Design, use cases are realized in a design model Implementation in terms of design classes Constitute the basis for identifying test cases and test procedures Basis for planning Foundation for what is described in user manuals Definition of ordering units

OOAD with UML / Session 5 / 15 of 19 Apply use case model-1  Defining the problem  Defining the bounds of the problem  Understanding the vocabulary associated with the problem domain

OOAD with UML / Session 5 / 16 of 19 Apply use case model-2 Bank of Aptech wants to computerize its operations. This bank will provide Retail Services to its customers. The services are defined in terms of products the bank offers. These are:  Savings Account  Current Account  Fixed Deposit Account of three types viz., short, medium, and long term  ATM

OOAD with UML / Session 5 / 17 of 19 Apply use case model-3  Deposit money  Withdraw money  Check balance  Process transaction  Print receipt

OOAD with UML / Session 5 / 18 of 19 Apply use case model-4  Customer  ATM

OOAD with UML / Session 5 / 19 of 19 Summary Use cases provide the basic ground to find out the classes in the model Use case diagrams exhibit the relation between the actors and system functions in the model Most of the time, use case diagrams are the first diagram while drawing the model of a system Use case diagrams give the broad overview of the model