Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
The SRS serves multiple stakeholders, including developers, testers, and project managers, providing a comprehensive description of the ATM system's intended functions, interfaces, and constraints. It aims to facilitate understanding among all parties involved in the ATM's lifecycle, from design to deployment and maintenance.
Typology: Lab Reports
1 / 15
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.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.
2.3 User Classes and Characteristics Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the most important user classes for this product from those who are less important to satisfy. 2.4 Operating Environment Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist. 2.5 Design and Implementation Constraints Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software). 2.6 User Documentation List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards. 2.7 Assumptions and Dependencies List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).
3. External Interface Requirements 3.1 User Interfaces Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification. 3.2 Hardware Interfaces Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of
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.
Appendix C: To Be Determined List Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure. Sample for SRS (Library Management System)
1. Introduction 1.1 Purpose The main objective of this document is to illustrate the requirements of the project Library Management system. The document gives the detailed description of the both functional and non- functional requirements proposed by the client. The purpose of this project is to provide a friendly environment to maintain the details of books and library members. The main purpose of this project is to maintain easy circulation system using computers and to provide different reports. This project describes the hardware and software interface requirements using ER diagrams and UML diagrams. 1.2 Document Conventions Entire document should be justified. Convention for Main title Font face: Times New Roman Font style: Bold Font Size: 14 Convention for Sub title Font face: Times New Roman Font style: Bold Font Size: 12 Convention for body Font face: Times New Roman Font Size: 12 1.3 Scope of Development Project Library Management System is basically updating the manual library system into an internet- based application so that the users can know the details of their accounts, availability of books and maximum limit for borrowing. The project is specifically designed for the use of librarians and library users. The product will work as a complete user interface for library management process and library usage from ordinary users. Library Management System can be used by any existing or new library to manage its books and book borrowing, insertion and monitoring. It is especially useful for any educational institute where modifications in the content can be done easily according to requirements. The project can be easily implemented under various situations. We can add new features as and when we require, making reusability possible as there is flexibility in all the modules. The language used for developing the project is Java as it is quite advantageous than other languages in terms of performance, tools available, cross platform compatibility, libraries, cost (freely available), and development process. 1.4 Definition, Acronyms, Abbreviation JAVA platform independence
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
Add books and their information to the database Edit the information of existing books Can check the report of the existing books Can check the report of the issued books Can access all the accounts of the students The features that are available to the Members are:- Can view the different categories of books available in the Library Can view the List of books available in each category Can own an account in the library. Can view the books issued to him Can put a request for a new book Can view the history of books issued to him previously Can search for a particular book 2.4 Operating Environment The product will be operating in windows environment. The Library Management System is a website and shall operate in all famous browsers, for a model we are taking Microsoft Internet Explorer, Google Chrome, and Mozilla Firefox. Also it will be compatible with the IE 6.0. Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher version. The only requirement to use this online product would be the internet connection. The hardware configuration include Hard Disk: 40 GB, Monitor: 15” Color monitor, Keyboard: 122 keys. The basic input devices required are keyboard, mouse and output devices are monitor, printer etc. 2.5 Assumptions and Dependencies The assumptions are:- The coding should be error free The system should be user-friendly so that it is easy to use for the users The information of all users, books and libraries must be stored in a database that is accessible by the website The system should have more storage capacity and provide fast access to the database The system should provide search facility and support quick transactions The 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 The dependencies are:- The specific hardware and software due to which the product will be run On the basis of listing requirements and specification the project will be developed and run The end users (admin) should have proper understanding of the product The system should have the general report stored The information of all the users must be stored in a database that is accessible by the Library System
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.
The LMS should allow librarians to add, delete and modify items in database, and check availability of the items. The LMS should generate request’s reports for librarians every day, on base of which librarians could make decisions about acquiring or retirement the item The LMS should create notification and send to patrons by e-mail automatically after item’s overdue The LMS should provide to search, request and renew items either from the library computers (LMS application) or from outside the library through University site(web-based) though the Internet. The LMS should provide access to previous Access-based database, online databases
5. Nonfunctional Requirements 5.1 Performance Requirements 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 5.2 Safety Requirements 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. 5.3 Security 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 constraints Proper user authentication should be provided No one should be able to hack users’ password 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.
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
Appendix B: Glossary The following are the list of conventions and acronyms used in this document and the project as well: Administrator: A login id representing a user with user administration privileges to the software User: A general login id assigned to most users Client: Intended users for the software SQL: Structured Query Language; used to retrieve information from a database SQL Server: A server used to store data in an organized format Layer: Represents a section of the project User Interface Layer: The section of the assignment referring to what the user interacts with directly Application Logic Layer: The section of the assignment referring to the Web Server. This is where all computations are completed Data Storage Layer: The section of the assignment referring to where all data is recorded Use Case: A broad level diagram of the project showing a basic overview Class diagram: It is a type of static structure diagram that describes the structure of a system by showing the system’s cases, their attributes, and the relationships between the classes Interface: Something used to communicate across different mediums Unique Key: Used to differentiate entries in a database