Scribd
Upload
92 views5 pages

Software Design Lab 2 (19132020)

The document outlines the requirements for a library management software system. It describes features to ensure user account security such as user authentication, administrator monitoring, and limiting member access. It also lists functional requirements for administrators to manage books and user accounts, and for users to search for books, view issue records, and register. External interface requirements include a graphical user interface, hardware specifications, supported programming languages, and communication through windows. Non-functional requirements address system performance, data backup/recovery, security, and software quality attributes. The document also describes data categories for different user and book types.

Uploaded by

Rohan
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
92 views5 pages

Software Design Lab 2 (19132020)

The document outlines the requirements for a library management software system. It describes features to ensure user account security such as user authentication, administrator monitoring, and limiting member access. It also lists functional requirements for administrators to manage books and user accounts, and for users to search for books, view issue records, and register. External interface requirements include a graphical user interface, hardware specifications, supported programming languages, and communication through windows. Non-functional requirements address system performance, data backup/recovery, security, and software quality attributes. The document also describes data categories for different user and book types.

Uploaded by

Rohan
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
You are on page 1/ 5

Software Design

Lab
Rohan.B
19132020

Step 3 :
System Features
The users of the system should be provided the surety that their
account is secure. This is possible by providing:
1.User authentication and validation of members using their unique
member ID
2. Proper monitoring by the administrator which includes updating
account status, showing a popup if the member attempts to issue
number of books that exceed the limit provided by the library policy,
assigning fine to members who skip the date of return
3. Proper accountability which includes not allowing a member to see
other member’s account. Only administrator will see and manage all
member accounts
1.Description and priority:
The planned Library Management Scheme would take care of the
specifics of the latest book at any moment. The book dilemma, book
return, would immediately update the new book information so that
the user will have the latest book details updated.
2.Stimulus response:
The responses section describes all of the outputs that are the result of
processing done in the specification unit. Each response is composed
of a destination name and a message type. The events are grouped
under local names, such that each group of responses is generated in
the same way in the requirements section of the specification unit.
3.Functional Requirements :
Administrator Menu:
In this module we can do the following:
 Admin should be able to insert, modify and delete books.
 Can accept or reject a new user according to the library policy.
 Can get the information of any member who has borrowed a
book.
 Add and edit book categories and arrange books by categories. 
 Can record books returned by users.
Book entry: 
In this module we can enter a new book and store it.
Book issue:
In this module we can issue a book to the student.
Book record:
In this module we can keep the records of various booksbeing issued 
and returned.
Register student
: In this module we can keep the record of how manystudents have we 
registered

Step 4:
EXTERNAL INTERFACES REQUIREMENTS
User Interface:
The program offers a decent graphical interface for the user that can
be run on the device by an administrator, performing the necessary
tasks such as designing, reviewing, displaying the book information.
 Allows users to access quick reports in between real hours,
such as Book Issues/Returned, etc.
 Based on various requirements, stock verification, and search
service.

Hardware interface:
• Operating system: window
• Hard disk:40 GB
• RAM: 256 MB
• Processor: Pentium(R)Dual-core CPU

Software interface :

  Java language
 Net beans IDE 7.0.1
 MS SQL server 2005

 Communication interface: Window

Non-functional Requirements :
Performance Requirement:
The proposed system that we are going to develop will be used as the
Chief performance system within the different campuses of the
university which interacts with the university staff and students.
Therefore, it is expected that the database would perform functionally
all the requirements that are specified by the university. The
performance of the system should be fast and accurate . Library
Management System shall handle expected and non-expected errors
in ways that prevent loss in information and long downtime period.
Thus it should have inbuilt error testing to identify invalid
username/password .The system should be able to handle large
amount of data. Thus it should accommodate high number of books
and users without any fault.
Safety Requirement Department of Information Technology:
The database may get crashed at any certain time due to virus or
operating system failure. Therefore, it is required to take the database
backup so that the database is not lost. Proper UPS/inverter facility
should be there in case of power supply failure.
Security Requirement
1. System will use secured database
2. Normal users can just read information but they cannot edit or
modify anything except their personal and some other
information.
3. System will have different types of users and every user has
access constraints. Proper user authentication should be
provided
4. No one should be able to hack users’ password
5. There should be separate accounts for admin and members such
that no member can access the database and only admin has the
rights to update the database.
Software quality attributes:
1. There may be multiple admins creating the project, all
of them will have the right to create changes to the
system. But the members or other users cannot do
changes
2. The project should be open source
3. The Quality of the database is maintained in such a
way so that it can be very user friendly to all the users
of the database
4. The user be able to easily download and install the
system 
Other Requirements
Data and Category Requirement:
There are different categories of users namely teaching staff,
Librarian, Admin, students etc. Depending upon the category of user
the access rights are decided.It means if the user is an administrator
then he can be able to modify the data,delete, append etc. All other
users except the Librarian only have the rights to retrieve the
information about database. Similarly there will be different
categories of books available. According to the categories of books
their relevant data should be displayed. The categories and the data
related to each category should be coded in the particular format.

You might also like