Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Software requirements specification

78,096 views

Published on

  • Real Ways To Make Money, Most online opportunities are nothing but total scams! ★★★ http://ishbv.com/ezpayjobs/pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • thanks
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • We hired An Indian software company- commediait.com for our management software project so they asked for SRS document, I got help from your ppt. thanks for sharing.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • mast hai. kaam aasan ker diya
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Software requirements specification

  1. 1. SoftwareRequirementsSpecificationLIBRARY MANAGEMENT SYSTEM By Reddy Harish(10MSE0015) Kishore Majety(10MSE0030) Krishnasai Gudavalli(10MSE0263)Slot-C1
  2. 2. TABLE OF CONTENTS1. Introduction1.1 Purpose1.2 Scope1.3 Intended Audience Definitions, acronyms and abbreviations2. Overall Description2.1 Product Perspective2.2 Product Functions2.3 Operating Environment2.4 User Characteristics2.5 Design and Implementation Constraints2.6 Assumptions and Dependencies3. External Interfaces Requirements 3.1 User Interfaces 3.2 Hardware Interfaces 3.3 Software Interfaces4. Functional Requirements5.Behaviorial Requirements6. Non-Functional RequirementsLibrary Management System SRS Document By Harish-Kishore-Krishnasai
  3. 3. 1. Introduction1.1 PurposeThe purpose of this document is to describe the LibraryManagement System . This document contains the functional,behavioral and non-functional requirements of the project and italso contains the guidelines for system engineers and designersto start working the project.1.2 ScopeLibrary Management System is basically updating the manuallibrary system into a internet-based application so that the userscan know the details of their accounts, availability of books andremaining time for borrowing.The project is specifically designed for the use of librarians andlibrary users. The product will work as a complete user interfacefor library management process and library usage from ordinaryusers. Library Management System can be used by any existingor new library to manage its books and book borrowing,insertion and monitoring .1.3 Audience Definitions, Acronyms andAbbreviations1.3.1 Audience DefinitionsThe intended readers of this document are the developers of thesite, testers, library owners and managers and coordinators.Any suggested changes on the requirements listed on thisdocument should be included in the last version of it so it can bea reference to developing and validating teams.Library Management System SRS Document By Harish-Kishore-Krishnasai
  4. 4. 1.3.2 Acronyms and MeaningAbbreviations AcronymMS SQL Microsoft Structured Query LanguageASP Active Server PagesISBN International Standard Book NumberIEEE Institute of Electrical and Electronics Engineers 1.4 References IEEE 830-1998 standard for writing SRS document. I Sommerville, Software Engineering, 8th ed, Addison- Wesley, 2007. 2. Overall Description 2.1 Product Perspective Library Management System SRS Document By Harish-Kishore-Krishnasai
  5. 5. Library Management System is a replacement for the ordinarylibrary management systems which depend on paper work forrecording book and users information.2.2 Product Functions2.2.1 Administrators  Admin should be able to insert, modify and delete books.  Can accept or reject a new user according to the library policy or payment methods.  Increase the period for borrowing a book for specific type or group of users.  Can get the information (status report) of any member who has borrowed a book.  Add and edit book categories and arrange books by categories.  Add and edit authors and publishers information.  Can send lateness warnings to people who have exceeded deadline date.  Can record books returned by users.Library Management System SRS Document By Harish-Kishore-Krishnasai
  6. 6. 2.2.2 Normal Users (Library Members)  The member should be provided with the updated information about the books catalog.  Members are given a access to check their account’s information and change it.  Members have the ability to search through books by subject, title, authors or any information related to the book.  Can extend the period of borrowing books according to the library policy.  The customer may suggest a book to be brought to the library book collection.2.3 Operating EnvironmentThe Library Management System is a website and shall operatein all famous browsers, for a model we are taking MicrosoftInternet Explorer ,Google Chrome,Mozilla Firefox with FlashPlayer and JavaScript.2.4 User CharacteristicsUsers of this Library Management System are members,librarians and the administrators who maintain the website.Members and librarians are assumed to have basic knowledge ofcomputers and Internet browsing. Administrators of the systemshould have more knowledge of internal modules of the systemand are able to rectify small problems that may arise due to diskcrashes, power failures and other catastrophes.Library Management System SRS Document By Harish-Kishore-Krishnasai
  7. 7. 2.5 Design and Implementation Constraints  The information of all users, books and libraries must be stored in a database that is accessible by the website.  MS SQL Server will be used as SQL engine and database.  The Online Library System is running 24 hours a day.  Users may access from any computer that has Internet browsing capabilities and an Internet connection.  Users must have their correct usernames and passwords to enter into their online accounts and do actions.2.6 Assumptions and Dependencies  The product needs the following third party products.  Microsoft SQL server to store the database.  ASP.net to develop the Product.Library Management System SRS Document By Harish-Kishore-Krishnasai
  8. 8. 3. External Interfaces Requirements3.1 User InterfacesLogin Interface :In case the user is not registered yet, he can enter the details andregister.Which asks the user to type his username and password .If the user entered either his username or password incorrectlythen an error message occurs. Search :The member or librarian can enter the type of book he is lookingfor and the title he isinterested in them ,then he can search forthe required book by entering the book name. Categories view :Categories view shows the books categories view with ability toLiberian to add/edit or delete category from the list. Librarian’s Control PanelThis control panel will allow librarians to add, confirm, orremove users; add, edit, orremove a medium. And managelending options.3.2 Hardware InterfacesLibrary Management System SRS Document By Harish-Kishore-Krishnasai
  9. 9. Only the recommended configuration (basic requirements of acomputer system ) no other specific hardware is required to runthe software.3.3 Software Interfaces  Browser to load and view the web pages  Operating System4.Functional Requirements4.1.1 Librarian:Insert book:This action is done to add new book to library book collectionDelete / modify book :This event is to delete an existing book or modify itsinformation.Delete member:Admin can delete a member due to some specific rules.Return book:Admin should confirm the return of books borrowed by users4.1.2 Normal User :Library Management System SRS Document By Harish-Kishore-Krishnasai
  10. 10. Register: When new user enters for the first time then he has toregisterExtending borrowing deadline : Member can extend the borrowing time to some limitdecided by Admin4.1.3 Common Functions :Login: Both Admin and members must be logged in beforethey modify any informationSearch for book : When user or admin wants to search on some book byname, author or subject etc.5.Behaviroal RequirementsLibrary Management System SRS Document By Harish-Kishore-Krishnasai
  11. 11. Use case diagram:Library Management System SRS Document By Harish-Kishore-Krishnasai
  12. 12. 6. Non-functional RequirementsError handling  Library Management System shall handle expected and non-expected errors in ways that prevent loss in information and long downtime period.Performance Requirements  The system shall accommodate high number of books and users without any fault.Safety Requirements  System use shall not cause any harm to human usersSecurity Requirements  System will use secured database  Normal users can just read information but they cannot edit or modify anything except their personal and some other information.  System will have different types of users and every user has access constraintsLibrary Management System SRS Document By Harish-Kishore-Krishnasai

×