FUNDAMENTALS OF ENGINEERING DESIGN

Slides:



Advertisements
Similar presentations
CS 411W - Notes Product Development Documentation.
Advertisements

Professors C.V. Hollot & Christopher Salthouse Department of Electrical and Computer Engineering 13 September 2012 Senior Design Project – SDP13 Problem.
Software Testing and Quality Assurance
1 SPIRIT Agenda for Monday July 16, Welcome for the Day (BC/NG/HD and faculty) AIM for Stars overview (Neal) Lesson Idea List distribution (Neal)
Silicon Prairie Initiative on Robotics in Information Technology
Silicon Prairie Initiative on Robotics in Information Technology
1 Introduction to System Engineering G. Nacouzi ME 155B.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
1 SPIRIT Silicon Prairie Initiative on Robotics in Information Technology Engineering Design Tools.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
 Design creates a new artifact (system, component or process) to meet a given need.  Broad Classifications ◦ Creative Designs – the first PDAs ◦ Variant.
Lecture 4: Phases of Engineering Design
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
EENG 1920 Chapter 1 The Engineering Design Process 1.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
ECE 2799 “The Engineering Design Process” Prof. Bitar and Prof. Michalson Last Update – 3/18/15.
Feasibility Study.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
Requirement Analysis 중앙대학교 전자전기공학부. Design for Electrical and Computer Engineers 3. Requirement analysis Our plans miscarry because they have no aime.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Project Selection And Needs Identification
EENG 4910/4990 Engineering Design Murali Varanasi September 02, 2009.
Request for Proposal (RFP)
Systems Development Life Cycle
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Lecture 2. An Overview of Engineering Design JANUARY 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lecture 5. Need Analysis and Problem Definition SPRING 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
1 FUNDAMENTALS OF ENGINEERING DESIGN. 2 Outline Introduction to engineering design Engineering design process Documentation and writing technical reports.
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.
By: Wilmer Arellano.  1. Form a team  2. Find a Team Leader  3. Find Three Potential Topics  4. Find a Mentor  5. Select a Topic.
 System Requirement Specification and System Planning.
An Overview of Engineering Design
Classifications of Software Requirements
Design and modeling 10 step design process
Ten-Stage Design Process
Chapter 2 Design Tools.
THE PROCESS OF EMBEDDED SYSTEM DEVELOPMENT
Ten-Stage Design Process
Design Process Overview
(Additional materials)
Software Requirements
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
Request for Proposal (RFP)
Design Process Overview
Spring Semester 2015 Lecture 7 Needs vs. Wants
Requirements Analysis
An Overview of Engineering Design
Design Process Overview
Chapter 13: Systems Analysis and Design
Software Requirements Specification Document
Design Analysis Higher Product Design.
What is a Design Process?
Software requirements
Design Process Overview
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Foundations of Technology The Engineering Design Process
Chapter 11 Describing Process Specifications and Structured Decisions
By the end of this chapter, you should:
CS/EE/ME 75(a) Nov. 19, 2018 Today: Prelimnary Design Review Homework.
FdSc Module 107 Systems Analysis
Design Process Overview
An Overview of Engineering Design
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Presentation transcript:

FUNDAMENTALS OF ENGINEERING DESIGN

Outline Introduction to engineering design Engineering design process Documentation and writing technical reports

The role of the design engineer Designer Customer Client Manufacturer User Operator Need for communication

Design Process Customer needs a solution to a problem Properly functioning system Requirement analysis System Design (Conceptual Design + Preliminary Design) Detailed design and test System integration and product test

Requirement Analysis Customer needs a solution to a problem Assess needs Statement of problem Specify design requirements Requirement specifications

Needs assessment The aim is not to solve the problem but to understand what the problem is What does this client want? What is the problem that the design is to solve? The objectives (goals) and constraints of the problem should be identified Objectives: summary of the needs that the design is to satisfy (helps us to choose among alternative design configurations) Constraints: the design must satisfy (takes logical values 0 or 1, helps to decide acceptable or not)

How to assess needs? (1/2) Question the customer Explore resources To define the design problem To understand budget and schedule constraints Reliability and maintenance constraints Explore resources Expertise (knowledge and experience) Technical literature (books, journals,www) Measurement and testing equipments (equipment suppliers) Similar designs (competitors, patent search)

How to assess needs? (2/2) Search legal and regulatory restrictions Allocation of frequency bands Restriction on tower heights Environmental impacts Safety Sustainability Manufacturability issues

Importance of manufacturability and communication Second floor collapsed, 114 people died

Statement of the problem (1/3) In the language of the customer, normally straightforward, non technical and non quantifiable

Statement of the problem (2/3) Tools that help Question the customer Differentiate Needs and Wants Wants True needs Needs as reflected to problem statement

Statement of the problem (3/3) Make Input/Output Analysis Preview the user interface and operation of the device

Objective trees Make a list of objectives according to the assessed needs and restrictions Group the relevant objectives Form a hierarchical tree structure

Specify design requirements Translating client and user needs into terminology that helps us find ways to realize those needs and measure how well we met them How will everyone that takes part in the design know that it is done? It turns the problem statement into a technical, quantified specification Sets out criteria for verifying that the design meets its intended objectives Describes the test for verification

