Wear Test Portal Systems Requirements

Transcription

1 EXECUTIVE SUMMARY PURPOSE The purpose of this document is to provide the reader with the functional and nonfunctional requirements gathered through focused interviews with stakeholders (See Exhibit 1). Through current and future system analysis data diagrams and system process models for proposed Wear Test Portal have been generated. This report represents the statement of what the system must do, and the characteristics that the system must have. SYSTEM RECOMMENDATIONS (For extended Requirements See Section 4.0 and for extended System Process Models See Exhibit 4) The system proposed is a web based portal with a database backend eliminating the duplication of work and several pain points of the current system. Project Goals - The database stores Wear Test personal information including historical Wear Test Study information and current activity preferences. - User Interface provides the ability to modify and update the database - Wear Testers can easily contact the Company X internal team High Level Pages & Functionality - Log In - Home Screen - Account Page - Wear Test History - Shipping Information - Contact Us SYSTEM COSTS (For extended Cost Analysis and Project Plan See Exhibit 6 and 7) 3 Year ROI Initial Investment: $6,540 Investment Gain: $9,060 Annualized ROI: 33.61% Intangible Costs & Benefits - Increased satisfaction and engagement with wear test community - Increased compliance for wear testers ADDITIONAL COMMENTS This portal will be public consumer facing and therefore must be in compliance with Wear Test NPPI and protecting proprietary information for the Company X Brand. RECOMMENDATION The recommendation is that Company X move forward with ALLISIN Consulting to execute the Design Phase for the cost of $1,040. 3

2 TABLE OF CONTENTS 1.0 Introduction Purpose Definitions, Abbreviations and Acronyms System Request Current System Recommended System Functional Requirements Non-Functional Requirements Data Modeling System Costs and Benefits Costs Benefits Return On Investment (ROI) Project Plan Recommendation Approval and authority to proceed Systems Analysis Phase invoice Appendix Exhibit 1: MEETING NOTES (10/25) Exhibit 2: Current System Use Case Exhibit 3: Proposed System Use Case Exhbit 4: Process Models Exhibit 5: Database Diagram Exhibit 6: Extended Project Plan & Costs Exhibit 7: Schedule By Personnel Exhibit 9: High Level Wireframes Exhibit 10: Company Description

3 1.0 INTRODUCTION This report contains the System Requirement Analysis as performed by ALLISIN Consulting for the Wear Test Portal. 1.1 PURPOSE The purpose of this document is to provide the reader with the functional and nonfunctional requirements gathered through focused interviews with stakeholders (See Exhibit 1). Through current and future system analysis data diagrams and system process models for proposed Wear Test Portal have been generated. This report represents the statement of what the system must do, and the characteristics that the system must have. 1.2 DEFINITIONS, ABBREVIATIONS AND ACRONYMS Table 1: Definitions Term Wear Tester Wear Testing Wear Test Analyst Wear Test Study Definition Community members who are sent shoes to wear on runs and provide feedback through surveys The process of identifying errors or problems with the shoes well in advance of them reaching market Member of the Wear Test Team responsible for coordination of community Wear Testers A 6-week period when a Wear Tester tests a pair of shoes for the Wear Test Analyst Table 2: Acronyms and Abbreviations Term GUI NPPI ROI WT Definition Graphical User Interface Non-Public Personal Information Return on Investment Wear Test 2.0 SYSTEM REQUEST This project has been initiated for the creation of an automated system to track and maintain information about community Wear Testers for the Company X Wear Test (WT) team. The system should allow for individual WT participants to update their own personal details without the need for the involvement of a Wear Test Analyst. Additionally, the system will increase overall communication and engagement displaying historical study records and shipping information. 3.0 CURRENT SYSTEM 5

