OBJECT ORIENTED METHODOLOGIES Week04. Agenda… © Jerry Kotuba SYST39409-Object Oriented Methodologies 2  This week  Quiz 1  Take up ICE-01  Check “Grade.

Slides:



Advertisements
Similar presentations
Week 2 The Object-Oriented Approach to Requirements
Advertisements

Requirements Diagrams With UML Models
Use-Cases.
Use case tutorial examples.
Use Case & Use Case Diagram
Object Oriented Methodologies
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
Lecture 9 Descriptors, Events & Event Tables INFO1409 Systems Analysis & Design Module HND Year /9.
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
Extending the Requirements Model - techniques for detailing use cases
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Interaction Diagrams Activity Diagram State Machine Diagram
Systems Analysis and Design in a Changing World, Fourth Edition
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
Documenting Requirements using Use Case Diagrams
Object Oriented Analysis Process
Task Analysis Analyzing and representing the activities of your users.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Use Case Example.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
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
A Student Guide to Object- Orientated Development
Lesson 1 Week01.
Quiz 1. Who is the guru of Extreme Programming?
Use Cases 2 ENGR ♯10 Peter Andreae
State Diagrams / System Sequence Diagrams (SSDs)
Jerry KotubaSYST39409-Object Oriented Methodologies1 Object Oriented Methodologies Week04.
Use Case Modeling. Watch the video on use cases Review at minute 2:41-3:37.
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
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Faculty of Computer & Information
Object Oriented Methodologies
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Systems Analysis and Design in a Changing World, 6th Edition
Object Oriented Design Jerry KotubaSYST Object Oriented Methodologies1.
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.
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 8 UML Use Case Modelling.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Systems Analysis and Design in a Changing World, Fourth Edition
Use cases Week Use‐case diagram 2 – Depicts the interactions between the system and external systems and users. – Graphically describes who will.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.
USE CASE Pertemuan 7 Matakuliah: Konsep object-oriented Tahun: 2009.
Week04 Project Requirements.
UML - Development Process 1 Software Development Process Using UML.
Use Case Model Use case description.
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.
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
 System Sequence Diagrams Sheridan SYST Engineering Quality Systems 11.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
Chapter 3: Software Design –Use case Diagram Nouf Alghanmi.
 Week03 Jerry Kotuba SYST30009-Engineering Quality Software 1.
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Systems Analysis and Design in a Changing World, Fourth Edition
Use Case Model.
Pharmacy Use Case.
SE-565 Software System Requirements IV. Use Cases
Use Case Modeling - techniques for detailing use cases
Object Oriented Analysis and Design
INFS 6225 Object Oriented Systems Analysis & Design
Requirements Management
Use Case Model Use case diagram – Part 2.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Engineering Quality Software
Presentation transcript:

OBJECT ORIENTED METHODOLOGIES Week04

Agenda… © Jerry Kotuba SYST39409-Object Oriented Methodologies 2  This week  Quiz 1  Take up ICE-01  Check “Grade Book”  Use Case Narratives  Use Case “Adornments”  Activity Diagrams a.k.a. Workflow Diagrams

Learning Outcomes © Jerry Kotuba SYST39409-Object Oriented Methodologies 3  Know what “use case scenarios” are  Learn how to identify and show relationships between Use Cases. [Includes & Extends]  Learn how to build a use case narrative for each use case and why the narratives are important.  Understand what use case Pre-conditions/Post- conditions are and why they are important.  Learn how to describe a use case with an activity or workflow diagram.

Use Cases J.N.Kotuba SYST Object Oriented Methodologies 4  Analysts define use cases at three levels  Brief  Intermediate  Fully developed

