Software Engineering Case Study - Software Requirements Specification for Digital Library Management System (SRS)

Software Requirements Specification for

Digital Library Management System

Library user account manage system

SRS-001: The system shall display the user account information including
user ID, last and first name, and user position, privilege.
SRS-002: The system shall use a graphic user interface which allows
librarians to choice actions including removing,
changing and adding user
account and account information

Logging

Within the system, logging will be used to provide a trail of transactions that
have taken place. This might either be for developer debugging purposes,
administrative checks on usage, or research on the usability of interfaces.
SRS-003. Transaction logs MUST be kept for each service provided.
SRS-004. Sufficiently detailed client session logs MUST be generated to
support analysis of user activities. Security and Privacy
SRS-005. The user’s password MUST never be exposed to compromise.
SRS-006 User session logs stored for usability and other research MUST be
anonymous.

Book download

SRS-007: When download e-book , the system shall show all the e-book
information and check particular user including:
• the first and last name of the user
•the library card number
•the library card expiring date
•to check valid user or not

A Digital Library System
• check e-book information
• the ISBN of the book
•the title of the book
•location(url)
SRS-008: When download the books, the system shall display the
information of the e-book which is just being downloaded including: ISBN, title.
Search book record

The system shall display a list of books which are matching the search
criteria sorted by book titles including:
•the category
•the ISBN
•the title
•the author
When required by users, the system shall display the information about a
particular-book including:
•the category
•the title
•the ISBN
•the publisher
the brief description of the book (if any stored in database) the location

Data Entry

The data entry requirements are concerned with how data is entered and
validated.

A Digital Library System

SRS-009: The system shall allow a user to enter his/her data via a keyboard
SRS-010: The system shall allow a user to enter his/her data via choose an
item via a mouse.
SRS-011: Whenever the "date" data is needed, it shall be entered only by
choose date from a online calendar.
SRS-012: The system shall allow the user to
enter
the library card number
and ISBN both by typing or scanning.
SRS-013: The system shall allow the user to enter book borrowing, recalling
data as frequently as required.
SRS-014: The system shall allow the user to attach notes to each account
SRS-015: The system shall allow the user to add or change information in an
account including: last name, first name, user ID, user position, user
privilege.
SRS-016: the system shall allow the user to delete an entire account.
Search book record
SRS-017: The system shall allow the user typing in search criteria
including book title, key word in title, ISBN, subject, category.
SRS-018: The system shall allow the user choose language option which the
searched book is used including English, Arabic
SRS-019: If the search result are a list of books, the system shall allow the
user to choose any one of them to see the details.
Update book database
SRS-020: The system shall allow the user to add or change the record
information including:
A Digital Library System
§the category
§the title
§the ISBN
§the publisher
§the brief description of the book
§the location in library
§the purchase date
§the price
SRS-021: the system shall allow the user to put "delete" for a existing e-
book and specify the deleting reason.

Report Generation

the report generation requirements are concerned with the report generation
capabilities of the Library system.
SRS-01: The system shall have a report feature that will allow the user to
generate a report showing the information of a particular patron.
SRS-02: The system shall have a report feature that will allow the user to
generate a report showing the information of book purchase information in a
period including the book titles, category, the author, the publisher, the
price. It also shall give statistic data about the total number of books
purchased, the money paid by category.
SRS-03: The system shall be generate those reports to the display, a file or a
printer which is linked to the system.

Design Constraints

SRS-040: The system shall be installed in a windows-NT network.

Security Requirements
SRS-04: The account management system shall only be used by
managers or users with defined privileges.
SRS-05: The Patron information report shall be generated by users who have
librarian account.
SRS-06: The book purchase report shall only be generated by managers or
users with defined privileges.
SRS-7: Database update data shall be committed to the database only after
the managers have approved.
Reliability

SRS-08: The system shall be recovered within 10 minutes if it is down.
SRS-09: The system shall be recovered without intervention at user terminal
if it is down.
SRS-010: The system shall show appropriate messages at terminal when
system is down.
SRS-011: The system shall have 99% reliability during library operating
hours.
SRS-012: Scheduled down time after library operating hours shall not be
more than 1 hour per day.
SRS-013: The system shall generate error messages when the user attempts
to enter invalid data.
3.1.8 Extensibility
SRS-014. System must be able to extend to store and deliver new content
media types.

A Digital Library System
SRS-015 System must be able to extend to support synchronization of
content
media based on shared work/item structure.
SRS-016. System MUST be able to extend to include music thesaurus in
later versions.
SRS-017. System MUST be able to extend support to MMTT components
built in later versions.
SRS-018
.
System MUST be able to extend to support data sharing between
records.
SRS-019System MUST be able to extend to support more sophisticated
bookmaking including additional context (e.g. size and configuration of
viewer) and book marking of other record types.

1 Comments