Coursework 1: System Analysis and Design of QAHE Library System

This coursework report details the system analysis and design of a library management system for QAHE University. It includes a Use Case Diagram illustrating interactions between users (admin, staff, students) and the system for tasks like recording stock, updating member details, tracking loaned items, and generating late fee notifications. A Conceptual Class Diagram defines entities such as User (Staff, Students), Admin, Book, Transaction, and Bill, outlining their attributes and functions. Interaction diagrams, specifically UML Sequence Diagrams, model processes for adding new items, generating fines, updating member details, and reserving items. The system aims to streamline library operations, manage transactions, and provide efficient services to its users. The report provides a comprehensive overview of the system's architecture, components, and functionalities, contributing to a better user experience within the QAHE library.

Running head: SYSTEM ANALYSIS AND DESIGN OF QAHE
System Analysis and Design of QAHE
Name of the Student
Name of the University
Author note

1SYSTEM ANALYSIS AND DESIGN OF QAHE
Table of Contents
Coursework 1: Systems Design Report...........................................................................................2
1. Use Case Diagram...................................................................................................................2
2. Conceptual Class Diagram......................................................................................................5
3. Interaction Diagrams...............................................................................................................9
3.1 UML Sequence Diagram for Adding New Item and Generating Fine..................................9
3.2 UML Sequence Diagram for updating Member Details......................................................11
3.3 UML Sequence Diagram for Reserving Items....................................................................13
Bibliography..................................................................................................................................15

2SYSTEM ANALYSIS AND DESIGN OF QAHE
Coursework 1: Systems Design Report
1. Use Case Diagram
(Figure 1: Use Case Diagram for the Library System of QAHE)
(Source: Created by author)

3SYSTEM ANALYSIS AND DESIGN OF QAHE
The new form of library management system that would be built for QAHE University
will hold responsibility for transforming the ordering and management experience for teachers,
students and admin. The digital management system would help the members of the university to
easily manage each of the transactions and systems that are performed within the library. This
system would thus be mainly used for people who would visit the library for reading books,
consulting of books and making maximum use of software.
The description of the use cases for the different components are described as follows:
1. Recording Library Stock – The admin would hold the primary responsibility to keep
a record of every item that would be stocked within the library. The digital management system
would maintain a track of each of the items within the library. Each of the items would be
assigned with a unique ID that would help in proper identification of every item. This ID would
also be helpful for the admin to locate the particular item and also know the exact location of the
item. Based on gaining information about the record of every item, the admin would also be able
to check the stock of books, CDs or DVDs present within the library.
2. Updating of library members – The admin would be responsible for keeping a track
of each of the members who would reserve or borrow books from the library. Hence, in order to
perform this operation, the admin would need to put in major details within the digital
management system. The system would be designed in such a manner that it would include each
of the necessary details within it. This would include – the name of the student or teaching staff,
contact information such as their branch, year, roll number and number of books previously
issued.

4SYSTEM ANALYSIS AND DESIGN OF QAHE
The admin would thus be provided with the added functionality to modify the
information as and when required if necessary. They would search for the books as mentioned by
the student when they would mention it to the admin. However, whenever a student would pass
out from the university, the admin would delete the candidature and different records from the
database of the digital management system.
3. Track record of Loaned Items – The system would keep a record of the items, which
would be loaned to a user. This system would provide the loan facility for a certain duration of
time. Users would receive a notification when they need to return the books or items to the
library. When the duration of the returning of items would be completed, the student would be
provided with a notification regarding the late fees that need to be paid by them.
4. Generation of Notification for Late Fees – The system of late fees would only be
initiated when a user would not submit an item within the duration of returning. The system
would calculate the total number of days for which the item had not been returned. This amount
would be calculated accordingly and thus e-mail reminders would be sent to the user to return the
item along with the fees amount.

5SYSTEM ANALYSIS AND DESIGN OF QAHE
2. Conceptual Class Diagram
(Figure 2: Conceptual class Diagram for the Library System of QAHE)
(Source: Created by author)

6SYSTEM ANALYSIS AND DESIGN OF QAHE
The conceptual class descriptions for the two primary form of conceptual class within the
diagram is described as follows:
1. User – The user within the system includes the teaching staff and students who would
borrow or reserve books for their use. The user within the system comprises of the following
entities, which includes user ID, name, branch and book limit. Users would be provided with
different kind of functions that includes: requestBook(), returnBook(), renewBook() and
enquiry(). Thus, they would be able to support four kind of functionalities as requesting for any
particular book, returning of borrowed books to the library, renewal of any book or perform any
kind of enquiry to the digital system. The user includes two important sub-aspects, which are:
 Staff – They would be provided with a staff ID, which is a unique ID generated by the
