1 / 75

Mission Science

Mission Science. By Team 07. Team 07 Members. Ashwini Ramesha : OCE Chen Li : Requirements Engineer Jiashuo Li : Prototyper Ritika Khurana : Project Manager Siddhesh Rumde : Life Cycle Planner Sowmya Sampath : Software Architect Yun Shao : Feasibility Analyst

aaronbrown
Download Presentation

Mission Science

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 By Team 07

  2. Team 07 Members AshwiniRamesha: OCE Chen Li: Requirements Engineer JiashuoLi :Prototyper RitikaKhurana: Project Manager SiddheshRumde: Life Cycle Planner SowmyaSampath: Software Architect Yun Shao : Feasibility Analyst Farica Mascarenhas : IV & V

  3. Strong and Weak points Strengths Weaknesses • Peer review • Collaborative, supportive • Online tools • Client communication • Remote student availability • Time constraints due to heavy course load

  4. Overall Project Evaluation • Identified new requirements • Identified new risks • Developed functional prototype for navigation programmability • Started Construction Phase

  5. AshwiniRamesha Operational ConceptDescription

  6. Current Workflow 5

  7. Purpose, Vision & Proposed Workflow 6

  8. Business Workflow 7

  9. Benefit Chain Diagram 8

  10. System Boundary Diagram 9

  11. Capability Goals • OC-1 Navigation programmability: Fun-to-use interface to help elementary school children learn programming to control navigation of iRobot. • OC-2 Sensor programmability: Fun-to-use interface to help elementary school children learn programming to control navigation of iRobot. • OC-3 Loop and wait constructs: The interface shall allow drag & drop of programming constructs like if-then-else, for and while loops. • OC-4 Sounds and light programmability: The interface shall allow drag & drop of musical notes and LED on/off instructions. • OC-5 Demo mode programmability: The interface shall allow drag & drop of pre-programmed demo modes. 10

  12. Levels of Service Goals • LOS-1: Seamless interoperability between GUI and compiler. • Win condition: The system shall generate instructions for iRobot in C which is then later compiled for deployment on the microcontroller using the APIs of iRobot. • Measure: Number & severity of faults found in code generation & compilation modules. • LOS-2: Detect and report ambiguous instructions in an understandable way. • Win condition: The system shall detect and show logic errors (conflicting/inconsistent instructions) in a easy-to-understand way. • Measure:Feedback from stakeholders like undergraduate students and elementary school teachers on the framed help & error messages. • LOS-3:Reasonable frequency of reading sensor data. • Win condition: The system shall enforce a tolerance limit of +/- 2 to 3% error in angle of turning. • Measure: Manual testing and recording results for variety of sample inputs. • LOS-4:Portability above Windows 7 • Win condition: The system shall be a native windows 7 and above application. • Measure: Regression test results on the windows versions above 7. 11

  13. Organizational Goals • OG-1:Generate more excitement toward STEM fields. • OG-2:Widen the user sector for iRobot. • OG-3:Improved understanding in students about logic and control systems. • OG-4:Decrease time needed to program iRobot to execute complex instruction set. • OG-5: Use of iRobots to improve funding opportunities for Mission Science. 12

  14. Constraints • CO-1:Windows as an Operating System: The new system must be able to run on Windows 7/8/8.1 • CO-2: Zero Monetary Budget: The selected NDI/NCS/COTS should be free or no monetary cost. • CO-3: C#as a Development Language: Visual studio C# will be used as a development language for the Drag & Drop GUI interface. 13

  15. Jiashuo Li Prototype

  16. What we have prototyped • Drag & Drop Operation which is the main capability of the system • Easy for kids to program • Instruction with parameters • FORWARD 0.3 1 • Workflow (Functioning) • Create (Open) • Compile & Load • Run • Translate Program to C • Win AVR Integration • Debugging Interface Time Distance 15

  17. Instruction Candidates Program Parameters: The parameters of each instruction Debugging Interface Load default program Show text source code More COLORS 4-Panel Interface 16

  18. Build and Load 17

  19. Win AVR Integration 18

  20. Risks, Problems and Mitigation • Low sensor resolution -> Cannot rotate accurately • Try using script command • Find the sweet point for sensing • Ineffective development tools • Contact manufacturers • Build Microcontroller simulation environment • Kids may lost their interest • Ask for what they want 19

  21. Chen Li Requirements

  22. ESS(MostsignificantRequirements) 21

  23. System 22

  24. ImplicitRequirements • Prepareuserguide • Preparetroubleshootingguide 23

  25. SowmyaSampath Architecture

  26. Use Case diagram 25

  27. Hardware Component Diagram 26

  28. Software Component Diagram 27

  29. Deployment Diagram 28

  30. Design Class Diagram 29

  31. Sequence Diagram 30

  32. Siddhesh Rumde Life Cycle Plan

  33. Modified since FCR ARB Modules Estimation Plans for 577b Re-baseline Foundation Phase Iteration 1 Core Capability Iteration 2 Full Capability Transition Iteration Overview 32

  34. Prototype 33

  35. Modules 34

  36. Estimation • Total SLOC estimated : 3953 lines • Most Likely effort: 11.51 PM • 11.51/1.67=6.89 person • 7 members in 577b 35

  37. Skillset of New Members • UI/UX Design • C and C# Programming • Good Analytical Skills • Visual Studio 36

  38. Re-baseline Foundation (Jan 12 - Feb 11) • Re-baseline the project (Jan 13-Jan17) • Requirement Requirement Engineer • Prototype Prototyper • Architecture Architect • Plan for testing Tester • Prepare Products for RDCR (Jan 23-Feb 5) 37

  39. Construction Iteration 1 (Feb10 - Mar26) • Duration: Feb 10  Mar 26 • Modules: • Navigation • Sensor • Light & Sound • Capability: • Navigation • Sense-Navigate • Play Sound • Display LED Lights 38

  40. Detailed Plan 39

  41. Core Capability Drive-through • CCD: an activity allows clients to try on must-have capabilities. • Schedule: March 25 • Preparation: • Hardware & Software • Dry Run • Risk Management • Usage Scenarios • Feedback From Students 40

  42. Construction Iteration 2 (Mar26 - Apr08) • Duration: Mar 26  Apr 08 • Modules: Export • Capability: • Enhance User Interface • Integration testing and System testing • Fix defect and prepare for release 41

  43. Dates & Activities for Client • Re-baseline Development Commitment Review: Feb 11 • Core Capability Drive-through: March 25 • Transition Readiness Review: Apr 8 • Transition & Training: Apr 20 • Operational Commitment Review: Apr 27 • Client Evaluations: May 4 42

  44. Yun Shao Feasibility evidence

  45. Business Case • Cost analysis • Personnel analysis • Hardware and software analysis • Benefit analysis • ROI analysis 44

  46. 45

  47. Hardware & Software Analysis • Hardware • iRobot • Platform computer • Software • Visual studio license • Win AVR 46

  48. Benefit Analysis • More elementary school students interest in iRobot and STEM • 50% increase • More funding for Mission Science • 10% increase 47

  49. ROI Analysis 48

  50. ROI Analysis 49

More Related