Download Software Requirements Specification for Library Management System and more Lab Reports Software Engineering in PDF only on Docsity!
Analysis and identification of the suitable process models Aim: To prepare a Software Requirement Specification (SRS) document for the analysis and identification of the suitable process model for the applications. Procedure: Table of Contents Revision History
1. Introduction 1.1 Purpose 1.2 Document Conventions 1.3 Intended Audience and Reading Suggestions 1.4 Product Scope 1.5 References 2. Overall Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Classes and Characteristics 2.4 Operating Environment 2.5 Design and Implementation Constraints 2.6 User Documentation 2.7 Assumptions and Dependencies 3. External Interface Requirements 3.1 User Interfaces 3.2 Hardware Interfaces 3.3 Software Interfaces 3.4 Communications Interfaces 4. System Features 4.1 System Feature 1 4.2 System Feature 2 (and so on) 5. Other Nonfunctional Requirements 5.1 Performance Requirements 5.2 Safety Requirements 5.3 Security Requirements 5.4 Software Quality Attributes 5.5 Business Rules 6. Other Requirements Appendix A: Glossary Appendix B: Analysis Models Appendix C: To Be Determined List Revision History Name Date Reason For Changes Version
1. INTRODUCTION
1.1 Purpose Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem. 1.2 Document Conventions Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority. 1.3 Intended Audience and Reading Suggestions Describe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type. 1.4 Product Scope Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here. 1.5 References List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.
2. Overall Description 2.1 Product Perspective Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful. 2.2 Product Functions Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.
the data and control interactions between the software and the hardware, and communication protocols to be used. 3.3 Software Interfaces Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint. 3.4 Communications Interfaces Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.
4. System Features This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product. 4.1 System Feature 1 Don’t really say “System Feature 1.” State the feature name in just a few words. 4.1.1 Description and Priority Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9). 4.1.2 Stimulus/Response Sequences List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases. 4.1.3 Functional Requirements Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available. Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind. REQ-1: REQ-2:
System Feature 2 (and so on)
5. Other Nonfunctional Requirements 5.1 Performance Requirements If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features. 5.2 Safety Requirements Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied. 5.3 Security Requirements Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied. 5.4 Software Quality Attributes Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning. 5.5 Business Rules List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules. 5.6 Other Requirements Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project. Appendix A: Glossary Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS. Appendix B: Analysis Models Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.
SQL Structured query Language DFD Data Flow Diagram CFD Context Flow Diagram ER Entity Relationship IDE Integrated Development Environment SRS Software Requirement Specification LMS Library Management System 1.5 References Books Software Requirements and Specifications: A Lexicon of Practice, Principles and Prejudices (ACM Press) by Michael Jackson Software Requirements (Microsoft) Second Edition by Karl E. Wiegers Software Engineering: A Practitioner’s Approach Fifth Edition By Roger S. Pressman Websites http://www.slideshare.net/ http://ebookily.net/doc/srs-library-management-system
2. Overall Description 2.1 Product Perspective This is a broad level diagram of the project showing a basic overview. The users can be either staff or student. This System will provide a search functionality to facilitate the search of resources. This search will be based on various categories viz. book name or the ISBN.
Further the library staff personnel can add/update the resources and the resource users from the system. The users of the system can request issue/renew/return of books for which they would have to follow certain criteria 2.2 Product Functions The Online Library System provides online real time information about the books available in the Library and the user information. The main purpose of this project is to reduce the manual work. This software is capable of managing Book Issues, Returns, Calculating/Managing Fine, Generating various Reports for Record-Keeping according to end user requirements. The Librarian will act as the administrator to control members and manage books. The member’s status of issue/return is maintained in the library database. The member’s details can be fetched by the librarian from the database as and when required. The valid members are also allowed to view their account information. 2.3 User Classes and Characteristics The system provides different types of services based on the type of users [Member/Librarian]. The Librarian will be acting as the controller and he will have all the privileges of an administrator. The member can be either a student or staff of the university who will be accessing the Library online. The features that are available to the Librarian are:- A librarian can issue a book to the member. Can view the different categories of books available in the Library Can view the List of books available in each category Can take the book returned from students
Any update regarding the book from the library is to be recorded to the database and the data entered should be correct 2.6 Requirement Software Configuration:- This software package is developed using java as front end which is supported by sun micro system. Microsoft SQL Server as the back end to store the database. Operating System: Windows NT, windows 98, Windows XP Language: Java Runtime Environment, Net beans 7.0.1 (front end) Database: MS SQL Server (back end) Hardware Configuration:- Processor: Pentium(R)Dual-core CPU Hard Disk: 40GB RAM: 256 MB or more 2.7 Data Requirement The inputs consist of the query to the database and the output consists of the solutions for the query. The output also includes the user receiving the details of their accounts. In this project the inputs will be the queries as fired by the users like create an account, selecting books and putting into account. Now the output will be visible when the user requests the server to get details of their account in the form of time, date and which books are currently in the account.
3. External Interface Requirement 3.1 GUI The software provides good graphical interface for the user and the administrator can operate on the system, performing the required task such as create, update, viewing the details of the book. It allows user to view quick reports like Book Issued/Returned in between particular time. It provides stock verification and search facility based on different criteria. The user interface must be customizable by the administrator All the modules provided with the software must fit into this graphical user interface and accomplish to the standard defined The design should be simple and all the different interfaces should follow a standard template The user interface should be able to interact with the user management module and a part of the interface must be dedicated to the login/logout module Login Interface : In case the user is not yet registered, he can enter the details and register to create his account. Once his account is created he can ‘Login’ which asks the user to type his username and password. If the user entered either his username or password incorrectly then an error message appears. Search: The member or librarian can enter the type of book he is looking for and the title he is interested in, then he can search for the required book by entering the book name. Categories View : Categories view shows the categories of books available and provides ability to the librarian to add/edit or delete category from the list. Librarian’s Control Panel : This control panel will allow librarian to add/remove users; add, edit, or remove a resource. And manage lending options.
4. System Features 4.1 Scope of the work There are several motivations to order new computer-based University LMS: To modernize University Library database, where data was stored in a card-based catalog To optimize librarians’ work and time To join small Access-based database, where library has stored information about digital items (software, music) To expand services of library and patron’s possibilities To check ability of commercial using of library management systems. The LMS will allow remote access to library database via Internet only for patrons after authorization procedures. The patrons could search, renew items, send requests. The University LMS will provide remote access to other databases. 4.2 Scope of the product Features provided by the library management system: Store necessary information about items in the library: Author Item’s title Call number Year of publication Location in the library Number of copies Current status System will provide librarian to add, modify, and remove items to/from the library database, and check availability of the item. System will allow patron to get information about his/her status after authorization procedures: User name User address Student number Number and information about checked out items Requested items information Possibility to search and request items in the inter library loans, online databases through Internet. 4.3 Functional requirements Functional requirements are the following: The LMS should store all information about librarians and patrons, their access keys, priority and etc. The LMS allow searching items by author, title or keywords The LMS should support 500 patrons and 1000 requests/min simultaneously.
Appendices
Appendices
5.4 Requirement attributes 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. The project should be open source. 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
The user be able to easily download and install the system 5.5 Business Rules A business rule is anything that captures and implements business policies and practices. A rule can enforce business policy, make a decision, or infer new data from existing data. This includes the rules and regulations that the System users should abide by. This includes the cost of the project and the discount offers provided. The users should avoid illegal rules and protocols. Neither admin nor member should cross the rules and regulations. 5.6 User Requirement The users of the system are members and Librarian of the university who act as administrator to maintain the system. The members are assumed to have basic knowledge of the computers and internet browsing. The administrators of the system should have more knowledge of the internals of the system and is able to rectify the small problems that may arise due to disk crashes, power failures and other catastrophes to maintain the system. The proper user interface, user manual, online help and the guide to install and maintain the system must be sufficient to educate the users on how to use the system without any problems. The admin provides certain facilities to the users in the form of: Backup and Recovery Forgot Password Data migration i.e. whenever user registers for the first time then the data is stored in the server Data replication i.e. if the data is lost in one branch, it is still stored with the server Auto Recovery i.e. frequently auto saving the information Maintaining files i.e. File Organization The server must be maintained regularly and it has to be updated from time to time
6. Other Requirements 6.1 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. Appendix A : Appendix A: Admin, Abbreviation, Acronym, Assumptions; B: Books, Business rules; C: Class, Client, Conventions; D: Data requirement, Dependencies; G: GUI; K: Key; L: Library, Librarian; M:Member; N: Non-functional Requirement; O: Operating environment; P:Performance,Perspective,Purpose; R: Requirement, Requirement attributes; S: Safety, Scope, Security, System features; U: User, User class and characteristics, User requirement
pendix B
