Slide 1 Use Case Sequence Diagram Explained. Slide 2 Steps for Building a Sequence Diagram 1)Set the context 2)Identify which objects and actors will.

Slides:



Advertisements
Similar presentations
How to Register at My. SSS. Before starting, please ensure you have following : Your SSS Number Your account MNCs SSS Number :
Advertisements

How to register to access the members only pages on our website 1. Scroll down to the bottom of the home page and click on the text (arrowed)
Sign Up to Become a Member of the Student Union LearnZone College Links Student Union 1 2 Log In to Sign Up.
BT Wholesale Broadband Escalations Portal Adding or Retrieving Notes
Chapter 6: Behavioral Modeling
9/10/2004Use Case Workshop 1 CSC480 Software Engineering Workshop 1 Requirements Modeling.
Cisco Confidential 1 © Cisco and/or its affiliates. All rights reserved. Last Updated: April 2014 Instructions for Navigating in the Training.
Information System Engineering
Interaction Diagrams Activity Diagram State Machine Diagram
Systems Analysis and Design in a Changing World, Fourth Edition
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
THE OBJECT-ORIENTED DESIGN WORKFLOW UML2 Sequence Diagrams.
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Object Collaborations. Objectives: Object Interaction (cont.) You will be able to:  Use sequence diagrams to detail object interactions.
To Add a 2 nd to your NGIN Account October 9, 2012.
CitiManager Cardholder Self- Registration
Updating User Information Password – use this field to change your own password Confirm Password – retype the new password for verification purposes To.
Blaha and Rumbaugh Sections 7.2 and 8.2
Slide 1 Use Case Sequence Diagram. Slide 2 Interaction Diagrams l Interaction diagrams model the behavior of use cases by describing the way groups of.
Chapter 7: The Object-Oriented Approach to Requirements
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Extended Class Diagram.
SMART Agency Tipsheet Staff List This document focuses on setting up and maintaining program staff. Total Pages: 14 Staff Profile Staff Address Staff Assignment.
Welcome to the Virtual Math Teams of the Math Drexel University A Quick Tutorial for Beginners Step 1. First of all, you need to go to this URL.
CQRS User Story – SERVICE PROVIDER Chris Brown – project manager 05 September 2012 Calculating Quality Reporting Service.
Introduction to Sequence Diagrams
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.
In the web address box enter Enter your user ID (first and last initial 7 digit ID number) Select Log in.
Returning Students You registered last year. If you remember your , type it in at the top of the screen Click on “Password Help”
How to Verify and Activate your Free APICS Student Membership For general questions, please contact: Steven Aspacher Senior Manager, Student Membership.
TEXTBOOK ADOPTIONS Mastering the New Online Adoption Process.
19 March 2015 Traning class of “Commumerce.com”. Content Main part Easy to understand, and illustrated 1 2 Buyer 3 Seller Registration.
Plan Design Analyze Develop Test Implement Maintain Systems Development Life Cycle eBookSharing.
To access our web services, go to……. Click on Customer Login.
University of Southern California Center for Systems and Software Engineering CS577a: Sequence Diagrams and ‘Design Classes’ David Klappholz, Nupul Kukreja.
Use Case Modeling Example By: Dr. Issam Al-Azzoni.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
DESIGN PART 2: OBJECT-LEVEL SEQUENCE DIAGRAMS WITH AN EXAMPLE OF COMPOSITION BTS430 Systems Analysis and Design using UML.
AudioLunchbox Screen Prototypes. Start Up Screen Login Account Create Order Screen Admin Panel Welcome Screen Verify Order Page Payment/ Order Confirmed.
Granite School District Crosspointe Gradebook Parent/Student Portal
This is a short presentation to explain how and why to login to the CIM website as a member. Benefits are: Access to myCIM (private member area, contains.
Database Design Normalisation. Last Session Looked at: –What databases were –Where they are used –How they are used.
Online Parking System.
Rotary Member Access A Tool for Club Presidents and Secretaries.
How Your Customers Will Pay Online & by Phone
Employee Self Service Review and Print Benefits Confirmation 1.
Applicant sends request for username and password to; Applicant sends request for username and password.
Data Flow Diagrams. A diagram which shows the movement of data in a system.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Lecture Notes for Revisiting Use Case Descriptions.
Member Access. This presentation will help you familiarize yourself with the functions of Member Access. Throughout this presentation, you can enter the.
After receiving the confirmation , use the link and Login Id provided to retrieve your password.
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 The Manage by Group screen allows you to: Create a New Group  Add individuals.
Getting Started with. Before you register A valid address Course ID from your instructor Student access code Before you register, be sure you have:
Logging On – to Rotary databases Two Distinct Resources – Club Website & Database Referred to often as ClubRunner – Rotary International.
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
COMP 2710 Software Construction Sequence Diagrams (cont.)
Step 1 Login on UHCP Site
Behavioral Modeling.
How to Use Members Area of The Ninety-Nines Website
Mastering the New Online Adoption Process
JC manufacturing, inc West Marine Ordering
Interaction diagrams Interaction diagrams are models that describe how groups of objects collaborate in some behavior. Typically, an interaction diagram.
Reception volunteers: How to use the membership administration system
JC manufacturing, inc Belk Ordering
--Valid address --Course ID --Access Code or
Smart Cookies – Volunteer Registration
USA Softball Background Check
MyLion Registration Website | Mobile device
Placing a Broadband Provide Order Version 1
NSVFA Membership Renewal
Presentation transcript:

Slide 1 Use Case Sequence Diagram Explained

Slide 2 Steps for Building a Sequence Diagram 1)Set the context 2)Identify which objects and actors will participate 3)Set the lifeline for each object/actor 4)Lay out the messages from the top to the bottom of the diagram based on the order in which they are sent 5)Add the focus of control for each object’s or actor’s lifeline 6)Validate the sequence diagram

