...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
...< Project scenario name > Software Requirements Specification Version < X.0> < team Name > < Scenario Name > Software Requirements Specification Version < X.0> Team Guide:( Faculty Guide’s Name ) Members:(Team members name) College Name: Department: State: / Page 1 < Project scenario name > Software Requirements Specification Version Revision History Date Version 1.0 2.0 Description Synopsis Synopsis Author / Page 2 < Project scenario name > Software Requirements Specification Version X.0 Table of Contents Description 1.0 Introduction 1.1 1.2 1.3 1.4 1.5 1.6 Purpose Scope Definition, Acronyms, and Abbreviations References Technologies to be used Overview Page No. 2.0 Overall Description 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Product Perspective Software Interface Hardware Interface Product Function User Characteristics Constraints Architecture Design Use Case Model Description / Page 3 < Project scenario name > Software Requirements Specification Version X.0 2.9 Class Diagram ........................................................................ Sequence Diagram s ............................................................... 2.10 Database Design .................................................................... 2.11.1 2.11.2 ER Diagram ............................................................... Schema ...................................................................... 2.12...
Words: 739 - Pages: 3
...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 For Library Management System Prepared by:- Soumili Sen Nayan Patil Neha Singh Anita Singh Academic Year: 2013-2014 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...
Words: 2807 - Pages: 12
...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
...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
...such an effort. He had no trouble getting functional support for the R&D effort necessary to put together a technical proposal. All of the functional managers continually remarked to Gary "This must be a biggy. The director of engineering has thrown all of his support behind you." On December 2, the RFP was received. Gary identified one trouble area. The technical specifications stated that all components must be able to operate normally and successfully through a temperature range of -65 degrees F to 145 degrees F. Current testing indicated the Scientific Engineering Corporation design would not function above 130 degrees F. An intensive R&D effort was conducted over the next three weeks. Everywhere Gary looked, it appeared that the entire organization was working on his technical proposal. Gary and Henry Larsen met a week before the final proposal was due to develop a company position concerning the inability of the preliminary design material to be operated above 130 F. Gary was concerned. Every approach he tried indicated that the original design wouldn't work. He didn't think the specification requirements could be met without a change in materials. Gary wanted to tell the customer the truth, let the chips fall where they may and start over, and he told Larsen this. But Larsen had a different approach. Henry Larsen. Watch Video | Read Transcript The proposal was submitted after two solid months of sixteen-hour days. On February 10, Space Technology Industries...
Words: 279 - Pages: 2
...variety of existing and future services, using industry accepted design and installation methods. To define standards that will enable the design and implementation of structured cabling systems for commercial buildings and between buildings. The telecommunications industry standards, codes and practices are defined in various state and agencies on web sites defined in a catalog that can purchase and downloaded and read for immediate enforcement of these guidelines used for each industry. These policies are intended to answer faxes of infrastructure practices and not to be a substitute for knowledge of industry accepted practices, standards and codes. Policies are not intended to be used in lieu of a construction specification document, are used to abide to the specifications. Communications technologies can be complex and designed and installed by experienced professionals. Telecommunications are considered a fourth utility, to be designed, funded and installed with the same importance as Electrical, Plumbing and HVAC. The designer has the responsibility of providing a design using accepted engineering and architectural practices and recommends a Registered Communications Distribution Designer (RCDD) to be used as a consultant for the design of the telecommunications. In many cases the need will arise to consult with other engineers from other trades or...
Words: 1394 - Pages: 6