TRANSITION READINESS REVIEW

GOTRLA

TEAM 15Aayush Jain, Ankith Nagarle, Anushila Dey, Deepak

Earayil, Elaine Lo, Nidhi Baheti, Presha Thakkar, Suhani Vyas

Operational Concept Review

System Purpose• Establish a better Attendance

Tracking system.• Enables better monitoring of the

program leading to improved program quality.

System Boundary Diagram

Expected Business Workflow

Desired Capability GoalsCapability Goals Priority Goals

OC-1 Student management: The system is capable of adding/editing and deleting girl’s data.

Must have

OC-2 Volunteer management: The system is capable of adding/editing and deleting data of volunteer coaches.

Must have

OC-3 Class Management: The system is capable of Adding/Editing and Delete classes.

Must have

OC-4 Attendance Tracking: The system shall provide the methods to check-in the girls and store the attendance data.

Must have

Organizational Goals

Organizational Goals• OG-1: Improved Attendance Monitoring • OG-2: Reduced Paperwork for attendance• OG-3: Better tracking of program quality• OG-4: Increased support to teams having

issues.

TRR SPECIFIC OUTLINE

• Current Project Status– Web application (90% complete)– 1 win condition pending (WC_3425)– Mobile application (90% complete)– 1 win condition pending (WC_3262)

Transition Objectives

• Two Phased transition plan - Beta testing phase and training phase.

• Post transition support - Will provide support till 12/31/14.

• Nature of product transition - New System

Transition Strategy

• Beta Testing Phase - 12/01/14 - 12/05/14– Beta Testing by the client and program staff– The application has been hosted on the live

server. – 12/01/14 - 12/05/14 is the beta testing phase..

• Training Phase - 12/07/14 - 12/12/14– Training Program Staff– Refine User Manual

PRODUCT DEMO

WIN CONDITIONS• WC_3425: As a user (Admin, Program staff, volunteer) I can reset/update

my account password so that I can login to the system • WC_3281: The system shall be easy and intuitive to use

• WC_3279: The system shall be accessible via a desktop and mobile device

• WC_3280: The system shall be down for no more then 3 to 5 hours a month and preferably not after school hours.

• WC_3278: As a staff member I can export (first name, last name, team name (classes), attendance, date (week number)) the data (excel, csv) for each roster from the system so that we can analyze the attendance data

WIN CONDITIONS• WC_3478: The system shall be easily monitored and maintained

• WC_3277: As an Admin I can add/Remove/Edit Program staff & should have all the privileges of the program staff so that Security of the system is maintained.

• WC_3276:As a volunteer I can Login to the mobile application so that I can access the system

• WC_3275: As a GOTRLA staff member I can Login to the system so that I can access the system

• WC_3274: As a volunteer I can access the schedule of the program weeks so that I know when to conduct the classes.

WIN CONDITIONS• WC_3273:As a GOTRLA staff member I can schedule the program weeks so

that coaches know when to conduct the classes.

• WC_3271: As a GOTRLA staff member I can Add/Update and Delete volunteer coaches for each class so that We can monitor attendance of the volunteers and support the team roster when required.

• WC_3270: As a GOTRLA staff member I can Add/Edit and Delete girls data so that the coaches can take attendance

• WC_3269: As a GOTRLA staff member I can Add/Edit and Delete classes so that we can Volunteers have up-to-date information

• WC_3266: Maximum Budget : $750

WIN CONDITIONS• WC_3265: As a Staff member I can monitor which girls have turned in

paper work/payment so that we have their copy liability waiver forms.

• WC_3264: As a admin , I can identify the which girl's paper work/payment is done so that we have their copy liability waiver forms

• WC_3263: As a GOTRLA program staff member, I can regularly and immediately check each site's attendance sheet, so that I can offer support to any teams having issues immediately.

• WC_3262: As a volunteer coach, I can check in the girls and other coaches on my roster remotely and in real time, so that GOTRLA staff can monitor program quality immediately and efficiently

ADDITIONAL FUNCTIONALITIES• Search - As a staff member or admin, I can search through the data

to see if it contains any of the search value - TC-02-03, TC-03-03