4 The current WT Management System is housed in a non-normalized Access database. This database has over 36,000 individual Wear Test Records with over 30 fields. All updates to this database are done through a manual data entry process (See Exhibit 2). For communication purposes the team currently leverages a Facebook group and s but finds that it lacks the ability to properly facilitate communication, and even harder to enforce standards. 4.0 RECOMMENDED SYSTEM The system proposed is a web based portal with a database backend. The database will store personal information as well as historical Wear Test Study information and current activity and shoe preferences. Specific fields will be displayed to end users through a web based portal, providing a GUI to update the database. There will be integrations to an external shipping API allowing for display of shipment tracking. Additionally, the WTP will allow for Wear Testers to easily contact the Company X internal team eliminating the duplication of work and several pain points of the current system. See Exhibit 3 For Proposed System Use Case See Exhibit 4 for System Process Models 4.1 FUNCTIONAL REQUIREMENTS For High Level Wireframes See Exhibit 9 1. Log In 1.1 The system shall prompt a user for an and password if they reach the system without being logged in. 1.2 No information or navigation options shall be presented if a user is not signed in 1.3 The system shall only display user account information for logged in user 1.4 The system shall provide a logout button visible on all pages 1.5 If a user is inactive for 30 minutes the system will log out and prompt a user for their sign in credentials to re-authenticate 1.6 Log In functionality will be executed through external plug in 2. Home Page 2.1 The system shall display information about the Wear Test Program 2.2 The system shall display navigable links to the following pages Account Page Wear Test History Page Wear Test Shipping Information Contact Us Page 3. Account Page 3.1 Each wear tester will be associated with a corresponding ID 3.2 The system will allow users to access their account information page 3.3 The system will allow users to view and update their personal information including personal details, shoe preferences and frequency of certain activities Shoe Preferences will be generated from set list of brand models as set by Wear Test Analysts Frequency of Activities will be generated from a set list of activities and frequency as set by Wear Test Analysts 3.4 The system requires all form fields are completed prior to saving updated record to database If field is not completed user receives error message indicating what field is missing and record will not save 3.5 System will display confirmation to user that their updates have been saved 6

5 4. Wear Test History Page 4.1 The system will allow users to view history of studies they have participated in including: Wear Test Study Name Wear Test Start Date Wear Test End Date 4.2 If user is not currently enrolled in Wear Test Study system will display messaging to user indicating no active studies 5. Wear Test Shipping Information Page 5.1 If there is an active shipment for a user then the system shall display Shipping Number Estimated Arrival Date 5.2 If no active shipment is available for user then system shall display No Active Shipments messaging 5.3 Shipment data is hosted and integrated through an external program already existing for the Wear Test Team No data stored in Wear Test System Read only shipping information available based on Wear Tester ID 6. Contact Us Page 6.1 The system shall allow for WT to contact the Wear Test Team from the portal 6.2 A Contact Us Form shall contain the following required information Sender Name Sender Message 6.3 If the fields are not completed when a user attempts to submit the form error message will be displayed 6.4 If an invalid address is submitted an error message will be displayed 6.5 Upon successful submission of a Contact Us form a success message will be displayed to the user 6.6 The system will generate an to the wear tester at weartest@company X.com 6.7 No communication history or data shall be saved in the database 4.2 NON-FUNCTIONAL REQUIREMENTS 1. Performance 1.1 System will be monitored and meet standard BR.com web performance standards 1.2 The system shall be available for use 24 hours per day 2. Security 2.1 The WTP is only available for those are logged in 2.2 Customer information is secure 2.3 Company X Proprietary information is secure 2.4 The system shall be up to date with firewall and virus protection 3. Operational 3.1 The WTP will run on all Priority One (P1) Browsers as outlined by the Digital Products Team 3.2 The WTP must meet all current BR.com design standards 3.3 s generated by the system should not have more than 12 hours of latency 3.4 In the event of system failure customer information will be preserved 3.5 The system shall support 400 simultaneous users (average number of Wear Testers active at a time) from 8am-5pm PST and 100 simultaneous users at other times 4.3 DATA MODELING 7

