mission science information and data management system 3 0 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Mission Science Information and Data Management System 3.0 PowerPoint Presentation
Download Presentation
Mission Science Information and Data Management System 3.0

Mission Science Information and Data Management System 3.0

154 Vues Download Presentation
Télécharger la présentation

Mission Science Information and Data Management System 3.0

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Mission Science Information and Data Management System 3.0 Prototype Team3

  2. Team Operational Strengths/Weakness

  3. Team Technical Strengths/Weakness

  4. Open Win Conditions • Win Condition (WC_2712): As an administrator, I assign standardized names for tools, supplies and materials and consolidate multiple references to the same item. • Win Condition (WC_2594): As a student worker, I can view the inventory that have I reserved. • Win Condition (WC_2593): As a student worker, I can view the availability of material quantities and reserve them. • Win Condition (WC_2347): As an administrator, I can see available reserve and future needs of inventory. • Win Condition (WC_2346): As a student worker, I can input data so that I can save time(debug the existing problems identified on the proposal with data entry)

  5. OCD – System Purpose-- Yinlin Zhou • Allow instructors and student workers to design open-ended projects • Allow instructors to view the qualities of the programs and get feedbacks from kids. • Allow instructors and student workers to manage the inventories better.

  6. OCD – Program Model

  7. OCD – Benefit Chain

  8. OCD – System Boundary

  9. OCD- Capability Goals

  10. OCD- Level of Service Goals

  11. OCD- Organizational Goals • OG-1:Improve elementary school students’ critical thinking skills • OG-2: Increase retention in programs • OG-3: Help education organization easily report of data for funding • OG-4: Increase elementary school students’ interests in science • OG-5: Help education organization get the feedbacks from students

  12. OCD - Constraints • CO-1: Windows as an Operating System: • The new system must be able to run on Windows 7. • CO-2: Use MS Access 2010 as the tool: • The new system should be implemented on MS Access.

  13. OCD – Proposed New System Element Relationship Diagram

  14. OCD – Proposed New System Business Workflow

  15. Win-Win Agreements

  16. Top 2 High Risks to Prototype-- Yinlin Zhou • Data communication between STEM Management System and current system • Design a report subsystem to allow clients to search anything they want

  17. Prototype STEM MS MSIDMS 2.0 Other Tables Inventory

  18. Report Subsystem GUI Design

  19. Report Subsystem Search Example

  20. Implement Dynamic List Box

  21. Prototype Test 1 Result of Search STEM By Module

  22. Prototype Test 2 Result of Search Student By Activity

  23. Prototype Test 3 Result of Search STEM By Student

  24. Architecture • System Context Diagram • Behavior of the System • Use Cases ChenguangLiu

  25. System Context System

  26. Behavior of the System

  27. Use Cases • Create STEM Project

  28. Use Cases • Create STEM Project

  29. Use Cases • Create Activity

  30. Use Cases • Create Activity

  31. Use Cases • Create Survey

  32. Use Cases • Create Survey

  33. Use Cases • Search

  34. Use Cases • Search

  35. Life Cycle Plan • Strategy • Increments • Responsibility • Recourses Fei YU

  36. Life Cycle Plan • Life Cycle Strategy: • ICSM • Increments in Development phase and transition: • Construction iteration • Core Capability Drivethrough • Transition Readiness Review

  37. Current Status • As a one semester team, we are currently still in the foundation phase. • Both items in foundation phase and development phase will be planned

  38. Key Stakeholder Responsibility Fei YU Project Manager, Life cycle planner Team Management, Plan for life cycle Yunpeng CHEN Requirement Engineer, Feasibility Engineer Interact with clients. Identify requirements p Feasibility evidence Yinlin ZHOU Prototyper, Operational Concept Engineer Prototype Develop operational concept Steven Lee QFP, Requirement Engineer Identify requirements, Monitor quality during development Amy PENG Tester, Builder, UML modeler Develop the system Test the system Darin Client Give feedback for the development. Katherine LIU Software Architecture Develop Software Architecture Develop Develop system.

  39. Project Plan


  41. Feasibility Evidence • Process Feasibility • Personnel Costs • Quantitative Benefits • ROI • Major Risks • Level of Service Feasibility • Capability Feasibility YunpengChen

  42. NDI/NCS Evaluation & Analysis Process Feasibility

  43. Business Case Analysis----Personnel Costs

  44. Business Case Analysis----Quantitative Benefits

  45. Business Case Analysis----ROI

  46. Major Risks

  47. Level of Service Feasibility • Interoperability: System must be available for every student worker to manipulate on the entire system and do his own operations. According to the win-win agreements of : • WC-2593 • WC-2348 • WC-2592 • Availability: System must be available at least 12 hours a day. According to the win-win agreements of : • WC-2349 • WC-2347

  48. Capability Feasibility

  49. Darin Gray Basic Demographic: Science Coordinator, Pre-College Programs, Viterbi School of Engineering, USC Description Darin is the administrator of Mission Science Program. He coordinates the activities and manage the program budget for nine elementary and middle school-based science clubs, develop standards-based curriculum for "hands on" projects, activities and experiments. User Scenario Recently, a new national standard project-STEM has come into use. Darin needs to incorporate the new project into the system. Current system does not support the new kind of project’s organization, which is that projects include several modules, and modules are consist of several activities. Student worker can create their own activities based on the overarching idea of the project that Darin comes up with. • Attributes • Experienced in teaching and education management • Specialist of kids’ development • Goals & Aspirations • Incorporate STEM into current system • Improve current system functionality

  50. Stephanie Description Stephanie is a Science Educator that enjoys working with students in the middle school and elementary school grade levels. She is a recent undergraduate who is interested in teaching and developing middle school science curriculum. She has spent many hours volunteering and working with students in elementary and middle school classrooms. Basic Demographic: Age: 19 Undergraduate Student • Attributes • Passionate about helping kids • Good at collecting information User Scenario Stephanie is responsible for analyzing and quantify students’ answers to numerous surveys regarding the science heuristic model. She has to collect all the surveys of one activity and analyze if students learn from the activity. She is exhausted dealing with all the results of survey manually. • Goals & Aspirations • Survey management system • Reduce manual work • Extract survey searching result files