1 These are the Skills You Need to Build a House – What’s Missing?

Slides:



Advertisements
Similar presentations
Wireless network Usually use Radio Frequency (RF) technology Adv :
Advertisements

Teaching materials to accompany:
Product Design L8- Ch9: Product Architecture Dr. Husam Arman 1.
INSE 6411 Product Design Theory and Methodology
Motherboard Further Information Click on the image for details about each component.
Terms 4 Definitions and Questions. Motherboard The main board of a computer, usually containing the circuitry for the central processing unit, keyboard,
1 Systems Engineering Part 2 Product Architectures.
Chapter 9: Product Architecture
Teaching materials to accompany:
FIU Chapter 7: Input/Output Jerome Crooks Panyawat Chiamprasert
BHEL – Electronics Division, Bangalore
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Lecture 6 October 22, Agenda HW presentations Acceleration of materials Midterm discussion Product Architecture Exercise Team Assessment.
Product Structure. Make to order (Dell Computers) Make to stock (Roaster Pans) Delayed Differentiation (Washing Machines)Delayed Differentiation Product.
Software Connectors. Attach adapter to A Maintain multiple versions of A or B Make B multilingual Role and Challenge of Software Connectors Change A’s.
SWE Introduction to Software Engineering
Motherboard & System Unit. System Unit  The box in which the motherboard and other components of the computer is stored.  On a desktop computer it’s.
PCB L AYOUT P LANNING AND D ESIGN. BLOCK DIAGRAM All electronic equipments can be considered as systems comprising a set of interacting elements responding.
The SCSI Interface Objectives In this chapter, you will: -Understand the different SCSI standards and confusing naming schemes -Identify cables and connectors.
Configuration Design Architecture Abstract embodiment
COMPONENTS OF THE SYSTEM UNIT
Programmable logic control Data Processing Computer System Key Board Light Pen Mouse PLC a Process Control Computer System Motion Sensor Sound Sensor.
The Internal Components of a Personal Computer (PC)
Introduction to USB Development. USB Development Introduction Technical Overview USB in Embedded Systems Recent Developments Extensions to USB USB as.
Design for Disassembly (DfD) Reduce, Recycle, Reuse
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Product Architecture and Modularity Systems Engineering MG587 Karl T. Ulrich and Steven D. Eppinger 3rd Edition, Irwin McGraw-Hill, 2004.
1 Rev: 3/29/07 MSE-415: B. Hawrylo Chapter 9 Product Architecture MSE-415: Product Design Lecture #9.
Protocol Architectures. Simple Protocol Architecture Not an actual architecture, but a model for how they work Similar to “pseudocode,” used for teaching.
COMPUTER PARTS.
An Introduction to Software Architecture
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
IS312: information systems theory and applications LECTURE 1:SYSTEMS THEORY AND MAIN CONCEPTS Information Systems Department.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
New Product Development Management NPDM 8 Mohsen SADEGHI Department of Graduate School of Management and Economics Sharif University of Technology.
SOFTWARE DESIGN.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
The Guts. CPU CPU Socket The CPU is generally a 2 inch ceramic square with a silicon chip located inside. The chip usually about the size of a thumbnail.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Kuliah 9 : Product Architecture. Dira Ernawati, ST.MT2 Planning Concept Develop. System- Level Design Detail Design Testing And Refinement Production.
Product Architecture, Industrial Design, Design for Manufacturing.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
Product Architecture Chapter 9 EIN 6392, summer 2012 Product Design for Manufacturability and Automation.
Unit 2 Architectural Styles and Case Studies | Website for Students | VTU NOTES | QUESTION PAPERS | NEWS | RESULTS 1.
UNIT – III DESIGN OF PRODUCT, SERVICE AND WORK SYSTEMS.
John D. McGregor Class 4 – Initial decomposition
1 CMPT 275 High Level Design Phase Modularization.
EPT 221 CONFIGURATION DESIGN. Objective of This Lecture Describe the configuration design phase Describe ways to generate product and parts configurations.
CSC480 Software Engineering Lecture 10 September 25, 2002.
Chapter 13 – I/O Systems (Pgs ). Devices  Two conflicting properties A. Growing uniformity in interfaces (both h/w and s/w): e.g., USB, TWAIN.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Software Engineering Issues Software Engineering Concepts System Specifications Procedural Design Object-Oriented Design System Testing.
Lecture VIII: Software Architecture
Tata McGraw CHAPTER 4 Product and Service Design.
Brandon Halleran.  The power supply for your personal computer gives your machine all the different voltages it needs to operate properly. It is able.
Information Technology INT1001 Lecture 2 1. Computers Are Your Future Tenth Edition Chapter 6: Inside the System Unit Copyright © 2009 Pearson Education,
Slide 1 Chapter 8 Architectural Design. Slide 2 Topics covered l System structuring l Control models l Modular decomposition l Domain-specific architectures.
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
1 The user’s view  A user is a person employing the computer to do useful work  Examples of useful work include spreadsheets word processing developing.
P10203 LV1 MOTOR CONTROLLER FINAL REVIEW MAY 14, 2010 Electrical: Kory Williams, Adam Gillon, Oladipo Tokunboh Mechanical: Louis Shogry, Andrew Krall.
Modular C ontroller S eries Product Introduction.
CompSci 280 S Introduction to Software Development
Workplace Examples of Design for Disassembly
Part 3 Design What does design mean in different fields?
An Introduction to Software Architecture
Universal Serial Bus (USB)
Product Design for Manufacturability and Automation
Presentation transcript:

