Project 3-I. System Requirements Specification Document

Transcription

1 Project 3-I System Requirements Specification Document Interrogue Polling Company, Inc. Penn State Harrisburg COMP413W Fall 2007 Version 1.0 COMP413W Consulting Group Page 1 of 14

2 [This page intentionally content-free.] COMP413W Consulting Group Page 2 of 14

3 Abstract The Interrogue Polling Company is assessing the feasibility of automating their core business of opinion survey production. This initiative has been branded, Interrogue Improvement Initiative, or Project-3I. This documents puts forth the functional and non-functional requirements for the business process automation within the scope of Project 3-I. COMP413W Consulting Group Page 3 of 14

4 Revision History Date Version Description Author 08/15/ Initial version Loretta Euler, CCG Analyst Approvals Paul Drake, President, Project Sponsor Date Prof. J. Lobur, CIO, COMP413W Consulting Group, Inc. Date COMP413W Consulting Group Page 4 of 14

5 Table of Contents 1.0 Introduction Goals and Objectives Scope of Solution Overall Description Product Context Product Features User Classes, Roles, and Characteristics Operating Environment Detailed Requirements Use Cases Non-Functional Requirements External system interfaces Quality Assurance COMP413W Consulting Group Page 5 of 14

6 [This page intentionally content-free.] COMP413W Consulting Group Page 6 of 14

7 1.0 Introduction July of this year, the Interrogue Polling Company engaged the COMP413W Consulting Group to assess the feasibility of automating their core business of opinion survey production. Corporate management has dubbed this project the Interrogue Improvement Initiative, or Project-3I. Project-3I will take place in phases, with a "go," "no-go" decision being made at the end of each phase. Project scope is limited to actual survey production and results compilation. This document provides the detailed functional requirements for the processes that will be automated within the scope of this project Goals and Objectives The leadership of the Interrogue Polling Company is concerned that the company's lack of a Web presence is causing them to fall behind their competition. Before proceeding, company leadership realizes that automation efforts are always risky. Consequently, the company must first be comfortable that a payback will be realized from this initiative. In addition to the main goal of moving into Internet space, it is believed that the talents of the staff of Interrogue Polling Company will be more effectively used when automated support is provided to it Scope of Solution In-scope processes shall be those that lend themselves easily to automation. Ideal automation candidates are those processes that deemed repetitive, have little variation between the different types of surveys, and lend themselves to procedural description by process experts. Out-of-scope processes involve the creative work that is far too complex to automate, such as formulating question phraseology and response metrics. Additional out-of-scope areas are primarily of financial character, such as billing, general accounting, and payroll. The nature of these processes is such that their automation is effectively dealt with by commercial-off-the-shelf (COTS) software. Project 3-I Scope Summary In-Scope Processes Out-of-Scope Processes 1. Survey creation Billing 2. Survey execution Accounting & Payroll 3. Survey results compilation Asset & Facilities Management COMP413W Consulting Group Page 7 of 14

8 2.0 Overall Description Project 3-I aims to automate the tedious work of survey creation, execution, and results compilation. The remainder of this document provides specifics as to the functionality that will be delivered within the scope of this project Product Context The "as-is" and "to-be" business processes employed by the Interrogue Polling Company are described in the document titled "Project 3-I Business Process Model." The software product to be built will be used within this context as a standalone aid for technical specialists (agents) who create and compile the results of public opinion surveys Product Features The first iteration of the polling software includes only the creation and maintenance of the opinion polling software. Version 2 of this document will encompass survey execution, survey results compilation, and system administration functions User Classes, Roles, and Characteristics Agent: A skilled Interrogue employee who specializes in the creation of opinion poll questions. Client: A customer of Interrogue who commissions the design, execution, and data compilation for polls or surveys. Subject: An individual who has been selected at random from a defined population who is taking part in a public opinion poll. Technician: The primary user of the survey creation software who will place survey questions on a Web form, and supply response metrics as directed by the agent. The technician also arranges for the survey to be staged on execution servers and hyperlinked by sponsoring Web pages. Usability Specialist: A person who is skilled in the creation of computer software so that it facilitates ease of use by humans, and is compliant with Section 408 of the Americans with Disabilities Act Operating Environment The software will execute within standards web browsers (Mozilla FireFox and Microsoft Internet Explorer versions 5 and later). The application software will be hosted on a central application server, and the backend database will be MySQL. COMP413W Consulting Group Page 8 of 14

9 3.0. Detailed Requirements This section describes the functional requirements for the automation that will be put in place within the initial phase of Project 3-I. Additional functionality will be provided throughout the lifetime of this project Use Cases Use cases describe how a system will be used. They describe overt behaviors. The initial work on Project 3-I is comprised by the use cases that follow. The system will consist of three principal parts: 1. Survey creation 2. Poll execution 3. Poll results compilation The functional requirements for each of these is given below: Figure 1: Overview System Use Case for Project 3-I COMP413W Consulting Group Page 9 of 14

10 3.1.1 Survey Creation General Description: Survey creation will require at least the following functions: U.1.1. New Survey U.1.2. Edit Survey U.1.3. Delete Survey U.1.4. Preview Survey Each of these is described generally in its own use case given below. Figure 2: Survey Creation Use Case COMP413W Consulting Group Page 10 of 14

