Please see attachment for Assignment. 

  You will complete this assignment and add it to your Assignment 2  from last week 

Quick Resources

Use Case Diagrams

1.  Ambler, Scott (n.d.). System Use Cases: An Agile Introduction.  Retrieved from 

System Use Cases: An Agile Introduction

2.  See Scott Ambler’s article Reuse in Use-Case Models: <>, <>, and Inheritance  retrieved from  

Reuse in Use-Case Models: Extends, Includes, and Inheritance

3.  See 

http://www.agilemodeling.com/artifacts/useCaseDiagram.htm

 for other examples of use case diagrams.

4. See  Larman, Chapter 6

Using a CASE Tool for Use Case Diagrams

1.  Visual Paradigm. (2016 March 4).  Drawing use case diagrams.  Retrieved from 

https://www.visual-paradigm.com/support/documents/vpuserguide/94/2575/6362_drawinguseca.html

Activity Diagrams

1. Please see 

http://www.agilemodeling.com/style/activityDiagram.htm

 for an example of an activity diagram. 

2.  Ambler, Scott (n.d.). UML2 Activity Diagrams: An Agile Introduction.  Retrieved from 

http://www.agilemodeling.com/artifacts/activityDiagram.htm

3.  Ambler, Scott (n.d.). UML2 Activity Diagramming Guidelines.  Retrieved from 

UML Activity Diagram: Diagramming Guidelines

 .  This style guide includes general guidelines, activities, decision points, guards, parallel activities, Swimlanes, and action objects.

Using a CASE Tool for Activity Diagrams

1.  Rmb1905. (2009 March 10).  9.01_Activity Diagrams Basic Symbols. [Video file].  Retrieved from 

2.  Visual Paradigm. (2016 March 4).  Drawing activity diagrams.  Retrieved from 

https://www.visual-paradigm.com/support/documents/vpuserguide/94/2580/6713_drawingactiv.html

3.  Visual Paradigm. (2016 March 4).  Splitting control flow in activity diagram.  Retrieved from 

https://www.visual-paradigm.com/support/documents/vpuserguide/94/2580/85419_splittingcon.html

Use Cases, Detailed Use Cases, and Mockups

1.  See  

Maintain Instructor Use Case Example

 for a use case diagram, detailed use case, and mockups with dialog for the ITOT Case Study.

IT Online Training (ITOT) Analysis Specification

with the word “Insert” or “Provide” are explanatory and should be removed from your document after you follow the directions. Other symbols <> require you to insert names.

This document is intended to provide a partial analysis specification for the project case study, IT Online Training. This document includes an introduction, use case diagrams, detailed use cases, activity diagrams, domain class diagrams, and domain state diagram. Parts of this specification will come from the IT Online Training Specification and from your assignments. This document integrates some of the analysis diagrams and project specification details to provide a single reference. Headings are used to provide easier navigation. To see the heading navigation, in Word click on the View tab and check the Navigation Pane box.

You will submit this document for each assignment with new sections completed and added to it. You can revise any previous sections as needed. Remember to insert you name and class information at the top of this document.>

1. Introduction

1.1 Problem Description

1.2 Sponsor Project Description

1.3 Sponsor Requirements

2.

System Use Case Diagram

2.1 System Use Case Diagram

Customer

”.>

2.2 Use Case Diagram Description

2.3 List of Actors and Definitions

“An actorName is a

…

”.

Then add additional details as necessary. Use the following table format.>

2.4 List of Use Cases and Description

…

3. Detailed Use Case and Activity Diagram

3.1. Use Case

above with the actual name of your use case Manage Shopping Cart Use Case. For example it might read Manage Shopping Cart Use Case.>

3.1.1. Use Case Description/Scenario

above with the actual name of your use case, for example, Manage Shopping Cart Use Case Description/Scenario. In this section insert a description/scenario for this use case.>

3.1.2 Use Case Detailed Steps

.

Use Case and History

Actors, Description, Preconditions, Postconditions

Normal Path

Alternative Path

User Action

System Action

Use Case Related System Issues

Exceptions:

I

ncludes:

Priority:

Frequency of Use:

Business Rules:

Special Requirements:

Assumptions:

Notes and Issues:

3.1.3 Form/Screen Mockup and Dialog

above with the actual name of your use case like Manage Shopping Cart so that it reads Manage Shopping Cart Form/Screen Mockup.

