Library Management System

Software Requirements Specification

Version 1.0

Student Id: MC06040151 Student Name: Azhar Hussain Supervisor Name:

0 2 3 Description Library Management System Library Management System Library Management System Author Mc060401541 MC060401541 MC060401541 .Revision History Date (dd/mm/yyyy) 23-Oct-2009 23-NOV-2009 30-DEC-209 Version 1.

.......................................................................................6 MEMBER....................................................................................................................................................................................................................12 Manage Article Permission............................................................................................................................................................................................................17 ......................................................................................................................................8 USER CASE DIAGRAM MAIN VIEW...........................13 Inquiry Issuance.....................................8 MEMBER.................................................................................................................................................................................................................................................................................................................................................13 Inquiry Article..................................................15 Check In Article.............................................................................................................................................................8 ACTORS.....................................................................................................................................................................................................................................................................................................................................................................................4 INTENDED AUDIENCE .....................................................................................................................16 Issue Member Ship...........................................7 Software interfaces..........................................................4 PROJECT SCOPE.................................................................10 Search Article.......................................................................................................................................7 NONE FUNCTIONAL REQUIREMENT...... Librarian.......................................................................................................................................4 FUNCTIONAL/NONE FUNCTION REQUIREMENTS............................................................................14 Inquiry members............................................................11 Check Account............................................................................................................................................................................................................9 USAGE SCENARIOS...................................10 Login..........................................................................................................................................................................................................................................................................................................................................................................................................................................8 LIBRARIAN DATABASE........................................................................................................................................................................................................................................................................................................................................................................................6 FUNCTION REQUIREMENT............6 THE LIBRARIAN...............................................................................................7 Software Quality Attributes.........................................................................10 Request Article......................................................................................11 Maintain inventory..................................................................................6 Asst................................................................................................7 Guest...............................7 Safety Requirements...........................................................................................................................................................................16 Inquiry waiting for approvals....................................................................7 Hardware Constraints..............................................................................................................................................................................................................................................................................7 Hardware Interfaces.......................12 Manage Member Permission...........................................................................................................................................................................................................8 GUEST...............................7 Security Requirements......................................................................................................................................................................................................................................15 Check Out Article...........................................................17 Request registration.............................PURPOSE ............................7 Software Constraints................

• Print the spine labels for the book. • Find what a specific person has borrowed from you. effort. It can satisfactorily cater to all the basic functions of a small library. Articles. The reader is assumed to have basic knowledge of LMS. Library Management system is a small footprint software suitable for personal / individual Libraries. testers . Knowledge and understanding of Unified Modeling Language (UML) diagrams is also re quired. Moreover we have limited staff resources. The document is intended for the customer and the developer (designers. these "work around" waste time. It offers the following modules Cataloguing. we find ourselves "making them works" by finding "ways to work around" system inadequacies. Managing the holdings manually is a not a simple job. author etc. There are few solutions but many a times. • Search if you have a specific book in your collection based on the title. Circulation. Bound volumes are substantial part of the holding. Project Reports. You can store the information about the books and other material and control the movement of the same. Circulation. Silent Features • Control the movement of books and other material and avoid loosing the same. Many solutions do not keep up with the technological changes and hence prove to be time wasters. and skills that should be spent on user services. Intended Audience The intended audience consists of • Software Project Managers • Software Engineers • Software Developers • Library Organizers Project Scope LMS is essentially meant of collections.Purpose This document describes the software requirements and specification (SRS) for LMS software. Queries . Overall Description Modern Libraries are not made up of just Books but CD ROM’s. maintainers). Accessioning and Housekeeping. It is a multi-user version and can take care of all the fundamental functions of a Library like Cataloguing.

