Premium Essay

Software Requirements Document

In: Computers and Technology

Submitted By tahossue
Words 2566
Pages 11
Table of Contents
1. DOCUMENT OBJECTIVE 4
1.1 PROJECT OVERVIEW AND OBJECTIVES 4
1.2 BUSINESS BENEFITS 4
2. IMPACTS 5
2.1 IMPACTED BUSINESS AREAS 5
2.2 IMPACTED PRODUCTS 5
2.3 EXPECTED IMPACTED SYSTEMS 5
2.4 TRAINING AND COMMUNICATION REQUIREMENTS 5
2.5 CUSTOMER COMMUNICATIONS 5
2.6 OTHER IMPACTS 5
3. PROJECT SCOPE 6
3.1 MANAGING SCOPE CHANGE 6
3.2 ITEMS IN SCOPE 6
3.3 ITEMS OUT OF SCOPE 6
3.4 TIMEFRAME AND BUDGET CONSTRAINTS 6
3.4.1 Estimated Timeframe 6
3.4.2 Budget Constraints 6
3.4.3 Ownership 6
4. RISK ANALYSIS 7
4.1 ISSUES AND RISKS 7
4.1.1 Outstanding Issues 7
4.1.2 Risks 7
4.1.3 Risk Assessment Rating 7
4.2 BUSINESS RISK 7
4.3 TECHNICAL RISK 7
5. CONSTRAINTS, ASSUMPTIONS, DEPENDENCIES AND RESOURCES 8
5.1 CONSTRAINTS 8
5.2 ASSUMPTIONS 8
5.3 DEPENDENCIES 8
5.4 RESOURCES 8
6. BUSINESS FUNCTIONS 9
6.1 HIGH LEVEL BUSINESS FUNCTIONS 9
6.2 DETAILED BUSINESS FUNCTIONS 9
6.3 BUSINESS PROCESS FLOWCHART/S 9
7. SYSTEM SOLUTION OPTIONS 10
7.1 SYSTEM SOLUTION OPTION ONE 10
7.1.1 Description of System 10
7.1.2 Sample Screen Shots / Reports 10
7.1.3 Technical Considerations 10
7.1.4 Operational Considerations 10
7.1.5 Schedule Timeframes 10
7.1.6 Training Requirements 10
7.1.7 Budget 10
7.1.8 Future Requirements Fit 11
7.1.9 System Solution Advantages 11
7.1.10 System Solution Disadvantages 11
8. RECOMMENDATION 12
9. USE CASE DIAGRAM 13
10. HIGH LEVEL USE CASES 14
11. USER INTERFACE DESIGN 15
11.1 SCREEN 1 DESCRIPTION 15
11.2 SCREEN 1 DESIGN 15
12. DETAILED CLASS DIAGRAM 16
13. DATABASE DESIGN/CHANGES 17
14. EXTENDED USE CASES AND SCENARIOS 18
15. IMPLEMENTATION AND CONVERSION 19
15.1 IMPLEMENTATION REQUIREMENTS 19
15.1.1 Timing of Software Release 19
15.1.2 Software Switches 19
15.1.3 Implementation Processing 19
15.1.4 Backout Considerations 19
15.2 CONVERSION REQUIREMENTS 19
15.2.1 Conversion Jobs 19
15.2.2…...

Similar Documents

Premium Essay

Business Requirement Document

...IS 390 Group Project Milestone Two Due: Oct. 29th In this milestone, you are to deliver a document called BRD (Business Requirement Document). Although difference formats exist for BRD, the one you are required to present is popularly used in current IS practice. It serves as a “contract” between you and your client on the scope, schedule & expected outcome of your project. A BRD contains seven sections. I. Version Control Since a BRD might go through several rounds of revision (iterative process, remember?), this first section is simply used to keep track of the project history. A. Revision history: Simply a table with the following columns: Version# (0.1, 0.2…), Date of revision, Responsibility (Author), Description. I assume that you will have only one version given the short time available, which is fine. B. RACI chart RACI chart is used in organizational design to make assignments and designate levels of involvement and responsibility. In a system project, it lists the roles played by each of the team members during each developmental stage. To develop a RACI chart, first identify tasks involved in this stage. Your tasks should include at least the following: 1. Correspondence with the client: meeting setup and follow-up. 2. Preparation for the interview: design of interview questions and flow 3. Leading interviewer(s): the ones who ask the majority of the questions 4. Interview notes-takers: team members who...

Words: 1349 - Pages: 6

Premium Essay

Software Requirement Specification

...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

Free Essay

Save Documents and Software of Video Meeting

...1. Introduction The company is a greeting card manufacturers and exporter. The office is unit 6, 7 and 10 on the 17th floor in Fortress Tower Center. There are around 12clerical staffs, 10sales representatives and 5 managers. The company has some issues for their existing systems. One is that staffs are using USB flash drive to store sensitive documents for work at home and it is easy to lose. Second is to reduce the number of business trips. Third is to reduce communication expense. Fourth is that some clients cannot send and receive large drawing. Fifth is that all engineering drawings and proposals are important assists should be retaining from disaster. Sixth is to found a way to minimize the effort and loan procedures. Seventh is that full wireless network coverage is required in all office areas. 2. Solutions to the addressed issues 2.1. Save documents 2.1.1. Dropbox Dropbox is a free service that lets you bring all your photos, documents, and videos anywhere. Any file you save to your Dropbox will also automatically save to all your computers, phones, and even the Dropbox website. This means that you can start working on your computer at school or the office, and finish on your home computer. Never email yourself a file again!(1) 2.1.2. Drop Box (for business) The space is 1,000 GB when you start to use it. If you run out, tell them and they will increase it for free. It support WORD、EXCEL、POWER POINT、PDF etc. The files are stored using 256-bit......

