Modern Systems Analysis and Design

Unit 6

Agenda
Important

Dates

Homework Midterm Unit

Appendices 7A, 7B, 7C, and 7D

Work

To-Do

Important Dates
Assignment Assignment 2 Assignment 3 Final Exam Due Dates Mar. 26 Apr. 09 TBA

Homework
I

was very lenient when I marked your homework and exam

If you think I shouldnt be so generous, please feel free to let me know

Some

students only did one question incorrectly

They are not serious

Copy

solutions from web or answer keys

Using incorrect symbols Calculation not correct.

3/12/2014Chapter 2

ROI, Breakeven?
Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall 4

Homework
Did not follow the rules to draw DFD Type your work and organize your solutions in correct order If you put little or no effort into your homework, your exam suffers

3/12/2014Chapter 2

Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall

Midterm
Decision table not in correct format DFD did not follow the rules Fill in the blanks not good Some students got almost full mark Some students got very low mark Dont lose your confidence, you will have chance as long as you work hard. I gave you perfect marks in the part of in class practices

Participation is required to get the credit in this part.

3/12/2014Chapter 2

Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall

Modern Systems Analysis and Design

Seventh Edition

Unit 6
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases

Modern Systems Analysis and Design

Seventh Edition

Jeffrey A. Hoffer Joey F. George Joseph S. Valacich

Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases

Learning Objectives
Explain

use cases and use case diagrams and how they can be used to model system functionality. Present the basic aspects of how to create written use cases. Discuss process modeling with use cases for electronic commerce application.
Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

Use Cases
A use case is a depiction of a systems behavior or functionality under various conditions as the system responds to requests from users. An actor is an external entity that interacts with the system.

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

10

Use Cases (Cont.)

FIGURE 7-26 A use case diagram for a university registration system

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

11

Use Cases (Cont.)

Most actors represent user roles, but actors can also be external systems. An actor is a role, not a specific user; one user may play many roles, and an actor may represent many users. A use case model consists of actors and use cases.

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

12

Use Cases diagrams

Use case diagram: a picture showing system behavior along with the key actors that interact with the system Abstract use case is when a use case is initiated by another use case. A use case represents complete functionality.

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

13

Definitions and Symbols

Use Case
Actor Boundary Connection
<<include>>

Include relationship Extend relationship

<<extend>>

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

14

Definitions and Symbols (Cont.)

Actor is a role, not an individual.

Involved

with the functioning of the system at some basic level Represented by stick figures

Use case represents a single system function.

Represented

as an eclipse

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

15

Definitions and Symbols (Cont.)

System boundary includes all the relevant use cases.

A

boundary is the dividing line between the system and its environment. Use cases are within the boundary. Actors are outside of the boundary. Represented as a box

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

16

Definitions and Symbols (Cont.)

Connection is an association between an actor and a use case.

Depicts

a usage relationship Connection does not indicate data flow Actors are connected to use cases with lines. Use cases are connected to each other with arrows.

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

17

Definitions and Symbols (Cont.)

Extend relationship is an association between two use cases where one adds new behaviors or actions to the other.
Extends

a use case by adding new behavior or actions Specialized use case extends the general use case.

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

18

Definitions and Symbols (Cont.)

Include relationship is an association between two use cases where one use case uses the functionality contained in the other.
Indicates

a use case that is used (invoked) by another use case Links to general purpose functions, used by many other use cases
Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

19

Definitions and Symbols (Cont.)

FIGURE 7-27 A use case diagram featuring an include relationship

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

20

Written Use Cases

Document containing detailed specifications for a use case Contents can be written as simple text or in a specified format Step-by-step description of what must occur in a successful use case

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

21

Figure 7-29 A template for writing use cases (Source: Cockburn, Alistair, Writing Effective Use Cases, 1st ed., 2001. Reprinted and Electronically reproduced by permission of Pearson Education, Inc. Upper Saddle River, New Jersey.)

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

22