• Sort - As a staff member or admin, I can sort that data alphanumerically - TC-02-03, TC-03-03

• Pagination - As a staff member or admin, I can choose how many records to be displayed on each page

• Import TC- As a staff member or admin, I can import teams or girls data from CSV files to populate the database TC-02-05, TC-03-05

SUPPORT PLAN

SUPPORT OBJECTIVE• The objective of this support plan is to guide the

support of GOTRLA application.• To provide good customer satisfaction.• The volunteer coaches are able to use the

application to check in girls attendance.• The admin and program staff is able to

manage/monitor the data using the web application.

• Trouble shoot bugs in the system as quickly as possible.

ASSUMPTIONS FOR SUPPORT PLAN• The team might provide new releases after TRR

– Regarding the client concerns and bug fixes (mostly related to user interface).

– Missing points of the system(remaining issues) will be discussed with client and added into Support Plan document.

• The support will be intermediate.• If client/maintainer has any questions about the system

we will try our best to answer them via– Telephone– Email

• The Support plan will be referred by the staff only after undergoing basic training to use the system.

SUPPORT PLAN (cont’d)

• The documents required are given with final deliverables to the client.– Database Schema, GitHub repository, Source code

with comments and other resources (system database including sample data)

SUPPORT ENVIRONMENT

Server Side Requirements:• Server : Yahoo Web Hosting• Memory: 500 GB Diskspace• Data transfer: 5000 GB per month • I/O Devices for Maintenance Issues

User Side Requirements• Internet Connection• Web Browser(chrome/safari/firefox)• I/O Devices to operate Web Browsers properly.

TEST CASES, PROCEDURES AND RESULTS

TEST CASESID Test Case

TC-01 Website access― TC-01-01 Check access to web interface

TC-02 Admin role― TC-02-01 Check admin login to web interface― TC-02-02 Check admin accessibility to site and data― TC-02-03 Admin is able to view/search/sort data― TC-02-04 Admin is able to add/edit/delete data― TC-02-05 Admin is able to import data from CSV

TC-03 Program staff role― TC-03-01 Check program staff login to web interface― TC-03-02 Check program staff accessibility to site and data― TC-03-03 Program staff is able to view/search/sort data― TC-03-04 Program staff is able to add/edit/delete data― TC-03-05 Program staff is able to import data from CSV

TEST CASESID Test Case

TC-04 Volunteer coach role― TC-04-01 Check access to mobile application― TC-04-02 Check volunteer coach login to mobile application― TC-04-03 Check volunteer coach accessibility to application and data― TC-04-04 Volunteer coach is able to edit attendance

TC-05 Generate report summary― TC-05-01 Check report completeness/correctness― TC-05-02 Check report export

TC-06 Resetting/Updating password― TC-06-01 Reset password from web application― TC-06-02 Reset password from mobile application

TC-07 Rainy day cases― TC-07-01 Multiple coaches record attendance― TC-07-02 Attendance is recorded but then a girl shows up late― TC-07-03 Error handling

TEST PROCEDURE

• Unit testing• Integration testing• System testing

TEST RESULTS

• 22 test cases – 3 bugs• Bugs found

– #591 - Sorting on names is dependent on case – #592 - When sorting on numbers, double digit

values get sorted by their first value and then second value

– #593 – missing reset password functionality

QUALITY FOCAL POINT

TECHNICAL DEBT

• Addition of Import Feature

• Change in the required format of the input file

TRACEABILITY MATRIXPriority Win

ConditionRequirements Use Case Test Case Verification

Type1 WC_3269 OC-3, CR-2 UC-3 TC-03-03,

TC-03-04Testing

2 WC_3270 OC-1, CR-2 UC-3 TC-03-03, TC-03-04

Testing

3 WC_3277 CR-1 UC-2 TC-02-02, TC-02-03, TC-02-04, TC-03-02

Testing

4 WC_3271 OC-2, CR-2 UC-3 TC-03-03, TC-03-04

Testing

5 WC_3265 OC-1 UC-5 TC-03-03 Testing

6 WC_3279 PR-1 UC-1 TC-01-01, TC-04-01

Testing

7 WC_3268 CR-3 UC-8 TC-04-03 Testing

