P10041 Managerial Review. MSD I Primary Objectives Determine and Refine Customer Needs Map Customer Needs To Engineering Specs Develop Project Plan Thoroughly.

Slides:



Advertisements
Similar presentations
Chapter 14 Network Design and Implementation. 2 Network Analysis and Design Aspects of network analysis and design Understanding the requirements for.
Advertisements

P10041: TEAK - Sound and Music Sheryl Gillow Heather Godlewski Bryan Lozano Jeremy Schuh Mechanical Engineering Electrical Engineering Sponsors: The National.
MSD Detailed Design Review Agenda P11212 : LVE Controls, RF Module Meeting Purpose 1. Present an overview of the project. 2. Review Detailed Design. 3.
MICE Electronics Update Mice Target Workshop – Dec 2010 P J Smith James Leaver.
Project Review. Current State Currently on track to meet our mission objectives and cover all customer needs – Unpredictable to know whether or not sensors.
MSD-I Project Review Modular Motion Tracking Sensors 1.
P08009 Audible Memo Board Phase II Friday, February 22, 2008 P08009: Audible Memo Board Phase II Sponsor: Dr. Hopkins Advisor: Professor Slack Jon GosligaElectrical.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
RockSat-C 2011 ISTR Payload Subsystem Integration and Testing Report Universities/Institutions Team Members Date.
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
MSD-II Project Review Modular Motion Tracking Sensors 1.
Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Design Reviews Objectives of the Design Review Participants for a successful.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Development Processes and Product Planning
Target Controller Electronics Upgrade Status P. Smith J. Leaver.
EDGE™ Project Review P Automation/Improvement of Wegmans Cookie Line Packaging Project Team: Stephanie Rager (IE), Bruno Coelho (ME), Mark Voss (ME),
Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Design Reviews Objectives of the Design Review Participants for a successful.
P08009 Audible Memo Board Phase II Monday, October 22, 2007 P08009: Audible Memo Board Phase II Sponsor: Tala Hopkins Jon GosligaAudio Output Lead Loic.
EE496A Senior Design Project I Dr. Jane Dong Electrical and Computer Engineering.
Low Cost Fundus Camera P15590 December 11th, 2014
Program Management Satisfy requirements of all individual projects with minimal resources Human resource is the most expensive Leadership Methods of documenting.
Detailed Design Review Project P13363 Members: Justine Converse (IE) James Cover (CE) Alexander Eschbach (EE) Jason Hang (ME) Ashley Trode (EE) Guide:
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Introduction to Computer Technology
P Clean, Self-Sustained Photovoltaic Energy Harvesting System Josh Stephenson Mike Grolling Thomas Praderio KGCOE MSD TECHNICAL REVIEW.
Digital Microfluidics Control System II P15610 Complete Detailed Design.
Phase II Review MSD II P Size is too big and not comparable with original testing Hinge is not possible with rapid prototyping, metal hinge would.
Electrical Engineering 4OI4 Design Project By: Daniel Ho and Chris Ho.
Communication Device for Handicapped Kids Dec Client Heartland Area Agency Sue Young Advisor Yao Ma Advisor Yao Ma Alex Leith Brian Grove Steve Peters.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
S/W Project Management
Rational Unified Process (Part 1) CS3300 Fall 2015.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
PROPOSING TO WRITE A PROPOSAL? BY PAPIA BAWA. What are Proposals? Long reports usually written in response to a specific request or in response to your.
Objective 2.02 Utilize project-management skills to improve workflow and minimize costs.
Software Development Process and Management (or how to be officious and unpopular)
System Development Life Cycle. The Cycle When creating software, hardware, or any kind of product you will go through several stages, we define these.
MSD II Week 5 Update P13265: Motorcycle Safety Lighting and Portable Electronics Charging System.
Software Engineering Management Lecture 1 The Software Process.
Detailed Design & Component Selection. Detailed Design Phase Portion of the engineering design process where the engineering team can completely describe.
Preliminary Detailed Design Review P15080 Flow Culture System November 13, 2014.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
ECE445: The Design Review Sept 2, Documentation Roadmap Request for Approval Proposal Design Review Final Paper &Presentation Sept 10Sept 16Sept.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
ECE398: The Design Review Fall What the Design Review is  Board meeting with engineers- (faculty, TA, classmates)  Structured discussion of your.
P16221 – FSAE Shock Dynamometer Preliminary Detailed Design Review November 13, 2015.
The Comprehensive Project Plan
MSD II Week 7 Update P13265: Motorcycle Safety Lighting and Portable Electronics Charging System.
P08311: FPGA Based multi-purpose driver / data acquisition system Sponsor: Dr. Marcin Lukowiak Team MemberDisciplineRole Andrew FitzgeraldCEProject Manager/FPGA.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Preliminary Detailed Design Review Group P16228: Mike, Zach, Joe, Elijah & Bernie.
T Project Review RoadMappers I2 Iteration
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Complete Design & Gate Review. Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard.
What has been accomplished at the end of MSD 1 & 2?
T Project Review Wellit I1 Iteration
T Project Review Sotanorsu I2 Iteration
PROJECT MANAGEMENT Software Engineering CSE
EMIS Chapter 5 Much of Chap 5 and 6 varies depending on the contract type. Two major types are important so we’ll digress to Contracting 101 for.
P10203 LV1 MOTOR CONTROLLER FINAL REVIEW MAY 14, 2010 Electrical: Kory Williams, Adam Gillon, Oladipo Tokunboh Mechanical: Louis Shogry, Andrew Krall.
1 Introduction to Engineering Spring 2007 Lecture 4: Engineering Design II.
Software Engineering Management
P07307: Controls for Dynamic Suspension
Introduction to Engineering Design II (IE 202)
Team P16228: Magnetically Levitated Propeller
Detailed Design Presentation
Detailed Design Review Solar Thermal Water Heater
Detailed Design Review: P18001
Presentation transcript:

P10041 Managerial Review

MSD I Primary Objectives Determine and Refine Customer Needs Map Customer Needs To Engineering Specs Develop Project Plan Thoroughly Document Design Process Generate, Refine, and Select Kit Concepts (4) Assess Feasibility of Kit Implementations Assess and Plan for Mitigation of Kit Risks  Finalize Designs Create Bill of Materials  Prototype Designs  Finalize Bill of Materials  Address Budgeting Concerns and Ordering Concerns (Long Lead Time Parts) Create Preliminary Test Plans Create Plan Forward (MSD II Schedule)

Project Plan Evaluation Customer Needs and Engineering Specs completed on time Activity ideation took longer than expected and deserved more time than allotted Planned to have system level design completed by week five, but didn’t start until then Completed majority of the detailed design phase action items before DDR Planned to start prototyping designs for detailed design review, but won’t be starting until MSD II Finalizing Kit Design was scheduled for week nine, some designs require focus Finalize Bill of Materials was scheduled for week eight Risks were successfully foreseen even though all designs not finalized

Causes Most of these deviances result from the delay caused by concept generation and Kit selection. To have a sufficient degree of evaluation, many ideas needed to be generated and refined or expanded on Also, as a result of feasibility studies some approaches are being re-examined Being over ambitious in planning, and wanting to rush progress

What we would do differently Requested a postponement of Systems Level Design Review Spend more time choosing concept screening methodology Have a meeting agenda to make group time more efficient

MSD II Project Plan

Evolution of Risk Assessments As Kit ideas became more refined more individual Kit Risks were created The Team Risks did not grow to a large extent, most Team Risks were mitigated or could not be avoided i.e. loss of team member, or are too far off into the future The original Risk Assessment seen at the SDR did not have comments, and were not mitigated.

Electronic Keyboard Kit Detailed Design PCB Whole Design or Purchase Development Board – If using development board I will need a shield to put the DAC, convert signal to – bi-polar, implement power amplifier it can be either pcb or protoboard Determine method of outputting signal from micro-controller – Monophonic? Don’t need extra hardware – Polyphonic? Can this be achieved with Pulse Width modulation? Or Would I need DAC Determine how to convert signal from unipolar to bipolar, or if not necessary Determine design of power amplifier – Condition signal and use audio amplifier IC? – Make own power amp with power BJTs? Select components, and verify that rated specs will not be violated i.e. current/power Design will need to consider meeting budget To begin build-test activities… Finalize design BOM Order parts Prototype EXPECT ALL TO BE DONE IN FIRST WEEK OF MSD II

Electronic Keyboard Kit Risk Assessment Differences – Early risks focused on things that could go wrong with an analog keyboard – Risks have evolved to focus on time compression of learning pcb layout or avoiding it by using dev board and protoboard – All risks are commented on and a mitigation is determined Risk assessment has been continually updated Customer Needs – Many needs are on track to being met; will be determined after kit design is finalized – Some needs won’t be met until MSD2

Current State of Risks Electronic Keyboard IDRisk ItemEffectCause Likelihood Severity Importance Action to Minimize RiskOwnerCommentsMitigated? 1 Not Able to interface PCB board with a through hole or socket section for student manipulation. Money wasted on PCB, kit non-functional Poor planning, not doing enough research into getting PCBs made 236Contact professional once design completed Bryan Use female headersY 2 PCB creation absorbs a disproportionate amount of fund allocation Other kits could be compromised or limited in scope, or this kit may need massive redesign In-effective planning between purchaser, and designer133 Create Bill of materials and discuss with purchaser, then revise and propose to DebartoloAllCost is $33 per board if under certain sizeY 3 Keyboard doesn't sound good, meaning that frequencies of oscillators did not match what they were designed to be Keyboard is dissonant, and not pleasurable to play or hear Tolerance in components causes electrical resonance point to drift224 Consider alternate designs that guarantee harmonic intervals, or determine through monte-carlo simulation the worst case dissonance and determine severity of deviance.Bryan Implementing a Microcontroller for precise frequency controlY 4Circuitry not durable enoughKit life will be compromisedNo enclosure designed212Consider adding enclosureBryan/Sheryl Team seems unfamiliar with design of enclosures for circuitryN 5Kit activity time too shortKit quality compromisedKit designed poorly122 Consider adding more things to add in activityBryanNeeds to be evaluated by testingN 6 Frequency response of filter doesn't allow designed tones to passKit non functionalImpropper planning/design133 Design oscillators to coincide with speaker frequency responseBryanF=1/(2pi*R*C)Y 7 Student Presses all keys at once putting summing amplifier at riskKit damageImpropper planning/design236 Use voltage reducing amps or voltage limiting circuitryBryanNo summing amplifier required in design nowY 8 Taking too much time to learn pcb layout softwareNo kitSee Risk122 Study tutorial over break, play with softwareBryan N 9Mistake made in pcb layoutBad buildRushing through layout122 Study tutorial over break, play with software Bryan N