Slide 3 Steps for Building a Sequence Diagram To do these steps, the best tool is a Message Analysis Table. As we progress thru the steps we will both show how to develop the Message Analysis Table and then show how the sequence diagram is constructed from that table.

Slide 4 1)Set the context. a)Select a use case. b)Decide the initiating actor. Steps for Building a Sequence Diagram 3 Register Membership Customer

Slide 5 1)Set the context. a)Select a use case. b)Decide the initiating actor. Steps for Building a Sequence Diagram Use Case NameRegisterAsMember Use Case ID3 Initiating ActorCustomer Message Analysis Table

Slide 6 2)Identify the objects that may participate in the implementation of this use case by completing the supplied message table. a) List candidate objects. 1)Use case controller class 2)Domain classes 3)Database table classes 4)Display screens or reports Steps for Building a Sequence Diagram

Slide 7 2)Identify the objects 1)Use case controller class Steps for Building a Sequence Diagram RegisterAs Member Controller

Slide 8 2)Identify the objects 2)Domain Objects Steps for Building a Sequence Diagram RegisterAs Member Controller Member

Slide 9 2)Identify the objects 3)Database Table Classes Steps for Building a Sequence Diagram RegisterAs Member Controller Member Table

Slide 10 2)Identify the objects 4)Display Screens and/or Reports Steps for Building a Sequence Diagram RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen

Slide 11 2)Identify the objects Steps for Building a Sequence Diagram Candidate Objects/Classes Use Case ControllerRegisterAsMemberController DomainDatabase Table Display Screens or Report Other UC MemberMemberTableMemberApplicationScreen NewUserNamePasswordScreen ConfirmationScreen

Slide 12 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. 1)Examine each step in the normal scenario of the use case description to determine the messages needed to implement that step. 2)For each step: 1)Identify step number. 2)Determine messages needed to complete this step. 3)For each message, decide which class holds the data for this action or performs this action 3)Make sure that the messages within the table are in the same order as the normal scenario