Specifications How can I express what the client wants in terms that helps me as an engineer Expressible as numbers and measures Precise description of the properties of the object being designed

Specification types (1/2) Design specs : provide basis for evaluating the design Functional specs: what the thing must do? Input-output relations Black boxes and transparent boxes

Specification types (2/2) Performance specs: tells us how well the design is Metrics : Tools for testing and measuring the performance

Documentation Overview (executive summary) Statement of the problem Operational description (draft user’s manual) Requirement specifications Design deliverables Preliminary system test plan Implementation considerations Service and maintanence Manufacture Appendices A: Studies (experimental results) B: Relevant standards and legal and regulatory restrictions

Design Process Customer needs a solution to a problem Properly functioning system Requirement analysis System Design (Conceptual Design + Preliminary Design) Detailed design and test System integration and product test

System Design Conceptualization Synthesis Analysis

Conceptualization Develop a rough, early form of solution An idea or notion that can be a solution Primitive solutions, no definite form or character Lack organization and structure

Idea generation Brainstorming Search similar designs Seek quantity of concepts not quality No judgement or analysis of concepts Search similar designs Patents: no need to reinvent the wheel

Synthesis Create a well-defined structure for the concept Sufficient detail that helps analysis Preliminary design Block diagram of the system Each block will be designed in the detailed design

Block-diagram basics Implementable with a single technology analog or digital Common functions grouped in one block common power supply Try to avoid feedback loops between blocks designed by different engineers, may be unstable Keep in mind the standards Logic 0/1 voltage levels for TTL and MOS technologies Specify the parameters of analog signals Frequency, BW

Analysis Determine if the synthesized system meets the objectives Determine the risks Develop mathematical model for the blocks Analyze (simulations or experiments) Go back to synthesis, refine a solution Analyze again Evaluate the alternative solutions Choose one solution

Documentation The concept The block diagram Explain the principle of operation Background information The block diagram With specification of inputs and outputs Functional description of the blocks Subsection for each block Description of the system How the blocks interact with one another to make the system work System analysis Results of mathematical analysis, simulations and experiments and evaluations

Example Customer needs a solution to a problem of designing a guitar tuner

Problem Statement The accuracy of the device will be measured by the difference between the pitch of a tuned string and the correct pitch. The limits should be well within those of a guitar that has been professionally tuned and then played for one week without further tuning

The guitar tuner

Objective trees Fast Good performance for beginners Accurate Guitar Tuner Inexpensive Marketable Portability Convenience (ease of operation) Maintanence

Ranking objectives Pairwise comparison charts P I C M Total - 1/2 1 3 Portability I Inexpensive C Convenience M Maintenance Total - 1/2 1 3 2

Weighted objectives Ranking points Add 1 Weighted objectives 1/2 1.5 1.5/10=0.15 I 3 4 4/10=0.4 C 2 3/10=0.3 M Sum=10 Sum=1

Weighted objective trees Fast 0.3| 0.12 Good performance for beginners 0.4 | 0.4 Accurate 0.7|0.28 Guitar Tuner Inexpensive 0.4|0.24 Portability 0.15|0.09 Marketable 0.6 | 0.6 Convenience 0.3|0.18 Maintanence 0.15|0.09

How to specify design requirements Search out expert sources The guitar can drift up to 20 cents in a week f1 is X cents higher than f2: f1/f2=2 X/1200 Analyze similar designs (reverse engineering) Precision tuners have an accuracy of 2 cents Conduct tests and experiments Signal levels and response time

Compare with a professional tuner (6+2 = 8 cents) Performance specs: Accuracy requirement is 6 cents Metrics : Compare with a professional tuner (6+2 = 8 cents)

Evaluation F A P I C M Total 3.96 5.34 4.3 5.66 0.12 0.28 0.24 0.09 0.18 M Total S1 8 0.96 6 1.68 4 2 3.96 S2 0.0 10 2.4 0.72 0.36 5.34 S3 0.48 1.12 1.44 4.3 S4 2.24 0.54 1.8 5.66 10: Excellent,8: Good, 6: Satis., 4: Av., 2: Unacceptable, 0: Failure

Design Process Customer needs a solution to a problem Properly functioning system Requirement analysis System Design (Conceptual Design + Preliminary Design) Detailed design and test System integration and product test

Detailed Design,System Integrations and Tests Develop detailed design of each block specified in the system design Implement, test, and verify each block Integrate system, produce prototype Test system according to the test plan developed in requirements specification document Verify design, iterate if necessary Prepare detailed design documentation

Documentation Main deliverable of the design project Used to build and test the product in the factory Block diagrams and functional description To allow upgrades and extensions Shematic diagrams, PCB layouts, parts list For manufacturing engineers and technicians Key points in the circuit, test procedures and test fixtures For technicians in the repair department

Advice for young engineers When doing detailed design of a well-specified block, spend equal time on Design (synthesis, analysis, debugging) Testing Documentation

Writing Technical Reports Common mistakes Poor organization (Outline) Spelling, grammar, and punctuation mistakes Misused words Redundancy Lengthy paragraphs and/or sentences Missing figure captions Missing citations Inappropriate tone (formal)

No Job's Finished Until the Paperwork is Done