Mission Science By Team 07 1. Team 07 Members Jiashuo Li Chen Li Sergey Mukhin Hanadi Mardah Yun Shao Farica Mascarenhas 2.

Slides:



Advertisements
Similar presentations
Making the System Operational
Advertisements

Test Automation: Coded UI Test
14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
CS0004: Introduction to Programming Visual Studio 2010 and Controls.
Software Quality Assurance Plan
1 SOFTWARE TESTING Przygotował: Marcin Lubawski. 2 Testing Process AnalyseDesignMaintainBuildTestInstal Software testing strategies Verification Validation.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Documentation Testing
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Building Information Systems Chapter 13 VIDEO CASES Video Case 1: IBM: Business.
Quality is about testing early and testing often Joe Apuzzo, Ngozi Nwana, Sweety Varghese Student/Faculty Research Day CSIS Pace University May 6th, 2005.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Systems Analysis and Design in a Changing World, 6th Edition
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
Introduction to Software Testing
Introduction to Computer Technology
Release & Deployment ITIL Version 3
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
TRR ARB Presentation Women at Work Website Redesign.
Introduction to Interactive Media 02. The Interactive Media Development Process.
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
Healthy Kids Zone Team Introduction Chad Honkofsky 2.
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
GLAST Science Support CenterAugust 9, 2004 Implementation of the Standard Analysis Environment (SAE) James Peachey (HEASARC/GLAST SSC—GSFC/L3)
Incell Phonium Processor Project Plan Document Dale Mansholt Aaron Drake Jon Scruggs Travis Svehla.
Smart Digital Valve Control Simulator May April 25, 2001 Client: Client: Fisher Controls Intl. Inc. Contacts: Contacts: Patrick Ryan and Jeff Seyller.
RUP Implementation and Testing
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
Elockbox Team08 Fall2014 Jian Lei Role(s): Project Manager / Builder Da Lu Role(s): Prototyper / System/Software Architect Cheng Role(s):Feasibility Analyst.
1.  Project: temporary endeavor to achieve some specific objectives in a defined time  Project management ◦ Dynamic process ◦ Controlled and structured.
End HomeWelcome! The Software Development Process.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Mission Science By Team 07. Team 07 Members Ashwini Ramesha : OCE Chen Li : Requirements Engineer Jiashuo Li : Prototyper Ritika Khurana : Project Manager.
TRANSITION READINESS REVIEW GOTRLA TEAM 15 Aayush Jain, Ankith Nagarle, Anushila Dey, Deepak Earayil, Elaine Lo, Nidhi Baheti, Presha Thakkar, Suhani Vyas.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Introduction to Making Multimedia
Group 2 : Team Battleship Team Members: Zhen Cai Christopher Campbell Justin Doll Jason Miller Nicholas Rimer Raeginald Timones.
Software quality factors
Development Commitment Package iRobot GUI PROTOTYPE 2.0 Jiashuo Li.
Software Engineering Lecture # 1.
United Nations Oslo City Group on Energy Statistics OG7, Helsinki, Finland October 2012 ESCM Chapter 8: Data Quality and Meta Data 1.
Chapter 3-Multimedia Skills
RUP Deployment RUP Deployment Workflow
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
Thrdplace Social Networking Team #7 1. TRR Outline Operational Concept Overview System benefits to Customer 1.Introduction Demo of System Operational.
1 Infrastructure Trial Running a Dress Rehearsal.
Mission Science By Team 07. Team 07 Members Ashwini Ramesha : OCE Chen Li : Requirements Engineer Jiashuo Li : Prototyper Ritika Khurana : Project Manager.
Chapter 2-Introduction to Making Multimedia
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Engineering (CSI 321)
Transitional Readiness Review Team 08
ShareTheTraining TRR ARB Presentation Team 11
DCR ARB Presentation Team 5: Tour Conductor.
Mission Science By Team 07.
Chapter 10 Development of Multimedia Project
Development Commitment Package
Introduction to Software Testing
Chapter 1 (pages 4-9); Overview of SDLC
Mission Science By Team 07.
CSCI 577b Tasks and Activities
A Global Trojan Solution
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
ARB Schedule Locations
Software Verification, Validation, and Acceptance Testing
Team 7- SCRIPTONOMICS Advanced movie script analytics made simple
Chapter 2-Introduction to Making Multimedia
Team 7- SCRIPTONOMICS Advanced movie script analytics made simple
Presentation transcript:

Mission Science By Team 07 1

Team 07 Members Jiashuo Li Chen Li Sergey Mukhin Hanadi Mardah Yun Shao Farica Mascarenhas 2

Introduction Hanadi Mardah 3

Operational Concept Overview Drag and Drop interface to program instructions to control iRobot’s behavior and movement Improve understanding on logic and control systems Generate interest towards STEM program Easy of programming in new system compared to coding instructions in C language in the old system Most of the win conditions met except WC_3297: The system shall detect and show logic errors (conflicting/inconsistent instructions) in an easy-to-read way 4

