Multidisciplinary Senior Design I

Slides:



Advertisements
Similar presentations
The Gas Advantage ! Information contained in this document is the intellectual property of Venus Gas Products & Services (Mysore) Pvt. Ltd. (VGPSPL) and.
Advertisements

P14007: Wheelchair Assist.
Test Automation Success: Choosing the Right People & Process
Copyright 2009  Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter  Develop.
Systems Analysis and Design 9th Edition
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Client Interview & Requirements Gathering Workshop ITEC 455 Business Requirements Analysis September 28, 2010 Marisa Thomas, Jesse Felter, Don Draper Deloitte.
Chapter 5: Project Scope Management
ECM Project Roles and Responsibilities
LEARN. NETWORK. DISCOVER. | #QADexplore Implementing Business Process Management: Steps to Success WCUG – November 18, 2014.
TEAM LEADER: DANIEL FENTON KENNEDY KONG MARIE REVEKANT DAVID ENGELL ERIC WELCH DEREK ZIELINSKI CHRIS FREEMAN MELISSA HARRISON RYAN MUCKEL ROBERTO CASTILLA.
PEV Performance Verification System - Team Kristeen Yee - Team Leader, Stephanie Zambito, Soham Chakraborty, Leslie Havens, Danielle Koch, Mike Allocco,
P14007: Wheelchair Assist Che-An Lee Phil Medalie Dan Schuster Tom Elliot.
1. 2  Team Members:  Dan Fenton (CE) – Team Lead  Ryan Muckel (ME)  Christopher Freeman (ME)  Derek Zielinski (EE)  Eric Welch (EE)  Kennedy Kong.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
S/W Project Management
CLEANROOM SOFTWARE ENGINEERING.
MSF Requirements Envisioning Phase Planning Phase.
Multidisciplinary Senior Design Project Charles Alexander, Tom Christen, Kim Maier, Reggie Pierce, Matt Fister, Zach Mink Underwater Thermoelectric Power.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Motor Assisted Wheelchair Design Review 09/10/15.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
SPX Data Acquisition PROBLEM DEFINITION REVIEW John Dong David Haller Adam Johnson Thomas Klaben Luke Kranz.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
P13026: Portable Ventilator
FOODSERVICE JBP GUIDEBOOK
Team P15441 Mini Air Daniel Probst Usama Haq Nathan Serfass Joshua Erbland Alexander Cornell 2/10/15P
BENCHMARKING. WHAT IS BENCHMARKING? Benchmarking is the activity of comparing a product, a component, an application, a software package, a process, an.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
EDGE™ Final Project Plan Presentation P09001 – RFID Reader & Active Tag Philip Davenport (Industrial and Systems Engineering)
System Development Life Cycle (SDLC). Activities Common to Software Projects Planning : Principles Principle #1. Understand the scope of the project.
P14471 Vibration Testing Application. Team Introductions NameRoleMajor Brett BillingsTeam LeaderIndustrial Engineer Nick GrecoLead EngineerMechanical.
Smart Cane – P14043 Lauren Bell, Jessica Davila, Jake Luckman, William McIntyre, Aaron Vogel.
Requirement Specification SRS document is a contract between the development team and the customer How do we communicate the Requirements to others? Firm.
Senior Design 2  Intelligent Wheelchair  Group Members  Jose Vivian  Oscar Garcia  Alan Mairena.
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Project Management PTM721S
P16512 – 3D Printing Ink Development Test Rig
Service Management World Class Operations - Impact Workshop.
BUSINESS DRIVEN TECHNOLOGY
Requirements Analysis Scenes
Software Configuration Management
12 Steps to Useful Software Metrics
Multidisciplinary Senior Design I: Problem Definition Review
Quality Assurance (Unplanned Inspections) Scenario Overview
Maintaining Quality Test Optimization with Increasing Software Complexity Ankit Goyal Software Engineer II Adobe Systems.
Right Move, Right Place, Right Time
Please highlight one choice only
P15001: Soft Ankle-Foot Orthotic
P15073: Autonomous IV Stand Michael Binger, Caitlin Conway, Nick Goddard, Nicholas Jacobs, Christina Pysher, & Ethan Whritenor Mike September 11, 2014.
Requirements Analysis
Lockheed Martin Canada’s SMB Mentoring Program
CIS 375 Bruce R. Maxim UM-Dearborn
12/8/2018 Title Page.
Project Management Process Groups
Chapter 11: Software Configuration Management
Employee engagement Close out presentation
CS385T Software Engineering Dr.Doaa Sami
Please highlight one choice only
Project Status Update PYYNNN – Project Title Here
Chapter 12 Project Communication and Documentation
P18325: Automated Breast Pump Cleaning System (Team ABC’s)
The Realities of Client Behavior
Lesson 3.2 Product Planning
APMP Professional Certification
Presentation transcript:

