System-Level Design

PRODUCT ARCHITECTURE

Carlos Andrés Miranda 1

System-Level Design

2
 System-Level Design

Concept System-Level Detail Testing and Production

Planning Development Design Design Refinement Ramp-Up

▪ Product architecture is determined by decisions at several points in the early stages of the
development process.

▪ Product architecture defines the embodiment of the concept and plans how it will be
implemented in the downstream process.

3
Product Architecture
A product can be thought of in both functional and physical terms.

• The functional elements of a product are the individual operations and transformations that
contribute to the overall performance of the product.

• The physical elements of a product are the parts, components, and subassemblies that ultimately
implement the product’s functions.

4
Product Architecture
The physical elements of a product are typically organized into several major physical building
blocks, which we call chunks.

Each chunk is then made up of a collection of components that implement the functions of the
product.

5
Product Architecture
Definition

The architecture of a product is the scheme by which the functional elements of the product are
arranged into physical chunks and by which the chunks interact.

The architecture of a product is the arrangement of functional elements into physical chunks which
become the building blocks for the product or family of products.

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

module
module

module
module
Product
module
module

module
module

7
Product Architecture
Critical architecture decisions

• Decomposition of the product into its sub-systems and components

• Allocation of product functions to the sub-systems and components

• Specification of modular variants of sub-systems and components

• Assignment of design responsibility for sub-systems and components

8
Product Architecture
Modular architecture – Integral architecture

Two designs of bicycle brake and shift controls. The levers on the left exemplify a modular architecture; the lever on the right uses an
integral architecture.

9
Product Architecture

protect cargo
box
from weather

connect to
hitch
vehicle

minimize
fairing
air drag

support
bed
cargo loads

suspend
springs
trailer structure

transfer loads
wheels
to road

10
Product Architecture

protect cargo
upper half
from weather

connect to
lower half
vehicle

minimize
nose piece
air drag

cargo hanging support

straps cargo loads

spring slot suspend

covers trailer structure

transfer loads
wheels
to road

11
Product Architecture
• Chunks implement one or a few functions entirely.
• Interactions between chunks are well defined.
• Modular architecture has advantages in simplicity
and reusability for a product family or platform.

Swiss Army Knife 12

Product Architecture
• Functional elements are implemented by multiple
chunks, or a chunk may implement many functions.
• Interactions between chunks are poorly defined.
• Integral architecture generally increases performance
and reduces costs for any specific product model.

13
Product Architecture
• Functional elements are implemented by multiple
chunks, or a chunk may implement many functions.
• Interactions between chunks are poorly defined.
• Integral architecture generally increases performance
and reduces costs for any specific product model.

High-Performance Wheels 14
Product Architecture
Types of modularity

15
Product Architecture
Types of modularity

Slot-Modular Bus-Modular Sectional-Modular

Architecture Architecture Architecture

16
Product Architecture
Establishing the architecture

The end result of this activity is an approximate geometric layout of the product, descriptions of the
major chunks, and documentation of the key interactions among the chunks.

17
Product Architecture
Establishing the architecture

The end result of this activity is an approximate geometric layout of the product, descriptions of the
major chunks, and documentation of the key interactions among the chunks.

1. Create a schematic of the product.

2. Cluster the elements of the schematic.
3. Create a rough geometric layout.
4. Identify the fundamental and incidental interactions.

18
Product Architecture
Establishing the architecture

1. Create a schematic of the product.

A schematic is a diagram representing the team’s understanding of the constituent elements of the
product.

19
 Enclose
Printer Print
Cartridge

Provide
Structural Accept
Support Position Display
Cartridge User
Inputs Status
In X-Axis

Position
Store
Paper
Output In Y-Axis Control
Printer
Store Supply
“Pick” DC
Blank
Paper Paper Power

Communicate
Command
with
Host Printer
Functional Flow of forces or energy
or Physical Flow of material
Elements Connect
Flow of signals or data to
Host

Schematic of the DeskJet printer. Note the presence of both functional elements (e.g., “Store Output”) and
physical elements (e.g., “Print Cartridge”). For clarity, not all connections among elements are shown.
20
Product Architecture
Establishing the architecture

1. Create a schematic of the product.

The schematic diagram ensures that the team understands the basic elements of the product
needed to produce an operating design.
Some of these elements will be actual components that the team recognizes are required for the
design.
Other elements will still be in functional form because the team has not yet specified their
embodiment.

21
Schematic diagram of the Shot-Buddy showing flows between components.
22
Product Architecture
Establishing the architecture

2. Cluster the elements of the schematic.

The challenge of step 2 is to assign each of the elements of the schematic to a chunk.

23
 Enclosure
Enclose
Printer Print
Cartridge

Provide User Interface Board

Structural Accept
Support Position Display
Cartridge User
Inputs Status
Chassis In X-Axis

Position
Store
Paper
Output In Y-Axis Control Power Cord
Printer and “Brick”
Store Supply
“Pick” DC
Blank
Paper Paper Power

Paper Tray Print

Mechanism Communicate
Command
with
Host Printer
Host Driver
Functional Connect Software
or Physical Chunks to
Elements Host
Logic Board
24
Product Architecture
Establishing the architecture

2. Cluster the elements of the schematic.

One way of deciding on the formation of modules is to start with the assumption that each design
element will be an independent module and then cluster the elements to realize advantages, or
commonalities.
Some of the reasons for clustering elements include requiring close geometric relationship or
precise location, elements that can share a function or an interface, the desire to outsource part of
the design, and the portability of interfaces.

25
26
Product Architecture
Establishing the architecture

3. Create a rough geometric layout.

A geometric layout can be created in two or three dimensions, using drawings, computer models, or
physical models.

27
28
Product Architecture
Establishing the architecture

3. Create a rough geometric layout.

Making a geometric layout allows the designer to investigate whether there is likely to be
geometrical, thermal, or electrical interference between elements and modules.

A trial layout positions modules in a possible physical configuration.

29
30
Product Architecture
Establishing the architecture

4. Identify the fundamental and incidental interactions.

There are two categories of interactions between chunks:

Fundamental interactions are those corresponding to the lines on the schematic that connect
the chunks to one another.

Incidental interactions are those that arise because of the particular physical implementation of
functional elements or because of the geometric arrangement of the chunks.

31
 User Interface
Enclosure Cartridge
Board

Styling Alignment
Thermal
Vibration Print Distortion Logic Host Driver
Paper Tray
Mechanism Board Software

Thermal RF
Distortion RF Interference
Shielding
Power Cord
Chassis
and “Brick”

Incidental interaction graph.

32
Product Architecture
At the conclusion of the embodiment design phase of the product development process, each
product module must be described in complete detail. The documentation on each module should
include:

• Functional requirements
• Drawings or sketches of the module and its component parts
• Preliminary component selection for the module
• Detailed description of placement within the product
• Detailed descriptions of interfaces with neighboring modules
• Accurate models for expected interactions with neighboring modules

33
Product Architecture
The design of modules may often proceed independently after the product architecture is
completed.

This allows the module design tasks to be given to teams specializing in the design of one particular
type of subsystem.

34