digital management system. They would need to register themselves with that unique ID
and thus the system would permit them to reserve or borrow books.
 Students – The students would also be provided with a unique ID generated from the
digital management system. Students would have an additional function that would be
included within their conceptual class, which is fine(). This method or function would
calculate the total number of fines that are applied over any particular student and the
total amount that needs to be paid by them.
2. Admin – The admin would also perform important kind of functionalities in relation to
maintaining of track record of borrowed books, reserved books and restocking of books and
other items within the library. They would also be responsible for adding members, updating
their records, deleting old members and also keep a proper form of check whether any item
would need to purchased or replaced in the future.

7SYSTEM ANALYSIS AND DESIGN OF QAHE
The admin would also check whether a user is fined based on many kind of aspects.
These include returning of borrowed items after the certain period is over. The primary functions
of the admin would be to issue books, maintain a track of returned books, perform registration of
new members, and give permission for renewal of books, search of books and collect fine from
the students who would be marked as per the terms and conditions of the library.
3. Book – The conceptual class for book would comprise of each of the items that might
be ordered by the staff and students. The conceptual class of book includes certain sub-aspects
that includes: Magazines, CDs and DVDs. Each of the items presented within the university
would comprise of a unique ID. This would be highly helpful in differentiating each of the items
based on their IDs. It would also comprise of title for the book or the item, author or publisher as
mentioned within the label of CD, DVD or magazine. The digital management system would
also store the purchase date for each items. This information would be stored along with the ID
of the user who would borrow or reserve the particular item.
The items would also comprise of store number, which would be extremely helpful for
the admin to locate the exact area from where the item could be collected and thus provided to
the user. The conceptual class for book also comprises of two important functions, which are
display() and update(). Upon entering the ID of the item into the digital management system, the
display function would display the total number of details for the particular item. The update
function would provide the necessary updates regarding the particular item. This function would
display whether the item is borrowed or reserved by a user.
4. Transaction – The conceptual class for transaction would comprise of certain
attributes, which would help the admin to maintain the different kind of transactions that would
be made within the system. A transaction ID would be generated whenever a user would reserve

8SYSTEM ANALYSIS AND DESIGN OF QAHE
or borrow items from the library. The issue date and due date would also be shown in this
transaction. Hence, this would help the admin to update the details of the user accordingly.
However, the conceptual class of transaction would include certain functions such as
creation of transaction, deletion of transaction, display of transaction and updating transaction.
Every kind of payment made or clearing of due fines would be considered as a form of
transaction. This would thus be stored within the system.
5. Bill – Whenever a transaction would be completed, the system would generate a bill.
This bill would be produced by the system and thus could be used by the admin and user for
future references. A bill ID would be automatically generated after a transaction is completed.
The conceptual class for bill would comprise of two important functions that includes
createBill() and updateBill(). Every time a transaction would be completed, the create bill
function would generate the bill while on the other hand, the update bill function would update
the latest records within the bill.

9SYSTEM ANALYSIS AND DESIGN OF QAHE
3. Interaction Diagrams
3.1 UML Sequence Diagram for Adding New Item and Generating Fine
(Figure 3: UML Sequence Diagram for Adding New Item and Generating Fine)
(Source: Created by author)

10SYSTEM ANALYSIS AND DESIGN OF QAHE
The above diagram depicts the process of addition of a new item within the library
system and generating an amount of fine whenever a user would not submit the item within the
assigned deadline of submission. The admin would firstly validate the record of the student and
issue a certain item to the student or staff. Upon completion of the transaction, a bill would be
generated to the user based on calculating the time period during which the book would be
submitted back to the library.
Whenever a student would check the present record of the student, they would be able to
check whether any amount of fine has been imposed upon them. Any amount of fine, if
applicable, would need to be paid by the student upon which admin would proceed with lending
an item to the student.

11SYSTEM ANALYSIS AND DESIGN OF QAHE
3.2 UML Sequence Diagram for updating Member Details
(Figure 4: UML Sequence Diagram for updating Member Details)
(Source: Created by author)