Level of Use Case

Refers to degree of detail in the use case description Five suggested levels (Cockburn)
1. 2. 3.

4.
5.

White as seen from clouds Kite birds-eye view Blue sea-level view Fish below sea-level Black bottom of the sea
Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

summary

detail

Chapter 7 Appendix A

23

Sample Format for Written Use Case

Title descriptive name, matches name in use case diagram

Primary actor usually a user role

Stakeholders any group or individual with an interest in the function of the use case
Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 24

Chapter 7 Appendix A

Sample Format for Written Use Case (Continued)

Precondition conditions that must be satisfied in order to execute the use case Minimal guarantee outputs that can be expected if the service attempt failed Success guarantee outputs that can be expected if the service succeeds
Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 25

Chapter 7 Appendix A

Sample Format for Written Use Case (Continued)

Trigger an event or action that initiates the use case

Main success scenario description of sequence of interactions between actor and use case during the use case execution Extensions detailed description of how errors are handled
Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 26

Chapter 7 Appendix A

Electronic Commence Application: Process Modeling Using Use Case

High

level functions are identified (figure7-33)

Represent work or actions Involve customer Fill order requires another actor: shipping clerk
The

first written use case deals with the entire process of buying a product at the WebStore
Summary use case without functional requirement

The

second one is at the sea level

27

Browse catalog
2011 Pearson Education, Inc. Publishing as Prentice Hall

3/12/2014Chapter 7 Appendix A

Electronic Commence Application: Process Modeling Using Use Case (Cont.)

Use case at kite level

Chapter 7 Appendix A

2011 Pearson Education, Inc. Publishing as Prentice Hall

28

Use case at sea level Corresponds with Step 1 of kitelevel use case

Chapter 7 Appendix A

2011 Pearson Education, Inc. Publishing as Prentice Hall

29

Summary
In

Appendix A you learned how to:

Explain use cases and use case diagrams and how they can be used to model system functionality. Present the basic aspects of how to create written use cases. Discuss process modeling with use cases for electronic commerce application.

Chapter 7 Appendix A

Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall

30

Modern Systems Analysis and Design

Seventh Edition

Jeffrey A. Hoffer Joey F. George Joseph S. Valacich

Chapter 7 Appendix B
Object-Oriented Analysis and Design: Activity Diagrams

Learning Objectives
Understand

how to represent system logic with activity diagrams.

Chapter 7 Appendix B

2014 Pearson Education, Inc. Publishing as Prentice Hall

32

Process Modeling: Activity Diagrams

Activity Diagrams
Show

the conditional logic for the sequence of system activities needed to accomplish a business process. Clearly show parallel and alternative behaviors. Can be used to show the logic of a use case.

Chapter 7 Appendix B

2014 Pearson Education, Inc. Publishing as Prentice Hall

33

Use Activity Diagrams to:

Depict the flow of control from activity to activity. Help in use case analysis to understand what actions need to take place. Help in identifying extensions in a use case. Model work flow and business processes. Model the sequential and concurrent steps in a computation process.
2014 Pearson Education, Inc. Publishing as Prentice Hall 34

Chapter 7 Appendix B

FIGURE 7-36 Activity diagram for a customer order process

Chapter 7 Appendix B

2014 Pearson Education, Inc. Publishing as Prentice Hall

35

Process Modeling: Activity Diagrams (Cont.)

Elements of Activity Diagrams:

Activity:

a behavior that an object carries out while in a particular state

Branch:

a diamond symbol containing a condition whose results provide transitions to different paths of activities
a (circular ?) diamond symbol where different paths converge
2014 Pearson Education, Inc. Publishing as Prentice Hall 36

Merge:

Chapter 7 Appendix B

Process Modeling: Activity Diagrams (Cont.)

Fork: Join:

the beginning of parallel activities

the end of parallel activities

Swimlanes:

columns representing different organizational units of the system

37

Chapter 7 Appendix B

