ElockboxTeam08

Fall2014

Jian LeiRole(s): Project Manager / Builder

Da LuRole(s): Prototyper / System/Software Architect

Cheng ChengRole(s):Feasibility Analyst / Tester

Hanadi Omar A MardahRole(s): Life Cycle Planner / UML modeler

Mu BaiRole(s): Requirements Engineer / Builder

Xiaochen WangRole(s): Operational Concept Engineer / Builder

Garret CatronRole(s): IIV&V / Quality Focal Point

CS557A - Software Engineering

Introduction● Operational concept overview

E-lockbox e-management system.

E-lockbox is important to be secure and usable.

The capabilities are similar to the one on Salesforce.

2

Introduction● TRR specific outline

TRR Demo Support Plan Test Cases, Procedures and results Quality Focal Point Technical Debt Traceability Matrix Transition Plan

3

Introduction● Transition objective

Full capabilities meets requirements.

Deploy the system on the server

Successful training the system functionalities.

Check and provided some feedbacks from clients.

Delivering system source codes for future maintain.

Packaging up all documentations and UML diagrams.

4

Introduction

● Transition Strategy

The alpha tests

The system is running on developers’ virtual web-server machines.

The beta tests

The system is conducted on client’s server.

5

Demo

● Security● User Management● Case Management● Document Management● Mass Email● Report Generation

6

Demo - Security

● Email Verification Code● 10 minutes Session timeout● Security questions

7

Demo - User Management

● Create a new user● Edit users’ information● Activate / Deactivate a user● Search a user

8

Demo - Case Management

● Create a new case● View the case● Edit Basic Information● Edit Services● Add/Edit Address

Information● Add/Edit Additional

Contacts● Add/Edit Emergency

Contacts

● Add/Edit Education History● Add/Edit Work History● Add/Edit Activity● Add vital documents● Add/Edit Accounts● Add/Edit Youth Services

9

Demo - Document Management

● Upload documents(.pdf, .jpg, .png)● Delete documents● Download documents● Print Documents

10

Demo - Mass Email

● Specified the recipients to include● Select a email template● Send out email● Email Activity is automatically recorded

11

Demo - Report Generation

● Case Reporting

● Activity Reporting

12

Support Plan

● Objective and Assumption1 PHP, Apache, MySQL2 Laravel web framework3 Web development – HTML, CSS, JavaScript, JQuery and Bootstrap libraries4 Amazon S35 PHPStorm/SourceTree

● Support strategies lifetime 1 Laravel framework (community support) http://laravel.com

2 JQuery - http://jquery.com/3 Bootstrap - http://getbootstrap.com/4 Amazon S3

● Release strategy, requirement determination, and Process● Environment Support

○ Hardware and Software

● Support Responsibilities

13

Test Cases, Procedures and Results

• Test all features, include old features and new features we added.

• Specifically, 22 Test cases in total.

14

Test Cases, Procedures and Results

• Methods we use Black box Functional testing Logic driven testing• Testing Levels

Unit testing System testing

15

Test Cases, Procedures and Results

Main features are all working wellBugs we have found and fixed:

◦ 62 bugs found/ 60 of them fixed◦ 22 test cases implemented/ 20 passed/2 may failed

in some specific situationsConcerns:

◦ Some bugs still remains◦ Some Inconvenience still remains◦ New risks

16

Quality Focal Point

17

Technical Debt

● Mass Email sender address is hardcoded● Captcha functionality developed but disabled

because it caused errors with the rest of the site.● Coding format is inconsistent from multiple

developers.

18

Traceability Matrix

Traceability MatrixOCD Win-Win SSAD Test Case

OC-1 Document Management

WC_3332 TC-01

WC_3331

WC_3325 UC_2

WC_3330 UC_6 UC_15

OC-2 Case Management WC_3329 UC_7 UC_12 TC-02WC_3326 UC_4

OC-3 Report Generation WC_3324 UC_3 TC-03OC-4 User Management WC_3333 TC-04

WC_3327 UC_1 UC_5 UC_10

UC_13 UC_9 UC_11 UC_14 UC_15

OC-5 Mass Email WC_3328 UC_8 TC-0519

Summary of Transition Plan

Hardware Preparation● Amazon S3 as storage

● Digital Ocean as host and server● No hardware

Software Preparation● Transfer all codes and documents to bitbucket and help our

clients or maintainers to learn it

● Linux, MySQL, Apache, PHP in the host server

20

Summary of Transition Plan

Site PreparationOur clients have already held:

● Three domain names: https://www.mylaspace.com (.net, .org)

● Digital Ocean Account● Amazon S3 Account● Data on Salesforce

Staff Preparation:● User Manual

● Training Material

21

Software Product Elements● Code● Documents: OCD, FED, LCP, SSAD, TPC, UM, TP, TM, SP ● Data imported from Salesforce

Milestone Plan:● Delivery of the system● Data transition from Salesforce● Trainings (admin, case manager, general user, youth user)

Summary of Transition Plan

22

Summary of Transition PlanStakeholder Roles & Responsibilities & Schedule

Date Role Responsibility Location

11/21/14 Team,Clients,Professors CCD session USC campus

12/03/14 Team Deploy the system USC campus

12/04/14 Team Product Archiving, Project Release

USC campus

12/05/14 Team,Clients,Professors DCR ARB Living Advantages

Not Applicable Team, Clients, Users User Training Not Applicable

Not Applicable Team, Clients Support and Solve problems Not Applicable

23

FeedbackQuestions

24