1 These are the Skills You Need to Build a House – What’s Missing?

2 What You Need is the Architecture! What is the function of each room? What rooms should interconnect? Where does the plumbing go? How is the wiring laid out? What rooms should not be adjacent? What rooms should be clustered? What about the HVAC layout?

3 The Architecture Provides The Plan The architecture answers these questions: How can the functions be grouped? How should the groups be arranged? What interconnections are necessary? What isolations are necessary?

4 PRODUCT ARCHITECTURE Sources: Ulrich KT and Eppinger SD, Product Design and Development, 3rd ed., McGraw Hill, 2004 Reinertsen DG, Managing the Design Factory: A Product Developer’s Toolkit, Free Press, 1997

5 Elements of Products Functional elements: individual operations and transformations that contribute to the overall performance of the product –often combined into modules Physical elements: the parts, components, and sub-assemblies that ultimately implement the product’s functions.

6 What is Product Architecture? The scheme by which the functional elements of the product are arranged into physical chunks (modules) and by which the physical chunks interact (at interfaces). Module AModule B Interface

7 Planning Product Development Process Concept Development Concept Development System-Level Design System-Level Design Detail Design Detail Design Testing and Refinement Testing and Refinement Production Ramp-Up Production Ramp-Up Product architecture is determined early in the development process. Platform decision Concept decision Decomposition decision

8 Product Architecture: Definition The arrangement of functional elements into physical chunks which become the building blocks for the product or family of products. Product module

9 Primary Types of Product Architecture Modular Nonmodular (Integral) Most products have some degree of modularity!

10 Modular Architecture Chunks (modules) implement one or several elements Interactions between chunks (at interfaces) –must be well-defined –fundamental to the primary functions of the product Modular architecture - allows a design change in one chunk (module) without requiring changes to other chunks (other modules)

11 Modular Product Architectures Characteristics: 1) Chunks (modules) implementing one or a few functions entirely, and 2) well-defined interactions between chunks (interfaces). Swiss Army Knife Sony Walkman

Examples Video Games –Modular: gaming systems (e.g. GameCube) –Integrated: stand-alone arcade games Power Supplies –Modular: power bricks –Integrated: on-board power converter

13 Types of Modularity Slot- modular architecture Bus- modular architecture Sectional-modular architecture

14 Slot-Modular Architecture each interface between chunks different - various chunks cannot be interchanged example: automobile radio - implements exactly one function, but interface different from any other components in the vehicle

15 Bus-Modular Architecture a common bus to which chunks connect via the same type of interface examples: track-lighting, shelving system with rails, expansion card for PC

16 Sectional-Modular Architecture all interfaces of same type, but no single element to which all other chunks attach assembly built by connecting chunks to each other via identical interfaces examples: piping systems, office partitions

17 Modular Architecture of the Sony Walkman