Use Case Narrative: Fill Prescription J.N.Kotuba SYST Object Oriented Methodologies 5 Step 1.Pharmacist inputs Patient ID Step 2.System displays patient medical record Step 3.Pharmacist verifies dosage, potential allergic reactions and/or interaction with other medications. Step 4.The Pharmacist fills the prescription and updates the patient’s medical record on the system with details of the new prescription. Step 5. The system prints a label which is sent to the nurses station and the Billing Dept is given Patient and Prescription details. Alt Step 3. If the pharmacist determines a possible negative condition exists, then the Doctor is contacted Alt Step 4. The prescription is held for disposition.

J.N.Kotuba SYST Object Oriented Methodologies 6 Brief Description of Create New Order Use Case

J.N.Kotuba SYST Object Oriented Methodologies 7 Intermediate Description of Telephone Order Scenario for Create New Order Use Case

J.N.Kotuba SYST Object Oriented Methodologies 8 Fully Developed Description of Telephone Order Scenario for Create New Order Use Case

Use Case Narrative:  Do’s  Use complete sentences  How is the use case initiated and how does it end  What the initial and final actions and state of the system look like  Don’ts  Use abbreviations or sentence fragments J.N.Kotuba 9 SYST Object Oriented Methodologies

J.N.Kotuba SYST Object Oriented Methodologies 10

Components of the Use Case Diagram J.N.Kotuba SYST Object Oriented Methodologies 11  Use Case  Actor  System Boundary

Use Case Diagrams © Jerry Kotuba SYST39409-Object Oriented Methodologies 12  How use case diagrams show relationships  Between actors and use cases  Between use cases

ATM Example  Use Case: Withdraw Money  Flow of events  The user inserts an ATM card  The system prompts the user to enter a password  The user enters the password.  The system validates the password  Use Case: Deposit Money  Flow of events  The user inserts an ATM card  The system prompts the user to enter a password  The user enters the password.  The system validates the password 13 Common Behaviours

ATM Example  Use Case: Withdraw Money  Flow of Events  Include [login]  Use Case: Deposit Money  Flow of Events  Include [login] 14 Use Case: Login Flow of events The user inserts an ATM card The system prompts the user to enter a password The user enters the password. The system validates the password

© Jerry Kotuba SYST39409-Object Oriented Methodologies 15 Withdraw Money Deposit Money Login >

Use Case Relationships © Jerry Kotuba SYST39409-Object Oriented Methodologies 16  Includes  Case In Point – “Stop Payment”  Extends  Case In Point – “Register Student”

© Jerry Kotuba SYST39409-Object Oriented Methodologies 17 Example

Comments on Include & Extend © Jerry Kotuba SYST39409-Object Oriented Methodologies 18  Tend to see more includes.  Extends are fewer.

More About Actors © Jerry Kotuba SYST39409-Object Oriented Methodologies 19  People  External Systems  Time

Exercise…your turn © Jerry Kotuba SYST39409-Object Oriented Methodologies 20  Interpret and explain the use case diagram  Explain the various roles of those using the inventory system and the functions that each role requires.  Explain the relationships and the ways the use cases are related to each other.

© Jerry Kotuba 21 SYST39409-Object Oriented Methodologies

Use Case Narratives- Preconditions & Post Conditions © Jerry Kotuba SYST39409-Object Oriented Methodologies 22  Hospital Pharmacy Case Study

Use case scenarios… © Jerry Kotuba SYST39409-Object Oriented Methodologies 23  Case In Point

Use Cases © Jerry Kotuba SYST39409-Object Oriented Methodologies 24  Use cases tell;  the customer what to expect  the developer what to code  the technical writer what to document  and the tester what to test.

Activity Diagram J.N.Kotuba SYST Object Oriented Methodologies 26  A type of workflow diagram that describes the user activities and their sequential flow.  Illustration:  The following slide summarizes the workflow of how a customer request for a quotation to modify a computer system is handled.

Jerry Kotuba Object Oriented Methodologies 27

Notation

Your Turn… Activity Diagrams –ICE-02 © Jerry Kotuba SYST39409-Object Oriented Methodologies 29

Next Class © Jerry Kotuba SYST39409-Object Oriented Methodologies 30  Introduce Objects & Class Diagrams