2014 Pearson Education, Inc. Publishing as Prentice Hall

Summary
In

this appendix you learned how to:

represent system logic with activity diagrams.

Chapter 7 Appendix B

2014 Pearson Education, Inc. Publishing as Prentice Hall

38

Modern Systems Analysis and Design

Seventh Edition

Jeffrey A. Hoffer Joey F. George Joseph S. Valacich

Chapter 7 Appendix C
Object-Oriented Analysis and Design: Sequence Diagrams

Learning Objectives
Understand

how to represent system logic with sequence diagrams.

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

40

Dynamic Modeling: Sequence Diagrams

Sequence diagram: depicts the interactions among objects during a certain period of time

May be presented either in a generic form or in an instance form. Generic form shows all possible sequences of interactions sequences corresponding to all the scenarios of a use case. Instance form shows the sequence for only one scenario.

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

41

Dynamic Modeling: Sequence Diagrams (Cont.)

Elements of a sequence diagram

Objects: represented by boxes at top of diagram Lifeline: the time during which an object exists Messages: means by which objects communicate with each other

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

42

Dynamic Modeling: Sequence Diagrams (Cont.)

Activation: the time period during which an object performs an operation Synchronous message: a type of message in which the caller has to wait for the receiving object to finish executing the called operation before it can resume execution itself
2014 Pearson Education, Inc. Publishing as Prentice Hall 43

Chapter 7 Appendix C

Dynamic Modeling: Sequence Diagrams (Cont.)

Simple message: a message that transfers control from the sender to the recipient without describing the details of the communication (represented by a transverse tick mark) Asynchronous message: a message in which the sender does not have to wait for the recipient to handle the message
2014 Pearson Education, Inc. Publishing as Prentice Hall 44

Chapter 7 Appendix C

FIGURE 7-38 Sequence diagram for a class registration scenario without prerequisites

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

45

FIGURE 7-39 A generic sequence diagram for the prereq courses not completed use case

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

46

FIGURE 7-40 Sequence diagram for Hoosier Burgers Hire employee use case

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

47

Summary
In

this appendix you learned:

How to represent system logic with sequence diagrams.

Chapter 7 Appendix C

2014 Pearson Education, Inc. Publishing as Prentice Hall

48

Modern Systems Analysis and Design

Seventh Edition

Jeffrey A. Hoffer Joey F. George Joseph S. Valacich

Chapter 7 Appendix D
Business Process Modeling

Learning Objectives
Understand

how to represent business processes with business process diagrams.

Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

50

Business Process Modeling

Business Process: a standard method for accomplishing a particular task necessary for an organization to function Business Process Modeling Notation (BPMN): business processing modeling approach established by the Object Modeling Group (OMG)

Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

51

Basic Notation
Event: a trigger that initiates the start of a process Activity: an action that must take place for a process to be completed Gateway: a decision point Flow: shows the sequence of action in a process

Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

52

Basic Notation (Cont.)

Specialized event notation (e.g from message, or at particular time)

Specialized flow notation (sequence, default, or message flow)

Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

53

Basic Notation (Cont.)

Swimlane: a way to visually encapsulate a process

Pool: a way to encapsulate a process with two or more participants (collaborative diagram)
Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

54

Figure 7-41 Depicting a recruiting process with BPMN

Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

55

Summary
In

this appendix you learned:

How to represent business processes with business process diagrams.

Chapter 7 Appendix D

2014 Pearson Education, Inc. Publishing as Prentice Hall

56

Practice and Discussion

You may work with other students in your group for the following questions: Problems and exercises 2 on pages 234 Problems and exercises 1 on pages 238 Problems and exercises 3 on pages 248 Problems and exercises 3 on pages 253

Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall

3/12/2014Chapter 1

57

Work to do

Review
Appendices

7A, 7B, 7C, and 7D

Read
Chapter

8
on practice and discussion slides 2
58

Complete
Questions

Continue
Assignment
Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall

3/12/2014Chapter 1