...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 Prepared by [author] [name of your organization] Guidance: Blue text like this is guidance. Delete it and insert text describing your project, in ordinary font. SRS on the Web or Wiki: If you SRS is on the web, in a Wiki, in Trac, or Redmine, then you can divide this template into several pages or documents. Each section or subsection of this template can be a hyperlink to another page containing that part. In Trac and Redmine, your wiki can contain links to documents in SVN. If you are using Word format for a document, putting it in SVN makes sense. SRS in Redmine: Create a "Requirements" category in Redmine (in the Documents tab) and put the SRS there. Each section of this template can be a hyperlink to a separate document or wiki page. Or, if you need a single SRS (maybe your instructor wants it printed), you can link to a single document that follows this template. Note that you can create links to documents in SVN. Table of Contents This table of contents is auto-generated by MS Word using paragraph styles Heading1 - Heading4 and TOCEntry. Don't edit this TOC manually. Table of Contents ii Revision History ii 1. Introduction 1 1.1 Purpose 1 1.2 Document Conventions 1 1.3 Project Scope 1 1.4 References 1 2. Overall Description 1 2.1 Product Perspective 1 2.2 Product Features 2 2.3 User Classes and Characteristics 2 2.4 Operating Environment...
Words: 1818 - Pages: 8
...Request 38. 25-Sep-2007 Version 1.0 – System Development Life Cycle Guide released. DIR Document 25GU-1-1 ii Texas Project Delivery Framework SYSTEM DEVELOPMENT LIFE CYCLE GUIDE Contents Introduction ................................................................................................................................1 Use of the System Development Life Cycle Guide ....................................................................2 Section 1. System Life Cycle Processes...................................................................................3 1.1 Introduction ......................................................................................................3 1.2 System Life Cycle Processes and the Organization ........................................4 Section 2. Development Process ..............................................................................................5 2.1 Introduction ......................................................................................................5 2.2 System Development Life Cycle Models .........................................................6 Section 3. System Development Life Cycle Activities ...............................................................8 3.1 Development Process Tailoring .......................................................................9 3.2 System Requirements...
Words: 10250 - Pages: 41
...CPSC 4392 Capstone Project Spring 2011 Software Requirements Specification EZ Inventory Management System (EZIMS) Sean Cox 501-249-1250 srcox@ualr.edu Advisor: Dr. Chia-Chu Chiang Department of Computer Science University of Arkansas at Little Rock Little Rock, Arkansas 72204-1099, USA 501-569-8142 cxchiang@ualr.edu EZ Inventory Management System 1. Introduction 1. Purpose 2. Scope 3. Definitions, acronyms, and abbreviations 4. References 5. Overview 2. Overall description 1. Product perspective 2. Product functions 3. User characteristics 4. Constraints 5. Assumptions and dependencies 3. Specific Requirements 1. Functional Requirement 2. External Interface Requirement 3. Performance Requirements 4. Design Constraints 5. Software System Attributes 1. Introduction 1.1 Purpose The purpose of this document is to provide the specifications for the software which is to be developed. The purpose of the EZ Inventory Management Systems (EZIMS), is to provide the customer with an effective way to manage their current inventory and provide a history of previous inventory. 1.2 Scope The software product to be produced is called EZ Inventory Management System (EZIMS). This program is to be a standalone executable which provides an interface...
Words: 1338 - Pages: 6
...Dependencies 4 3 Specific Requirements 4 3.1 USE-CASE REPORTS 4 3.2 Supplementary Requirements 4 4 Supporting Information 4 REVISION HISTORY |Date |Version |Description |Author(s) | | | | | | | | | | | | | | | | Introduction [The introduction of the Software Requirements Specification (SRS) should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of the Software Requirements Specification.] [Note: The Software Requirements Specification captures the complete software requirements for the system, or a portion of the system. The following document describes a typical Software Requirements Specification outline for a project using use-case modelling. This artefact consists of a package containing use cases of the use-case model and applicable Supplementary Specifications and other supporting information. [Many different arrangements of a Software Requirements Specification are...
Words: 848 - Pages: 4
...Software Requirements Specification for Hostel Management System Version 1.0 approved Prepared by: Supriya Singla(100803098) Shaveta Dhiman(100803090) Surabhi Agarwal(100803099) Thapar University(Patiala) Table of Contents 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 1 2.1 Product Perspective 1 2.2 Product Features 2 2.3 User Classes and Characteristics 2 2.4 Operating Environment 2 2.5 Design and Implementation Constraints 2 2.6 User Documentation 2 2.7 Assumptions and Dependencies 3 3. System Features 3 3.1 room allocation 3.2 room configuration………………………………………………………………………………. 3.3 mess bill management…………………………………………………………………………… 3.4 fines management 4. Other Nonfunctional Requirements 5 4.1 Performance Requirements 4.2 Safety Requirements 4.3 Security Requirements 4.4 Software Quality Attributes Introduction 1 Purpose The purpose of this document is to present a detailed description of the project. It will explain the purpose and the different features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. 3 Document Conventions Every requirement is having its own priority .Higher priority requirement is marked with a higher number and...
Words: 933 - Pages: 4
...Managment System Software Requirements Specification for Hostel Management System Version 1.0 approved Prepared by: Supriya Singla(100803098) Shaveta Dhiman(100803090) Surabhi Agarwal(100803099) Thapar University(Patiala) Table of Contents 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 1 2.1 Product Perspective 1 2.2 Product Features 2 2.3 User Classes and Characteristics 2 2.4 Operating Environment 2 2.5 Design and Implementation Constraints 2 2.6 User Documentation 2 2.7 Assumptions and Dependencies 3 3. System Features 3 3.1 room allocation 3.2 room configuration………………………………………………………………………………. 3.3 mess bill management…………………………………………………………………………… 3.4 fines management 4. Other Nonfunctional Requirements 5 4.1 Performance Requirements 4.2 Safety Requirements 4.3 Security Requirements 4.4 Software Quality Attributes Introduction 1 Purpose The purpose of this document is to present a detailed description of the project. It will explain the purpose and the different features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. 3 Document Conventions Every requirement is having its own priority .Higher priority requirement is marked with a...
Words: 298 - Pages: 2
...Software Requirements Specification For Student mark analysis system 1. Introduction 1.1 Purpose ``1.2 Scope 3 Definitions, Acronyms, and Abbreviations 4 References 5 Overview 2. General Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics 2.4 General Constraints 2.5 Assumptions and Dependencies 3.1 External Interface Requirements 3.1.1 User Interfaces 3.1.2 Hardware Interfaces 3.1.3 Software Interfaces 3.2 Functional Requirements 3.2.1System features Front end(student front) Back end(administrative tools) 3.3 Non-Functional Requirements 3.3.1 Usability requirements 3.3.2 Performance requirements 3.3.3 Compatibility requirements 1. Introduction 8 Purpose “STUDENT MARK ANALYZING” is used to enter and manage the student records in an organized manner, as the number of student is high it is difficult to maintain the record manually. 9 Scope The software product to be produced in “analyzing marks” helps in easy evaluation of the student based on the marks obtained in the examination. It also get results of the statistics of the result by displaying the number of student passed and failed in the class along with the pass percentage. The software displays the rank list of the student. 10 Definitions, Acronyms, and Abbreviations M.A.S:- Marks Analysis System MTT1:- Mid Term Test...
Words: 1271 - Pages: 6
...User Characteristics 3 3.4 General Constraints 4 3.5 Assumptions and Dependencies 4 4. Specific Requirements 4 4.1 External Interface Requirements 4 4.1.1 User Interfaces 4 4.1.2 Hardware Interfaces 4 4.1.3 Software Interfaces 4 4.1.4 Communications Interfaces 4 4.2 Functional Requirements 4 4.3 Use Cases 7 4.4 Classes 8 4.5 Non-Functional Requirements 9 4.5.1 Performance 9 4.5.2 Reliability 9 4.5.3 Scalability 9 4.5.4 Security 9 5. Analysis Models 9 5.1 Sequence Diagrams 9 5.2 Collaboration Diagrams (STD) 10 5.2 State-Transition Diagrams (STD) 11 5.4 ACTIVITY DIAGRAM……………………………………………………………………………………….15 5.5 DEPLOYMENT DIAGRAM…………………………………………………………………………………15 2. Introduction The Online Student Course registration system is automated system where the user can register the student for various courses. This is proposed for automating the student’s course registration. While the student joins any educational institution his admission is made on the basis of his previous records. The students who wish to the institution must be given with the available course details. The student is allotted with a seat in the institution based on the marks that he scored in the institution he studied previously. After the confirmation of his joining the student must be given with new identity and records as per the institution. 2.1 Purpose The purpose of this document is to present a detailed description of the Online Course Registration System. It will explain the...
Words: 338 - Pages: 2
...Fall 2015 TERM PROJECT ASSIGNMENT [pic] Objectives The assignment's objective is to gain experience in software engineering practices. Project The project will be chosen by each group from one of the project descriptions in the attached “Project Proposals” document. The names and numbers of group members along with the project topic that is chosen must be submitted under the heading Projects Groups and Topics Assignment on the moodle page of the course by 8.10.2015 by each team. The project will be undertaken in teams consisting of three or four members. All the members must belong to the same lab group. 1 Expected Work The teams should apply waterfall process model. They are free to use any tool or report format that may be preferred for its being very suitable for the teams specific task. For example teams may add a data flow diagram or even a flowchart to their analysis or design if they think they are necessary to get the job done. “Getting the job done” is however a strict requirement and it is expected from the team as a pay-back of the freedom that they have been granted. You will frequently find the instructors act as customers who even do not know what exactly they should expect from the project, or in general from software or computers. On the other hand the team should be motivated to discover and demonstrate what the project may do for the end users. The teams must perform all kinds of research including moving...
Words: 1146 - Pages: 5
...Guidance for Use Case Template Document each use case using the template shown in the Appendix. This section provides a description of each section in the use case template. 1. Use Case Identification 1.1. Use Case ID Give each use case a unique numeric identifier, in hierarchical form: X.Y. Related use cases can be grouped in the hierarchy. Functional requirements can be traced back to a labeled use case. 1.2. Use Case Name State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples: • View part number information. • Manually mark hypertext source and establish link to target. • Place an order for a CD with the updated software version. 1.3. Use Case History 1.3.1 Created By Supply the name of the person who initially documented this use case. 1.3.2 Date Created Enter the date on which the use case was initially documented. 1.3.3 Last Updated By Supply the name of the person who performed the most recent update to the use case description. 1.3.4 Date Last Updated Enter the date on which the use case was most recently updated. 2. Use Case Definition 2.1. Actor An actor is a person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that...
Words: 824 - Pages: 4
...Licensed to Gustavo Simues A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 2.0 www.theiiba.org Order ID: IIBA-200911231134-455082 Licensed to Gustavo Simues International Institute of Business Analysis, Toronto, Ontario, Canada. ©2005, 2006, 2008, 2009, International Institute of Business Analysis. All rights reserved. Portions of Appendix A: Glossary are from The Software Requirements Memory Jogger, by Ellen Gottesdiener, ©2005 GOAL/QPC and are used with permission. Cover Image ©2006 iStockphoto.com/Damkier Media Group. Version 1.0 and 1.4 published 2005. Version 1.6 Draft published 2006. Version 1.6 Final published 2008. Version 2.0 published 2009. Second Printing. ISBN-13: 978-0-9811292-1-1 (print) ISBN-13: 978-0-9811292-2-8 (PDF and EBook) Permisson is granted to reproduce this document for your own personal, professional, or educational use. If you have purchased a license to use this document from IIBA®, you may transfer ownership to a third party. IIBA® Members may not transfer ownership of their complimentary copy. This document is provided to the business analysis community for educational purposes. IIBA® does not warrant that it is suitable for any other purpose and makes no expressed or implied warranty of any kind and assumes no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information contained herein. IIBA®, the IIBA®...
Words: 96708 - Pages: 387
...REQUIREMENTS COLLECTION Template A GUIDE FOR REQUIREMENTS GATHERING AND TRACE-ABILITY MATRIX DEVELOPMENT Revision: 1.0 About this document 3 Guidelines for using the Requirements Collection Template 4 Requirement ID: 4 Requirement Type 4 Parent Requirement#: 5 Source and source Document: 5 Dependencies: 5 Definitions of Priorities: 5 Tracking Requirements and status 6 Status Options: 6 Change History: 6 Clarification/specification of Requirement 6 Rationale: 6 Acceptance/Fit Criteria: 6 Dependencies: 6 The requirements collection template form 7 Requirements Traceability Matrix 8 About this document Requirements are the foundation of the project and the development of the product that the project has been organized to develop. The purpose of this document is to present a standardized requirements collection template. The template proposed in this document serves a variety of purposes. It is intended for all types of project requirements: • Business • User • System • Functional • Non-Functional The template is useful for the development of a traceability matrix because it tracks a requirement to its parent requirement, and requests the source and or document from which the requirement came. The template also supports specific, measureable, attainable, realistic and testable requirements by asking for supporting clarifications...
Words: 1161 - Pages: 5
...holds and secures the member information. The proposed system is a Membership Information system that will save and updates any single information of a member of Churches of Christ. This system have data requirements for this to have best result, it requires information such as the member’s data which is so much important. Churches of Christ is using traditional system in recording member’s information and it is so difficult to manage every data with this kind of system that’s why Churches of Christ needs to improve their way of managing and recording information of the present and incoming member. 2.2 System Description 2.2 System Description Membership in Churches of Christ in the selected local which is in Riverside Quezon City has traditionally been done on paper, processed by hand and response letters written from a template and that’s why secretaries in Churches of Christ works so hard in order to serve the current and incoming member of their local . As the researcher studied the process of how the secretaries and the officers of Churches of Christ in Local of Riverside Quezon City, he thought of alternatives to make it better which is developing a electronic system that manages the information of the members. Membership Information System (MIS) is a software application for membership of Churches of Christ to manage member data and also their attendance. Membership...
Words: 1794 - Pages: 8
...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