CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIES PRELIMINARY DESIGN REVIEW.

Slides:



Advertisements
Similar presentations
Criteria for Formatting of the Project Report
Advertisements

Protocol & Test Review Spaceport America Student Launch University/Institution Team Members Date.
Chapter 18 Working Drawings.
Team Name Critical Design Review Team Members Date Fall 2011 Rev A
1 Introduction to System Engineering G. Nacouzi ME 155B.
Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Design Reviews Objectives of the Design Review Participants for a successful.
Engineering H193 - Team Project Gateway Engineering Education Coalition Final Report – An Overview Week 4 Day 2.
CSULB EE400D Documentation Instructional Series
Instructions & Notes This template was created to help you: – Show the team where you are going via slides representing each planned activity. – Keep your.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Brainstorming & Project Management
CPIS 357 Software Quality & Testing
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
Product Evaluation & Quality Improvement. Overview Objectives Background Materials Procedure Report Closing.
Final Presentation Take out Sr. Project Handbooks Page 24.
CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIES PRELIMINARY DESIGN REVIEW.
Blog Post Grading. GENERAL OVERVIEW Do the posts capture the progress and development of your project?
EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW.
Project Deliverables CEN Engineering of Software 2.
Software Development Problem Analysis and Specification Design Implementation (Coding) Testing, Execution and Debugging Maintenance.
FINAL REPORT LAYOUT Criteria for Formatting of the Project Report.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Design Report – Fall Semester. Title Page List name of project and team number List date List team members, advisor, sponsor Team logos.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter Final Report – An Overview Week 4 Day 2.
EG1003: Introduction to Engineering and Design Product Evaluation & Quality Improvement.
Overview Participants manufacture a marketable desktop organizer. The team submits a documentation portfolio of the activities and the product made during.
Technical Report Outline Title Page Frontispiece Abstract Table of Contents List of Figures/ List of Tables.
EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW.
Brainstorming & Project Management ENGR Brainstorming  Proposing new ideas  Free flowing exchange of ideas  No judgment  No decisions  Build.
EE400D DOCUMENTATION INSTRUCTIONAL SERIES BLOG POSTS.
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Advanced Higher Computing Science
Your Name or Team’s Member’s Names Current Date
Introduction to Project Management
Product Validation Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Planetary Lander PDR Team Name
Scope Planning.
Week 14: Festivals of the World
Chapter 2 Design Tools.
CSULB EE400D Documentation Introduction to Engineering Design Series
Data Synthesis and Analysis
CSULB Department of Electrical Engineering Thursday, October 19, 2017
CSULB Department of Electrical Engineering Thursday, October 19, 2017
Introduction to New Product Development (Portfolio)
The FTC Engineering Notebook
Defining the Activities
Software Requirements analysis & specifications
Request for Proposal (RFP)
Mechanical Project Challenge
SMA Powered Micro Robot
Sr. Project Presentation Guidelines
SEM Operations PE - Utilize project-management skills to improve workflow and minimize costs PI – Develop project plan.
Product Evaluation & Quality Improvement
EMIS 7307 Chapter 6.
Click to add title Planning for LSST Verification George Angeli LSST All Hands Meeting Tucson August 15, 2016.
4th Edition Chapter 20 Design Teams.
Project Management Process Groups
Brainstorming & Project Management
Introduction to Engineering Design II (IE 202)
Team Name Conceptual Design Review
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Design Brief.
Introduction to Engineering Design II (IE 202)
Modern Systems Analysis and Design Third Edition
CIS 4328 – Senior Project 2 And CEN Engineering of Software 2
CBGD: Nguyễn Thanh Tùng
Welcome 1 This is a document to explains the chosen concept to the animator. This will take you through a 5 section process to provide the necessary details.
Command and Data Handling
TECHNICAL REPORTS WRITING
Modern Systems Analysis and Design Third Edition
Presentation transcript:

CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIES PRELIMINARY DESIGN REVIEW

The Preliminary Design proceeds from a clear definition of the Mission Objective(s) and Profile Program/Project Level 1 Requirements/Verification System/Subsystem Level 2 Requirements/Verification This material was codified in the Preliminary Design / Project Planning Blog Post. The Preliminary Design Review presents how your design has proceeded to date with the goal of meeting these objectives and requirements.

PRELIMINARY DESIGN REVIEW GUIDELINES Power Point Presentation 45 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. Have simple and uncluttered visual materials. Do not put too much information on one visual. Plagiarism – Provide source for all visuals, text, block diagrams, etc.

PDR OUTLINE Title PageProject Manager Program Objectives & Mission ProfileProject Manager Requirements and Verification Program/ProjectProject Manager System/Subsystem System, Subsystem Engineers Design InnovationProject Manager Systems/Subsystem DesignSystem Engineer Product Breakdown Structure Software Design Electronic System Design System Block Diagram(s) Interface Definitions Mechanical System Design

