1 / 24

Elockbox

Detailed operational concept and transition strategy for a secure e-management system. Includes tests, support plan, and stakeholder responsibilities. Demo on security, user and case management, document handling, email, and reporting.

katyb
Download Presentation

Elockbox

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Jian Lei Role(s): Project Manager / Builder Da Lu Role(s): Prototyper / System/Software Architect Cheng 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 Elockbox Team08 Fall2014 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.

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

  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.

  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.

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

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

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

  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

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

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

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

  13. Support Plan • Objective and Assumption 1PHP, Apache, MySQL 2 Laravel 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 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

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

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

  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

  17. Quality Focal Point

  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.

  19. Traceability Matrix Traceability Matrix

  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

  21. Summary of Transition Plan Site Preparation Our 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

  22. Summary of Transition Plan 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)

  23. Summary of Transition Plan Stakeholder Roles & Responsibilities & Schedule

  24. Feedback Questions

More Related