Our orders are delivered strictly on time without delay
Paper Formatting
Double or single-spaced
1-inch margin
12 Font Arial or Times New Roman
300 words per page
No Lateness!
Our orders are delivered strictly on time without delay
Our Guarantees
Free Unlimited revisions
Guaranteed Privacy
Money Return guarantee
Plagiarism Free Writing
Interaction Models
You will add an SSD (System Sequence Diagram) and a Detailed Sequence Diagram based on your detailed use case for Manage Shopping Cart. You will also need to refer to your class diagram and activity diagram or detailed use case steps. This will complete the Analysis Specification for the IT Online Training Case Study. See the list of Resources at the end of this assignment for details on the two types of sequence diagrams and activity diagram.
Course Objective(s) CO4: Explain the software development process including system conception, domain analysis, and application analysis and their respective models.
CO9: Apply your knowledge of object oriented and UML concepts by designing and developing UML models.
In this assignment, you will complete the following sections in your Analysis Specification
Sections 6, 6.1, 6.2
Instructions 1. Review the resources listed in the Quick Resources below on Sequence and Activity diagrams.
2. Create a UML compliant SSD (System Sequence Diagram) based on your detailed use case, "Manage Shopping Cart". The SSD shows only two objects--the Actor and the System and the messages between them.
2.1 Use your CASE tool to create the UML compliant SSD and add it to Section 6.1 of your Analysis Specification from Week 3. Also add a discussion of your SSD.
3. Create a UML compliant Detailed Sequence Diagram based on your detailed use case, "Manage Shopping Cart". The Detailed Sequence Diagram shows Actors and all Objects involved in the detailed use case. Remember that Objects are instances of Classes.
Sample Answer
Sequence Diagrams for "Manage Shopping Cart"
This section presents the System Sequence Diagram (SSD) and the Detailed Sequence Diagram, providing a dynamic view of the "Manage Shopping Cart" use case.
6.1 System Sequence Diagram (SSD)
The SSD focuses on the events and messages that pass between the Actor (Customer) and the System (IT Online Training System).
SSD Discussion
The System Sequence Diagram illustrates the system's external behavior for the "Manage Shopping Cart" use case. The diagram begins with the customer initiating a search and culminates in the confirmation of the cart's contents.
searchForCourse(keywords): The interaction begins with the Customer sending a command to the System to find a course.
displayCourseDetails(courseList): The System responds with the results.
addItemToCart(courseID, quantity): The primary action where the Customer sends an action signal and required data to the System to update the cart.
displayCart(cartItems): The System returns a view of the updated cart.
updateItemQuantity(itemID, newQuantity) and removeItem(itemID): These are optional, iterative actions allowing the Customer to modify the cart contents.
displayCart(updatedItems): The System confirms any modifications.
The Detailed Sequence Diagram maps the system events in the SSD to the internal object interactions and method calls within the IT Online Training System. This diagram assumes the existence of the following classes from the Class Diagram:
Customer: The actor who initiates the request.
:ShoppingCart (Control/Entity): Represents the current session's shopping cart.
:CourseCatalog (Control/Entity): Manages the list of available courses and course details.
:CartItem (Entity): Represents a single course entry in the cart.
:DisplayManager (Boundary): Responsible for presenting information to the user.
For clarity, the diagram focuses on the addItemToCart(courseID, quantity) system event.