PDR OUTLINE - CONTINUED Design and Unique TasksSubsystem Engineers Details on Electronic, Power, Mechanical, and Electro-Mechanical Subassemblies Including Design Process: sketches, back of the envelope, trade-off studies, models… Project StatusProject Manager Work Breakdown Structure Project Schedule Top Level Schedule System/Subsystem Level Tasks Burn Down and Project Percent Completion System Resource ReportsSystem Engineer Mass Power Other… Project Budget

TITLE PAGE Artistic Rendering of your Project This may be in the form of a drawing, 3D model, photo, or some combination. The rendering should be creative and reflect positively on your project. Team Member Names Division Assignments

PROGRAM OBJECTIVES TBD

MISSION PROFILE TBD

LEVEL 1& 2 REQUIREMENTS REQUIREMENT EVALUATION RUBRIC Is the requirement, Quantitative, Verifiable, and Realizable? Is the requirement located at the correct level (1 – Program/Project) Is the requirement response to a higher level requirement or customer’s objective (Requirement Flow Down)? Is the linkage clearly defined? Does requirement provide links to source material? Does the requirement move the design process forward?

LEVEL 1& 2 REQUIREMENTS REQUIREMENT EVALUATION RUBRIC - CONTINUED Are equations used to calculate a requirement provided and are answers correct? If calculations overly complicate the slide you may simply provide a link. The requirements that are missing are the hardest to discover and will be factored into your evaluation. Is language in the form of a requirement? Avoid multiple requirements within a paragraph. (i.e., breakup statements that contain multiple requirements)

LEVEL 1 REQUIREMENTS WITH VERIFICATION What is this requirement missing?

LEVEL 2 REQUIREMENTS WITH VERIFICATION

DESIGN CREATIVITY AND/OR INNOVATION A summary of the “Creativity Exercise.” How has the exercise effected the design of your project? Example is TBD

SYSTEM DESIGN PRODUCT BREAKDOWN STRUCTURE TBD

SYSTEM DESIGN SOFTWARE DESIGN Software Block Diagram – Example is TBD

SYSTEM DESIGN SOFTWARE DESIGN Brief summary of each software block, its inputs and outputs. Example is TBD

ELECTRONIC SYSTEM BLOCK DIAGRAM Identify Custom PCB component of the project. Custom PCB

INTERFACE DEFINITION DESIGN EXAMPLE

SYSTEM MECHANICAL DESIGN An exploded view of the robot showing mechanical and electromechanical subassemblies Photo Credit: Fab Academy 2013 – Final Project, Working on a Programmable, Modular, Mobile Robot.Final Project, Working on a Programmable, Modular, Mobile Robot.

SUBSYSTEM DESIGN AND UNIQUE TASKS THE DESIGN PROCESS Sketch of the Design Ideas Back of the Envelope Calculations Trade Off Studies Models Mathematical Computer Simulation Physical Models (Rapid Prototyping) Full-scale Prototypes Scale Models

SUBSYSTEM DESIGN AND UNIQUE TASKS Planned Simulations and Tradeoff studies

SUBSYSTEM DESIGN AND UNIQUE TASKS Electronics / Custom PCB Fritzing Diagram Breadboard Photo Schematic

SUBSYSTEM DESIGN AND UNIQUE TASKS Completed Simulations and Tradeoff studies Rapid Prototyping Example

PROJECT STATUS WORK BREAKDOWN STRUCTURE (WBS)

PROJECT STATUS TOP LEVEL SCHEDULE TBD

PROJECT STATUS SYSTEM/SUBSYSTEM LEVEL TASKS

PROJECT STATUS BURN DOWN AND PROJECT PERCENT COMPLETION Photo Credit: Wikipedia – Burn down chartBurn down chart

SYSTEM RESOURCE REPORTS Resources that are important to your project need to be tracked over the life of the project. UFO Ab-ducted, BiPed, Spider, – Power and Mass 3DoT Projects – Power, Mass, and 3D Print Time Over the life of the project; as simulations and experiments are run, trade-off studies completed, models and prototypes built and tested, you will be able to finalize your design. Until then, there will always be uncertainty. This level of uncertainty is managed by allocating margins to project resources. This may be done at the system, subsystem, and/or component level. Example are TBD

PROJECT BUDGET Cost must be managed by all projects Example is TBD

APPENDIX Sources for outside information.

SUMMARY Focus On Original work – what you have learned Demonstration of the Engineering Method – From Objectives to Design Demonstrations with real hardware Do Not Show Product Pages Copied Promotional Text No linkage to Requirements

RESOURCES Introduction to Engineering Design and Problem Solving Design Synthesis Preliminary Designs PDR Outline Document F'14.pdf F'14.pdf PDR Grading Criteria