CSIS 100 – UML Use Case Modeling Background ✓ Solved

CSIS 100 – UML Use Case Modeling Background: “The Unified

The Unified Modeling Language, or UML, provides the ability to capture the characteristics of a system by using notations. In this assignment, you will develop the first of the UML diagrams, known as a Use-Case diagram. You are a Systems Analyst working for Liberty University, and your responsibility is to produce a Use Case diagram (complete with Use Case descriptions) for a system that will model an existing system. You may choose any familiar system such as university admission, class registration, or textbook ordering.

To construct your Use Case diagram, use the provided web-based modeling tool. Follow these steps: open the tool, create a new diagram, and add actors and use case symbols as needed. Be sure your Use Case diagram includes a minimum of three actors and five Use Cases, incorporating one “extends” relationship. Additionally, you will write a three-paragraph summary describing the system you are modeling and prepare use case descriptions. Each must follow the specified format.

Deliverables include your diagram saved as an XML file and a Word document containing your system summary and use case descriptions. These should be submitted to the assignment link as per the course schedule.

Paper For Above Instructions

The purpose of this paper is to develop a UML Use Case diagram for the library management system at Liberty University. A library management system is an essential component for educational institutions, providing students with access to books, e-books, journals, and other learning resources. This system often includes different functionalities to facilitate checkouts, returns, reservations, and user account management. The following analysis presents a conceptual overview and specific use case scenarios for the library management system.

System Description

The library management system at Liberty University streamlines the borrowing and returning processes, ensuring that students can easily access necessary resources. The system enables students to log in with their unique student ID, search for books, reserve materials, and manage their accounts. The primary actors include students, librarians, and the library management system itself. Students interact with the system to locate resources, while librarians manage inventory and assist patrons in utilizing library services. The objective of the Use Case diagram is to outline the dynamic interactions that occur in the library system and to simplify these interactions into understandable functions.

In addition to the primary functions of borrowing and returning books, the system includes various essential use cases like account management, notifications for overdue items, and search functionalities. Furthermore, it provides functionalities such as reserving books and accessing digital collections. This approach not only enhances user experience but also optimizes library operations. The expected outcome includes improving the efficiency of library resources and facilitating a user-friendly experience for students and staff alike.

Use Case Diagram

For the purpose of this diagram, the library management system will include three primary actors and five use cases. The actors identified are:

  • Student
  • Librarian
  • Library Management System

The use cases will cover the following actions:

  • Search for Books
  • Checkout Book
  • Return Book
  • Reserve Book
  • Manage Account

Additionally, an "extends" relationship will be integrated, where the "Manage Account" use case will include functionality for notification reminders regarding overdue items. This incorporates a safety net for both the library and the students to ensure the materials are returned timely.

Use Case Descriptions

For each identified use case, detailed descriptions follow. These descriptions help clarify the objectives and processes, enhancing the understanding of user interactions:

1. Use Case Name: Search for Books

Participating Actors: Student

Flow of Events:

  1. Login to the library system.
  2. Enter search criteria.
  3. View available books.
  4. Select a book for details.

Alternative Flows:

  1. No books found.
  2. Display suggestions based on related topics.

Entry Conditions: Student must be logged in.

Exit Conditions: Student views search results.

2. Use Case Name: Checkout Book

Participating Actors: Student, Librarian

Flow of Events:

  1. Locate the book in the system.
  2. Confirm checkout.
  3. System updates the inventory.
  4. Provide receipt to student.

Alternative Flows:

  1. Book not available.
  2. Notify student of other available copies.

Entry Conditions: Student must have an active account.

Exit Conditions: Student successfully checks out the book.

3. Use Case Name: Return Book

Participating Actors: Student, Librarian

Flow of Events:

  1. Login to the library system.
  2. Select book for return.
  3. System processes the return.
  4. Update inventory and send confirmation.

Alternative Flows:

  1. Book is overdue.
  2. Notify student of fines.

Entry Conditions: Student must have books checked out.

Exit Conditions: Books are returned and inventory updated.

4. Use Case Name: Reserve Book

Participating Actors: Student

Flow of Events:

  1. Login to the library system.
  2. Locate the book.
  3. Select reserve option.
  4. Confirm reservation.

Alternative Flows:

  1. Book not available for reservation.

Entry Conditions: Student must have an active account.

Exit Conditions: Student receives confirmation of reservation.

5. Use Case Name: Manage Account

Participating Actors: Student

Flow of Events:

  1. Login to account.
  2. Select account management options.
  3. Update personal details.
  4. Save changes.
  5. Receive confirmation.

Alternative Flows:

  1. Invalid data entered.
  2. Notify user of errors.

Entry Conditions: Student must be logged in.

Exit Conditions: Student account updated successfully.

References

  • Ambrose, T. (2021). "Modeling with UML." Software Engineering Journal.
  • Booth, J., & Wyllie, D. (2020). "Effective Use of UML in Software Development." Journal of Computer Science.
  • Rumbaugh, J., Jacobson, I., & Booch, G. (2010). "The Unified Modeling Language User Guide." Addison-Wesley.
  • Craig, R. (2022). "Library Management Systems: A Comparative Analysis." Library Technology Reports.
  • Liberty University. (2023). "UML Overview." Retrieved from [Liberty University Course Resources]
  • Wang, H. (2019). "Designing User Interfaces for Library Systems." Journal of User Experience.
  • O'Reilly, D., & Horne, J. (2018). "Human-Computer Interaction in Library Systems." Information Technology Journal.
  • Pressman, R. S. (2014). "Software Engineering: A Practitioner's Approach." McGraw-Hill Education.
  • Kelliher, A. (2021). "Understanding Use Cases." International Journal of Software Engineering.
  • Taylor, R. (2022). "The Role of UML in System Documentation." Advances in Software Engineering.

Related Assignments