Design Cycle. 1.What is the problem? – Often identified by a “customer” need 2.Define requirements – This does not mean a design solution. – The requirements.

Slides:



Advertisements
Similar presentations
Fall CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Senior Design Lecture 3 Corporate organization Product development.
Advertisements

Design Process © 2013 Project Lead The Way, Inc.Engineering Design and Development.
EQUIPMENT VALIDATION.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
CS 411W - Notes Product Development Documentation.
Alternate Software Development Methodologies
ITIL: Service Transition
PURPOSE OF DFMEA (DESIGN FAILURE MODE EFFECTS ANALYSIS)
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Chapter 5: Project Scope Management
Systems Engineering Management
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Hazard and Operability Studies - HAZOP ChE 258 Chemical Process Safety University of Missouri - Rolla Fike Corporation.
CSULB EE400D Documentation Instructional Series
Unit 9 Manufacturing Systems CHAPTER 21- PRODUCT AND PROCESS DESIGN.
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Process Safety Management
Project Life Cycle Lecture - 18.
From Research Prototype to Production
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Task: Copyright © 2003 PM tec, Inc; D. Sankey; D. Padelford. All rights reserved. 1 Fast Start For Projects  Electric Dipole Moment Project Facilitator:
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Engineering System Design
Six Steps of Problem Solving And Engineering Design Process SVES Colleges of Engineering UML – ATP Lecture 2.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Project Scoping Fundamentals Alan Lively Project Delivery Specialist Local Government Section April 6, 2010.
Lecture 1: Project Initiation SYS366 Definition of a Project A Project is a sequence of unique, complex, and connected activities having one goal or.
INFO 637Lecture #51 Software Engineering Process II Defining Requirements INFO 637 Glenn Booker.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Project Life Cycle – Project Initiation © Ed Green Penn State University All Rights Reserved.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.
Problem Statement Expanding the capabilities of an auto repair paint drying system that uses newly developed ultraviolet (UV) light activated paint. This.
Introduction to Biomedical Engineering Design Chapter 1.
Requirement Handling
Develop Project Charter
Expert System Job Offer Evaluation Software May Abstract The project’s focus is to decide what criteria should be used to determine which job offer.
Engineering Design Process
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
Smart Home Technologies
Introduction to Biomedical Engineering Design Chapter 1.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
10 Aug 2010 ECE/BENG-492 SENIOR ADVANCED DESIGN PROJECT Meeting #4.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.
6 Modeling, Testing, and Final Outputs Permission granted to reproduce for educational use only.© Goodheart-Willcox Co., Inc. Objectives Explain the.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Failure Modes and Effects Analysis (FMEA)
The Engineering Design Process
Information Technology Project Management, Seventh Edition.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Design Process Engineering Design and Development
The Engineering Design Process
Chapter 6: Database Project Management
Introduction to Biomedical Engineering Design
UNIT II.
Introduction to Biomedical Engineering Design
Verification and Validation Unit Testing
Systems Engineering for Mission-Driven Modeling
Connected Vehicle Reference Implementation Architecture (CVRIA)
The Engineering Design Process
The Engineering Design Process
ME321 - Kinematics and Dynamics of Machines Design Process Notes
The Engineering Design Process
LECTURE 3: Requirements Engineering
The Engineering Design Process
Information system analysis and design
Presentation transcript:

Design Cycle

1.What is the problem? – Often identified by a “customer” need 2.Define requirements – This does not mean a design solution. – The requirements definition process, in cooperation with the customer, identifies what the end product needs to do, and any associated constraints 3.Brainstorm / Research – What is already out there? What works, what doesn’t, and why? – What are some concepts that can be adopted for this product? 4.Develop a prototype – Develop solid model – Breadboard components / processes – Integrate – Document design, problems, limitations 5.Test – Does the design meet the requirements? 6.Redesign

NASA System Requirements Review

NASA Preliminary Design Review

NASA Critical Design Review

NASA Systems Acceptance Review

ME 122 Process 1.Downselect “bug” 2.Define product solution requirements and constraints 3.Present bug, requirements, constraints 4.Brainstorm options / research alternatives 5.Breadboard / model 6.Present preliminary concept 7.Prototype 8.Test 9.Present results and recommended further work

Requirements Definition From NASA: – The following definitions differentiate between requirements and other statements. Shall:This is the only verb used for the binding requirements. Should/May: These verbs are used for stating non-mandatory goals. Will:This verb is used for stating facts or declaration of purpose. For ME 122: (HW for Monday– minimum 4 requirements in each category) Automatic Door Widget Example… – Function “The widget shall have the capability to unlock a standard (DEFINE) office door” – Performance “The widget shall perform (TASK) within 30 +/- 5 seconds of receiving a command” – Interface “The widget shall accept input from a human operator speaking five (5) distinct pre-defined voice commands”. – Environment “The widget shall function in an environment from 0-90 degrees Celsius” “The widget shall be recoverable from an environment from degrees Celsius” – Safety “The widget shall have no surface exposed to human contact in excess of touch temperature (50 degrees Celsius)”.

Terms Related to Design and the Design Process Design Cycle:Process of: design,build, test, break, redesign FOMFigures of Merit (how do you measure the important stuff) KPPKey Performance Parameters (design is filled with trades – you have to decide early on what is most important) Ops ConConcept of Operations. The time line of everything. Who uses it, who touches it, who repairs it, where it goes, how it is used. RequirementsEngineering contractual language. Requirements are quantified and verified. RiskFormally tracked issues that keep engineer up at night. Documented and tracked on “likelihood vs. consequence” tables. Hazards AnalysisFormal tracking of things that can go wrong. Designs with components that get hot can cause fires. Each hazard has a formal hazard control plan.

Terms Related to Design and the Design Process Interfaces:Things the design connects: environments, humans, mechanical, electrical, fluid, structural PDRPreliminary Design Review. Formal audit of documents that declares everybody knows system requirements, and the design team can sign up to ICD (Interface Control Document) CDRCritical Design Review: The formal audit of the design, where the customer releases the money to build the thing. BreadboardEarly design iteration “thing” – no effort to package BrassboardMiddle design iteration “thing” – no effort to package, but uses components intended for final build PrototypeMiddle design iteration “thing” EDUEngineering Development Unit. A prototype that can be tested, and test results predict performance. Qualification UnitPrototype that is controlled. Results can verify requirements are met

Terms Related to Design and the Design Process Qualification:Proving the design meets the requirements Acceptance:Proving that each item (by serial number) can be used. StakeholdersThe list of people involved. A deliberate list should be kept, and at each critical review – all stakeholders should formally accept, or write down their concern. P&IDProcess and Instrumentation Diagram. The engineering drawing of the components in a design, how they are configured, and where the instruments are located. Process SheetSimilar to P&ID, a term used by chemical engineers. It is a map that tracks all mass flow, and tracks all energy flow. FMEAFailure Modes and Effects Analysis. A way of tracking hazards.

ME 122 Class Assignment Due Next Lecture Each Team Will Present: Project Title Team Members and Job Assignments Concept of Operations 2 Key Performance Parameters 3 important requirements