1 / 36

LEMA PILOT SCHOOL INTEGRATED SCHEDULING SYSTEM

LEMA PILOT SCHOOL INTEGRATED SCHEDULING SYSTEM. TEAM 12. By David Wiggins. The Agenda. Transition Objectives and Strategy Explanation Project Completion Status Risks Data Reporting and Archiving Demo of the Website Demo of the FET Support Plan

haamid
Download Presentation

LEMA PILOT SCHOOL INTEGRATED SCHEDULING SYSTEM

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. LEMA PILOT SCHOOL INTEGRATED SCHEDULING SYSTEM TEAM 12

  2. By David Wiggins

  3. The Agenda • Transition Objectives and Strategy Explanation • Project Completion Status • Risks • Data Reporting and Archiving • Demo of the Website • Demo of the FET • Support Plan • Tasks & People involved in the Transition Plan • Site preparation • Operational Testing • Training • Evaluation • Transition Schedule & Roles

  4. Transition Objectives and Strategy Explanation • Test the system for Acceptance. • Transition the System from the “creators” to the “users”. • Train the users and maintainers so they can carry the project forward. • Equip the users with documentation to refer to when “things go wrong”.

  5. Project Completion StatusThings we’ve been waiting on • Login page and permissions • Received Team 4’s work two days ago • Kush and Sang are both working it • Student progress tracking • Waiting on Team 4 • Dragon Drawing scans from LEMA

  6. Risks

  7. Data Reporting & Archiving ThammanoonKawinfruangfukul

  8. FET Manual import schedule Export activity.csv in Schedule Management page Scheduling System SIS Import Teacher/StudentSchedule.csv in Schedule Management page Import DistrictCourseList.csv in Course Profile List page

  9. Import District Course List Scheduling System SIS FET

  10. Export activity list Scheduling System SIS FET

  11. Import Final Schedule Scheduling System SIS FET

  12. Product status demonstration

  13. System and Software Support Plan Eunyoung Hwang

  14. Support Objectives • To guide the system’s support stakeholders in successfully operating and maintaining the system • To facilitate the seamless operations once the system has been delivered to the client. • To ensure that a system and software maintainer can easily handle emergent situation after transition. • To identify the support environment on hardware, software, and facilities. • To help the smooth integration for usage with legacy system, Columbia and SIS.

  15. Support Assumptions • If system requires modification during the support period, the client will notify the project team with the stable requirements and schedules. • The client will provide all necessary resources during the support period. • Continuity of funding for Web Hosting and staffing for maintaining and operation. • The client is responsible for upgrades, operation and maintenance of the system after it is deployed

  16. Support Lifetime • The USC development team is accountable to provide seamless support for the system until the end of the semester, May 4th, 2012. • The user and technical training will be provided to the clients and maintainers with detailed support manual. • The support for COTS to provide guidelines and documents is available via their web sites as a reference.

  17. Support Responsibilities

  18. HW, SW, site, staff preparation ThammanoonKawinfruangfukul

  19. Hardware, Software, and Site preparation • Dream Host • (http://www.lemahs.net/) • FTP and SSH access • Web server supported • PHP and MySQL supported • System deployment (04/20/12) • Symfony 2.0 • Database migration • Source code • PC Host • Internet access • Windows based • System deployment (04/20/12) • Free Timingtable (FET)

  20. Staff preparation and schedule

  21. Operational TestingMark Villanueva

  22. Previous Testing Activities • Unit Testing: • Performed by developers in individual checkout area • Integration Testing: • Performed by developers on greenbay development server • Acceptance Testing: • Performed by tester on greenbay development server • Bugs are reported to bugzilla and re-tested • Only tested implemented capabilities • Still need to test constraints management, student progress tracking, Team 4 interoperability, FET

  23. Previous Testing Activities (cont.) • Planned additions to ATPC: • Add test cases for constraints management, student progress tracking, Team 4 interoperability, FET • End-to-end thread testing • Rainy-day input scenarios

  24. Operational Testing • Detailed plan: • 04/18/12-04/20/12: • Initial testing on LEMA server • Complete run-through of ATPC • Emphasis on newly implemented modules • Failed test cases become bugs • 04/20/12-04/24/12: • Interim testing on LEMA server • Performed on a clean install of the software • Test bug fixes and code changes • Full regression testing

  25. Operational Testing (cont.) • 04/24/12-04/30/12: • Formal testing on LEMA server • Clean install of software from media • Complete run-through of Test Procedures • Exercised by more than one tester using multiple web browsers • Risks: • Need more details about deployment environment for FET tool • Heavy dependency on Team 4 capability • Require time with students for focus group and stress testing • Must ensure test data is properly formatted

  26. TrainingLouis Demaria

  27. Hands on training provided to users on site during and after the installation Team members will be available for question and answer This could identify bug fixed which can be quickly resolved by development team User manual provided as part of the overall software delivery Users should have a full working knowledge of the system before the end of the CSCI577b class.

  28. Roles

  29. Training Schedule

  30. Measure of Success

  31. Training • Each stakeholder should have a clear understanding of some part of the system • Training feedback will be collected after all training is complete • We are interested in how well we performed in training each stakeholder

  32. EvaluationMark Villanueva

  33. Evaluation Plans • Focus groups: • Semi-formal drive-through and training with end users • Receive feedback on usability and reference documents • Closeout report: • Client accepts product • Notes satisfaction level and provides comments

  34. Software DeliverablesMark Villanueva

  35. Software work products • Release package: • - Complete build packaged in a .tar.gz file • Copied to once-writable media • Installed on top of default Symfony baseline • Contents: • Server-side executables • php controller modules • Non-executable files • html files for web page display • css for web page styling • Images • Client-side executables • javascript libraries • Full file listing will be added to Transition Plan

  36. THANK YOU

More Related