EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW.

Slides:



Advertisements
Similar presentations
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
Advertisements

Proposal Analysis Review NMSGC Student Launch University/Institution Team Members Date.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
1 Spring 2007 CSCI 660 CSCI-660 Project Title Project team members’ names.
Mark Nelson Alessandro Canossa Design documents Spring 2011
EMIS Chapter 6. EMIS Chapter 6 EMIS Chapter 6 Fig 6.2 shows where the SEMP fits into the earliest program stages. Fig 6.5 has an.
Complete and Present Prototype Project 6 Status report: Tuesday, October 5 th Due: Saturday, October 9 th Presentation: Tuesday, October 12 th.
Systems Engineering Management
CSULB EE400D Documentation Instructional Series
MSD P07302Design Review1 Motor Controller Subsystem MSD P07302 Project Sponsor: KGCOE Project Members: D. ShenoyProject Manager S. TallauSoftware Design.
Lab 08: AEV Design Analysis Tool Advanced Energy Vehicle (AEV)
Effective Methods for Software and Systems Integration
Introduction to Interactive Media 02. The Interactive Media Development Process.
Lesson 7 Guide for Software Design Description (SDD)
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
Managing the development and purchase of information systems (Part 1)
Common PDR Problems ACES Presentation T. Gregory Guzik March 6, 2003.
NCSX Management Overview Hutch Neilson, NCSX Project Manager NCSX Conceptual Design Review Princeton, NJ May 23, 2002.
CS 3610: Software Engineering – Spring 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class.
EE400D DOCUMENTATION INSTRUCTIONAL SERIES MEETING MINUTES.
EDGE™ Preparing a Poster for a Publication and Display Prepared by Edward Hensel (ME) Elizabeth DeBartolo (ME) Copyright © 2005 Rochester Institute of.
Some Sub-Activities within Requirements Engineering 1.Prototyping 2.Requirements Documentation 3.Requirements Validation 4.Requirements Measurements 5.Requirements.
Project Title (as descriptive as possible) Group Members CPE495 Group ??? Computer Engineering Design I Electrical and Computer Engineering The University.
Lecture 7: Requirements Engineering
CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIES PRELIMINARY DESIGN REVIEW.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class project.
Lab 07: AEV Design Analysis Tool Advanced Energy Vehicle (AEV)
Blog Post Grading. GENERAL OVERVIEW Do the posts capture the progress and development of your project?
Request for Proposal (RFP)
EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW.
Project Deliverables CEN Engineering of Software 2.
November 3, 2015  Embry Riddle Prescott Team #TBD Member1, Member2, Member3, Member4 [Alphabetical] Real-Time Systems Software Proof-of- Concept [12+
Critical Design Review (CDR)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
RBSP Radiation Belt Storm Probes RBSP Radiation Belt Storm Probes 12/25/20151 Flight Software Template for Instrument Critical Design Review Gary M. Heiligman.
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
PMC xx/xxxx Project Title & Project Code Presenter:
Chapter 6: Writing the Front Matter and Executive Summary.
September 10, FY 2003 Plans Bob Simmons. September 10, Introduction Overview of Project and Engineering Plans Project Plans Engineering Plans.
Project Management Requirements Prof. Ralph Locurcio, PE Dr. Troy Nguyen, PE.
ENGR 1181 College of Engineering Engineering Education Innovation Center Introduction to Technical Communication.
Technical Report Outline Title Page Frontispiece Abstract Table of Contents List of Figures/ List of Tables.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
GLAST LAT ProjectPeer Review & CDR Preparation Document: LAT-PR Preparation Schedule Subsystems Peer Reviews –ACD January 7-8, 2003 –CALMarch.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Visual Basic.NET Comprehensive Concepts and Techniques Chapter 1 An Introduction to Visual Basic.NET and Program Design.
CS646: Software Design and Architectures Introduction and Overview †  Definitions.  The general design process.  A context for design: the waterfall.
CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIES PRELIMINARY DESIGN REVIEW.
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Topic: Introduction to Computing Science and Programming + Algorithm
ISA 201 Intermediate Information Systems Acquisition
Software Verification and Validation
CSULB EE400D Documentation Introduction to Engineering Design Series
ISA 201 Intermediate Information Systems Acquisition
CSULB Department of Electrical Engineering Thursday, October 19, 2017
CSULB Department of Electrical Engineering Thursday, October 19, 2017
Introduction to New Product Development (Portfolio)
0.0 Instrument Suite Name Presenter’s name
An Introduction to Visual Basic .NET and Program Design
Critical Design Review
Chapter 1 (pages 4-9); Overview of SDLC
Lockheed Martin Canada’s SMB Mentoring Program
Project Title, date “Team Name: Team members, …”
EMIS 7307 Chapter 6.
CS 8532: Advanced Software Engineering
ECE 477 Design Review Team ??  Fall 2012
Members: Keshava Shiva Sanjeeve Kareena
Basic Design Documentation
PSS verification and validation
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
Presentation transcript:

EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW

The purpose of the PDR is to present the “requirements” and conceptual design of your project. The purpose of the CDR is to present the “design” of your project. The next phase of the project should be implementation of this design, not further design.

CRITICAL DESIGN REVIEW GUIDELINES Power Point Presentation / submit to Beachboard 40 minute maximum duration Each person in the group should present their own work. Be familiar with the material, do not reed it from the overhead or from a sheet of paper Speak clearly, with authority, and eloquently Practice the presentation to ensure all topics are covered in the time allotted.

CDR OUTLINE – PART 1 OF 3 Title Page Executive SummaryProject Manager Project Objectives and Mission Profile Design with Illustrations Major Project Features (Specifications) System DesignAll Divisions Detailed System Block Diagram(s), with Summary of Design Solutions Experimental Results What you did to arrive at Design Solution for System, Subsystem, and Components Do experimental results and observations meet Design Requirements?

CDR OUTLINE – PART 2 OF 3 Systems/Subsystem Design Electronics Interface Definitions Breadboard(s), Fritzing, Schematics, PCB Layout Software – Specifications, Pseudo-code, or flowchart, C++ Hardware – 3D Models and prototype prints Verification and Validation Test Plans System and Subsystem, Hardware and Software Test Plan A few short paragraphs on your plans for verifying that your design meets design requirements and how you will validate that you built the right product for the mission. Verification and Validation Matrices

CDR OUTLINE – PART 3 OF 3 Project Work Breakdown Structure (Who is doing what?) Resource Reports (Mass, Power) Updated Cost Schedule Status – Fabrication Project Percent completion and/or Burn Down Diagram Project Demonstrations

TITLE PAGE/EXECUTIVE SUMMARY Title Page What are you presenting (i.e., Critical Design Review) Name of Project Stylized Photo, Illustration, 3D Model Project Members (Who is doing what?) Executive Summary Project Objectives and Mission Profile Preferred Design Annotated Photo, Illustration, exploded 3D model – Summary Level Major Project Features (Specifications) Key Features of the Design Implemented Innovative Design Features

TITLE PAGE What is missing?

EXECUTIVE SUMMARY PROJECT OBJECTIVE AND MISSION PROFILE What is missing?

EXECUTIVE SUMMARY PREFERRED DESIGN WITH ILLUSTRATION An annotated Photo, Illustration, or exploded 3D model showing the major subsystems/components of your design

Executive Summary Major Project Features (Specifications) What is missing? Talk about the key and/or innovative design features of your product

SYSTEM DESIGN Detailed System Block Diagram Walk the audience through each subsystem/component block and how they are interconnected (i.e., subsystem and interface descriptions)

EXPERIMENTAL RESULTS Trade-off Studies, Models, and Rapid Prototyping What you did to arrive at Design Solutions for System, Subsystem, and Components Computer Simulations including Solidworks, Simulink, Multisim, Matlab, LabVEIW, LTspice, etc Do experimental results and observations meet Design Requirements?

EXPERIMENTAL RESULTS

EXPERIMENTS What is missing?

EXPERIMENTS What is missing?

SUBSYSTEM DESIGN Electronics Interface Definitions Systems Engineer Breadboards, Fritzing Diagram, SchematicsElectronics and Control Engineers PCB LayoutManufacturing Engineer Hardware System and Component 3D Models Prototype Prints

UPDATED INTERFACE DEFINITION

ELECTRONICS DESIGN Breadboards, Fritzing Diagram, Schematics…

SUBSYSTEM DESIGN PCB Layout Example

SUBSYSTEM DESIGN Hardware Examples

SOFTWARE DESIGN SpecificationsSystems Engineer Android App, Arduino Command and TelemetrySystems Engineer Present any pseudo-code and/or flowcharts which provide an overview of the software as well as sample C++ Code highlighting your code. Subsystem Electronics and Control Engineers Present any pseudo-code and/or flowcharts which provide an overview of the software as well as sample C++ Code highlighting your code.

SOFTWARE DESIGN Code Snip-it

VERIFICATION AND VALIDATION TEST PLANS Review NASA System Engineering Handbook and Verification and Validation lectureVerification and Validation System and Subsystem, Hardware and Software Test Plan A few bullet points on your strategy for verifying that your design meets design requirements and how you will validate that you built the right product for the mission. Verification and Validation Matrices

VERIFICATION AND VALIDATION TEST PLANS A few bullet points on your strategy for verifying that your design meets design requirements and how you will validate that you built the right product for the mission. What is missing?

PROJECT Work Breakdown Structure (WBS) Resource Reports Mass Power Updated Cost Schedule Status Update Schedule Project Percent Completion/Burn Down Diagram (if available)

PROJECT STATUS RESOURCE REPORTS What is missing?

PROJECT STATUS Schedule Status Example

PROJECT STATUS What is missing?