Project Clarification: Objectives Tree BE 20–Engineering Design with Computer Applications Week 4: 15-September-2004.

Slides:



Advertisements
Similar presentations
Developing an Attributes List Taken from engineering design: a project-based introduction by dym & little.
Advertisements

Testing Relational Database
Understanding Customer Requirements
Developing an Attributes List Taken from engineering design: a project-based introduction by dym & little.
Product specification
Lecture 5: Requirements Engineering
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Johnb DFDs and Design John Bell The DeMarco notation.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Problem Solving and Algorithm Design
FORMULATING A DESIGN PROBLEM PART 2. Pengumuman – dari Puan Marina Sila download lab module untuk minggu depan dari portal  lab project management Hantar.
STUDYING COLLEGE TEXTBOOKS AND INTERPRETING VIAUAL AND GRAPHIC AIDS
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
System Design and Analysis
Chapter 1 Introduction to Object- Oriented Programming and Problem Solving.
Requirements Analysis Concepts & Principles
Silicon Prairie Initiative on Robotics in Information Technology
Silicon Prairie Initiative on Robotics in Information Technology
1 Lecture 5 Introduction to Software Engineering Overview  What is Software Engineering  Software Engineering Issues  Waterfall Model  Waterfall Model.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Management Tools Problem Solving Chapter 17 Doug Winter, Christy Blew, Anh Le, Jennifer Stoltz.
ES305: Virtual Tools in Engineering Design: The Eng. Design Process James Carroll, Associate Professor Electrical and Computer Engineering.
Introduction to Systems Analysis and Design Trisha Cummings.
Introduction To System Analysis and design
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
Title page. 1. Identify the Problem Write a statement that answers the following questions. What are you trying to design? What are the requirement gaps?
CSI315 Web Applications and Technology Overview of Systems Development (342)
GENERAL CONCEPTS OF OOPS INTRODUCTION With rapidly changing world and highly competitive and versatile nature of industry, the operations are becoming.
Unit B065 – Coding a solution PREP WORK 1)Make sure you keep a work log / diary. Use the table on page 16 of the hand book as a template 2)Keep a bibliography.
CHAPTER 4 Engineering Communication
Introduction to Objects Adapted from “TEN STEPS TO OBJECT-SPEAK” a CPT Tech Talk by Joy Starks September 17, 1999.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Developing an Objectives-Constraints Tree
CPSC 2150 August 21, Chapter 1 Object Oriented Software Development This is an introductory course In this chapter we will look at 3 topics Challenges.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Systems Analysis and Design
I Power Higher Computing Software Development The Software Development Process.
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
ENGM 620: New Magnificent 7 New Magnificent 7– 16 October 2010 Quality Tools –Ishikawa’s Basic Seven –The New Seven –Bonus Tools.
The Software Development Process
DESIGN 1 DPT224 TOPIC 2: ENGINEERING DESIGN PROCESS.
Systems Development Life Cycle
CS 100 Introduction to Computing Seminar September 21, 2015.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Systems Design.  Application Design  User Interface Design  Database Design.
Chapter 11  2000 by Prentice Hall System Analysis and Design: Methodologies and Tools Uma Gupta Introduction to Information Systems.
4-2 CHAPTER 4 Engineering Communication © 2011 Cengage Learning Engineering. All Rights Reserved.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Lecture 2. An Overview of Engineering Design JANUARY 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
McDonough Bolyard Peck Educational Series Building Commissioning Presented by: Doug Wrenn Steve Baxter July
Introduction to System Analysis and Design MADE BY: SIR NASEEM AHMED KHAN DOW VOCATIONAL & TECHNICAL TRAINING CENTRE.
1 1 Design Objectives Trees AAE 490B Week 2 Lecture 5 AAE 490B Week 2 Lecture 5.
Synthetic Approaches to Data Linkage Mark Elliot, University of Manchester Jerry Reiter Duke University Cathie Marsh Centre.
Senior DesignSeattle Pacific UniversitySenior Design Design-1 Seattle Pacific University Stages of Engineering Design 1. Identify project and goals 2.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
What’s the Objective? Objectives (or goals) are expressions of the desired attributes and behaviors that the client wants to see in the product – Objectives.
 System Requirement Specification and System Planning.
Design and modeling 10 step design process
Ten-Stage Design Process
OVERVIEW Impact of Modelling and simulation in Mechatronics system
Objectives State the reasons for the complexity involved in the development of software Define the following terms Objects Classes Messages Methods Explain.
Ten-Stage Design Process
Appendix D: Network Model
Introduction to Systems Analysis and Design
Welcome W 6.2 Introduction to Engineering Design II (IE 202)
Presentation transcript:

Project Clarification: Objectives Tree BE 20–Engineering Design with Computer Applications Week 4: 15-September-2004

Design Process Overview  What drives design?  Design process has five distinct phases (Dym & Little, 2003)  The end goal:  Product that customers WANT Product that meets need

Design Process Overview = Product that meets need

Original Design Overview  Def’n: Development of a product, process, assembly or component not previously in existence  Clarification phase is perhaps the most important phase  As a designer, you must understand the problem your customer wants solved  Structured approaches exist to help guide you through this phase

