1

SYSTEM & ANALYSIS DESIGN (SAD)

Pertemuan 10

Project Report : Modelling Business &

System Requirements with UCD &
UCS

Candiwan

Prodi MBTI – Fakultas Ekonomi & Bisnis

 2

OUTLINE

2
 3

Review Use Case Diagram

1 on Project

3
 4

Review

A use case always describes three things:

• an actor that initiates an event
• the event that triggers a use case
• the use case that performs the actions triggered by the event
Four Types Of Behavioral Relationships And The Lines Used To Diagram
•Communicates
•Includes
•Extends
•Generalizes

4
 5

2 Making Use Case Diagram 1

5
 6

Case : Restaurant System

Functional Requirement:
1.Receptionist produce restaurant table chart
2.A customer can request table before going to restaurant
3.A customer place an order
4.A waiter will collect the order
5.An external system manage menu & order so customer can place an order and collected by waiter
6.A customer can pay bill through three ways; by cash, by credit card, or by cheque
7.The cashier will collect money based on billing system information produced by external system
8.The cashier can update account based on billing system information produced by external system

Task: draw the use case diagram based on those requirement

 7

7
 8

3 Making Use Case Diagram 2

8
 9

Case : ATM

Model only the transactions

Customer accounts assumed to exist
Opening and closing of accounts is handled by another portion of the system
Include operations “deposit”, withdraw”, “check balance”, “transfer”
If balance is zero or less than the amount to be withdrawn, then withdrawal should
fail
 10
Login

Logout

Deposit
customer

Withdraw

Check balance

Database
Transfer

All dependency relationships are of type <<include>>

 11

Use case narratives - ATM

Deposit
Using this functionality, a user will be able to add some money to his/her account
Account identification and amount to be deposited must be input
Upon completion, the balance in the account will be updated to include the
additional amount

•Check balance
• A user can check the balance in an account using this functionality
• Account identification must be input and the balance in the account will be output
• The account remains unchanged upon completion
 12
Login

Logout
Validate
Deposit account
customer

Withdraw

Update account

Check balance

Database
Transfer

All dependency relationships are of type <<include>>

Use case diagram for ATM - revisited

 13

Review Use Case Scenario

4 on Project

13
 14

Review

• Use case scenario is the description of the use case.

• Three main areas:
• Use case identifiers and initiators
• Steps performed
• Conditions, assumptions, and questions
• Each use case scenario may create one sequence diagram,
although sequence diagrams are not always created for
minor scenarios.
14
 Three Sections A Use Case Scenario 15

Use case name: Register for Conference UniqueID: Conf RG 003

Area: Conference Planning

Actor(s): Participant

Stakeholder Conference Sponsor, Conference Speakers

Level Blue

Description: Allow conference participant to register online for the conference using a secure Web site.

Triggering Event: Participant uses Conference Registration Web site, enters userID and password, and clicks the logon button.

Trigger type:  External  Temporal

Steps Performed (Main Path) Information for Steps

1. Participant logs in using the secure Web server userID, Password

More steps included here…

12. Successful Registration Confirmation Web page is sent to the participant Registration Record Confirmation Number

Preconditions: Participant has already registered and has created a user account.

Postconditions: Participant has successfully registered for the conference.

Assumptions: Participant has a browser and a valid userID and password.

Success Guarantee: Participant has registered for the conference and is enrolled in all selected sessions.

Minimum Guarantee: Participant was able to logon.

Requirements Met: Allow conference participants to be able to register for the conference using a secure Web site.

Outstanding Issues: How should a rejected credit card be handled?

15 Priority: High

Risk: Medium
 16

5 Making Use Case Scanario 1

16
 Nama Usecase : Registrasi
Aktor : Tamu 17
Pre-Condition : Tamu telah memasuki menu penjelasan registrasi
Post-Codition : 1. Data anggota tersimpan ke dalam database sistem.
2. Tamu sudah dapat melakukan login sebagai anggota.
Skenario Normal
Aksi Aktor Reaksi Sistem
1. Tamu memilih menu registrasi
2. Sistem menampilkan form registrasi
3. Tamu memasukkan data registrasi
4. Sistem memvalidasi masukan data
kemudian menampilkan isi masukan
5.Tamu memeriksa data-data yang
ditampilkan, dan menekan tombol OK
6. Sistem menyimpan data Tamu dan
menampilkan halaman Utama
Skenario Alternatif 1 : Gagal Melakukan Registrasi
Aksi Aktor Reaksi Sistem
1. Tamu memilih menu registrasi
2. Sistem menampilkan form registrasi
3. Tamu memasukkan data registrasi
4. Sistem memvalidasi masukan data
dan sistem menampilkan form registrasi
kembali karena ada data penting yg
tidak diisi pelanggan, yaitu nama,
17
alamat, nomor telepon, e-mail,
 18

Making Use Case Scanario 2

6

18
 19
Making Use Case Scanario 2

19
 20

Summary Use Case Diagram and Use

7 Case Scenario on Project

20
 21

Summary

• Use-case diagram is a diagram that depicts the interactions between the system and external systems
and users.
 graphically describes who will use the system and in what ways the user expects to interact with the system.
• Use case scenario is the description of the use case.
• Use-case diagram and scenario can drive entire development effort.
• Project manager or systems analyst uses business requirements use cases to estimate and schedule the
build cycles of the project.
 Build cycles are scoped on the basis of the importance of the use case and the time it takes to implement the use case.

21
 22

References
Main
Kenneth E. Kendall, Julie E. Kendall (2014), Systems Analysis and Design, 9th Edition, Prentice
Hall

Support
Howard Podeswa (2010), UML for IT Business Analyst, Second Edition, Cengage Learning
Whitten & Bentley (2007) Systems Analysis and Design Methods, 7 th Edition, McGraw-Hill
Alan Dennis, Barbara H Wixom, David Tegarden (2005), System Analysis and Design with UML
Version 2.0