MIS 4330 Assignment 2 Use Case Diagrams 30 Points

Mis 4330 Assignment 2 Use Case Diagrams 30 Pointsassignmentconsi

Consider the following scenario then complete the exercises below: A Video Store (AVS) runs a series of fairly standard 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.

Paper For Above instruction

Develop a use case diagram for the AVS scenario and create detailed use case descriptions for each use case identified. The use case description must include the use case name, actor, brief description, normal flow of events, and exception flow of events. Ensure the descriptions are thorough, capturing all possible variations and exceptions to give a comprehensive understanding of each process.

The use case diagram should encapsulate all actor interactions with the system, including cataloging videos, renting videos, returning overdue videos, paying overdue fees, printing overdue reports, calling customers for overdue reminders, and removing damaged videos. Each use case should be clearly labeled, indicating the primary actors involved, such as customers and store managers, along with other possible actors like the system or database.

This exercise aims to visualize the interactions within the video rental system clearly and provide detailed procedural descriptions for each interaction to foster understanding and facilitate system design and development.

References

  • Saroyan, William. "Hello Out There." In Bennett Cerf and Van Henry Cartmell (Eds.), Thirty Famous One Act Plays. Random House, 1949, pp. 549-566.
  • Cummings, Edward Estlin. "love is more thicker than forget." In 100 Selected Poems. Grove Press, 1959.
  • Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Software Development Process. Addison-Wesley.
  • Jacobson, I., & Objectory AB. (1992). Object-Oriented Software Engineering: A Use Case Driven Approach. ACM Press.
  • Cockburn, A. (2000). Writing Effective Use Cases. Addison-Wesley.
  • Reenskaug, T. (1979). The Model-View-Controller (MVC) paradigm.
  • Usman, M., & Li, F. (2017). "Use Case Modeling for Interactive System Development." International Journal of Software Engineering & Applications.
  • Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach. McGraw-Hill.
  • Hall, K. (2001). "Use Case Diagram." In Object-Oriented Modeling and Design, Addison-Wesley.
  • Larman, C. (2004). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Addison-Wesley.

Related Assignments