1 Post-Mortem Team Goonies Spinal Fusion Data Acquisition System Post Mortem Review 4/28/2012.

Slides:



Advertisements
Similar presentations
How Your Research Administration Team Supports You From Start to Finish Michelle Melin-Rogovin, Manager of Research Administration Research Administration.
Advertisements

Chapter 5: Common Support Problems
The Comparison of the Software Cost Estimating Methods
Configuration Management Backup/Recovery Project Review.
Curry Mouse EE 296 Project Proposal Presentation February 11, 2006.
Project Overview Project Name Company Name Presenter Name.
PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Chapter 7 System Design and Implementation System Design and.
July 04 Office of Grants and Institutional Development Project Definition: A Quick Overview Laura Qaissaunee Director: Grants and Institutional Development.
Unit Testing & Defensive Programming. F-22 Raptor Fighter.
Virtual Mechanics Fall Semester 2009
3D Building Modelling with ZE Modeller Team: ZENITH Julien Li-Chee-Ming, Damir Gumerov, Tudor Ciobanu.
By Anthony W. Hill & Course Technology1 Common End User Problems.
Designing a Disaster Recovery Policy by Ian Murphy.
DISCUSS ANY FOUR APPROACHES TO SYSTEM CHANGEOVER
1. 2 IMPORTANCE OF MANAGEMENT Some organizations have begun to ask their contractors to provide only project managers who have been certified as professionals.
1 Mgmt 3830 – Contemporary Database Applications Faculty of Management Professor Brian Dobing Web Site:
AGENDA Introduction to Virtual Mechanic Demo Architectural diagram and summary QA steps and user acceptance testing Bugs in the software Feedback from.
Copyright © 2008 OMAC. All rights reserved Packaging Automation Survey Summary Dave Bauman OMAC Technical Director.
Department of Innovation & Technology City of Boston Five Key Ways to Be a Successful Project Manager March 2014.
Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.
Medical Call Center Project Name Company Name Presenter Name.
HSMM-Mesh From Space South Texas Balloon Launch Team BLT-26.
How to start Milestone 1 CSSE 371 Project Info There are only 8 easy steps…
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
CS-EE University of Portland School of Engineering Heart Rate Monitor Post Mortem Review April 21 st, 2010.
Social Impact May 2007 Implementing the Business Plan Hyderabad India May 2007.
1. Hardware: each component on the microcontroller will need to be tested individually using multi-meters, logic analyzers, and circuit probe analysis.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
CS-EE 481 Spring s06-PM University of Portland School of Engineering Microprocessor-based Charge Controller Post Mortem Review Wednesday, April.
Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University.
In the Framework of: Financed by: Developed by: MODULE 11 Management Overview Business Plan Update.
GAN: remote operation of accelerator diagnosis systems Matthias Werner, DESY MDI.
CS-EE 481 Spring s07-PM University of Portland School of Engineering Team Enterprise: Biggerfoot Textbook Exchange Post Mortem Review Wednesday,
Spring CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Senior Design Lecture 2 Technical staff Prototype phase: DEP, TOP.
Version Control and SVN ECE 297. Why Do We Need Version Control?
University of Portland School of Engineering Acoustic Art: Revolutionizing The Way You Listen To Pictures Post Mortem Review April 14, 2011.
Post Implementation Review CSEM01 SE Evolution & Management Anne Comer Helen Edwards.
1. WHAT IS A PROJECT? “A project is a problem scheduled for solution.” This definition forces us to recognize that projects are aimed at solving problems.
CS-EE University of Portland School of Engineering Team Hemlock: Nite Bike Speed Display Post Mortem Review 04/21/2010.
CS-EE 481 Spring s08-PM University of Portland School of Engineering Post Mortem Review Wednesday, April 23rd.
1 CMBG 2009 Planning for Obsolescence June 27, 2009 John Parler South Carolina Electric & Gas.
Microcontroller Evolution
Class #1 Contract Delivery Systems
Project Name Company Name Presenter Name
[Project Name] Post-Mortem
PROJECT NAME POST-MORTEM
Commissioning and Testing the LHC Beam Interlock System
Project Name | Company Name | Presenter Name
Information Technology Project Management – Fifth Edition
Taking an Iteration Down to Code
Case Study on Selection of a Work and Asset Management System
Integration by Substitution
I Can Make a Ballpark Estimate
Lecture # 3 Software Development Project Management
Project Name Company Name Presenter Name
How will Dropbox work for Team Projects?
Making PowerShell Useful
[Project Name] Post-Mortem Presentation Template
Project Name Company Name Presenter Name
Arduino Controlled DC Load
Project Name Post-Mortem
Small Organizations are Different?
Project Name | Company Name | Presenter Name
Microcontroller Evolution
PROJECT PLANING AND EXECUTION
Surf Scoter: Electronic Ballast for a Fluorescent Lamp
Pro Tips Guidance from the Challenge Masters.
Planetarium Resuscitation Ongo-06 February 14th, 2002
Project Name Company Name Presenter Name
Formula Hybrid - Fall 2018 Lafayette College ECE 491.
Presentation transcript:

1 Post-Mortem Team Goonies Spinal Fusion Data Acquisition System Post Mortem Review 4/28/2012

2 Post-Mortem What Worked Well Analog circuitry design matched physical implementation –Well designed, easy to debug Set guaranteed times to meet early –Easy for scheduling –Able to meet deadlines easily Backup design worked –Alternative easier to configure than our original plan.

3 Post-Mortem What Went Wrong Digital design did not work. –PIC UART not working correctly –Required extra components, programming, and contact manufacturer Alternatives needed to be accounted for. –Need to find alternative to PIC –Required adjusting our budget –Plan to integrate components together.

4 Post-Mortem What Went Wrong (Continued) Switch to alternatives ASAP when part of design fails. –Don’t think you will be able to “work through” issue Needed spare components –Components blew up and needed to be replaced

5 Post-Mortem Recommendations Require backups for all components, even for what you think is easy. Make plans for how backup designs will be integrated into system. Understand everything about programming language you are using in the Fall. Know all of the resources available to you, such as documentation, professors, support centers, tutorials, etc. DON’T MAKE ASSUMPTIONS!!!