Software Quality Assurance
Tutorial 7 – Sequence Diagram
Activity 1
Draw a sequence diagram from the following use case:
ID & Name: UC-1: Registration
Primary Actor: Guest
Description: An unregistered user (guest) registers for an account.
Trigger: The unregistered user wants to create an account.
Pre-conditions: None
Post-conditions: Website shows successful registration message to user and user account
is stored in database.
Normal Flow: 1.1. User clicks “Register” from the website’s navigation bar
1.2. System shows a registration form
1.3. User enters information: first name, last name, email address,
password, confirm password and checks the “Agree to terms and
conditions” checkbox
1.4. User clicks “Register” button
1.5. System sends a verification email to the user’s email address
1.6. System displays a “Successful registration” page
Alternative Flows: 2.1. User clicks “Don’t have an account?” link on “Login” page
2.2. Continues from step 1.2
Exceptions: Exception #1: Form is not completely filled
1.4. User clicks “Register” button
1.5. System displays the registration form, highlighting the fields which are
not filled with the error label “Please fill this field”1
Exception #2: Email address is already used
1.4. User clicks “Register” button
1.5. System displays the registration form, highlighting the email address
field with the error label “This email is already used”
Exception #3: Password and confirm password don’t match
1.4. User clicks “Register” button
1.5. System displays the registration form, highlighting the confirm
password field with the error label “Confirm password doesn’t match
password”
Exception #4: Use forgot to agree to terms and conditions
1.4. User clicks “Register” button
1.5. System displays the registration form, highlighting the “Agree to terms
and conditions” checkbox
Exception #5: Verification email cannot be sent
1.5. System sends a verification email to the user’s email address
1.6. System fails to send a verification email. System reports related
information to the Administrator.
Activity 2
Draw a sequence diagram from the following use case:
ID & Name: UC-2: Order a pizza
Primary Actor: Customer
Description: A customer orders a pizza with many options.
Trigger: The customer wants to order a pizza.
Pre-conditions: The customer is logged in to the website.
Post-conditions: Website shows successful purchase message to customer and customer
order is stored in database.
Normal Flow: 1.1. Customer clicks “Start ordering” link from the website’s home page
1.2. System shows three pizza sizes to choose from: big, medium, small
1.3. User chooses a pizza size
1.4. System shows four topping options to choose from: pepperoni,
mushroom, seafood, none
1.5. Customer chooses a topping option
1.6. System shows a summary page with all pizza details, total cost and
total cost after tax
1.7. Customer clicks “Place order”
1.8. System shows a page with successful purchase message
Alternative Flows: None
Exceptions: Exception #1: Cannot fetch pizza sizes
1.1. Customer clicks “Start ordering” link from the website’s home page
1.2. System shows a page with the error message “Cannot fetch pizza
sizes”
Exception #2: Cannot fetch pizza toppings
1.3. User chooses a pizza size
1.4. System shows a page with the error message “Cannot fetch topping
options”
Exception #3: Chosen pizza is out of stock
1.7. Customer clicks “Place order”
1.8. System shows a page with the error message “We cannot prepare
your pizza at the moment, please come back tomorrow”