Provide a mockup (image) of whatever forms/screens that are used to illustrate the activities in your use case. Include a description of your forms/screens. These should support and illustrate your use case. For example for a Create Customer use case, a Create Customer screen with customer id, first and last name, address, phone numbers for work and cell phone boxes and a Submit Button would be an example of a form or web screen.

Include a discussion of the form including its content (data elements) and how they will be used. Identify the classes has these attributes. Include a dialog (step by step instructions on what happens when this form is used. While these forms/screens will be used in the application, they are also used as a storyboard to explain the user interface to the sponsors of the project. These can be used to create and verify the steps of your detailed use case. >

3.1.4 Activity Diagram Name for Use Case and Discussion

”

above with the actual name of your use case like Manage Shopping Cart. For example, Activity Diagram for Use Case Manage Shopping Cart. Insert the following:

1. An activity diagram for your use case

2. A discussion of the activity diagram.

Remember that the detailed use case steps should be reflected in your activity diagram.>

4. Domain Class Diagram

4.1 Domain Class Diagram(s)

< Insert your Domain Class Diagram here. Remember that classes are named with nouns or noun phrases. A domain class diagram includes classes with attributes and operations for each class and named relationships with multiplicity constraints. Associations need names. You do not need a name for generalization, aggregation, and composition relationships. You must have names for associations .

4.2 Class and Relationship Analysis

Then on the class diagram association between Instructor and Course you can name the association “teaches” and add the multiplicity constraints (1) near Instructor and (0..1) near Course.

4.3 List of Classes with Definitions, Attributes, and Operations

T Online Training

 Project Requirements 

2018

document. Remember that class names are nouns or noun phrases. To define a class, complete the phrase “A className is a …”. Additional information can then be added. Attributes are properties of a class like “customerID” and begin with a lowercase letter. Operations are actions that a class can perform and begin with a lower case letter followed by parentheses (). We can create a new instance of a class (Create), delete an instance of a class (remove), get ( read) values of the attribute, or set (change) values of the attribute. See the examples in the table below.

The examples below include all of the getter/setter methods for the attributes. You do not need to include them in this assignment, but for Assignment 2 when you create your class diagram, you can use the features of our CASE to so that the getter/setter methods will automatically be added

.

For now you can use a high level modify() and read() to represent the getter/setter methods.

Later In design these will be modified depending on the technology used. During analysis we want to be independent of technology as much as possible.>

Classes, Attributes, Operations, Requirement

…

…

…

…

4.3.1 List of Classes, Attributes, Operations, and Requirement Number Discussion

4.4 Domain Class Diagram Discussion

5. Domain State Diagram

5.1 State Diagram and Discussion

above with the name of the required class ShoppingCart State Diagram so that it reads like ShoppingCart State Diagram and Discussion. See the examples of state diagrams in the assignment. Complete the following:

1. Insert a state diagram for the class from your class diagram as indicated in the assignment.

2. Provide a brief discussion of your State Diagram.>

6. Sequence Diagrams

6.1 System Sequence Diagram (SSD) for Use Case and Description

above with the name of your detailed Use Case like Manage Shopping Cart so that it reads like System Sequence Diagram (SSD) for Manage Shopping Cart Use Case.

1. Insert a description of your SSD.

2. Insert a UML System Sequence Diagram (SSD) for your use case from Section 3 above. An SSD shows the actor and the System and the messages (including message name and parameters) required to implement the detailed use case description from Section 3. The SSD shows the inputs and outputs to/from the system for the use case.>

6.2 Detailed Sequence Diagram for Use Case and Discussion

above with the name of your use case like Manage Shopping Cart so that it reads like
Detailed Sequence Diagram for Manage Shopping Cart Use Case and Description
.

1. Insert a UML Detailed Sequence Diagram for your use case. A Detailed Sequence diagram shows the actor and instead of the System like in the SSD, it will show all of the objects (instances of classes) that are required to implement the use case. Your Class Diagram will be helpful here. The net messages should be the same as in your SSD above but you will have more detailed messages including message name and parameters among the different objects that are actually required to implement the use case. So now you will add objects across the top of your diagram and omit System. Include a discussion of your Detailed Sequence Diagram.>

2. Insert a discussion of your Detailed Sequence Diagram.

Appendix.

Analysis Specification 2018R2 Page 7