Words: 2947 - Pages: 12

Premium Essay

Software Requirements

...September 16, 2014 INSS 615- Mini Paper Chpt. 1 – Understanding Software Requirements Software requirements first start off deciding what to build and then how to document the process for designing the specified system needed or acquired. We will discuss what are software requirement, methodologies, requirements and architecture, and emerging trends. A software requirement is typically classified in two distinct functions. A stated by Thayer and Dorfman (2013) functional typically refers to requirements defining the acceptable mappings between system input values and corresponding output values. Non-functional refers to all constraints including, but not limited to, performance, dependability, maintainability, reusability, and safety. These two functions work intangible with common attributes and similar qualities that behavioral requirements deal with output values and deadlines, and developing quality attributes deals with deadlines and maintaining the goals achieved. One major issue inherent with requirements is discovering significant errors later during maintenance can be very costly. It is recommended to detect errors during the design and development so as is less expensive. The goal of requirements phase is to establish and specify precisely what the software must do without describing how to do it (Thayer and Dorfman, 2013). The ultimate outcome is to specify the problem to be solved and not its solutions. The average person doesn’t understand very technical...

Words: 571 - Pages: 3

Premium Essay

Software Requirement Specification of Library Mgmt System

...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......

Words: 2807 - Pages: 12

Free Essay

Software Digsn Documents

...10/10/2014 10/10/2014 Wiseman Fanele MKHWANAZI University of zululand Wiseman Fanele MKHWANAZI University of zululand Software Design Document (SDD) Version 1.0 Title of Project Medical indigenous knowledge system-query service Mentoring Mr P Tarwireyi, lecturer for Computer Science, University of Zululand Software Design Document (SDD) Version 1.0 Title of Project Medical indigenous knowledge system-query service Mentoring Mr P Tarwireyi, lecturer for Computer Science, University of Zululand Student no: 201131437 Contents 1. Introduction 2 1.1. Purpose of the System Design Document 2 1.2. Scope 2 1.3. Glossary 3 1.4. References 3 1.5. Overview of document 3 2.0. Assumptions / Constraints / Risks 4 2.1. Assumptions 4 2.2. Constraints 4 2.3. Risks 4 3.0. Architecture design 5 3.1. Medical indigenous knowledge system web MVC architecture 5 Figure 1 Architecture Design 5 4.0. Design 5 4.1. Class diagram 5 Figure 2 show how classes interact to each other to compose the full MIK System 6 4.2. Data flow diagram 6 Figure 3 its show that how the data flow during the user/patient interaction with MIKS 7 5.0. Use cases 8 Figure 4 System user case Diagram 8 6.0. Use case realizations 11 Figure 5 System Sequence Diagram 11 Figure 6 Administrator Sequence Diagram 11 Figure 7 User/Patient Sequence Diagram 12 7.0. Activity diagram 13 7.1. Activity......

Words: 2090 - Pages: 9

Free Essay

Software Requirements Specification

...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......

Words: 2239 - Pages: 9

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...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......

Words: 376 - Pages: 2

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...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......

Words: 376 - Pages: 2

Premium Essay

Software Requirements Specification Document

...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......

Words: 13282 - Pages: 54

Premium Essay

Software Requirement Specification

...< 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......

Words: 739 - Pages: 3

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...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......

Words: 376 - Pages: 2

Premium Essay

Quickbooks Accounting Software Computer Requirements

...QuickBooks System Requirement I. Operating systems supported Operating systems supported Windows 8, all editions including 64-bit, natively installed (QuickBooks R4 and later required) Windows 7, all editions including 64-bit, natively installed Windows Server 2012 (Small Business Server/Essentials), Windows Small Business Server 2011, Small Business Server 2008 Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003, including 64-bit,natively installed II. Database Servers: Windows: natively installed & Windows 8, Windows 7 (SP1), Windows Server 2008 R2, Windows Server 2008, Windows Server 2008 - Terminal Server Config., Windows Server 2003, Windows Small Business Server 2012, Windows Small Business Server 2011, and Windows Small Business Server 2008 Note: Windows Home Server Edition is not supported. III. Hardware and operating system requirements (client and server) 2.0 GHz processor; 2.4 GHz recommended 2-4 GB RAM recommended for multiple users for QuickBooks Enterprise Display optimized for 1024 x 768 screen resolution or higher with up to 1 Extended monitor All online services and subscription based features (such as Advanced Inventory) require Internet access. Windows: Administrator Rights required for the server computer when hosting Multi User Access Regional Settings are supported when set to English (United States) with keyboard setting to U.S. only Natively installed Disk space requirements: 10 GB of disk space or more......

Words: 454 - Pages: 2

Premium Essay

Software Requirements Specification

... | | | | | | | |Software Engineering | |MedPulse | |Software Requirements Specification | | | | | | | | ...

Words: 3076 - Pages: 13

Premium Essay

Software Requirement Analysis and Specification

...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......

Words: 2585 - Pages: 11