Electronic Keyboard Kit Individual Project Status Personal responsibilities – Help update project plan, and various group document templates – Electronic Keyboard Kit Microcontroller Design and Programming Oscillator Testing Filter Testing Amplifier Testing MSD1 Project Plan – Plan was too ambitious; I did not have enough time to finalize the kit design, plus it was requested that I change design MSD2 Project Plan – I am following the team MSD2 plan, with my own testing requirements

Electronic Keyboard Kit Individual Project Status Plan for MSD2 – Finish up all MSD1 action items – Follow project plan to complete all testing, building, and document writing Preliminary test plan is started What I would have done differently – Not wasted time on Analog design since it is not the industry standard anyway – Made a meeting agenda/action item template to maximize efficiency of the team’s time together

Hearing Aid Kit Detailed Design Open design activities Finalize design BOM Order materials for prototype Major subsystems Speakers will be purchased; speaker box design still needs to be determined Electrical circuit has been reviewed; new circuit ideas still need to be researched Cup telephone has been reviewed and design will work Budget Based on partial BOM, the budget should be met Will be determined after BOM is finalized To begin build-test activities… Finalize design BOM Order parts Prototype EXPECT ALL OPEN DESIGN ITEMS TO BE DONE IN FIRST WEEK OF MSD2

Hearing Aid Kit Risk Assessment Differences – Early risks focused on things that went wrong with the ear kit – Risks have evolved to more technical things that can go wrong with a new design – All risks are commented on and a mitigation is determined Key Risks – Most key risks deal with circuit assembly and usage issues Risk assessment has been continually updated Customer Needs – Many needs are on track to being met; will be determined after kit design is finalized – Some needs won’t be met until MSD2

Hearing Aid Kit Individual Project Status Personal responsibilities – Project organization (EDGE, templates, TO DO lists) – Communications Kit Homemade speaker testing Cup telephone testing Electrical circuit testing – Hearing Aid Kit Electrical circuit comparison Speaker design – Compared to the original project plan, I am behind schedule MSD1 Project Plan – Plan was too ambitious; I did not have enough time to finalize the kit design since my overall kit and circuit design changed MSD2 Project Plan – I am following the team MSD2 plan, with my own testing requirements

Hearing Aid Kit Individual Project Status Plan for MSD2 – Finish up all MSD1 action items – Follow project plan to complete all testing, building, and document writing Preliminary test plan is complete What I would have done differently – Researched electrical circuit options more thoroughly in the beginning of the design phase – Checked the project plan more often so I would have realized when I got off track and could have worked harder to get back on schedule – Made a meeting agenda/action item template to maximize efficiency of the team’s time together

Xylophone Kit Detailed Design Open design activities Schematics/Drawings BOM Preliminary Test Plan Ordering materials for Prototype Major subsystems Most current base design still has to be reviewed Bar materials have been reviewed and will work Budget Based on partial BOM, the budget should be met Will be determined after BOM is finalized To begin build-test activities… Finalize Schematics/Drawings BOM Order parts Prototype EXPECT ALL OPEN DESIGN ITEMS TO BE DONE IN FIRST WEEK OF MSD2

Xylophone Kit Risk Assessment Differences – Risks have evolved to focus more on the current base design – All risks are commented on and a mitigation is determined Key Risks – The size/weight is still a concern – Risks involving a noticeable difference in sound have been mitigated Risk assessment has been continually updated Customer Needs – Many needs are on track to being met; will be determined after kit design is finalized – Some needs won’t be met until MSD2

Xylophone Kit Individual Project Status Personal responsibilities – Project organization (EDGE, templates, TO DO lists) – Base design testing – Compared to the original project plan, I am behind schedule MSD1 Project Plan – Plan was too ambitious; I’m behind on detailed drawings and schematics MSD2 Project Plan – Following the team MSD2 plan, with my own testing requirements

Xylophone Kit Individual Project Status Plan for MSD2 – Finish up all MSD1 action items – Follow project plan to complete all testing, building, and document writing Preliminary test plan is still in progress What I would have done differently – Checked the project plan more often so I would have realized when I got off track and could have worked harder to get back on schedule – Figure out a way to maximize the efficiency of the team’s time together ie, how to make sure we didn’t get off track