Systems Analysis and Design, 7th Edition

Software Engineering, 7E
Chapter 5
Name: Oluwaseyi Adegoke

Questions T/F Questions M/C Questions Completion

1 F
2 T
3 F
4 F
5 T
6 T
7 F
8 T
9 T
10 F 10
1 B 1 Use case description
2 D 2 Scenarios
3 D 3 Post-condition
4 A 4 Lifeline
5 D 5 Loop frame
6 B 6 Asterisk
7 C 7 Alt frame
8 A 8 Transition
9 B 9 Destination
A 10 Pseudo-state

Essay Question 1.
A system sequence diagram (SSD) is used to define the flow of information in and out of the
automated system. It documents the inputs and the outputs and also identifies the interaction
between actors and the system.

Essay Question 2.
i. Negative (Neg) frame notation
ii. Optional (Opt) frame notation
iii. Alternative multiple fragment (Alt) frame notation
Case Study: TheEyesHaveIt.com Book Exchange

1. Domain model class diagram for Theeyeshaveit.com

2. List of use cases for Theeyeshaveit.com

User User goal & Resulting Use Case

Buyer - Opens account

- Searches books
- Makes orders
- Enters service code for seller’s rating (Optional)
- Reports issues
Seller - Registers with Theeyeshaveit to become a seller
- Adds book lists
- Supplies orders
- Sends confirmation email for shipment of orders.
Theeyeshaveit - Maintains processes
- Secures buyer detail
- Emails order detail to buyer and seller
- Updates book list
- Pays seller
Use case diagram for Theeyeshaveit.com
3. Add a seller use case
Use Case Name: Add a seller
Scenario: Register a new seller
Triggering Event: A new seller wants to have an account in order to sell books
Brief Description Seller creates an account by providing information such as name, address,
phone number, and a valid email address
Actors: Seller, registration server
Stakeholders: Accounting and sales departments
Precondition: Seller must have required information to get registered
Post-conditions: Seller’s account must be created.
Book list must be created.
Flow of Activities: Actor System
1. Seller connects to theeye- 1.1 System informs seller a reg-
shaveit.com website and fills istration confirmation email
out registration form pro- will be sent.
vided and submits. 1.2 System sends the registra-
tion confirmation email to
seller.
Exception Condi- 1.1 If the email supplied already exists in the system.
tions: 1.2 If the email supplied is not valid but still takes email format.
1.3 If the email has been barred.
Record a book order use case

Use Case Name: Record a book order

Scenario: Purchase a book
Triggering Event: A buyer wants to purchase a book from Theeyeshaveit
Description Customer goes to the website and searches for books. Customer selects
from search results and adds books to shopping cart. Customer proceeds to
checkout. Customer confirms purchase using valid email. System sends a
confirmation email to the customer.
Actors: Buyer, seller, registration server
Stakeholders: Accounting and sales departments
Preconditions: Book List and book information must be available
Post-conditions: Customer account must be available.
Book order must be placed.
Order detail must be sent to seller’s email.
Flow of Activities: Actor System
1. Buyer searches the web for 1.1 System searches keywords re-
books. lated to buyer’s search criteria.
1.2 System creates a shopping cart
and adds selected items it.
2. Buyer selects book to pur-
chase from the search re-
sults.
3. Buyer repeats step 1 and
step 2 until all desired books
are added to the cart.
4. Buyer proceeds to checkout. 4.1 System displays list of items for
a. If buyer wants to de- order confirmation.
select an item, he
clicks the item to be
deselected
 b. If buyer wants to
continue shopping,
he clicks the Con-
tinue Shopping but-
ton and goes back to
step 1 and step 2.
5. Buyer confirms the items se- 5. System displays buyer’s infor-
lected to be purchased. mation.
6. If there is a mistake in the
information, buyer makes
correction.
7. Buyer then confirms the or- 7.1 System records order and noti-
der. fies buyer with an email.
Exception Condi- 1.1 If all books in the category are sold out, books cannot be added to the
tions: cart.
4.1 If payment is rejected, system notifies buyer and seller
Add a seller sequence diagram
Record a book order sequence diagram