...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)...
Words: 1673 - Pages: 7
...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
...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 Specification...
Words: 2464 - Pages: 10
...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 Specification...
Words: 2464 - Pages: 10
...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
...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
... 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 in detail. This document is intended...
Words: 2711 - Pages: 11
...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
...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
... | | | | | | | |Software Engineering | |MedPulse | |Software Requirements Specification | | | |...
Words: 3076 - Pages: 13
...Contents i 1. Introduction 1 1.1 Purpose 1 1.2 Document Conventions 1 1.3 Intended Audience and Reading Suggestions 1 1.4 Project Scope 1 1.5 References 1 2. Overall Description 2 2.1 Product Perspective 2 2.2 Product Features 2 2.3 User Classes and Characteristics 3 2.4 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...
Words: 1254 - Pages: 6
...OpenLGU - Software Requirements Specification for ASSESSMENT REPORT Version 1.4 Prepared by Group Name: 204 Maria Kristina Dina Hazel Gatmaitan 2008-34358 2009-61185 mkristinadina@gmail.com hazelgatmaitan4science@gmail.com Lab Section: Lab Instructor: Date: AB-5L Andrel Del Rosario January 11, 2012, Wednesday Software Requirements Specification for Assessment Page ii Contents IN THIS TEMPLATE YOU WILL FIND TEXT BOUNDED BY THE “” SYMBOLS. THIS TEXT APPEARS IN ITALICS AND IS INTENDED TO GUIDE YOU THROUGH THE TEMPLATE AND PROVIDE EXPLANATIONS REGARDING THE DIFFERENT SECTIONS IN THIS DOCUMENT. THERE ARE TWO TYPES OF COMMENTS IN THIS DOCUMENT. THESE COMMENTS THAT ARE IN BLACK ARE INTENDED SPECIFICALLY FOR CMSC128. THESE COMMENTS THAT ARE IN BLUE ARE MORE GENERAL AND APPLY TO ANY SRS. PLEASE, MAKE SURE TO DELETE ALL OF THE COMMENTS BEFORE SUBMITTING THE DOCUMENT. .................................................................................................................................III THE EXPLANATIONS PROVIDED BELOW, DO NOT COVER ALL OF THE MATERIAL, BUT MERELY, THE GENERAL NATURE OF THE INFORMATION YOU WOULD USUALLY FIND IN SRS DOCUMENTS. IT IS BASED ON THE IEEE REQUIREMENTS AND WAS ADAPTED SPECIFICALLY FOR THE NEEDS OF SOFTWARE ENGINEERING COURSES. MOST OF THE SECTIONS IN THIS TEMPLATE ARE REQUIRED SECTIONS, I.E. YOU MUST INCLUDE THEM IN YOUR VERSION OF THE DOCUMENT. FAILURE TO DO SO WILL RESULT IN MARKS DEDUCTIONS. OPTIONAL SECTIONS WILL BE EXPLICITLY...
Words: 2799 - Pages: 12
...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
...1) An ATM SRS has a requirement to allow for cash withdrawals in $20, $10, and/or $5 denominations. a) Name the stakeholders for this system. (10 pts) Below are all the possible stakeholders from the beginning of the development phase to the end phase. ATM Engineer - Maintenance of the equipment by the bank’s engineers. This action may be initiated by the engineer on a routine basis. It may also be initiated by the equipment that can call the engineer when it detects an internal fault. Property / Shop Owners: Unloading of deposits and loading of cash by officials of the ATM owner. These actions occur either on a scheduled basis or when the central computer determines that the cash supply is low or the deposit receptacle is liable to be getting full. This stakeholder group concerns people who might live next to or close to an ATM machine. For example, many ATM machines can be found on the high street and perhaps only a few floors above will be someone's property. This group also includes shop owners as many ATM machines can be found located next to a shop. Audit: An audit trail for all activities will be maintained and sent periodically to the bank’s central computer. It will be possible for the maintenance engineer to save a copy of the audit trail to a diskette for transporting to the central computer. System Test Engineer – Bothe dialup and leased line support will be provided. The ATM will continue to provide services to customers when communications with the central...
Words: 3425 - Pages: 14
...report to my senior manager telling him in the report everything aspect of developing the software. In developing a new piece of software a creator must go through a series of processes to ensure that the requirements of the idea are met. There are models that can assist us when making something and following the processes in the model step by step can be help us complete the task. In this document I will describe the processes that are needed in developing the piece of software and linking them to the waterfall model. The method of the waterfall model is taking the fundamental processes of specification, development, validation and evolution and representing them as separate process phases such as requirements specifications, software design, implementation and, testing etc. Firstly, in developing a debugger for learner programmers the requirements need to be analysed. To do this we need to look at aspects of the brief such as the systems services, constraints (such as time and money) and the final goal of the software. Consultation with the system user at this point will be needed as to get more of an insight because we need to know as much as possible before starting so we do not have to go back on ourselves and waste resources. Speaking to university students can be helpful as you can get a direct answer of what they are looking for in a debugger that can help them. Requirements of the debugger will be presented on two levels of detail. The...
Words: 1455 - Pages: 6