DD. CDs. It supports various classification schemes like DDC. . It is a barcode and smart card enabled system and hence the issue and return of material is handled uniformly. The cataloguing module is based on AACR2 (Anglo American Cataloguing Rule Circulation Circulation module deals with issue and return of material from the Library. maps.Cataloguing .Salient Features You can create a catalogue of your books. You can issue member cards and also do the transactions. drawings and all similar collections using this module. and CC etc.

Inquiry Members Inquiry all current enrolled members to view their details 5. Update Article Any changes in articles should be updated in case of update 3. Add Article New entries must be entered in database 2.Functional/None Function Requirements This section gives the list of Functional and non functional requirements that are applicable to the Library Management system Function Requirement The Librarian 1. Inquiry Issuance Inquiry all database articles 6. Delete Article Wrong entry must be removed from system 4. Check out Article To issue any article must be checked out 7. also enabling/disabling of user permission can be set through this use case MEMBER 1. Authentication User must authenticated before accessing system 2. Search Article User can search any article 3. Inquiry waiting for approvals Librarian will generates all newly application which is in waiting list 9. Check Account This use case is used to check account details . it can be pledged 10. Request Article After successful searching member mark this book as requested article 4. Set user Permission From this user case Librarian can give permission categorically. Reserve Article This use case is used to reserve any book with the name of librarian. Check In article After receiving any article system will reenter article by Checking 8.

all other users other than library staff only have the rights to retrieve the information about database. delete.There are different categories of users namely teaching staff. append 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. Librarian Prepare Library database All data base must be prepared Guest 1. The availability of these tools will be governed by Hardware Interfaces Server Operating System: Windows Processor: Pentium 4. The database should have backup capabilities. Software Constraints The development of the system will be constrained by the availability of required software such as database and development tools. Therefore. Register user User must full fill all application form for registration NONE Functional Requirement Safety Requirements The database may get crashed at any certain time due to virus or operating system failure. library staff .Asst. administrator. Software Quality Attributes 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 Hardware Constraints The system requires a database in order to store persistent data.0 GHz or higher RAM: 1GB Mb or more Hard Drive: 80 GB or more ..students etc.. it is required to take the database backup Security Requirements We are going to develop a secured database for the university .

Processor: Pentium III or 2. RAM: 512 Mb or more Software interfaces Oracle database 8i or 10g Developer 2000 USECASE Actors • • • • Librarian Member Guest Asst. LIBRARIAN DATABASE You can say this as an assistant librarian. Librarian ACTORS The actors which are participating in the case are 4 namely LIBRARIAN The one who manages the library and its database and rapidly keeps on updating the students or people records for issuing books and etc.0 GHz or higher.Client Operating System: Windows. . MEMBER Library has registered members who is authorized to issue articles from library GUEST A guest who doesn’t have the membership of the library comes to it and wants to have membership.

Request Article .Search Article 9.Approve user Registration 5.Login 14.Maintain Inventory Guest «uses» 6 Manange Member Permission 13.Librarian 12. Check out article «extends» 3. Issue MemberShip 7 Manage Articles Permission 4.request registration Asst. Inquiry Issuances 2.User Case Diagram Main View Library Management System 1. Inquiry Members «extends» Librarian 11 Check In Article 12.Inquiry Articles Member 10.CheckAccount 8.

With this search companion.Modification history: Date 30-dec-2009 7. publisher etc.Usage Scenarios 1.Author: Azhar Hussain Project ID LMS 1.Post Conditions: System transfer control to user main screen to proceed further actions 5. User Fill in required information a. It also defines the actions a user can perform in LMS. For example.2. type.Abbreviated Title Login 3.1 6.Pre Conditions: User must be login 5. Asst.Actors Member 5.2.Use Case Title Search Article 2.Task Sequence . If in step 3 no user found then system display Invalid user name password error message and transfer control to Task Sequence no.3.2.Description Search article makes it easy to search for article on LMS.1. Members.1.Pre Conditions: User must have proper client installed on user terminal 5.Actors Librarian .Use Case Id 1 4. 5.Task Sequence 1. Use Case Title Login 2.Abbreviated Title Search Article 3.Description To interact with the system. user can specify several search criteria. 5. author name. Librarian 5.Exception 1. LMS will validate its registration with this system. System acknowledge entry 5. Enter user name and password 3. System show Login Screen 2. article name.Use Case Id 2 4.

Exception 1. User enter required information a. book description ISBN etc 3.Modification history: Date 30-dec-2009 7. (request Article) 6. User can view his desire results 2. System will show searching screen 2. Article will be added to user requested list and LMS reserved list 5. 5.2. 5.Use Case Id 3 4.Task Sequence 1.Description Check Account Check Account 4 Member .Use Case Title 2. If in step 3 at same time some other user reserved this article this user will get message of temporary reserved 6.1.1. User select his desire article to request for reservation 2.Abbreviated Title 3. By pressing search button system will list down all searching results 5.Description Request Article is process from which user can request any available article.Use Case Title Request Article 2. System will reserved article for current user.Pre Conditions: Member must be logged on 5.Actors Member 5.Author: Azhar Hussain Project ID LMS 1.Abbreviated Title Request Article 3.3. User can also request article to reserve for this check use case 3.Post Conditions: 1.Modification history: Date 30-dec-2009 7.Post Conditions: 1. It can be user name.3.Actors 5.Use Case Id 4.4.Author: Azhar Hussain Project ID LMS 1.

4 Exception There are many condition arises while maintaining inventory. It cannot be described here 6.Use Case Id 5 4.2.1.3.Task Sequence 1.3. User will be on member status screen 5.Modification history: Date 30-dec-2009 7.Pre Conditions: User must be login with its librarian account 5.Abbreviated Title 3.Pre Conditions: User must be login to the system 5.Actors Librarian 5.Use Case Title 2.Use Case Title Maintain inventory 2.1.Author: Azhar Hussain Project ID LMS 1. On this screen librarian can add. System will open Inventory main form 2.2.4 Exception No exception case 6.System will show member current issued articles.Author: Azhar Hussain Project ID LMS 1.Description From this use case system will maintain inventory 5. System will display all user history 5.Task Sequence 1. update or delete new items to inventory 5.Use Case Id Manage Member Permission Manage Member Permission 6 .Modification history: Date 30-dec-2009 7.Post Conditions: 1. transaction history and their deadlines 5.Abbreviated Title Maintain inventory 3.Post Conditions: System can have updated system inventory position 5.

Author: Azhar Hussain Project ID LMS 1.Task Sequence 1. 3. System show all users registered with LMS 2.Post Conditions: Article will be restricted or granted 6. User can grant or revoke any securities from this screen 5.Modification history: Date 30-dec-2009 7.1.2.Description This use case is used to set permissions on some Articles like reserved. 5.Modification history: Date 30-dec-2009 7. system will list down all assigned and unassigned permission of current user.Use Case Title Manage Article Permission 2. 3.Pre Conditions: Member must be logged on with librarian account 5.2.Actors Librarian 5.Task Sequence 1. Librarian can grant or revoke any securities from this screen 5. for internal use only or blocked due to any reason.Post Conditions: Member will be restricted or granted permission 6.Use Case Title Inquiry Issuance .3.Description From this user case Librarian can manage user permissions 5.4.Author: Azhar Hussain Project ID LMS 1. system will list down all assigned and unassigned permissions of current article. System show all articles entered in LMS 2.1. Librarian will select any user.3.Actors Librarian 5.Use Case Id 7 4.Abbreviated Title Manage Article Permission 3. User will select any article.Pre Conditions: Member must be logged 5.

Task Sequence 1. User enter required information 2.1.Abbreviated Title Inquiry Issuance 3. 5. This searching criterion is Article type. 5.Pre Conditions: Member must be logged on with librarian account.Use Case Id 9 4. 3. On pressing inquiry button system will display all resulting data according to criterion given 5.2. User will get all the information of article in LMS .Modification history: Date 30-dec-2009 7.Use Case Title Inquiry Article 2. Article or its issuance or completion date etc. User required criteria can be input on this system a. current status etc.2.Actors Librarian 5. Inquiry Article inquiry is used to inquiry all articles in a system.Post Conditions: 1.Description Articles have different details.Task Sequence 1.Abbreviated Title Inquiry Article 3. code etc By pressing search button system will list down all searching results 5. Label.Use Case Id 8 4.Post Conditions: 1.3. It can be author name. System will display issuance Inquiry form 2.Author: Azhar Hussain Project ID LMS 1.Description This use case is used to inquiry all the issued article by LMS.Actors Librarian 5.3. book description ISBN . Librarian can view issuance and made different decision 6.Pre Conditions: System must be logon to the system 5. 5. It also give details of its transaction history.1.2.

It can be member name.Actors Librarian 5.Description When any member is returning back article then Check in article is the process from which librarian can enter its issue return of article.3.Task Sequence .Use Case Title Inquiry members 2. or other member relevant information etc By pressing search button system will list down all searching results 5.Use Case Title Check In Article 2. current status. 5. Librarian will get all information from user 6.6. System will show Inquiry screen 2.1. User enter required information 3.Abbreviated Title Inquiry members 3.Post Conditions: 1.Pre Conditions: System must be logon to the system 5.Author: Azhar Hussain Project ID LMS 1.1.Modification history: Date 30-dec-2009 7.Actors Librarian 5.2.Pre Conditions: Member must be logged On 5.Modification history: Date 30-dec-2009 7.Use Case Id 11 4.Use Case Id 10 4.Author: Azhar Hussain Project ID LMS 1.Task Sequence 1.Abbreviated Title Check In Article 3.Description This use case is used to inquiry any users exist in LMS.2. 5. Librarian can also view their transaction history.

Actors Librarian 5.Description This use case is used to issue article to member 5.Actors Librarian 5.Use Case Title Inquiry waiting for approvals 2. System will mark this article as checked out article 5.3.Post Conditions: Article will be booked till checked in 6.Task Sequence 1.Abbreviated Title Inquiry waiting for approvals 3.Pre Conditions: User must be logon .1. System will mark this article as checked in article 5.Description Librarian can inquiry all new registration which are not entertained earlier 5.Post Conditions: Article will be available for any other issuance 6. User enters article and member code 3.Modification history: Date 30-dec-2009 7.Author: Azhar Hussain Project ID LMS 1.Pre Conditions: System must be logon to the system 5.3.2.Modification history: Date 30-dec-2009 7.1.Author: Azhar Hussain Project ID LMS 1.1. Librarian will enter article code and member code 2.Use Case Id 13 4.Use Case Title Check Out Article 2.Use Case Id 12 4. System display articles available for check out 2.Abbreviated Title Check Out Article 3.

Task Sequence 1.Abbreviated Title Request registration 3. User enters applicant code to register 2.2.Actors Librarian 5.3.Description To register applicants system will issue membership 5.Post Conditions: Application will become register user and removed from waiting for approval list 6.Author: Azhar Hussain Project ID LMS 1. System issue new membership number to applicant 5.Use Case Id 14 4.Pre Conditions: User must be logged on 5.Use Case Title Request registration 2. System will display all the results which are in waiting list 2.Abbreviated Title Issue membership 3.Modification history: Date 30-dec-2009 7. User select any applicant and request to register 3.Actors Librarian 5.3.1.Task Sequence 1.Use Case Title Issue Member Ship 2.Post Conditions: Application will become register user and removed from waiting for approval list 6. System transfer this application to registered members 3.2.Use Case Id 15 4.Modification history: Date 7.5.Description All new persons who want to register use this USECASE . System will register application as register user and give register code include (Issue membership) 5.Author: Project ID 1.

5.3.1.Modification history: Date 30-dec-2009 7. User enters his basic information 3.Pre Conditions: User must have valid client installed machines 5.Post Conditions: Applicant will be available in waiting for approval list 6. System will issue applicant number 5.2. System displays user registration form 2.Task Sequence 1.Author: Azhar Hussain Project ID LMS .

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.