1 / 63

Mission Science Information and Data Management System 3.0

Mission Science Information and Data Management System 3.0. Transition Readiness Review. Team 3. Overview. Introduction of TRR Demonstration Support Plan, Test and Quality Focal Point Summary of the Transition Plan. Brief Introduction to Our Project.

remy
Download Presentation

Mission Science Information and Data Management System 3.0

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. Mission Science Information and Data Management System 3.0 Transition Readiness Review Team 3

  2. Overview • Introduction of TRR • Demonstration • Support Plan, Test and Quality Focal Point • Summary of the Transition Plan

  3. Brief Introduction to Our Project • We are building (improving) a database. • The main goal is to add a new sub-system for a kind of newly created open-ended courses. • Sub-goals are fixing current defects, improve user experience. MSIDMS 2.0 STEM MS Activity Survey MSIDMS 3.0 Search

  4. Core Requirement New MS STEM System Old System STEM Idea Activity1 Module2 Module1 Activity2 Activity3 Activity1 Activity2 Activity4 Activity3 Activity4 Survey Survey Survey Survey

  5. Core and Related Requirements • New system to store and manage data for new course • Inventory defects • Duplicate, Storage size limitation, Reserve

  6. Core Capability Accomplishment • We fulfilled all core win-conditions • Implemented a fully functional new system that is compatible with the original one. • Added new functions with more user-friendly interface

  7. Core Capability Accomplishment (cont.) • Pay back most technical debts remained in the system. • Tool Name duplicate defects • Inventory management defects • MS Access file size 2GB limitation.

  8. Support Service • If there is no CSCI 577b group taking this MS in the next semester, we will act as the maintainer for the next semester. • Any problems encountered ( bugs ) will be managed. However, adding new features might not be feasible.

  9. TRR Outline • Demonstration of the Current System • Based on some daily operations • Support Plan, Test Cases Report and Quality Focal Point • Summary of Transition Plan

  10. Transition Objective • Teach our main client comprehensively about our system and client knows how to use all functions. • Merge the currently in used database with the developmental database • Operational Testing

  11. Transition Strategy • Focus on the main client ( Darin ) and student workers will learn how to use the system from our main client. • Tentative merging before finalized deployment. • Observation at operational testing.

  12. Demonstration Yinlin Zhou

  13. Overview • Core capabilities and relative win-condition • Accomplishment and current situation • Start Demonstration

  14. Capability Goals & relative win-condition • OC-1: STEM Project Management • OC-2: Survey Report System • OC-3: Inventory Management • OC-4: Assign Next Generation Science Standards • OC-5: Check Completeness of Student Data

  15. Capability Goals & relative win-condition OC-1: STEM Project Management STEM Project Details Activity Modify Create Create Modify

  16. Capability Goals & relative win-condition OC-2: Survey Report System School Year Survey Create Survey Modify Activity Survey Collect Answers

  17. Capability Goals & relative win-condition OC-3: Inventory Management

  18. Capability Goals & relative win-condition OC-3: Inventory Management Merge Duplicate Reservation Inventory (Fix Current Bugs) Search Inventory Pictures Add Check Availability

  19. Capability Goals & relative win-condition OC-4: Assign Next Generation Science Standards Add Create Next Generation Science Standards Activity Modify Modify

  20. Capability Goals & relative win-condition OC-5: Check Completeness of Student Data Check Completeness Student data

  21. Accomplishment and current situation • We have accomplished all of the requirements, except reservation part. • Functions that were completed: • Create, Modify STEM Projects and Activities • Create, Modify Surveys and Collect Results from Surveys • Add, View Availability of Inventories, Merge Duplicate ones in Database, Look up Pictures of Inventories

  22. Accomplishment and current situation Demo: - Student Sign-in: Fill in Student Sign-in Sheet Instructors Create School Year Survey - Create STEM Project: Create STEM Project Instructors Create Activity Students Workers Create Activity Survey

  23. Accomplishment and current situation Demo: - Student Sign-in: Fill in Student Sign-in Sheet Instructors - Create STEM Project: Create STEM Project Instructors Students Workers Create Activity

  24. Accomplishment and current situation Demo: - Create School Year Survey: Create School Year Survey Instructors - Create Activity Survey: Students Workers Create Activity Survey

  25. Accomplishment and current situation Demo: - Collect School Year Survey Results: Input School Year Survey Results Instructors - Collect Activity Survey Results: Students Workers Input Activity Survey Results

  26. Accomplishment and current situation Demo: - Modify STEM Project: Modify STEM Project Instructors Students Workers Modify Activity - Modify Survey Questions: Modify School Year Survey Questions Instructors Students Workers Modify Activity Survey Questions

  27. Accomplishment and current situation Demo: - Add Inventory: Student Workers Add Inventory - View Inventory Reservation: Students Workers View Inventory Reservation

  28. Accomplishment and current situation Demo: - Fix Problems (Duplicated Name of Tools): Student Workers Tool Merge - Look up Tool Pictures Students Workers Tool Pictures Look up

  29. Support Plan Yunpeng Chen

  30. Support Plan Software and Hardware

  31. Support Plan - Training • Our strategy on training is to help our client to operate on the system, he can learn how to use it under our guidance. Then, he can teach student workers about how to use our system • If they have some problems while using the system, they can contact us. We will provide training till next semester.

  32. Support Plan - Maintenance • If a team is assigned to take over the system next semester, we don’t need to do anything else after training. • If not, we will maintain the system for next semester and solve unexpected bugs in existing system.

  33. Test Plan and Test Results Jingwen Peng

  34. Overview • Test Case • Test Procedure • Test Result

  35. Test Cases

  36. Integration Testing – Big Bang Integration Test Procedure All STEM Project Utility Activity Survey Inventory

  37. Test Procedure- Input Data -Positive Testing -Negative Testing

  38. Test Procedure -Dependency Graph

  39. Test Procedure - Rate BI, Fail Probability, Criticality

  40. Test Procedure –Prioritization -Value First: TC-01-05 Create STEM Project= >TC-03-04 Create Activity (Instructor) > TC-05-06 Create Activity (Student Worker)>…… -Dependency Second: TC-01-05 Create STEM Project

  41. Test Result

  42. Quality Focal Point Steven Lee

  43. Metrics Reporting: Defect Status A majority of the bugs resulted from client/developer requests to modify the GUI to increase system usability and final acceptance testing. ARB CCD

  44. Metrics Reporting: Burndown Chart CCD DCR

  45. Technical Debt: Resolved (Part 1) Old System (Inherited): • (Bugzilla ID 361) Limited Memory Storage: Table used to store pictures, now they store links • (Bugzilla ID 362) Duplicate Tool Names • Tool Addition: Tools used to be added by direct modification to the database tables. Now a user interface is available to make tool additions/modifications.

  46. Technical Debt: Resolved (Part 2) New System: • (WC_2592) Blank Student Data • Create/Modify STEM: changed the user interface (must click to create versus direct modification table) • (GUI Design Change) All Textboxes converted to Combo Box: Enable auto-fill once partial information is inputted.

  47. Technical Debt: Unresolved • Distinct project/activity modification methods for old and new (newly created GUI) system. • Tool Inventory: the tool name is the key, instead of tool ID. • Tool Inventory: Tool <-> Project Relationship Table duplicates information that is found in other tables. • (Bugzilla ID 363) Student Name duplicate detection function instability • (Bugzilla ID 856) Blank Standard add error

  48. Traceability Matrix (Part 1)

  49. Traceability Matrix (Part 2)

  50. SummaryofTransitionPlan (Part 1) ChenguangLiu

More Related