...PCs Please use the document “Case Study Instructions Director’s Request for PCs” found in the Case Study Instructions conference topic for the list of requirements which should be met by this project. Part 1: For the case study outlines in the Instructions topic, create MS Word tables that identify and contain the hardware and software requirements to meet the director's requirements. The MS Word document in its final form will include 5 MS Word tables. It will include a two-paragraph narrative summary that classifies the user type and identifies the PC category(ies) that will be recommended. Think of the narrative summary as an executive summary where you outline the recommendations without going into a great deal of detail. You will write this executive summary after you have completed the tables. But place the executive summary after your title page, BEFORE the 5 tables. Students are expected to conduct external research to adequately address all aspects of the assignment requirements. Any outside sources should be correctly cited in APA style at the end of the table. Students will need to include specific requirements from the case study to show why each item is being recommended. Each element listed below must be incorporated into the assignment. Omissions will result in loss of points. |Requirement |Points Allocated |Comments | |Open and save an MS...
Words: 952 - Pages: 4
...“READ FIRST - Case Study Instructions – Director’s Requirements” for each of the parts described below. Part 1: Specifications Table (MS Word) Use the project description HERE to complete this activity. For a review of the complete rubric used in grading this exercise, click on the Assignments tab, then on the title Case Study Part 1 - PC Specs (Word)– click on Show Rubrics if the rubric is not already displayed. For the case study provided to you, create MS Word tables that identify and contain the hardware and software requirements to meet the director's requirements. The MS Word document in its final form will include 6 MS Word tables. It will include a two-paragraph narrative summary that classifies the user type and identifies the PC category that will be recommended. The specific instructions are found in the table at the end of this file. Students are expected to conduct external research to adequately address all aspects of the assignment requirements. It is suggested that students use a computer manufacturer's site (i.e., Apple, Dell, Toshiba) to help in identifying all the components needed to meet the director's requirements. Remember, although there are 5 computers to be purchased, you are required to configure only one, as the same one may be purchased for all 5 employees. Any outside sources should be correctly cited in APA style at the end of the table. Students will need to include specific requirements from the case study to show why each item is being...
Words: 2182 - Pages: 9
...Software Requirements Specification (SRS) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. The document in this file is an annotated outline for specifying software requirements, adapted from the IEEE Guide to Software Requirements Specifications (Std 830-1993). Tailor this to your needs, removing explanatory comments as you go along. Where you decide to omit a section, you might keep the header, but insert a comment saying why you omit the data. CS3911 (Team Number) (Team Name) Software Requirements Specification Document Version: (n) Date: (mm/dd/yyyy) Table of Contents 1. Introduction 5 1.1 Purpose 5 1.2 Scope 5 1.3 Definitions, Acronyms, and Abbreviations 5 1.4 References 5 1.5 Overview 5 2. The Overall Description 6 2.1 Product Perspective 6 2.1.1 System Interfaces 6 2.1.2 Interfaces 6 2.1.3 Hardware Interfaces 6 2.1.4 Software Interfaces 7 2.1.5 Communications Interfaces 7 2.1.6 Memory Constraints 7 2.1.7 Operations 7 2.1.8 Site Adaptation Requirements 7 2.2 Product Functions 8 2.3 User Characteristics 8 2.4 Constraints 8 2.5 Assumptions and Dependencies 9 2.6 Apportioning of Requirements 9 3. Specific Requirements...
Words: 6285 - Pages: 26
...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
...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
...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
...Experiment 02-Software Requirement Specification · Objective: To learn Software Requirement Specification (SRS) and design the documentation for given project. · Background: A software requirement specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform. · Pre-requisite: The general format of SRS consists of: · Functional Requirements Definition · Functional requirements are a subset of the overall system requirement. · These requirements are used to consider system behavior. · Trade-offs may be between hardware and software issues. · Non-functional Requirements Definition · It measures the documentation and the inputs for the various requirements in the system. · System Evolution · Starting from the specification and the data base schema, on how the system should be designed. · SRS Template for documentation Human resources system Software Requirements Specification Version 1.0 01/09/2015 Benita Jeyakumar Lead Software Engineer 1.0. Introduction - Human Resources System 1.1 Purpose The main purpose of human resources system is to maintain records regarding the employees of the company and to gather feedback from the users. The system includes information related to: · Employee records database · Recruiting management · Performance record ...
Words: 1452 - Pages: 6
...SWE 626 Team 2 Hotel Management 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...
Words: 2464 - Pages: 10
...SWE 626 Team 2 Hotel Management 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...
Words: 2464 - Pages: 10
...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 to an inventory database. The program is easy to use, so that users can easily...
Words: 1338 - Pages: 6
...goals, feasibility, requirements, and data flow for Kudler’s Frequent Shopper Rewards Program that is being developed (Kudler Fine Foods, Inc., 2008). We have addressed the issues involving the schedule and budget of the program’s design, implementation, training, and support. The proposal will also discuss the network upgrades of software and hardware related to this new program. After the stakeholders are identified, their participation and approval will be needed throughout the project life cycle. About Kudler Kudler Fine Foods is a California-based high end food store chain. Their products are marketed in upscale neighborhoods and shopping centers. Kudler’s mission is to provide their “customers the finest in selected foodstuffs, wines, and related needs in an unparalleled consumer environment....and (they) will go to extensive lengths to assure that Kudler’s is the purveyor of choice for customers aspiring to purchase the finest epicurean delights” (Kudler Fine Foods, Inc., 2008). Kudler’s 2007 Sales Plan focuses on “increasing customer loyalty by offering added high-margin services, (new) programs to increase loyalty and profitability of existing customers, and to gain new high-margin customers” (Kudler Fine Foods, Inc., 2008). Stakeholders By identifying the project stakeholders, Kudler can ensure that the project encompasses all the features needed to implement a successful program with immense satisfaction from both the user and the customer. The...
Words: 2639 - Pages: 11
...Quality Function Deployment of Custom Orientation Stabilization Integrated Systems September 23, 2012 Scott Jaster ENM5100 Quality Engineering Florida Institute of Technology ABSTRACT The purpose of this paper is to present a description of the Quality Function Deployment (QFD) process with respect to the development of an alternative means of multi-axis orientation stabilization. The intention is to discuss the quality control process of choosing the "best" components for the system, and meeting customer requirements before, during, and after product delivery. There will be an exploration of the Quality Function Deployment (QFD) process that pertains to the systems integration design, manufacture, and delivery process, from the user’s ultimate perspective. The interactions of the various components must be defined by the desired specifications, modeled, and analyzed to produce the optimal setup that meets the respective performance requirements of the user, while following along with the QFD process strategy. The focus will be on the House Of Quality (HOQ), described within. A related discussion will be the determination of the viability and functionality of designing a system capable of efficiently counteracting axial orientation wobbling; but this is the byproduct of the properly employed functional Quality process. Ultimately, the discussed Quality process allows the user to efficiently and subjectively determine the best engineering trade-offs related...
Words: 2914 - Pages: 12
...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 in...
Words: 2711 - Pages: 11
...Constarints…………… of the requirements Functional Requirement (Function) A Functional Requirement is a requirement that, when satisfied, will allow the user to perform some kind of function. For example: “The customer must place an order within two minutes of registering” For the most part, when people are talking about Business Requirements, they are referring to Functional Requirements which are generally referred to as “requirements”. Functional Requirements have the following characteristics: * uses simple language * not ambiguous * contains only one point * specific to one type of user * is qualified * describes what and not how Non-Functional Requirement A Non-Functional Requirement is usually some form of constraint or restriction that must be considered when designing the solution. For example: “The customer must be able to access their account 24 hours a day, seven days a week.” For the most part when people are talking about Constraints, they are referring to Non-Functional Requirements. Non-Functional Requirements have the same following characteristics: * uses simple language * not ambiguous * contains only one point * specific to one type of user * is qualified * describes what and not how Non-Functional requirements tend to identify “user” constraints and “system” constraints. Business requirements should be kept pure and not reflect any solution thinking. A system constraint is a constraint imposed by the system and not...
Words: 299 - Pages: 2
...Software Requirements Document Tanya Berezin Table of Contents SHOULD YOU READ THIS PAPER? WHAT IS A REQUIREMENTS DOCUMENT? WHY BOTHER WITH A REQUIREMENTS DOCUMENT? DO I HAVE TO WRITE A REQUIREMENTS DOCUMENT? WHO USES THE REQUIREMENTS DOCUMENT AND WHY? GENERAL PRINCIPLES IN WRITING A REQUIREMENTS DOCUMENT SECTIONS OF A REQUIREMENTS DOCUMENT PART I – APPLICATION OVERVIEW PART II – FUNCTIONAL REQUIREMENTS PART III – APPENDICES 3 3 4 5 5 6 9 10 12 15 WHO NEEDS WHAT? SUMMARY OF PURPOSE AND USAGE OF THE SECTIONS OF THE REQUIREMENTS DOCUMENT 17 HOW TO GET OTHERS TO READ THE REQUIREMENTS DOCUMENT? REFLECTING CHANGES IN REQUIREMENTS DOCUMENTING REQUESTS FOR ENHANCEMENTS TRACING REQUIREMENTS CONCLUSION AND FURTHER READING AUTHOR BIOGRAPHY 18 19 20 21 21 22 Should You Read This Paper? Should You Read This Paper? This paper discusses the purpose and contents of a requirements document for a business application. It is an introduction to the subject and will be most helpful to you if any of the following applies to you: • you are responsible for collecting requirements for a business application • you are leading a business application development project • you are not sure what a requirements document ought to look like or even if you need one • you are not sure what to do with a requirements document even if one miraculously appeared on your desk tomorrow This paper will help you write a professional requirements document. Once you feel you understand what a requirements document...
Words: 7624 - Pages: 31