18 Trailer Example: Modular Architecture box hitch fairing bed springs wheels protect cargo from weather connect to vehicle minimize air drag support cargo loads suspend trailer structure transfer loads to road A 1-to-1 correspondence between modules and functions.

Advantage of Modular Design: HP products are designed to be recycled. Recycling design features include: Modular design to allow components to be removed, upgraded or replaced Eliminating glues and adhesives, for example, by using snap-in features Marking plastic parts weighing more than 25g according t ISO international standards, to speed up materials identification during recycling Reducing the number and types of materials used Using single plastic polymers Using molded-in colors and finishes instead of paint, coatings or plating Relying on modular designs for ease of disassembly of dissimilar recyclable materials

20 Integral Architecture (Nonmodular) Functional elements of the product are implemented using more than one chunk A single chunk implements many functional elements Interactions between chunks ill-defined, may be incidental to the primary functions of the products Used with products with highest possible performance in mind

21 Trailer Example: Integral (Nonmodular) Architecture upper half lower half nose piece cargo hanging straps spring slot covers wheels protect cargo from weather connect to vehicle minimize air drag support cargo loads suspend trailer structure transfer loads to road

What is this?

Nail Clippers?

Ford Taurus Integrated Control Panel

25 Other Examples Modular architecture –Xerox copier –Personal computer –Residential AC units Singular (nonmodular) architecture –Table knife –High-performance transmission –Precision-ground bearings

Integral vs. Modular Integral Higher system performance Lower system cost (in large volume) Tightly coupled design teams Expensive Tooling Hard to change Modular Changeability Decoupled design teams Reduced performance Requires flexible manufacturing Cheaper at low volumes

27 Establishing the Architecture To establish an architecture: 1.create a schematic of the product 2.cluster the elements of the schematic to achieve the types of product variety desired. 3.define the interfaces

28 The Concepts of Integral and Modular Apply at Several Levels system sub-system component

29 Product Architecture = Decomposition + Interactions Interactions within chunks Interactions across chunks

30 Schematic For A Wristwatch Source:

31 Schematic For A Telephone Base Source:

32 Product Architecture Example: Hewlett-Packard DeskJet Printer

33 DeskJet Printer Schematic Store Output Store Blank Paper Enclose Printer Provide Structural Support Print Cartridge Position Cartridge In X-Axis Position Paper In Y-Axis Supply DC Power “Pick” Paper Control Printer Command Printer Connect to Host Communicate with Host Display Status Accept User Inputs Flow of forces or energy Flow of material Flow of signals or data Functional or Physical Elements

34 Cluster Elements into Chunks (Modules) Store Output Store Blank Paper Enclose Printer Provide Structural Support Print Cartridge Position Cartridge In X-Axis Position Paper In Y-Axis Supply DC Power “Pick” Paper Control Printer Command Printer Connect to Host Communicate with Host Display Status Accept User Inputs Paper Tray Print Mechanism Logic Board Chassis Enclosure User Interface Board Host Driver Software Power Cord and “Brick” Functional or Physical Elements Chunks

35 Geometric Layout The 3-D Schematic

36 Incidental Interactions Enclosure Paper Tray Chassis Print Mechanism User Interface Board Logic Board Power Cord and “Brick” Host Driver Software Styling Vibration Thermal Distortion RF Interference RF Shielding

37 Product Architecture Objectives Product architecture can be optimized to achieve certain economic objectives –Development Expense –Unit Cost –Product Performance –Development Schedule

38 Using Product Architecture to Achieve Economic Objectives Three key factors to consider when using architecture to achieve economic objectives 1.How modular to make the product (if at all) 2.How to handle variability within the system 3.How to manage the internal interfaces

39 1. Product Architecture and Modularity Two economic objectives most affected by modularity: –Lower development expenses Modules separated from each other except at the interfaces; internal workings immaterial Modules can be reused (no new development, no new testing) –Lower development cycle time Modularity permits concurrent development

40 The Dark Side of Modular Architecture Cost –Interfaces don’t come for free Usually require connectors, couplings, flanges, lines of code; may require special attention to tolerances and alignment Performance –Interfaces are potential bottlenecks –Modular system performance is usually less than with a tightly coupled, nonmodular system Mechanical systems: weak spot is usually the interface, not the components Electrical systems: connectors often limit bandwidth or reliability

41 Product Architecture --The End