0% found this document useful (0 votes)
15 views2 pages

Spring 2025 - CS510 - 1

The document outlines the requirements for an Online Library Management System for a university, categorizing each requirement as Functional, Non-Functional, Domain, or Inverse. It includes various functionalities such as user login, book search, and report generation, as well as system performance metrics like availability and user capacity. The requirements also address compliance with university policies and user interface considerations.

Uploaded by

Sumaiya Ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views2 pages

Spring 2025 - CS510 - 1

The document outlines the requirements for an Online Library Management System for a university, categorizing each requirement as Functional, Non-Functional, Domain, or Inverse. It includes various functionalities such as user login, book search, and report generation, as well as system performance metrics like availability and user capacity. The requirements also address compliance with university policies and user interface considerations.

Uploaded by

Sumaiya Ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Cs510 Assignment 1

Bc230202794

Scenario
(15 Marks)

Consider an Online Library Management System for a university. The system allows students and faculty
to search for books, check their availability, reserve books, and check out/return books. Librarians can
add new books to the catalog, manage user accounts (students/faculty), track book status (checked out,
available, overdue), and generate reports on library usage. The system needs to handle a large volume of
books and users and integrate with the university's existing student/faculty database.
Keeping in view the above scenario and the major types of Software Requirements, identify and write in
the respective column whether each requirement is Functional Requirement, Non-Functional
Requirement, Domain Requirement, or Inverse Requirement.

Solution:

Sr. # Requirement Type


A user cannot check out a book if they have outstanding fines
1 Inverse Requirement
exceeding $10.
2 The system shall allow users (students and faculty) to log in. Functional Requirement
Users shall be able to search the book catalog by title, author, or
3 Functional Requirement
ISBN.
The system shall integrate with the university's LDAP for user
4 Domain Requirement
authentication.
Overdue fines shall be calculated at a rate of $0.25 per day per
5 Domain Requirement
book.
The system must be available 99.5% of the time during Non-Functional
6
university operating hours. Requirement
The system must update book availability status in real-time Non-Functional
7
after check-out/return. Requirement
8 Librarians must be able to add new book records to the database. Functional Requirement
The system shall provide a report on the most frequently
9 Functional Requirement
checked-out books.
10 The system must be able to handle at least 500 concurrent users Non-Functional
Sr. # Requirement Type
searching the catalog. Requirement
The system shall comply with university data privacy policies
11 Domain Requirement
for user information.
12 A student cannot reserve more than 3 books at a time. Inverse Requirement
13 Books classified as "Reference Only" cannot be checked out. Inverse Requirement
The user interface should be intuitive and easy to navigate for Non-Functional
14
first-time users. Requirement
The system must be accessible from standard web browsers Non-Functional
15
(Chrome, Firefox, Edge). Requirement

You might also like