1 Introduction to Engineering Spring 2007 Lecture 4: Engineering Design II.

Slides:



Advertisements
Similar presentations
Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.
Advertisements

PURPOSE OF DFMEA (DESIGN FAILURE MODE EFFECTS ANALYSIS)
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
COE4OI5 Engineering Design. Copyright S. Shirani 2 Course Outline Design process, design of digital hardware Programmable logic technology Altera’s UP2.

Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Software Engineering Management Lecture 1 The Software Process.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
ME/MECA 238A1 ME/MECA 238A - Mechanical/Mechatronic Design Project I Course notes prepared by G.A. Kallio, based on The Mechanical Design Process, by D.G.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 24 Delivering the System.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Working Drawings (Production Drawings)
Nonbehavioral Specifications Non-behavioral Characteristics Portability Portability Reliability Reliability Efficiency Efficiency Human Engineering.
Software Prototyping Rapid software development to validate requirements.
Critical Design Review (CDR)
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter Final Report – An Overview Week 4 Day 2.
Documentation.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Requirements in the product life cycle Chapter 7.
What has been accomplished at the end of MSD 1 & 2?
“The Role of Experience in Software Testing Practice” A Review of the Article by Armin Beer and Rudolf Ramler By Jason Gero COMP 587 Prof. Lingard Spring.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Rekayasa Perangkat Lunak Part-6
Measurement and Evaluation in Your Personal and Professional Life
Introduction to Project Management
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Quality Control and Quality Assurance: Introduction
Assembly Drawings, Balloons, and Parts Lists
Software Engineering Management
Software Prototyping.
Design and modeling 10 step design process
Testing Tutorial 7.
Integration Testing.
Ten-Stage Design Process
Software Verification and Validation
Technical Scope of Work
Chapter 2 Design Tools.
The Marketing Research Process
The Systems Engineering Context
Computer tools for Scheduling
Ten-Stage Design Process
Documentation.
Introduction to New Product Development (Portfolio)
Chapter 6: Design of Expert Systems
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.
Introduction to New Product Development (Documentation)
ENGM92 Communication Unit 3
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Software Quality Engineering
Software Requirements analysis & specifications
Working Drawings (Production Drawings)
Engineering Processes
Chapter 2 The Process of Design.
Technical Scope of Work
Data Quality By Suparna Kansakar.
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Testing and Test-Driven Development CSC 4700 Software Engineering
Gathering Systems Requirements
4th Edition Chapter 20 Design Teams.
CSE 303 Concepts and Tools for Software Development
Welcome to Corporate Training -1
Introduction to Engineering Design II (IE 202)
Working Drawings Legal Documents that Provide All the Visual, Numerical and Textural Information Required to Manufacture a Component, Mechanism or Structure.
Engineering Processes
Gathering Systems Requirements
Test Cases, Test Suites and Test Case management systems
Working Drawings (Production Drawings)
PDT176 COMPUTER-AIDED DRAFTING CHAPTER 6 WORKING DRAWING
Presentation transcript:

1 Introduction to Engineering Spring 2007 Lecture 4: Engineering Design II

2 Review Design Steps Requirements Preliminary Design Class Project

3 Presentation & Delivery Test & Evaluation Preliminary Design Review - Design Steps Design is an iterative process: Word Description Detailed Design

4 Cost of Changes Costs increase exponentially as the project lifetime increases Cost Time

5 Outline Detailed Design Test & Evaluation Presentation Project

6 Detailed Design

7 Detailed Design Goals Starting with your selected preliminary design, develop it into a producible form that provides the desired function… in other words, develop a complete engineering description to include determination of the arrangement form dimensions materials method of fabrication for all the parts, and how exactly all the parts will be joined together in the final product.

8 Detailed Design Activities The “Five D’s” Doodling Digging Doing Documenting Design Reviewing

9 Activities I Doodling Understand the problem Figure out what needs to be done Sketch some ideas Digging Research Talk to experts Look at what’s out there Check out catalogs, vendor websites, hardware store

10 Activities II Doing Calculations Layouts Selections Components Materials  “When in doubt make it stout out of things you know about” Costs Make sure your design will do what it’s supposed to do!

11 Activities III Documenting Sketches Drawings Layout drawings Part drawings Assembly drawings Bill of Materials/ Parts List Technical reports and memos

12 Activities IV Design Reviewing Is it done? Will it all fit together? Will it work? Do you have enough information to build it?

13 Iteration Considerations You will go through various detail design steps several times Designs will be evaluated by referring to the customer requirements and your specifications You may need to go back to another concept/preliminary design again if your detail design can’t be made to work Depending on how your design works out, your specifications (and requirements) may need to be modified

14 Communications Considerations Your well-documented customer requirements and product specifications will be used to evaluate your design Your design should be well-documented with Sketches and drawings BOM Other information that supports your design decisions Think about who needs to use this information A well-documented design is essential to minimize hassles during fabrication of your product! You’ll need this for your final report and final presentation

15 Detailed Design Summary Be thorough – don’t leave details to the last minute Be diligent in documenting and checking your work Put enough effort into the design – before you build it – to convince yourselves that it will work A thoroughly documented design is a necessary prerequisite for building a successful product

16 Test & Evaluation

17 Testing Testing may be more expensive than development For example, testing adds 20 to 30% to the cost of a IC chip Hence it is cost-effective to Design for Test (DFT) Test plan/Test team/Test engineering

18 Testing Motivation People are not perfect We make errors in design and assembly Important and expensive activity Not unusual to spend 30-40% of total project effort on testing For critical systems (e.g. flight control): cost can be several times the cost of all other activities combined

19 Goals of Testing To reveal failures Most important goal of testing To measure quality Difficult to quantify, but still important To clarify the specification Always test with respect to a spec Testing shows inconsistency Either spec or the design could be wrong To verify contract Includes customer, legal, standards

20 Types of Testing Validation testing To demonstrate to the developer and the system customer that the software meets its requirements; A successful test shows that the system operates as intended. Defect testing To discover faults or defects in the software where its behavior is incorrect or not in conformance with its specification; A successful test is a test that makes the system perform incorrectly and so exposes a defect in the system.

21 Presentation

22 Presentations Presentations and technical writing are important: “….many practicing engineers credited the majority of their success in the field to their ability to communicate their findings and ideas efficiently…” There are many opportunities for presentations during a design task Preliminary Design Review Detailed Design Review Final Presentation

23 Class Project

24 Project Assignment You will work in groups to complete a design It will be a system of your choice: software, hardware, mechanical, other... You will select your own group members: 2 to 3 per group Your first task will be to come up with a word description: Due Feb 27