...Management System Software Requirements Specification Document Prepared by Team 1 Version: (1.1) Date: (02/11/2002) Table of Contents 1 Introduction 4 1.1 Purpose 4 1.2 Scope 4 1.3 Definitions, Acronyms, and Abbreviations. 5 1.4 Overview 5 2 The Overall Description 5 2.1 Product Perspective 5 2.1.1 Hardware Interfaces 5 2.1.2 Software Interfaces 5 2.2 Product Functions 5 2.3 User Characteristics 6 2.4 Apportioning of Requirements. 6 2.5 Assumptions and Dependencies 6 3 Specific Requirements 7 3.1 External Interfaces 7 3.1.1 User Interfaces 7 3.1.2 Software Interfaces 7 3.1.3 Hardware Interfaces 7 3.1.4 Communication Interfaces 8 3.2 Functional Requirements 8 3.3 Nonfunctional Requirements 100 3.3.1 Performance Requirements 100 3.3.2 Logical Database Requirements 100 3.3.3 Design Constraints 111 3.3.4 Standards Compliance 111 3.3.5 Reliability 111 3.3.6 Availability 111 3.3.7 Security 111 3.3.8 Maintainability 11 3.3.9 Portability 111 4 Change Management Process 122 5 Document Approvals 122 5.1 Team One Approval 122 5.2 Team Two Approval 122 6 Supporting Information 122 Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS. 1 Purpose The Software Requirements...
Words: 2464 - Pages: 10
...SCATS SALES AND CUSTOMER TRACKING SYSTEM Software Requirements Specification VERSION: FINAL 1.0 CONTENTS 1. INTRODUCTION 3 1.1 Purpose 3 1.2 Scope 3 1.3 Definitions, Acronyms, and Abbreviations 3 1.4 References 3 1.5 Overview 3 2. Overall Description 4 2.1 Product Perspective 4 2.1.1 User Interfaces 4 2.2 Product Functions 4 2.3 User Characteristics 4 2.4 Assumptions and Dependencies 4 2.5 Apportioning of Requirements 4 3. User requirement definition 5 4. System architecture 5 5. System requirements specification 5 5.1 Use Case Diagram for SCATS 5 5.2 Specification of actors 6 5.2.1 Customer 7 5.2.2 Sales Manager 7 5.2.3 Sales Person 7 5.3 Specification of Use Cases 8 5.3.1 Use Case 1. Employee Registration 8 5.3.2 Use Case 2. Product Registration 8 5.3.3 Use Case 3. Sales Registration 9 5.3.4 Use Case 4. Customer Registration 10 5.3.5 Use Case 5. SystemLogin 10 5.3.6 Use Case 6. Update Information 11 5.3.7 Use Case 7. System Output 12 5.4 External Interface Requirements 14 5.5 Performance Requirements 14 5.6 Design Constraints 14 5.7 Software System Attributes 14 5.7.1 Security 14 5.7.2 Maintainability 14 5.7.3 Portability 15 6. System models 15 7. System evolution 15 8. Appendices 16 Introduction 1 Purpose The purpose of this System Requirement Specification document is to describe the system services and constraints...
Words: 2711 - Pages: 11
...E-Store Project Software Requirements Specification Version Revision History |Date |Version |Description |Author | | | |SRS 1.0 |Group-1 | | | |SRS 2.0 |Group-1 | | | |SRS 3.0 |Group-1 | | | |SRS 4.0 |Group-1 | Table of Contents 1. Introduction 5 1.1 Purpose 5 1.2 Scope 5 1.3 Definitions, Acronyms, and Abbreviations 6 1.4 References 6 1.5 Overview 6 2. Overall Description 6 3. Specific Requirements 7 3.1 Functionality 7 3.1.1 Sell Configured to Ordered Products. 7 3.1.2 Provide comprehensive product details. 7 3.1.3 Detailed product Categorizations 7 3.1.4 Provide Search facility. 7 3.1.5 Maintain customer profile. 8 3.1.6 Provide personalized profile 8 3.1.7 Provide Customer Support. 8 3.1.8 Email confirmation. 9 3.1.9 Detailed invoice for customer. 9 3.1.10 Provide shopping cart facility. 9 3.1.11 Provide multiple shipping...
Words: 2870 - Pages: 12
...Management System Software Requirements Specification Document Prepared by Team 1 Version: (1.1) Date: (02/11/2002) Table of Contents 1 Introduction 4 1.1 Purpose 4 1.2 Scope 4 1.3 Definitions, Acronyms, and Abbreviations. 5 1.4 Overview 5 2 The Overall Description 5 2.1 Product Perspective 5 2.1.1 Hardware Interfaces 5 2.1.2 Software Interfaces 5 2.2 Product Functions 5 2.3 User Characteristics 6 2.4 Apportioning of Requirements. 6 2.5 Assumptions and Dependencies 6 3 Specific Requirements 7 3.1 External Interfaces 7 3.1.1 User Interfaces 7 3.1.2 Software Interfaces 7 3.1.3 Hardware Interfaces 7 3.1.4 Communication Interfaces 8 3.2 Functional Requirements 8 3.3 Nonfunctional Requirements 100 3.3.1 Performance Requirements 100 3.3.2 Logical Database Requirements 100 3.3.3 Design Constraints 111 3.3.4 Standards Compliance 111 3.3.5 Reliability 111 3.3.6 Availability 111 3.3.7 Security 111 3.3.8 Maintainability 11 3.3.9 Portability 111 4 Change Management Process 122 5 Document Approvals 122 5.1 Team One Approval 122 5.2 Team Two Approval 122 6 Supporting Information 122 Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS. 1 Purpose The Software Requirements...
Words: 2464 - Pages: 10
...Software Requirements Specification (SRS) System requirements are expressed in a software requirement document. The Software Requirement Specification (SRS) is the official statement of what is required of the system developers. This requirement document includes the requirements definition and the requirement specification. The software requirement document is not a design document. It should set out what the system should do without specifying how it should be done. The requirement set out in this document is complete and consistent. USER REQUIREMENTS In this system we find the operations depending on the Different end users. Functionality are listed below: Administrator: 1. Admin is the only user who can log in to the system, who has privileged access to the whole database. 2. He can view, modify or delete any kind of data 3. He can generate various periodic reports with regard to the whole database. 4. A unique password is given to the admin which can be used for availing the privileged access. 5. He can maintain the details of each branch’s details including warden’s and student’s details Student: 1. Student can view their information regarding fees, room and mess information. 2. Student can check the fine of them . 3. Student can pay the fine. 4. Students are also provided with user name and password for more security. Mess Manager: 1. The mess manager can see the data of the students. 2. The mess manager can...
Words: 710 - Pages: 3
...Operating Environment 3 2.5 Design and Implementation Constraints 3 2.6 User Documentation 3 2.7 Assumptions and Dependencies 3 3. External Interface Requirements 3 3.1 User Interfaces 3 3.2 Hardware Interfaces 3 3.3 Software Interfaces 4 3.4 Communications Interfaces 4 4. System Features 4 4.1 System Feature 4 5. Other Nonfunctional Requirements 4 5.1 Performance Requirements 4 5.2 Safety Requirements 5 5.3 Security Requirements 5 5.4 Software Quality Attributes 5 6. Project Plan 5 6.1 Team Members 5 Introduction 1 Purpose The software described in this document is the http://www.sdbct.ac.in/ website and associated support pages. This document seeks to provide the Software Requirements Specifications for the College Website. The purpose of this document is to record the requirements for the design and development of College Website. Rev1 of the website was created on or about summer of 2006. This document describes requirements for Rev2, summer of 2010. There may be a need for future updates of the website. The document reflects the current requirements of the project as understood by the project team. This document presents an initial description of the various functionalities and services provided by the software. The document will also serve the basis for acceptance testing by the user. The scope of the website is not only limited to attracting and encouraging high school students to take coursework at Sushila Devi Bansal College of Technology...
Words: 1254 - Pages: 6
...E-Store Project Software Requirements Specification Version Revision History |Date |Version |Description |Author | | | |SRS 1.0 |Group-1 | | | |SRS 2.0 |Group-1 | | | |SRS 3.0 |Group-1 | | | |SRS 4.0 |Group-1 | Table of Contents 1. Introduction 5 1.1 Purpose 5 1.2 Scope 5 1.3 Definitions, Acronyms, and Abbreviations 6 1.4 References 6 1.5 Overview 6 2. Overall Description 6 3. Specific Requirements 7 3.1 Functionality 7 3.1.1 Sell Configured to Ordered Products. 7 3.1.2 Provide comprehensive product details. 7 3.1.3 Detailed product Categorizations 7 3.1.4 Provide Search facility. 7 3.1.5 Maintain customer profile. 8 3.1.6 Provide personalized profile 8 3.1.7 Provide Customer Support. 8 3.1.8 Email confirmation. 9 3.1.9 Detailed invoice for customer. 9 3.1.10 Provide shopping cart facility. 9 3.1.11 Provide multiple shipping...
Words: 2870 - Pages: 12
...FERSOFT ONLINE BUS TICKET RESERVATION SYSTEM (OBTRS) SRS Document Revision #: v1.0 Date of Issue: 15 January 2008 Project Manager: Seçil AYDIN Software Requirements Specification OBTRS Approval Signatures Approved by: Business Project Leader Approved by: IM/IT Project Leader Prepared by: Business Project Manager Prepared by: IM/IT Project Manager Reviewed by: Quality Assurance Manager v1.0 16/01/2008 Page i Software Requirements Specification OBTRS TABLE OF CONTENTS 1. INTRODUCTION .............................................................................................. 6 1.1 .. PURPOSE .................................................................................................................. 6 1.2 .. SCOPE ....................................................................................................................... 6 1.3 .. DEFINITIONS, ACRONYMS AND ABBREVIATIONS .................................................. 7 1.4 .. REFERENCES............................................................................................................ 8 1.5 .. OVERVIEW................................................................................................................. 9 2. OVERALL DESCRIPTION ............................................................................. 10 2.1 PRODUCT PERSPECTIVE ......................................................................................... 10 2.1.1 SYSTEM...
Words: 5433 - Pages: 22
... | | | | | | | |Software Engineering | |MedPulse | |Software Requirements Specification | | | |...
Words: 3076 - Pages: 13
...CHAPTER-2 SYSTEMS REQUIREMENTS SPECIFICATION Software Requirement Specifications A software requirement specification is a document which is used as a communication medium between the customer and the supplier. When the software requirement specification is completed and is accepted by all parties, the end of the requirements engineering phase has been reached. This is not to say, that after the acceptance phase, any of the requirements cannot be changed, but the changes must be tightly controlled. The software requirement specification should be edited by both the customer and the supplier, as initially neither has both the knowledge of what is required (the supplier) and what is feasible (the customer). 2.1Introduction The following subsections of Software Requirement Specifications Document should facilitate in providing the entire overview of the Information system “ATTENDANCE MANAGEMENT SYSTEM” under development. This document aims at defining the overall software requirements for this system. Efforts have been made to define the requirements of the Information system exhaustively and accurately. 2.1 SYSTEM FLOW DIAGRAM 2.2 DATA FLOW DIAGRAM 2.2.1 DFD Level 0: 2.2.2 DFD Level 1: 2.2.3 DFD Level 2: 2.2.3.1 Admin: 2.2.3.2 Staff: 2.3 SYSTEM DESIGN 2.3.1 Entity Relationship Diagram 2.3.2 Use Case Diagram 2.4 Overall description of proposed system 2.4.1 Product Perspective The application will be windows-based...
Words: 256 - Pages: 2
...Hotel Management System 1 Hotel Management System Group 3 Fatima Al-Ghannam 200600561 Fatima Al-Tuhaifa 200700818 Advisor Mr. Mohammad Zikaria Prepared for: ASSE 4311 Assessment 3 Dr. Loay Al-Zubaidi June 20, 2011 Hotel Management System Abstract The project aims to build a system for managing the reservation of hotel. This system has a front-end by 2 using ASP.net with VB and it has a back-end of database which will be built with Oracle by using Oracle 10g and dreamcoder for oracle. The system will be able to add, delete and update the room, guest detail, and transaction. This system will find a solution for recording guest detail, searching for specific guest or available room in easy way; also it will find solution for calculating the bill automatically. The procedure of hotel reservation has been analyzed by logging into booking web site for hotel; such as, holiday inn’s web site and booking.com. Also; we installed Hotel booking system, which has been downloaded from http://www.hotelsystems.co.uk/, for more clear understanding of hotel reservation system. The ASP.net and VB are a new knowledge that we are going to gain during our working in this project. Keywords: hotel reservation system, booking, database of hotel. Hotel Management System Contents Part I Introduction ……………………………………………………………………………………... 8 1. Introduction ...........................................................................................................................
Words: 11693 - Pages: 47
...SOFTWARE REQUIREMENTS SPECIFICATION (SRS) FOR Student and Unit Management System (SUMS) – Registration Module Version 1.0 Prepared by: YEUNG Kam Fung (Ivan) Prepared for: Jim Briggs, University of Portsmouth DOCUMENT CHANGE HISTORY |Version Number |Date |Description | |1.1 |8th December 2005 |Jim made some formatting and content | | | |changes | |1.0 |4th December 2005 |Draft | Preface This document contains the Software Requirements Specification (SRS) of an Online Project Marking System for the School of Computing at the University of Portsmouth. The main aim of this project is to add functionality to the existing SUMS system in order to provide an online facility for managing and registering student accounts. This document has been prepared in accordance with the IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications [IEEE 1998]. Introduction This Software Requirement Specification is written accordance with the IEEE Std 830-1998 model. 1 Purpose This SRS Document contains the complete software requirements for the Online Project Marking System (OPMS) and describes the design...
Words: 1674 - Pages: 7
...CHAPTER 1 INTRODUCTION 1. Background When the word Hospital comes on our mind, the first thing we think about the queue that we have to pass away to get admitted on that hospital. Where every second means life of a person, waiting there for hours gives always a ridiculous feeling. Standing on that point, understanding the importance of time, we are planning to develop software for hospital management. Most of these facilities are today’s need of time. In this project an analysis has been made on the existing Hospital Management System. It is tried that the entire Hospital could be managed by within the system and users feel easy and comfortable to use the system. The system keeps a record of the patient, doctor and other staffs of the hospital management. The software also enables to update, delete the record and also provides the search facility. The system keeps information related to the persons who are willing to donate blood during emergency. 2. Objectives of Hospital Management System Main target is to provide reliable and efficient service to the members/nonmembers of the hospital who visited the hospital in search of it. 1. Patient registration. 2. Emergency Service. 3. Records Information about Hospital. 4. Blood Bank Maintenance. 5. Blood and Organ Donor Maintenance. 6. Doctor Consult. 7. Consultancy Record. 8. Staff Record Managements. 9. Patient Bill...
Words: 5841 - Pages: 24
...Introduction This narrative will describe the history of Riordan Manufacturing, Inc. and go into Riordan Manufacturing’s service request from their COO, Hugh McCauley and his request for a more sophisticated, state-of-the art, information systems technology within their Human Resources department which will encompass all plant locations. A detailed project timeline will be drafted to encompass the service request and detail out the project approach and specifics of meeting its requirements. Company Riordan Manufacturing, Inc. was founded by Dr. Riordan, a professor of chemistry, who had obtained several patents relative to processing polymers into high tensile strength plastic substrates. Originally is started in 1991 as Riordan Plastics, Inc because of the commercial applications of Dr. Riordan patents. The company's focus on research and development and licensing of its existing patents led to a venture capital in 1992 to purchase a fan manufacturing plant in Pontiac, MI. That was when the name was changed to "Riordan Manufacturing, Inc." In 1993, another manufacturing plant in Albany, GA was acquired to produce plastic beverage containers. And in 2000, Riordan opened a new manufacturing facility in China. Their entire fan manufacturing operation moved from Michigan to China to leave the Pontiac, Michigan facility to retool for the manufacturing of custom plastic parts. Request and Scope On November 28, 2011, Hugh McCauley, COO, of Riordan Manufacturing wanted...
Words: 882 - Pages: 4
...Innovation in a Requirement Life-Cycle Framework Abstract In this paper, a requirements-based framework of innovation is discussed. Both customer and expert defined requirements are considered. The proposed framework treats requirements as evolving entities and is implemented using a data-driven approach. It provides a new perspective in support of the innovative product development process. Keywords: Innovation, requirements management, evolutionary computation, data mining. 1. Introduction The volume of information entering a corporate decision-making landscape is increasing. Not too long ago, corporate business models were based on information asymmetry, neglecting the customer needs. Customers did not have the full information about the products available to them. With the creation of internet, the information revolution was bound to happen. Nowadays, a customer can literally search any product available in the global market. This search is usually based on variety of requirements ranging from functional to emotional. Companies can not neglect analysis of customer needs. Therefore, the ability to successfully translating customer requirements in the product development process is of paramount importance, if not the most important one. What is the best business model in today’s competitive market? This is the question that constantly haunts business leaders who are at the front-end of competition as well as the research communities who are continuously developing the...
Words: 2938 - Pages: 12