Slide 13 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. 1. Customer enters name, address, phone number, address, credit card number, and expiration date of credit card. 2. System validates member information. 3. Customer enters new user name and password for subsequent membership login. 4. System validates user name and password. 5. Customer confirms membership information. 6. System s membership confirmation to new member.

Slide 14 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. acceptMemberInformation() 1. Customer enters name, address, phone number, address, credit card number, and expiration date of credit card. Message

Slide 15 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. validateMembershipInformation () 2. System validates member information.. Message

Slide 16 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. acceptUserNamePassword () 3. Customer enters new user name and password for subsequent membership login.. Message

Slide 17 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. validateUserNamePassword () System validates user name and password. Message

Slide 18 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. acceptConfirmation () updateMembershipInformation () 5. Customer confirms membership information.. Message

Slide 19 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) b)List candidate messages. MembershipConfirmation 6. System s membership confirmation to new member Message

Slide 20 Steps for Building a Sequence Diagram For each step: 1)Identify step number. 2)Determine messages needed to complete this step. 3)For each message, decide which class holds the data for this action or performs this action We have done the first two steps – now lest decide which class should RECEIVE this message and thus have a method to perform the functions of the message.

Slide 21 Steps for Building a Sequence Diagram Step # Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember 3acceptUserNamePasswordNewUserNamePasswordScreen 4validateUserNamePasswordMember 5acceptConfirmationConfirmationScreen 5updateMembershipInformationMemberTable 6 MembershipConfirmationMember

Slide 22 Steps for Building a Sequence Diagram 2)Identify the objects (cont.) c)Begin sequence diagram construction. 1)Draw and label each of the identified actors and objects across the top of the sequence diagram. 2)The typical order from left to right across the top is the actor, primary display screen class, primary use case controller class, domain classes (in order of access), and other display screen classes (in order of access) 3)Set the lifeline for each object/actor

Slide 23 Steps for Building a Sequence Diagram c)Begin sequence diagram construction. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer

Slide 24 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer

Slide 25 4) Lay out the messages from the top to the bottom of the diagram based on the order in which they are sent. a)Working in sequential order of the message table, make a message arrow with the message name pointing to the owner class. b)Decide which object or actor initiates the message and complete the arrow to its lifeline. c)Add needed return messages. d)Add needed parameters and control information. Steps for Building a Sequence Diagram

Slide 26 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer acceptMemberInformation validateMembershipInformation acceptUserNamePassword validateUserNamePassword acceptConfirmation updateMembershipInformation MembershipConfirmation

Slide 27 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer acceptMemberInformation

Slide 28 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation

Slide 29 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword

Slide 30 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword validateUserNamePassword (username, password):valid

Slide 31 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword validateUserNamePassword (username, password):valid acceptConfirmation:confirmed

Slide 32 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword validateUserNamePassword (username, password):valid acceptConfirmation:confirmed

Slide 33 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword validateUserNamePassword (username, password):valid acceptConfirmation:confirmed updateMembershipInformation

Slide 34 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword validateUserNamePassword (username, password):valid acceptConfirmation:confirmed updateMembershipInformation memberhipsConfirmed()

Slide 35 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword validateUserNamePassword (username, password):valid acceptConfirmation:confirmed updateMembershipInformation memberhipsConfirmed() MembershipConfirmation

Slide 36 5)Add the focus of control (activation box) for each object’s or actor’s lifeline. 6)Validate the sequence diagram. Steps for Building a Sequence Diagram

Slide 37 Steps for Building a Sequence Diagram c. Set the lifeline for each object/actor. RegisterAs Member Controller Member Table Member Application Screen NewUser Name Password Screen Confirm- ation Screen Customer acceptConfirmation:confirmed MembershipConfirmation validateMembershipInformation (member information):valid acceptMemberInformation acceptUserNamePassword memberhipsConfirmed() validateUserNamePassword (username, password):valid updateMembershipInformation