Multidisciplinary Senior Design I Problem Definition Review Preparation

Agenda Questions to be Answered by the Problem Review Goals of the Problem Definition Review Mechanics of the Review An Example

Questions to be Answered What is the current state and why is it unacceptable? What does the desired state look like? Who are the stakeholders that benefit from the desired state? What are those benefits (can be qualitative or quantitative)? What stakeholders can be negatively impacted by the desired state? What are the limits of those negative impacts (can be qualitative or quantitative)? How will your system be used by stakeholders? What are quantifiable responses (engineering requirements) that your system must produce? Do you have a project plan (objectives, key milestones, responsibilities) that your team, Guide, and Customer agree to? What are some systems that already do (or are similar to) what you want to do? How do these (similar) systems compare to the desired state? What can you learn/borrow from them? Where should they be improved?

Goals of the Problem Definition Review Demonstrate that your team can answer the questions posed by: Clearly defined and agreed upon problem statement & project deliverables Prioritized list of Customer requirements Engineering requirements Use scenarios Draft of project plan Identify any gaps that exist between your ability to meet the above goal and your actual state Be honest (Don’t try to BS) Show your action plan to close gap by next review

Mechanics of the Review

P13026: Portable Ventilator Derek Zielinski Chris Freeman Melissa Harrison Ryan Muckel Roberto Castilla Zavala Daniel Fenton Kennedy Kong Marie Revekant David Engell Eric Welch

Agenda Introduce Team Project Background Problem statement & project deliverables Use scenarios Prioritized list of needs (customer rqmts) Engineering requirements Draft of project plan

Team Introduction & Roles

Current Product- Mediresp III Provide positive pressure ventilation 3 modes: CMV (constant mandatory ventilation) Assist CPR Manual Large and heavy 2-4 hour battery life FDA approval Patented Contains BVM backup

What is a PEV? A Portable Emergency Ventilator (PEV) is a device that can provide mechanical ventilation to a person who is incapable of breathing on their own Volume controlled Pressure controlled Spontaneously controlled Negative pressure controlled

PEV Theory of Operation Pressure controlled cycling is based on an applied positive pressure that is set by the clinician. In pressure controlled modes the total volume is variable as the ventilator is using only the pressure as a measurement for cycling.

P13026 Problem Statement Current State Desired State Project Goals A prototype was developed in 1990 that is too heavy, consumes to much energy and is not easy to use. Desired State The device should not interfere with first responders’ abilities to administer life-saving measures. A functional prototype which can be marketed to companies and ultimately be manufactured Project Goals Analyze the current design and the patent database Identify opportunities lighter more energy efficient easier to use more feedback and control to the user Constraints Consistent with the intellectual property and FDA approvals

Additional Project Deliverables Functional prototype which can be marketed to companies and can be the basis for a product that will ultimately be manufactured Appropriate design, test, manufacturing and supply chain documentation to support transition to a manufactured product Test data verifying correct operation Designs alternatives Other possible configurations Other possible use environments User’s guide for operation

P13026 Stakeholders I need to put this is pretty graphic

Use Scenarios Considered Scenario 1: Unresponsive patient, heart beating but not breathing – PEV assist and transport to hospital Scenario 2: Unresponsive patient, heart beating but not breathing – PEV assist and administer life-saving measure X Scenario 3: Unresponsive patient, heart not beating and not breathing – PEV assist and CPR

Unresponsive patient, heart beating but not breathing

P13026 Needs List Need Priority Have a modern look and feel 3  3 Is Light weight Is Small Is Easy to Use  9 Has Long-Lasting Portable Power Low Cost Functional Prototype Low UMC for Final Design Alert user of the following data: XXX Measure Oxygen Levels Measure CO2 Levels Transfer Data Wirelessly Assist Human to Breathe Integrates into CPR Process Does not interfere with the following life-saving measures: XXX Improves air quality delivered to patient Is safe Is reliable Needs to use principles in patents #5,211,170 and # 5,398,676 Needs to be consistent with FDA 510K Approval Ed, there is no way to sugar coat this, the needs list was terrible. This is a start, we need to rework the list

Key Performance Metrics Talk about value (coverage and avoid redundancy)

P13026 Engineering Requirements Talk about value (coverage and avoid redundancy)

P13026 Preliminary Schedule

P13026 Preliminary Schedule

Issue & Corrective Actions Please highlight any gaps Identify action plans to close them