6 This data modeling diagram represents the data that is used and created by the Wear Test Community Portal. To aid with requirements discovery with the Company X Team a low-fidelity data model prototype has been prepared. The diagram focuses on a logical data model, including tables and features, but not on the storing, creating, or manipulating data. For Database Model See Exhibit 5 As compared to the current system, which is housed in a non-normalized Access database, the new database is designed with four major tables D1 - Wear Tester D2 - Wear Test History D3 - Activity D4 - Shoes Preference To promote data integrity and consistency there several option lists including: Grade Type the grade of an as assigned by a Wear Test Analyst Gender type male, female or prefer not to answer Gait Type the result from analysis indicating support, neutral or other Update Source Type the source where the WT team recruited the WT Shoes Size List restricted to current size offerings from Company X for WT Trails Only Answer Yes or No indicating a WT preference for trail running Frequency of Activity - Restricted list of times per week an activity is performed Preference Rating User ranking of Company X category of shoes 5.0 SYSTEM COSTS AND BENEFITS 5.1 COSTS The WTP consists of four phases: Table 3: Phase Cost Breakdown Phase Total Cost Feasibly Analysis $80 Requirements Analysis $2,080 Design $1,040 Implementation $3,360 Total Cost $6,540 Future Phases Cost Break Down Design Phase: $1,040 Consultant fee: 10 hours *$100 + Operational team fee: 2 hours *$20 Implementation Phase: $3,360 Consultant fee: 32 hours *$100 + Operational team fee: 8 hours *$20 Operating Fees: $60/year The hardware and software will cost $60 in the first year, and it should cost $60 per year for ongoing operating fee. 8

7 For full Project Schedule & Cost Breakdown see Exhibit 6 For full Explanation of Cost Calculations see Exhibit BENEFITS The Wear Test Community Portal will reduce the working hours of operational team and save $5,200 in operational expenses annually. Moreover, calculating the amount of the potential benefits of increasing sales by improving product quality after gathering feedback from the wear testers is hard, but it undoubtedly will bring an increase in brand awareness and interest to Company X after the completion of this project. Table 4: Cost Benefit Matrix Cost Tangible - Operational Team Cost ($280) - System requirement analysis fee ($2,000) - System Design fee ($1,000) - System Implementation fee ($3,200) - Hardware and software (and upgrade fee) $60/per year Benefit Annual reduction in working hours of operational team ($5,200) Total Cost: $6,540 Intangible - Loss in Productivity while users learn new system Total Benefit: $5,200 Annually - Increase wear testers/customers satisfaction - Increase in brand equity - Increase in compliance by wear testers 9

8 5.3 RETURN ON INVESTMENT (ROI) The amount invested of the project is $6540, and the amount returned of the project is $15,600 in three years ($5,200 * 3). The investment Gain is $9,060 and the annualized three-year ROI is 33.61%. Since the potential benefits were not accounted in, the result is fairly reasonable and practical. 6.0 PROJECT PLAN After the completion of the system requirement phase, there are two more necessary phases to complete the WT portal project. ALLISIN Consulting will perform the design phase, focusing on how to develop the project and deciding exactly which system will be built aligning all components of the project. Also, system design will determine the overall system architecture, which includes the methods to store, create or manipulate date as well as the set of physical processing components and hardware. Three work items will be performed in December and done before 12/31/ Database Design 2. System Environment Design 3. Presentation Layer Design The next phase is the Implementation Phase, completing the work necessary to develop the system. This phase includes 5 major steps: 1.Build the local version system 2.Test the local version system 3.Transfer the local version system to online space 4.Usability design and testing 5.Training and transfer the system The Company X Operational Team will have one meeting during the design phase (2 WT analyst * 1 hour = 2 hours) and two meetings during the implementation phase (2 WT analyst * 2 hour = 4 hours). The target completion date for this project is 03/09/2018. For the all the personnel involved schedule, please see Exhibit 7. 10