8 WC_3276 PR-1 UC-1 TC-04-02 Testing

9 WC_3278 OC-4 UC-4 TC-05-02 Testing

TRACEABILITY MATRIX Priority Win

ConditionRequirements Use

CaseTest Case

Verification Type

10 WC_3263 OC-4 UC-6 TC-05-01 Testing

11 WC_3425 CR-4 UC-7 TC-06-01, TC-06-02

Testing

12 WC_3275 PR-1 UC-1 TC-02-01, TC-03-01

Testing

13 WC_3281       Demonstration

14 WC_3274 CR-3 UC-8 TC-04-03 Testing

15 WC_3273 OC-3, CR-2 UC-3 TC-03-04 Testing

16 WC_3266       Analysis

17 WC_3280       Analysis

18 WC_3262 OC-4, CR-3 UC-8 TC-04-04, TC-07-01, TC-07-02

Testing

SUMMARY OF TRANSITION PLAN

HARDWARE PREPARATION

• We are using the Yahoo server to host the web application • Hence no hardware preparation is needed at client's site.• The mobile application would be hosted on the Apple

store and Google play store respectively.• The volunteers who are the users of the mobile

application need to download the application on their smart phones

• Thus, there is no need to purchase any additional hardware and no staff time is required for hardware preparation.

SOFTWARE PREPARATION

• The web application can be accessed via a browser.

• The administrator needs to add other program staff members once the system is completely delivered.

• The client does not have any legacy software and hence there would be no compatibility issues with the new system.

SITE PREPARATION

• As the staff would be using the system through their current computers. We do not need any special setup to run the system.

• As long as there is a working internet connection the system is ready to be used.

• However, it is necessary for the volunteers to download and install the mobile application to record the attendance.

STAFF PREPARATION

• Our client might require to hire a maintainer(developer) in the future.

• We will create a new developer guide which would help any new developer understand how the system works and how to make changes to it if necessary.

Operational Testing

• Testing Cycle– User Acceptance Testing– Client Feedback - Issues Reported– Fix issues– Deploy

• Alpha Testing - Ongoing• Beta Testing - Pending

Operational Training• 11/20/14 - The client was familiarized with the basic functions of the web

application.

• 12/01/14 - The client and program staff will be given a review of the application.

• 12/01/14 - The client will be provided with credentials to use the application.

• 12/01/14 - The client will be provided with User Manual and Training Plan

• 12/08/14 - 12/12/14 - Training provided to the staff using the user manual.

Operational Evaluation• Client Feedback on product satisfaction

• Win conditions satisfied - WC_3281, WC_3478, WC_3280, WC_3278, WC_3277, WC_3276, WC_3275, WC_3274, WC_3273,

• Pending Win conditions - WC_3425, WC_3262

STAKEHOLDER ROLES AND RESPONSIBILITIES

Date Role Responsibility Location11/26/14 Client Purchase a domain to host web application Client's site

11/30/14 Team-15 Host the application on the server Team Location12/01/14 Team-15 TRR Presentation USC12/05/14 Team-15 To perform testing before final

delivery/transitionTeam Location

12/09/14 GOTRLA staff and Team-15

Provide training to all the staff members of the client and to the volunteers

Client's site

12/09/14 Team-15 Collect User feedback and measure of success

Client's site

12/09/14 Volunteers Download the GOTRLA mobile application

Client's site

12/15/14 Team-15 Hand-over the complete system to the client

Client's site

12/31/14 Team-15 Provide Technical support to the client Client's site

MILESTONE PLAN

• Transition Period : 11/26/14 – 12/31/14• Necessary Tasks

– Finish documents– Finish testing the system– Finish up final feature additions– Train client– Hand over system/ deploy system to client

SOFTWARE PRODUCT ELEMENTS

– User Manual– Training Plan– Transition Plan– Test Plan and Cases– Prototype Presentation– System and Software Architecture Description– Feasibility Evidence Description– Operational Concept Description– Life Cycle Plan

REQUIRED RESOURCES

• Hardware• Software• Initial data to provide product demo• Training Material• Stakeholders

FEEDBACK

THANK YOU