11 U.1.1. New Survey General Description: An Interrogue agent and client have jointly produced a visual mock-up of the poll (survey). Within the bounds of this use case, the paper prototype is converte`d to an operational survey. Precondition: A paper mock-up of the survey is available. The user has clicked the hyperlink to invoke this program Postcondition: An electronic prototype of the survey is created. Basic Flow U1.1.1 The basic Interrogue survey template appears along with a palette consisting of controls for adding questions, answers, page breaks, icons, and other devices required to create a visually appealing user interface. U1.1.2 The user key enters question text as provided on the prototype, along with appropriate visual aids such as icons, drop-down lists, and page breaks. U1.1.3 Once complete, the user presses the [Save] button. U1.1.4 The user enters a meaningful name for the survey, and the survey is stored under that name. U1.1.5 The user selects "Exit" to terminate the program. Alternative Flow: U1.1.4.a If a survey by the name given already exists in the system, a warning is displayed, and the user may overwrite or supply a different name for the survey. U1.1.4a. If the survey has not been saved, a warning is issued to that effect, and the user is given the opportunity to save the survey. U1.1.5.b. The user may close the browser at any time. If unsaved changes have been made, a warning is issued, and the user is given the opportunity to save the survey. U.1.2. Edit Survey General Description: A survey or prototype survey is modified until all interested parties are satisfied. Precondition: An electronic prototype of a survey has been created and someone has identified a need to change its behavior or appearance. Postcondition: A corrected survey (or prototype survey) is available. Basic Flow U1.2.1 The user is presented with a list of surveys from which one is selected for editing. COMP413W Consulting Group Page 11 of 14

12 U1.2.2 A palette is displayed consisting of controls for adding questions, answers, page breaks, icons, and other devices required to create a visually appealing user interface. U1.2.3 The user key enters new question text as needed, along with making changes to visual aids such as icons, drop-down lists, and page breaks. U1.2.4 Once complete, the user presses the [Save] button. U1.2.5 The user selects "Exit" to terminate the program. Alternative Flow: U1.2.4.a The user has the option to "save as" a different name. If a survey by the name given already exists in the system, a warning is displayed, and the user may overwrite or supply a different name for the survey. U1.2.5a. If the survey has not been saved, a warning is issued to that effect, and the user is given the opportunity to save the survey. U1.2.5.b. The user may close the browser at any time. If unsaved changes have been made, a warning is issued, and the user is given the opportunity to save the survey. U.1.3. Delete Survey General Description: A survey or prototype survey is removed from the system. Precondition: An electronic prototype of a survey has been created and someone has decided that it is no longer needed. Postcondition: The survey (or prototype survey) is removed from the system. Basic Flow U1.3.1 The user is presented with a list of surveys from which one is selected for deletion. U A confirmation message is provided giving the option to cancel the deletion. U1.3.3 The user presses the [Delete] button. U1.3.4 The user selects "Exit" to terminate the program. Alternative Flow: U1.3.2.a The user cancels the deletion. U1.3.4.a. The user may close the browser at any time. COMP413W Consulting Group Page 12 of 14

13 U.1.4. Preview Survey General Description: A prototype survey is executed in a sandbox environment to simulate the subjects' experience, but without making updates to any persistent data structures. Precondition: An electronic prototype of a survey has been created and a preview of it has been requested Postcondition: The survey (or prototype survey) has been executed. Basic Flow U1.4.1 The user is presented with a list of surveys from which one is selected for execution. U The survey is invoked and the user (tester) enters answers to exercise the survey form. U1.4.3 The user indicates that the test is complete. Results to that point entered are written to a temporary text file that can be viewed if needed. U1.4.4 The user selects "Exit" to terminate the program. Alternative Flow: U1.4.4.a. The user may close the browser at any time Survey execution General Description: A survey is executed from a Web server and the results are stored for later analysis. The following functions will be required: U.2.1. Display Survey U.2.2. Save Incomplete Survey U.2.3. Retrieve Incomplete Survey U.2.4. Download Survey Data Each of these is described generally in its own use case to be specified in a subsequent version of this document Survey results compilation General Description: After a survey has been completed, or it has otherwise been determined to do so, the results of a survey are analyzed and printed. At minimum, the following functions will be included: U.3.1. Transfer data to analytical server U.3.2. Set up analytical parameters as specified by the client U.3.3. Produce reports as requested by the client Each of these is described generally in its own use case to be specified in a subsequent version of this document. COMP413W Consulting Group Page 13 of 14

14 3.2. Non-Functional Requirements Surveys displayed on the Web must be compliant with Section 408 of the Americans with Disabilities act Surveys executed on the Web that have been stored by the user and retrieved later must be secured by a password. No traces of data identifying a particular user will be accessible by anyone other than the user Response time during survey execution for full page refreshes shall not exceed 5 seconds 90% of the time when the survey is accessed over the public Internet when the Web browser is connected at 640Kbps External system interfaces The survey execution function will be able to exchange data with the DataSource Inc.'s system that generates names, addresses, and addresses of potential survey takers. 4.0 Quality Assurance The functional modules of Project 3-I will be acceptable to the project sponsors when: 1. Surveys can be created, updated, deleted, and tested. 2. Surveys can be executed by poll takers over the Internet. These polls will be sufficiently user friendly as to keep the survey abandonment rate under 10%. Users wishing to save their surveys and restart them later may do so with a failure rate of less than 1%. 3. Survey data will be available for analysis at the conclusion of the survey and will be 100% in agreement with the selections that were made by the user. Various automated test tools will be utilized to assure that these testing goals are met. "User friendliness" will be measured by the use of focus groups drawn randomly from a sample set of Internet users provided by DataSource Inc. COMP413W Consulting Group Page 14 of 14