Case Study: Project Clarification  Counting Device for Packaging Bulk Items The users’ task in this case is to count specified numbers of different products and place in one box for shipping. For instance, 3 packages of product A, 5 packages of product B and 2 packages of product C go together in one box for shipping. Currently, the users are persons with disabilities and have difficulty counting the required number of products consistently. The current quality control mechanism is to weigh a completed box to check if the correct number of items is included. The variance in the weight of each package makes this check not entirely reliable. A device capable of counting each type of product as it is dispensed into a box is needed.

Case Study: Project Clarification (2)  After clarifying the customer’s statements, the design team’s charge was:  To create an assistive device to aid in counting and packaging dog food sample packets  Assistive device NOT fully automated replacement  Increase accuracy and reliability of packet count  No reduction of current production rate  Create an ergonomically friendly and versatile solution

Phase 1: Clarify Problem  Clarify the problem  Objectives tree formulation  Derive a functional model  Form engineering requirements

What’s the Objective?  Objectives (or goals) are expressions of the desired attributes and behaviors that the client wants to see in the product  Objectives are  ‘Be’ words  They are qualities the object should have  Clients tend to speak in terms of objectives  So, our task today is to uncover the objectives of a design project

Objectives Tree Method  The objectives tree method is an approach to transform vague design statements into more specific customer requirements  Make vague statements more specific by asking:  What is meant by that statement?  Other useful questions to ask when expanding and clarifying design objectives:  Why? How? What?

Objectives Tree Method (2)  Three step procedure: 1. Prepare a list of design objectives 2. Order the list into sets of higher-level and lower- level objectives 3. Draw a tree of objectives, showing hierarchical relationships and interconnections

Step 1: Listing the Objectives  This can be done by:  Talking with (interviewing) your customer  Thoroughly reading any written design statements and requirements  Brainstorming within your team  Take vague statements and make them clearer by asking “what is meant by this statement” Objectives Tree Method

Step 1 (cont.): Culling the Objectives  After the initial list is compiled, some things other than objectives may have slipped in  Constraints - restrictions or limitations on a behavior or some aspect of a design  Functions - operations the design is supposed to do  Implementations - ways to execute the functions  Check if each statement is an objective  Objectives are normally “being” statements  Try saying “an objective is to be [statement] ”  If it makes sense, then it’s most likely an objective  Objectives can also be written as “more (or less) of [the statement] is better than less (or more) of [the statement]” Objectives Tree Method

Step 1 Active Experimentation  As a team, generate a list of objectives for the bumble ball toy  “Experience” the bumble ball  Ask each other questions about what they want the bumble ball to do  Write down the statements and check if they are really objectives Objectives Tree Method

Step 2: Ordering the List  Group the statements into related topics using an affinity diagram Objectives Tree Method Design Objective Major objective 1 Second level objective 1.1 Third level objective Third level objective Second level objective 1.2 Major objective 2 Second level objective 2.1 …

Step 2 (cont.): Affinity Diagram  Copy design objectives to post-it ® notes  Place one on a board  Compare next objective card to the first  If different, begin a new column  If similar intent, place under the first column  Repeat for all design objective cards  Result: Objectives sorted by similar statement  Within each column there may be levels of objectives  Lower-level objectives answer the question “How?”  Higher-level objectives answer the question “Why?”  Transform to a hierarchical list of objectives Objectives Tree Method

Step 3: Draw the Tree  From Step 2, you have a clustered set of objectives  Notice that some of the objectives within a cluster may be more specific than others  This implies a hierarchical nature to the objectives  The hierarchy (general to more specific) can be represented in a graphical structure known as an objectives tree Objectives Tree Method

Step 3: Draw the Tree (2)  Consider the example objectives list and resulting tree for the design of a safe ladder: Objectives Tree Method The ladder should be safe The ladder should be stable Stable on floors and smooth surfaces Stable on relatively level ground The ladder should be reasonably stiff The ladder should be marketable The ladder should be useful Useful indoors Useful for electrical work Useful for maintenance work Useful outdoors Be useful at the right height The ladder should be relatively inexpensive The ladder should be portable Be light weight Be small when ready for transport The ladder should be durable

Step 3: Draw the Tree (3)  The Objectives Tree diagram looks like an “upside-down” tree  The overall objective of the tree is at the top  Underneath it, branches break the objective into more detailed objectives  Can have many levels and interconnections Objectives Tree Method As you move deeper into the hierarchy, the objectives answer the question “how is the above objective met?” As you move higher up in the hierarchy, the objectives answer the question “why are the below objectives important?”

Step 3: Draw the Tree (4)  The objectives tree diagram may alternatively be drawn on its side  Example: Car door Objectives Tree Method

Step 3: Draw the Tree (5)  What’s wrong with this tree? Objectives Tree Method Objectives are not distinct from higher level (only one sub- objective)

Step 3 Active Experimentation  Draw an objectives tree for the bumble ball Objectives Tree Method

Objectives Tree Summary  Determining a design’s objectives is part of clarifying the design problem  An objectives tree is a graphical way to show:  Your design’s objectives  The hierarchy of your objectives  Objectives are “being” words and express the attributes and behaviors expected by your client