object oriented methodologies week04. agenda… © jerry kotuba syst39409-object oriented...

OBJECT ORIENTED METHODOLOGIES

Week04

SYST39409-Object Oriented Methodologies

2

Agenda…

© Jerry Kotuba

This week Quiz 1 Take up ICE-01 Check “Grade Book” Use Case Narratives Use Case “Adornments” Activity Diagrams a.k.a. Workflow Diagrams


3

Learning Outcomes

© Jerry Kotuba

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.

SYST39409 - Object Oriented Methodologies

4

Use Cases

J.N.Kotuba

Analysts define use cases at three levels Brief Intermediate Fully developed


5

Use Case Narrative:Fill Prescription

J.N.Kotuba

Step 1.Pharmacist inputs Patient IDStep 2.System displays patient medical recordStep 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.

SYST39409 - Object Oriented Methodologies6 J.N.Kotuba

Brief Description of Create New Order Use Case


Intermediate Description of Telephone Order Scenario for Create New Order Use Case


Fully Developed Description of Telephone Order Scenario for Create New Order Use Case

9


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


11

Components of the Use Case Diagram

J.N.Kotuba

Use Case Actor System Boundary


12

Use Case Diagrams

© Jerry Kotuba

How use case diagrams show relationships Between actors and use cases Between use cases

13

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

Common Behaviours

14

ATM Example

Use Case: Withdraw Money

Flow of Events Include [login]

Use Case: Deposit Money

Flow of Events Include [login]

Use Case: LoginFlow of events

The user inserts an ATM cardThe system prompts the user to enter a passwordThe user enters the password. The system validates the password

© Jerry Kotuba

Withdraw Money

Deposit Money

Login

<<in

clud

es>>

<<includes>>


16

Use Case Relationships

© Jerry Kotuba

Includes Case In Point – “Stop Payment”

Extends Case In Point – “Register Student”

© Jerry KotubaSYST39409-Object Oriented Methodologies17

St udent Regis t r at ion Syst em

Cour se Cat alogue Syst emSt udent

Regis t er f orCour ses

Example


18

Comments on Include & Extend

© Jerry Kotuba

Tend to see more includes. Extends are fewer.


19

More About Actors

© Jerry Kotuba

People External Systems Time


20

Exercise…your turn

© Jerry Kotuba

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.


24

Use Cases

© Jerry Kotuba

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.


26

Activity Diagram

J.N.Kotuba

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 KotubaObject Oriented Methodologies27

Generate a quotation The customer initiates the process by requesting a quote. A salesperson receives the request and writes down the details of the request and then decides whether she can do it herself or whether she needs help. If she does not need help, then the salesperson enters the information into the computer system. If the salesperson needs help, then the technical expert performs the next step. The expert reviews the quote request to make sure that the requested components can be integrated into a functioning computer system. The expert then enters the information into the computer system. At this point, the computer system generates the detailed quote. The customer reviews the quote and decides whether it needs changes or is acceptable. If acceptable, places the order.

Notation

object oriented methodologies week04. agenda… © jerry kotuba syst39409-object oriented...

Documents