9 7.0 RECOMMENDATION The recommendation is that Company X move forward with ALLISIN Consulting to execute the Design Phase for the cost of $1, APPROVAL AND AUTHORITY TO PROCEED We approve the project - Wear Test Portal- as described above, and authorize ALLISIN to proceed to the Design Phase. Approved By Approved By Chris Calderon Date: Hannah Shultz Note: All above are for school project and totally provided for free. The contractors DON'T take any official responsibilities for this project. Date 9.0 SYSTEMS ANALYSIS PHASE INVOICE INVOICE / Queen Anne Ave Seattle, WA Client Name: Company X Wear Test Analysis Department Address: 3400 Stone Way N, Seattle, WA Item Description Quantity Price Per Total Feasibility Report Fee 1 $ 1, (Fee Waived) $ 0.00 Analysis Report Fee 1 $ 2, $ 2, Total $ 2,

10 APPENDIX EXHIBIT 1: MEETING NOTES (10/25) Access Database Recap & Integration Most Popular Table is the Wear Test Table and Wear Test Survey Want to have users be able to update First name Last Name Address Phone Number Road Brand (From Drop Down) Road Model (From Drop Down) This is currently collected through wear test surveys, Chris will be able to provide an example for us. Reporting capabilities will all be done through integration with current reporting. No reporting will be available on the WT Portal. Pages Navigation Navigation is provided to users to easily navigate between pages on website Log In Users must provide username and password to access the site Home Page Content Authors able to add information about the Wear Test Program Account Settings Page User is able to update their information (listed above) User is able to save their updates User receives a confirmation that their updates have been saved Error handling to prevent the submission of empty or blank fields Trail Brand (From Drop Down) Trail Model (From Drop Down) High Fit Active Brand (From Drop Down) High Fit Active Model (From Drop Down) Shoe Size Wear Test History Page If user is currently enrolled in WT Survey: User is able to see current Wear Survey test name including "SEASON - PHASE - STYLE - GENERATION" (fueled by the WT table) If user is not currently enrolled in any WT surveys then display "No Active Survey Messaging" If there are historical records for a WT then display List of past survey's that a WT has participated in Date of past survey WT participated in Wear Test Shipping Information Page If there is an active shipment for a WT then display o FedEx Shipping Number o Estimated Arrival Date If no active shipment for a WT then display "no shipments" messaging Security The entire portal can only be accessed with and password No credit card or payment information will be stored on the site Passwords must meet security standards Organizational Designs must meet current Company X Design Standards Site only for North America (no translations needed) 12

11 EXHIBIT 2: CURRENT SYSTEM USE CASE 13

12 EXHIBIT 3: PROPOSED SYSTEM USE CASE 14

13 EXHBIT 4: PROCESS MODELS EXHIBIT 4.1 SYSTEM DESIGN

14 EXIBIT 4.2 LEVEL 0 DFD 16

15 EXHIBIT 5: DATABASE DIAGRAM 17

16 EXHIBIT 6: EXTENDED PROJECT PLAN & COSTS Current Phase Upcoming Phases Task<Description Feasibility<Report Client'Meeting' Report'and'presentation Analysis<Report Client'Meeting Current'System'Analysis Future'System'Requirement' Report'and'presentation Design DB'Design System'Environment'Design Presentation'Layer Implementation Local'Version'System Local'Version'System'Testing Online'System Usability'Testing Cost Feasibility*Cost* Analysis*Cost* Design*Cost Implementation<Cost "Oct 9"Oct 16"Oct 23"Oct 30"Oct 6"Nov 13"Nov 17"Dec 3"Jan 1"Feb 1"Mar Consultant'fee:'$1200'*provided'for'free Operational'team'fee:'$80 Consultant'fee:'$2000 Operational'team'fee:'$80' Spent<Cost< $80 $2,080 $2,160 Estimate'Cost:'$1,000 Operational'team'fee:'$40 Estimate'Cost:'$3,200 Operational'team'fee:'$80 Hardware'&'Software'Costs'$60 Estimated*Total*Cost:*$6,540 18

17 EXHIBIT 9: HIGH LEVEL WIREFRAMES

18 EXHIBIT 10: COMPANY DESCRIPTION ALLISIN Consulting is a successful Consulting Group located in Seattle, Washington. Tackling tough problems, designing creative solutions through technology ALLISIN Consulting has expertise spanning customer experience, technology and data analytics. 20