1. Elockbox Team08 Fall2014 Jian Lei Role(s): Project Manager / Builder Da Lu Role(s): Prototyper / System/Software Architect Cheng Role(s):Feasibility Analyst / Tester Hanadi Omar A Mardah Role(s): Life Cycle Planner / UML modeler Mu Bai Role(s): Requirements Engineer / Builder Xiaochen Wang Role(s): Operational Concept Engineer / Builder Garret Catron Role(s): IIV&V / Quality Focal Point CS557A - Software Engineering

2. 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

3. Introduction ● TRR specific outline  TRR Demo  Support Plan  Test Cases, Procedures and results  Quality Focal Point  Technical Debt  Traceability Matrix  Transition Plan 3

4. 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

5. 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

6. Demo ●Security ●User Management ●Case Management ●Document Management ●Mass Email ●Report Generation 6

7. Demo - Security ●Email Verification Code ●10 minutes Session timeout ●Security questions 7

8. Demo - User Management ●Create a new user ●Edit users’ information ●Activate / Deactivate a user ●Search a user 8

9. 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

10. Demo - Document Management ●Upload documents(.pdf,.jpg,.png) ●Delete documents ●Download documents ●Print Documents 10

11. Demo - Mass Email ●Specified the recipients to include ●Select a email template ●Send out email ●Email Activity is automatically recorded 11

12. Demo - Report Generation ●Case Reporting ●Activity Reporting 12

13. Support Plan ● Objective and Assumption 1 PHP, Apache, MySQL 2Laravel web framework 3 Web development – HTML, CSS, JavaScript, JQuery and Bootstrap libraries 4 Amazon S3 5 PHPStorm/SourceTree ●Support strategies lifetime 1 Laravel framework (community support) http://laravel.com http://laravel.com 2 JQuery - http://jquery.com/ http://jquery.com/ 3 Bootstrap - http://getbootstrap.com/http://getbootstrap.com/ 4 Amazon S3 ●Release strategy, requirement determination, and Process ●Environment Support ○Hardware and Software ●Support Responsibilities 13

14. Test Cases, Procedures and Results Test all features, include old features and new features we added. Specifically, 22 Test cases in total. 14

15. Test Cases, Procedures and Results Methods we use Black box Functional testing Logic driven testing Testing Levels Unit testing System testing 15

16. Test Cases, Procedures and Results  Main features are all working well  Bugs we have found and fixed: ◦ 62 bugs found/ 60 of them fixed ◦ 22 test cases implemented/ 20 passed/2 may failed in some specific situations  Concerns: ◦ Some bugs still remains ◦ Some Inconvenience still remains ◦ New risks 16

17. Quality Focal Point 17

18. 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

19. Traceability Matrix OCDWin-WinSSADTest Case OC-1 Document Management WC_3332 TC-01 WC_3331 WC_3325UC_2 WC_3330UC_6 UC_15 OC-2 Case ManagementWC_3329UC_7 UC_12 TC-02 WC_3326UC_4 OC-3 Report GenerationWC_3324UC_3 TC-03 OC-4 User ManagementWC_3333 TC-04 WC_3327UC_1 UC_5 UC_10 UC_13 UC_9 UC_11 UC_14 UC_15 OC-5 Mass EmailWC_3328UC_8 TC-05 19

20. 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

21. Summary of Transition Plan Site Preparation Our clients have already held: ●Three domain names: https://www.mylaspace.com (.net,.org)https://www.mylaspace.com ●Digital Ocean Account ●Amazon S3 Account ●Data on Salesforce Staff Preparation: ●User Manual ●Training Material 21

22. 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

23. Summary of Transition Plan Stakeholder Roles & Responsibilities & Schedule DateRoleResponsibilityLocation 11/21/14Team,Clients,ProfessorsCCD sessionUSC campus 12/03/14TeamDeploy the systemUSC campus 12/04/14TeamProduct Archiving, Project Release USC campus 12/05/14Team,Clients,ProfessorsDCR ARBLiving Advantages Not ApplicableTeam, Clients, UsersUser TrainingNot Applicable Team, ClientsSupport and Solve problemsNot Applicable 23

24. Feedback Questions 24