Project Assignment #3: Activity And Use Case Diagrams ✓ Solved

Project Assignment #3: Activity Diagram / Use Case Diagram O

Project Assignment #3: Activity Diagram / Use Case Diagram ObjectiveThe purpose of the project is to create a use case diagram and activity diagram for A Video Store (AVS) System.Exercise Narrative:A Video Store (AVS) runs a series of fairly standard DVD video stores. Before a video can be put on the shelf, it must be cataloged and entered into the video database. Every customer must have a valid AVS customer card in order to rent a video. Customers rent videos for three days at a time. Every time a customer rents a video, the system must ensure that they do not have any overdue videos.

If so, the overdue videos must be returned and an overdue fee paid before customer can rent more videos. Likewise, if the customer has returned overdue videos, but has not paid the overdue fee, the fee must be paid before new videos can be rented. Every morning, the store manager prints a report that lists overdue videos. If a video is two or more days overdue, the manager calls the customer to remind them to return the video. If a video is returned in damaged condition, the manager removes it from the video database and may sometimes charge the customer.

AVS offers different types of memberships you can pay as you go $5 per DVD or subscribe to a monthly service for $50 that offers one daily DVD, or subscribe monthly for $100 that offers unlimited DVD rentals. Types of payments accepted areCash, Check, Credit card.Deliverables (Printed as PDF) ï‚· Cover Page from the 2nd page of this assignment handout ï‚· Complete Use Case Diagram in JUDE (make sure you use include / extends / generalization types of associations when applicable) ï‚· Complete Activity Diagram in JUDE Deliverables (Electronic) 1. Create a zip file of all your files and upload to blackboard in the same order of the printed deliverables.

Paper For Above Instructions

Introduction and objective. The AVS (A Video Store) system requires clear modeling of how customers interact with the store through use cases and how operations flow in activities. The goal is to produce a Use Case Diagram that captures primary actors, such as Customer, Store Clerk, and Store Manager, and their interactions with the AVS system, along with an Activity Diagram that details the step-by-step flow for core processes like renting a video, handling overdue items, and processing payments. This alignment supports both requirements communication and system design, providing a foundation for implementation and testing. UML-based modeling, including use cases, extends/includes relationships, and generalization, is widely advocated in software engineering literature as an effective method for analyzing and communicating functional requirements (Jacobson, Booch, & Rumbaugh, 1999; Fowler, 2003).

Actors and their primary responsibilities. The primary actors for AVS are: (1) Customer, who seeks to rent or return videos and handle payments; (2) Store Clerk, who assists with cataloging, checkout, and payments; (3) Store Manager, who oversees operations, prints overdue reports, and handles damaged items. A possible fourth actor is the AVS System itself, which enforces business rules and validates conditions such as card validity and overdue status. In a Use Case Diagram, these actors interact with key use cases such as Catalog Video, Validate Customer Card, Rent Video, Return Video, Pay Overdue Fee, Manage Membership, Print Overdue Report, and Handle Damaged Video. The relationships among use cases can be expressed using include, extends, and generalization as appropriate (Rumbaugh, Jacobson, Booch, 2005).

Use Case Diagram design. The core use cases for AVS can be defined as follows: Catalog Video (system updates the video database with new entries); Validate Customer Card (ensures a valid AVS customer card); Rent Video (customer rents a DVD for three days); Return Video (customer returns a DVD); Pay Overdue Fee (customer pays any overdue charges); Manage Membership (options: Pay-as-you-go at $5 per DVD; Monthly plan at $50 with one daily DVD; Monthly unlimited at $100); Print Overdue Report (store manager generates a daily/periodic report); Remove Damaged Video (manager removes damaged items from catalog and may charge the customer). The Rent Video use case should include Validate Customer Card and Check Overdue; Pay Overdue Fee can extend Rent Video when payment is required before continuing. If a video is overdue by two or more days, the system may trigger a reminder flow (extend or include/investigate its payment condition) (Jacobson, 1992; Larman, 2004).

Activity diagram considerations. The primary activity diagram should illustrate the Rent Video process, including: start, customer authentication (card validity), overdue check, payment processing if overdue or fees are due, video availability, checkout with due date set to three days, and end. A parallel activity includes the daily store manager’s activities: generating overdue reports and calling customers for reminders when items are two days overdue. A separate activity path handles damaged videos: if a video is returned damaged, the system flags it, the manager removes it from the catalog, and may issue a charge. The activity diagram should also model membership selection at checkout, showing that customers choose among Pay-as-you-go, Monthly (one daily), or Monthly (unlimited) plans, and that payment type can be Cash, Check, or Credit Card. These elements support a coherent process flow and clarity for implementation in JUDE (OMG UML Specification; Booch et al., 2005).

Design decisions and mapping to JUDE. The Use Case Diagram should reflect include/extends relationships: Rent Video includes Validate Customer Card and Check Overdue; Pay Overdue Fee extends Rent Video (when overdue exists). Membership types can be modeled as a separate include/extend decision when a rental occurs, or as a separate precondition/state in the Rent Transaction. The Activity Diagram for Rent Video should incorporate decision nodes for overdue status and payment completion, with a synchronization merge for successful checkout. The modeling approach adheres to standard UML practices described in foundational texts and official specifications (Jacobson, 1992; Fowler, 2003; OMG, 2015).

Implementation notes and best practices. When constructing the JUDE diagrams, it is advisable to label actors clearly (Customer, Clerk, Manager) and to annotate use cases with preconditions (valid AVS card) and postconditions (rental created with due date; overdue fees cleared). Use case relationships should be explicit: include for common subfunctions (Validate Card, Process Payment), extends for optional flows (Reminder Call, Damage Handling), and generalization for membership options if appropriate (Sommerville, 2015; Larman, 2004). The diagrams should be validated by stakeholders to confirm coverage of the narrative and business rules described in the exercise narrative (Sommerville, 2015; Kruchten, 2003).

Conclusion. The AVS use case and activity diagrams will provide a robust visualization of system behavior for rentals, payments, overdue management, and inventory control. By applying standard UML practices (include/extends/generalization) and aligning with well-established modeling guidance, the diagrams will facilitate communication across stakeholders and support subsequent software design and implementation (Booch, Rumbaugh, & Jacobson, 2005; Fowler, 2003; OMG, 2015).

References

• Jacobson, I., Booch, G., Rumbaugh, J. (1999). The Unified Software Development Process. Addison-Wesley.
• Booch, G., Rumbaugh, J., Jacobson, I. (2005). The Unified Modeling Language User Guide. Pearson.
• Fowler, M. (2003). UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd ed.). Addison-Wesley.
• Larman, C. (2004). Applying UML and Patterns (3rd ed.). Addison-Wesley.
• Sommerville, I. (2015). Software Engineering (10th ed.). Pearson.
• OMG. (2015). UML 2.5 Specification. Object Management Group. Retrieved from https://www.omg.org/spec/UML/2.5/
• Booch, G. (1991). Object-Oriented Analysis and Design with Applications. Benjamin/Cummings.
• Jacobson, I. (1992). Object-Oriented Software Engineering: OOSE. ACM Press/Addison-Wesley.
• Kruchten, P. (2003). The Rational Unified Process: An Introduction. Addison-Wesley.
• Hoffer, J. A., George, J. F., Valacich, J. S. (2010). Modern Systems Analysis and Design. Pearson.