TRR Outline Transition Objectives and Strategy Product status demo Support Plan Support Objectives Support Responsibility Support Environment Support Facilities Summary of Transition Plan Hardware, Software and Site Preparation Operational testing, training and evaluation Stakeholder roles and responsibilities Required Resources Software Product Elements 5

Transition Objectives All the must-have capabilities will be transitioned Intermediate support is provided after it has been transitioned. User Manual lists all operational procedures for Mission Science staff and elementary school teachers Beta testing performed before transitioned completely till no major unsatisfactory feedback is provided The new system will be deployed to all computers used by critical stakeholders 6

Transition Strategy Test prior to deploying system to client’s site Transition the system to client’s site Test the system at client’s site to verify no unexpected behavior exists Train critical stakeholders to use and maintain the system Provide documentation to assist with system functionalities and operational procedures 7

Product Status Demo Jiashuo Li and Sergey Mukhin 8

Instruction Demo Sergey Mukhin 9

Workflow Demo Jiashuo Li 10

Support Plan Yun Shao 11

Support Objectives Assist elementary school student on programming iRobot with provided GUI Correct inaccurate instruction given by elementary school student Record, report and try to fix unknown bugs 12

Support Responsibility Undergraduate school student Check generated error report from Validator Record and Report mistakes and bugs Familiar with iRobot Open Interface Technical Supporter Fix minor mistakes and bugs timely Familiar with C, C# and WPF 13

Support Facilities Existed test-purpose projects in current release An emulator has been built to help get the real-time sensor data from iRobot Documents 14

Summary of Transition Plan Farica Mascarenhas 15

Hardware, Software and Site Preparation Hardware iRobot with Microcontroller PC running with Windows Software Operating system: Windows 7/8.1 Compiler: WinAVR Visual Studio 2013 WPF based on.NET framework 4.5 Site Setup with PCs running Windows 16

Operational testing, training and evaluation Testing Unit testing to validate instructions work as expected when used in a program Module Testing to validate functionalities of each module and the interaction between them Acceptance Testing to verify client expectations are met and closely tie with the win conditions Continue to test through April 6, 2015 – April 22, 2015 Bugs are reported to Bugzilla and worked till resolved Final testing will be performed at the client’s site to ensure system behaves as expected 17

Operational testing, training and evaluation Testing TC-001: Navigation TC-002: Sensor TC-003: Song and LED TC-004: Demo Modes TC-005: Conflict Detection TC-006: Invalid Instruction TC-007: Invalid Parameters TC-008: Non Compiled Code Unit Test Cases 18

Operational testing, training and evaluation Training Hands on training will be provided to the client and undergraduate students after system setup Team members will be available to answer any questions during this time User Manual will be provided during the training sessions and as part of the software delivery Users will have a full working knowledge of the iRobot GUI before the end of CS 577b 19

Operational testing, training and evaluation Training GroupDescriptionSkill levels Undergraduate students The students assist the teachers on how to use the GUI The students should have basic knowledge in C language and basic understanding to operate the iRobot Elementary school teachers The teachers assist the students to develop logical program using the GUI The teachers should have basic knowledge in C language and basic understanding to operate the iRobot Elementary school students The students use the GUI to generate instructions to control the iRobot’s behavior The students should have some experience in using a computer Target Groups and Skill levels 20

Operational testing, training and evaluation Training Training Schedule DateTimeLocationContentsPerson being trained Responsible Personnel Training Materials 4/30/15TBDClient’s site Walk through of GUI features Edwin Lee and Ian TeamUser Manual GUI Video 4/30/15TBDClient’s site Walk through of GUI features Darin GrayTeamUser Manual GUI Video 21

Operational testing, training and evaluation Training Measurable goals Navigate through the GUI Understand what the icons represent on the GUI Create a new program by dragging and dropping instructions View source code of program Translate to C code Load to microcontroller Save the current program for future use Open a previously saved program Access system setting and configure as needed 22

Operational testing, training and evaluation Evaluation Note feedback on iRobot GUI and training materials during training sessions Note unknown bugs/issues found Provide a report on issues and risks, if any, and feedback at the end of the evaluation phase 23

Stakeholder roles and responsibilities DateRoleResponsibility 04/10/15DeveloperPrepare video on “How to use the iRobot GUI” 04/27/15Developer, ClientDeploy the system and provide support during the transition 04/30/15Trainer, Client, Undergraduate students Train client (Darin Gray) and undergraduate students (Edwin Lee and Ian) 04/30/15Development team, ClientDeliver the system (source code and documents are included) 24

Resources and Products Chen Li 25

Required Resources Documents iRobot iRobot® Create OPEN INTERFACE Serial Port Settings 26

Required Resources Hardware iRobot Mind Control Stick 27

Software Product Elements Projects Third-party libraries Pravate testing Translator 28

Software Product Elements Class diagram 29

Software Product Elements Documents For users User Manual For future developers Programming Manual High Level Instruction Definition 30

Documents High Level Instruction Definition, available on GitHub. 31

Thank you! 32