Lab 2 - Sequence Diagrams

UML, Lucid Chart, Sequence Diagrams

Due Feb 28 by class time.

This lab uses Lucid Chart.

Make sure you have an MVNU account. Lucid Chart Link

References (Please read):

  1. UML basics: The sequence diagram
  2. Introduction to Sequence Diagrams (presentation)
  3. Creating a UML Sequence Diagram in Lucid Chart

ATM Sequence Diagrams

An ATM has two major operations for users: Creating a session (logging in) and performing transactions within the session.

Creating a session

  1. Card inserted by user
  2. Session is created for user
  3. Session is invoked (performed)
  4. Session reads card
  5. Session read PIN from console
  6. Authenticated user performs transactions
  7. User ends session
Note: this simple model does not show any exception cases.


Customer Transactions

  1. Customer selects transaction from menu
  2. Transaction is send to bank (which is a different system, thus a different diagram)
  3. Transaction is logged
  4. If a status indicates PIN is incorrect, user is notified of success
  5. Receipt is printed
  6. Customer may select another operation (loop) or terminate

To Do Step 1:

Create a Sequence Diagram in Lucid Chart system

For this task, you will create a UML Sequence Diagram for the Use Case “Check out shopping cart” using Lucid Charts. It will be based on the Use Case description provided below:

Use Case Name Check out shopping cart
Scope DVD Online Store
Level subfunction
Primary Actors Customer, Bank System
Stakeholders and Interests Customer wants to buy DVDs
The DVD store wants to sell DVDs and charge money for the DVDs
Bank System wants to process credit card information to charge money
Preconditions The customer is registered in the system and the user is logged in
Success Guarantee The order is placed
Main Success Scenario 1. The Customer presses the "Check out" button
2. The system shows the contents of the shopping cart and asks for the Shipping Address
3. The Customer enters the Shipping Address
4. The system asks for credit card information
5. The Customer enters credit card information
6. The system sends the payment information to the Bank system
7. The Bank system returns transaction OK
8. The System creates the Order
9. The System sends a notification to the Deliver man
10. The System shows the Confirmation of Place Order page
Extensions 7 7. If the Bank system returns transaction NO OK, the system should show an Error Page explaining the reason of the failure.
Special Requirements
Frequency The store expects 1 orders placed every 10 minutes

To Do Step 2:

Create a complete model in Lucid Chart

This involves generating a list of requirements, a set of use cases, a sequence diagram for one of the following systems:

Select one of these systems and think about its underlying requirements. Develop a list of requirements that cover the main categories of the system's functionality. Then, develop a set of use cases that document the scenarios that are associated with these requirements until you have adequately covered the system's major features and leaves you with good coverage of the items in your requirements list.

Next, pick one of your longer use cases that documents an interesting service that the system provides and create a sequence diagram that documents how objects from your class diagram interact to provide that service. Since this service will no doubt require objects that are more related to the system's implementation domain, it is okay for implementation domain concepts to appear in this diagram.

You are encouraged to work in teams on this assignment. You should submit individual solutions however, and document the members of the team at the top of the assignment.

Turn in:

  1. A single DOC file with all solutions in order, and embedded.


To achieve this grade: Rubric
A Comprehensive set of requirements and 6-8 use cases that document the primary services of the system and which follow the use case style guidelines discussed in Lecture 7. High-quality class diagram and sequence diagram that make use of the various notations covered in class. Clear attention to detail is evident in the work and the document is well written.
B All requirements are met but with less polish and not all functionality/concepts are covered by the submitted software artifacts.
C All requirements are met but with low polish or with major gaps in the functionality/concepts covered by the lists and diagrams. Use case style guidelines are being ignored, notations are wrong, and there are problems with the overall quality of the writing in the document.
D The assignment was of low quality with the majority of diagrams missing or wrong. Answers are not polished, and the figures/lists contain problems with grammar and spelling.
F The assignment was either not submitted or was of extremely poor quality. Poor quality work would consist of almost all diagrams/lists either missing or wrong or answers lacking any form of detail and containing many grammatical/spelling errors.

Topic revision: r2 - 2014-02-19 - JimSkon
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback