...Software Requirements Specification Template CptS 322—Software Engineering 9 February 2005 The following annotated template shall be used to complete the Software Requirements Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any modifications to the overall structure of this document. Template Usage: Text contained within angle brackets (‘’) shall be replaced by your project-specific information and/or details. For example, will be replaced with either ‘Smart Home’ or ‘Sensor Network’. Italicized text is included to briefly annotate the purpose of each section within this template. This text should not appear in the final version of your submitted SRS. This cover page is not a part of the final template and should be removed before your SRS is submitted. Acknowledgements: Sections of this document are based upon the IEEE Guide to Software Requirements Specification (ANSI/IEEE Std. 830-1984). The SRS templates of Dr. Orest Pilskalns (WSU, Vancover) and Jack Hagemeister (WSU, Pullman) have also be used as guides in developing this template for the WSU-TC Spring 2005 CptS 322 course. Software Requirements Specification Lead Software Engineer Prepared for WSU-TC CptS 322—Software Engineering Principles I Instructor: A. David McKinnon, Ph.D. Spring 2005 Revision History Date Description Author Comments Document Approval The following...
Words: 1662 - Pages: 7
... | | | | | | | |Software Engineering | |MedPulse | |Software Requirements Specification | | | |...
Words: 3076 - Pages: 13
...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...
Words: 376 - Pages: 2
...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...
Words: 376 - Pages: 2
...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...
Words: 376 - Pages: 2
...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...
Words: 376 - Pages: 2
...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...
Words: 376 - Pages: 2
...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...
Words: 376 - Pages: 2
...SOFTWARE REQUIREMENTS SPECIFICATION RFID Parking Garage Anthony Nichols Matthew Nichols 1.0 Introduction Finding parking spaces for automobiles and motorcycles can a problematic venture due to limited space and time, while the selling of parking spaces is potential lucrative endeavor. Currently, most large parking garages, including airport parking, use a ticketing system in which users get a time-stamped ticket when entering the structure and pay a time relative fee when exiting. The transmission of these disposable tickets is a time inefficient process susceptible to error. These tickets can easily be lost, and with the lost tickets, the entire process disoriented. The manual payment process can also be time consuming when traffic is at a high rate. An RFID parking system would improve this by allowing the user to interact with the parking area with an RFID card at the entrance and exit of the parking area. An RFID parking system would also allow the user to keep an account on which the system would keep track of financial transactions. This would reduce the amount of time the user must interact with the system and increase the security of the user. A new system to allow ease of use and increased security of parking areas is needed 1. Goals and objectives • To provide individuals who require a parking area with a system that is efficient and easy to use. • To provide individuals with a system that accounts for the length of each visit and...
Words: 2239 - Pages: 9
...Abstract:-Software requirement analysis is a method to find out the requirements form the user to develop software. Software requirement analysis and specification also include the types of user requirements and the methods by which developer team can elicit the user requirement and develop suitable software for the user. Introduction:- ➢ Requirement analysis: - Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management. Requirements analysis involves frequent communication with system users to determine specific feature expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep and documentation of all aspects of the project development process from start to finish. Energy should be directed towards ensuring that the final system or product conforms to client needs rather than attempting to mold user expectations to fit the requirements. Requirements analysis is a team effort that demands a combination of hardware, software and human factors engineering expertise as well as skills in dealing with people. ➢ Software requirement analysis: - The success of any new software...
Words: 2585 - Pages: 11
...Software Requirements Specification for Mountain Bank Cell Phone App Version 5.0 approved CS455/Techs2ATee May 11, 2015 Table of Contents 1. Introduction 1 1.1 Purpose 1 1.2 Document Conventions 1 1.3 Intended Audience and Reading Suggestions 2 1.4 Project Scope 2 1.5 References 3 2. Overall Description 6 2.1 Product Perspective 6 2.2 Product Features 6 2.3 User Classes and Characteristics 7 2.4 Operating Environment 7 2.5 Design and Implementation Constraints 7 2.6 User Documentation 8 2.7 Assumptions and Dependencies 8 3. System Features 9 3.1 Establish Secure Session 9 3.1.1 Description and Priority 9 3.1.2 Stimulus/Response Sequences 9 3.1.3 Functional Requirements 9 3.1.4 Secure Session Test Script 10 3.2 Login 12 3.2.1 Description and Priority 12 3.2.2 Stimulus/Response Sequences 12 3.2.3 Functional Requirements 12 3.3 View Balances 13 3.3.1 Description and Priority 13 3.3.2 Stimulus/Response Sequences 13 3.3.3 Functional Requirements 13 3.4 View Transaction History 14 3.4.1 Description and Priority 14 3.4.2 Stimulus/Response Sequences 14 3.4.3 Functional Requirements 14 3.5 Transfer Funds 15 3.5.1 Description and Priority 15 3.5.2 Stimulus/Response Sequences 15 3.5.3 Functional Requirements 15 3.5.4 Funds Transfer between Accounts Test Script 16 3.6 Deposit 20 3.6.1 Description and Priority 20 3.6.2 Stimulus/Response Sequence 20 3.6.3 Functional Requirements 20 3.6.4 Successful Deposit Test Script 21 4. External...
Words: 13282 - Pages: 54
...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
...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
...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 (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
