MODULE 1

SYSTEMS AND SYSTEMS

UNIT 1
INTRODUCTION TO SYSTEMS
UNIT LEARNING OUTCOMES
 TLO 1: Discuss the essential insight about system and system thinking
with an orientation toward system engineering and analysis.

Answer the following question and submit your answers as a comment under “M1 Q&A”

What is a System?
Give an example of a system you know and describe its features. Please answer not
lessthan 3 sentences and not more than 5.

Read and research on Systems, System life cycle and Systems Engineering

3
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 WHAT IS A SYSTEM

Use of the word “System”. The word “system” has many contexts

There are PHYSICAL SYSTEMS such as

 Communications System
 Satellite System
 Pulley System
 Solar System

There are CONCEPTUAL SYSTEMS such as

 Religious Systems
 Social Systems
 Banking Systems
 Government Systems

More-esoteric examples, such as the consideration of individual and social behavior as a

system of purposeful events.

The common aspect of ‘system’ stems from its early use to refer to:
 The whole (or the set) that results when a number of things have been grouped
in aparticular manner.

So, what is a ‘system’ in the context of system engineering?

DEFINITION OF A SYSTEM

A system comprises:
1. COMPONENTS are the operating parts of a system consisting of input, process, and
output.
2. ATTRIBUTES are the properties or discernible manifestations of the components
of asystem. These attributes characterize the system.
3. RELATIONSHIPS are links between components and attributes
4. SYSTEM BOUNDARY

THE MISSION OF THE SYSTEM

The purpose of the system is called its mission

– Must be clearly stated by business management and stakeholders
– Represents the start point of the design process
– Provides the basis for the ultimate test of the system’s fitness-for-purpose

4
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 In the broadest sense, the mission of the system is to provide a solution to a business problem
Narrowing the definition of a system has two major implications:
1. The systems elements, attributes, relationships and boundary are not accidental
butresult from deliberate design (engineering)
2. A system must be managerially and operationally independent (and may well have
been procured independently)

TYPES OF SYSTEMS

There are four main classification of system:

– Closed/Open System
– Natural/Human-made or Human-modified system
– Physical/Conceptual System
– Precedented/Unprecedented

Closed/Open Systems

 An open system interacts with its operating environment through inputs and
outputsacross the boundary.
Ex: Steam Turbine, Water Pump

 A closed system is isolated from its external environment.

Ex: Piston and Cylinder

 We are only interested in useful systems. Which are therefore open

Natural/Human-made or Human-modified system

 Natural systems contain natural elements and are the result of natural processes.
Ex: (hydrologic, atmospheric, biological, geological) systems. Solar System, Human
Digestive System,

 Human-made systems come into existence through the efforts of humans and may
contain human-made elements or natural elements adapted to human-designed
purposes.
Ex: bikes, computers, maps, internet, lights, pipes

 Natural systems that have been modified for human purposes are called human-
modified systems.

 We are only interested in human-made/modified systems

Physical/Conceptual System
 Physical systems exist in a physical form.

 Conceptual systems do not have a physical form.

Ex: Banking System

5
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 Physical System – building of bank, cash, credit and debit cards
Conceptual System – online banking

 We focus on the physical system.

Precedented/Unprecedented
 A precedented system has been produces before

 An unprecedented system has not been previously produced and requires

substantialresearch and development.

 Systems Engineering is interested predominantly in the precedented systems

(those which we know how to engineer)

TECHNOLOGY AND TECHNICAL SYSTEMS

Technology
– the application of scientific knowledge to the practical aims of human life or, as it is
sometimes phrased, to the change and manipulation of the human environment.
– Branch of knowledge that deals with industrial arts, applied science, and engineering,
or the sum of the ways in which social groups provide themselves with the material
objects of their civilization.

Technology and Society

Human society if characterized by its culture.

Technical system
– A technical system may be used to represent all types of human-made artifacts,
including technical products and processes.
– Collection of activities that are performed by engineers within the processes of
engineering design, including generating, retrieving, processing, and transmitting
information about products.

Technological Growth and Change

– Technological growth and change is occurring continuously and is stimulated by an
attempt to respond to some unmet current nee and/or an attempt to perform
ongoing activities in a more effective and efficient manner

TYPES OF SYSTEMS

A wide variety of combinations of the characteristics can lead to a large number of types
of systems, each of which has markedly different properties.

Systems engineering is applied to open, physical systems that are human made/modified
from largely precedented elements.

6
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 A SYSTEM AND ITS ENVIRONMENT

OPERATING ENVIRONMENT

EXTERNAL
ELEMENT

EXTERNAL INTERFACE SYSTEM

SYSTEM OF INTEREST
(input/output) ELEMENT
SOI

SYSTEM INTERCONNECTION /
BOUNDARY RELATIONSHIP

SYSTEM AS A PRODUCT
In a physical sense, the term system is sometimes considered to be synonymous with
product—that is, we say that the project is delivering a system, or is delivering a product.

SYSTEM AS A CAPABILITY
Systems are much more than an aggregation of hardware or software products and also
include: organization, personnel, collective training systems, facilities, data, support and
operating procedures and organizational policies

CAPABILITY SYSTEM
 Each of the elements of a capability system will probably have a different
acquisition cycle, since each represent a different type of acquisition.
 Here we focus on the major equipment element so that the descriptions are less
cluttered.
 We must remember, however, that all elements are acquired in parallel and
must be brought back together prior to introduction into service in order to field
an operationalcapability.

CAPABILITY SYSTEM ELEMENTS – ACME AIR

Resources for our audit system example could include, but not limited to:
– Personal
– Support
– Facilities
– Organization, Policies and Procedures
– Collective Training
– Data
– Major Equipment

LOGICAL AND PHYSICAL DESCRIPTIONS

A system can be described in two broad ways:

7
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 LOGICAL (or functional) – what the system will do, how well it will do it, how it will be
tested, under what conditions it will perform, and what other systems will be involved
with its operation

PHYSICAL – what the system elements are, how they look, and how they are to be
manufactured, integrated, and tested.

Both the logical and physical descriptions of a system comprise a series of statements called
requirements

The two descriptions are valid independent descriptions of a system:

- We develop the logical description first
- How we implement current physical systems should not color unnecessarily the
wayin which we might describe future systems
- Upper-level trade-offs and feasibility analyses must be conducted at the logical
level before deciding on the physical implementation
- A logical description is ideally suited to the interface between systems engineering
and the business case.
- The logical description changes slowly; the physical description changes much faster

In the development of a system, therefore, there are at least two architectural views: a
system logical architecture, and a system physical architecture.

Of course, these two descriptions are the same system so they must be related. We
will see later how the logical architecture, as outlined in the requirements breakdown
structure (RBS), is mapped onto the physical architecture as represented by the
configuration items contained in the work breakdown structure (WBS).

HIERARCHICAL DESCRIPTIONS OF A SYSTEM

We can consider the system to a hierarchical composition of system elements (either

logicalor physical).

8
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
LOGICAL (FUNCTIONAL) HEIRARCHY
In a logical description of a system, the system’s mission is broken down into a
hierarchical structure of its major functions. The logical description or architecture is
therefore often calleda functional hierarchy, or a functional architecture.

PHYSICAL HIERARCHY
We use a simple four-layer representation (system, subsystem, assembly, component)
whichcan be more elaborate

SYSTEM SUBSYSTEM ASSEMBLIES COMPONENTS

It is common to allow the hierarchical terms to be relative. For example, an aircraft
system contains, among others, the engine subsystem, which may consist of assemblies
such as fuel tanks, pumps and lines, turbines, compressors, gear boxes, and hydraulic
pumps.

The engine manufacturer may consider the engine to be the system, comprising fuel,
powerplant, and hydraulic subsystems, and so on.

However, an implicit part of the definition of a system is that it must be able to stand
alone in its own right. An engine is therefore not a system – it is only useful as an element
of a system(that is, a subsystem).

9
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 HIERARCHY OF A SYSTEM OF INTEREST
It is probably better, therefore, to consider a system of interest (SOI) to comprise a
combination of interacting system elements, some of which may be systems in their own
right.

SYSTEMS / SYSTEMS-OF-SYSTEMS

10
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 SYSTEM OR SYSTEM-OF-SYSTEMS (SOS)

PROBLEM AND SOLUTION DOMAINS

Remember that a system can be considered to a solution to a problem

It is common to consider the activities being undertaken throughout the life of the
system to be in either the:
- Problem domain (problem space) where we use predominantly logical
descriptions,or
- Solution domain (solution space) where we use predominantly physical descriptions

Activities in the problem domain (including logical architecture) are the responsibility of
the customer (the business owner); activities in the solution domain (including the
physicalarchitecture) are commonly the responsibility of the organization implementing
the system (the developer).

UNIT 2
INTRODUCTION TO SYSTEMS LIFE
CYCLE UNIT LEARNING OUTCOMES
 TLO 1: Discuss the essential insight about system and system thinking
with an orientation toward system engineering and analysis.

SYSTEM LIFE CYCLE

GENERIC SYSTEM LIFE CYCLE

A system has a life. It is brought into being. used ang then disposed of when it no longer
serves its purpose

11
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
Throughout the life of a system, therefore, there are a number of phases and activities,
eachof which builds on the results of the preceding phase or activity.

The sum of all these activities is called a system life cycle.

A generic system life cycle can be divided into four very broad phases.

1. PRE-ACQUISITION PHASE
- The life cycle begins in the Pre-acquisition Phase with an idea for a system being
generated as a result of business planning

- Business needs confirmed and supported by a business case

- Ensures that only feasible, cost effective projects are taken forward to acquisition

2. ACQUISITION PHASE
- The acquisition phase is focused on the bringing the system into being and into the
service of the organization.

- The System is defined in terms of:

 business requirements
 stakeholder requirements, and
 system requirements

- A contractor is then normally engaged to develop/deliver the system.

3. UTILIZATION PHASE
- The system is operated and supported during the utilization phase.

- During Utilization the system may undergo a number of modifications and

upgradesto:
 rectify performance shortfalls
 meet changing operational requirements or external environments to
enableongoing support for the system to be maintained, or
 enhance current or performance reliability

4. RETIREMENT PHASE
- The system remains in service during the Utilization Phase until:
 the business has no further need for the system, or
 it no longer can meet the functions required of it, or
 it is no longer cost-effective to keep it in service.

- If the business need for the capability still exists in the organization, the
conclusion ofone system life cycle marks the start of another and the process
begins again.

12
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
PARTIES INVOLVED

Throughout the system life cycle, there are a number of parties

involved. The customer organization is managed by
 enterprise management who set the direction for the organization and
 business management who are responsible for the activities conducted by
 the operations element of the organization which is run by
 the operators—sometimes called the users

The systems used within the organization are acquired by:

- the acquisition element (also called the acquirer, or tasking activity) of the
organization under the auspices of

- a project manager who typically manages

- a project

Project managers are supported by a number of related disciplines including:

- systems engineering
- requirements engineering
- specialist engineering disciplines
- quality assurance, and
- integrated logistic support

Operators are supported in their operation of the system by the support element of the
organization. which supports, sustains, and maintains the system throughout Its life.

In addition to the operational, acquisition, and support staff, there are many others
withinthe customer organization who have a stake in the successful implementation of
the project.

These stakeholders can include representatives from the management, financial,

operations, supply. maintenance, and facilities areas of the organization.

PARTIES INVOLVED
The system is obtained from a supplier (also called the performing activity) who may
deliver the system off-the -shelf or may develop It, In which case they are often called
the developer.

The supplier (developer) may be an internal part of the customer (acquire) organization.

It is increasingly common these days for the supply or development to be undertaken

by anoutside organization called a contractor.

The relationship between the customer and the contractor ls defined by the terms and
conditions of the contract.

13
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 Often the contractor is not able to perform all of the work required and devolves
packagesof work to a number of subcontractors through number of subcontracts.

RESPONSIBILITY OF THE PARTIES INVOLVED

Responsibility for the various phases of the system life cycle is spread across the enterprise (or
organization) within which the eventual system will operate.

 Note that all parties are involved at all stages in the life cycle, with the roles and
responsibilities of each party shifting in emphasis between stages.

ACTIVITIES IN ACQUISITION AND UTILISATION PHASES

 Systems engineering is predominantly related to the Acquisition Phase of the

systemlife cycle and, to a lesser extent, the Utilization Phase.

 These two phases comprise a number of activities.

 The Acquisition Phase comprises the four main activities of Conceptual Design,
Preliminary Design, Detailed Design and Development, and Construction and/or
Production

 Here we look at each of these activities in a little more detail-we will examine
them inmuch more detail in later weeks.

CONCEPTUAL DESIGN

Formal transition from the business world to the project world-from the mission statement to
complete logical description of the system-of-interest.

Ensures proper definition of the system requirements.

Ensures appropriate engagement with business managers and upper-level stakeholders.

14
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
Business Needs and Requirements (BNR) are articulated and confirmed by business
management.

BNR are elaborated by stakeholders at the business operations level into a set of
StakeholderNeeds and Requirements (SNR)

SNR are elaborated by requirements engineers into system requirements in the System
Requirement Specification (SyRS)

The BNR. SNR and the SyRS are key elements of what is called the Functional Baseline

(FBL) Conceptual Design ends with the System Design Review (SDR), which finalizes the

initial FBL

SDR confirms the BNR. SNR and the SyRS, and provides a formal record of design
decisionsand design acceptance.

PRELIMINARY DESIGN
Converts the logical architecture in the initial FBL into description of the physical
subsystems (the upper-level physical architecture) that will meet the system
requirements.

Results in the Allocated Baseline (ABL), so-called because the functionality of the
system is now allocated to physical building blocks called configuration items (C),
which are described in Development Specifications.

Ends with a Preliminary Design Review (PDR)

DETAILED DESIGN AND DEVELOPMENT

Uses engineering disciplines to develop the individual subsystems. assemblies. and
components in the system.

Results in the Product Baseline (PBL) as the system is now defined by the numerous products
(subsystems. assemblies. An components) as well as the materials and processes for
manufacturing and construction.

Ends with Critical Design Review (CDR)

 15
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
CONSTRUCTION AND/OR DEVELOPMENT
Components are produced in accordance with the PBL specifications and the system is
ultimately constructed.

Ends with Formal Qualification Review (FQR), which provides the basis upon which the
customer accepts the system from the contractor.

FQR Is Informed by the results of acceptance test and evaluation (ATBE)

UTILISATION AND RETIREMENT PHASES

Major activities in Utilization Phase are:
- Operational Use
- System Support

Modifications may be

necessary.

The system life cycle ends with the Retirement Phase.

DEVELOPMENT APPROACHES

We have presented the life-cycle phases and activities in sequence.

This assumes the waterfall approach to development.

There are other approaches such as incremental, spiral, and evolutionary acquisition,
eachof which has strengths and weaknesses.

For simplicity, we continue to assume the waterfall approach for the majority of the
course- a solid understanding of the approach Is useful because It helps understand the
others, andthe others all have the waterfall approach as a fundamental building block.

UNIT 3
INTRODUCTION TO SYSTEMS
ENGINEERING UNIT LEARNING
OUTCOMES
 TLO 1: Discuss the essential insight about system and system thinking
with an orientation toward system engineering and analysis.

WHAT IS SYSTEMS ENGINEERING?

There Is a wide range of definitions of systems engineering, each of which tends to reflect
the particular focus of its source.

There is a wide range of definitions of systems engineering. each of which tends to reflect
the particular focus of its source.
 16
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 SYSTEMS ENGINEERING
 Systems engineering differs from mechanical, electrical, and other
engineering disciplines in several important way
 Systems engineering is focused on the system as a whole.
 It is focused on its total operation.
 It looks at the system from the outside, that is, at its interactions with other
systems and the environment, as well as from the inside.
While the primary purpose of systems engineering is to guide, this does not mean
thatsystems engineers do not themselves play a key role in system design.
Systems engineering bridges the traditional engineering disciplines.

Systems engineering encompasses:

1) technical efforts related to development, manufacturing, verification, deployment,
operations, support, disposal of, and training for, system products and processes
2) the definition and management of the system configuration
3) the translation of the system definition into a work breakdown structure
4) development of information for management decision-making.

There are, however, a number of common themes which indicate the key tenets of systems
engineering:
- Top-down approach
- Requirements engineering
- Life-cycle focus
- System optimization and balance
- Integration of specializations and disciplines
- Management

TOP-DOWN APPROACH

Traditional engineering disciplines are based on bottom-up approach:

- We design and build components, integrate them into the next higher level
element and so on until we have the system.
- This is very effective so long as we are trying to solve a particular, well-defined
problem.

Complex problems with many inter-relationships tend not to be suited to bottom-up solutions.

Start by looking at the system as a whole to provide a thorough understanding of the

systemand its environment and interfaces.

System-level requirements are developed.

Likely subsystems can then be considered and requirements assigned to individual

subsystems, the subsystems further broken down into assemblies, and then into components.

17
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 This process continues until a complete understanding is achieved of the system from top to
bottom which allows:
- Additional (derived requirements) to be developed.
- Interfaces between subsystems to be identified.

This approach Is well documented in process standards like ANSI/EIA-632.

BOTTOM-UP APPRAOCH

While design is top-down, integration is bottom-up.

At each stage of the integration, some form of integration testing will be conducted to
verify the successful integration.

REQUIREMENTS ENGINEERING
Complete and accurate definition of requirements is fundamental to project success.

Original need translates into statements of requirement which form the basis of
functional and (eventually) physical design.

These transitions must be managed by a rigorous process called requirements engineerin9.

‘Poor requirements cannot be rectified by good design'

Complete and accurate definition of requirements is fundamental to project success.

Original need translates into statements of requirement which form the basis of
functional and (eventually) physical design.

18
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
These transitions must be managed by a rigorous process called requirements engineering.

Once requirements have been collected, the systems engineering process then focuses
on the derivation and decomposition of these requirements from the system level right
down to the lowest constituent component (sometimes referred to as requirements flow
down).

REQUIRMENTS ENGINEERING
Requirements traceability Is essential:
- Forward traceability Is required so that design decisions can be traced from any
givensystem-level requirement down to a detailed design decision.
- Backward traceability means that any lower-level requirement is associated
with at least one higher-level requirement.

Traceability assures the customer that all requirements can be accounted for in the
design at any stage and that no unnecessary requirements are included

Traceability also supports the configuration control (change management) process.

Requirements traceability Is a feature of top-down design, which guarantees that

requirements can be satisfied at any stage.

LIFE-CYCLE FOCUS
Systems engineering maintains a life-cycle focus as decisions are made.

Often the temptation is to focus on acquisition issues in order to minimize acquisition

costs and schedules

Given that a system spends a majority of its life in utilization the full life-cycle cost (LCC)
mustbe considered

As a simple example, it is false economy to buy a cheaper car that has very high running
costs, if a slightly more expensive car can be acquired which has lower through- life costs
(and therefore a lower LCC)

SYSTEM OPTIMIZATION AND BALANCE

We cover this issue in detail later but basically a collection of optimally-designed
subsystems do not necessarily lead to an optimal system.

Systems engineering is looking for optimal system-level performance.

‘Consider an F1 Engine added to a small family car’

We cover this issue in detail later but basically a collection of optimally-designed

subsystems do not necessarily lead to an optimal system.

19
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 Systems engineering is looking for optimal system-level performance.

This sometimes must force subsystem and component designers down sub-optimal paths.

Also, system engineering recognizes that the system must be designed with balance in mind.
- For example we must balance system performance with other factors such as
social,ethical, cultural and psychological effects (and others).

INTEGRATION OF SPECIALIZATIONS/ DISCIPLINES

Systems engineering integrates a diverse range of technical disciplines and specializations.

Our aircraft example illustrates this point because it involves more than Just engineering
disciplines-must also Involve finance. legal. environmental specialists and so on.

Systems engineering defines the tasks that can be completed by these disparate
disciplines and specialties and then provides the management to integrate their efforts to
produce asystem.

This function is essential because of the complexity of large projects and their contracting
mechanisms. and the geographic dispersion of contractor and subcontractor personnel
across the country and around the world.

MANAGEMENT

Systems engineering clearly has a technical role to play but it also has a very important
management role.

There is a very strong link between the necessary functions of project management and
systems engineering.

Systems engineering products ensure project management decisions are informed.

More on this later.

PRACTICE EXERCISES:

Exercise 1 – Identify the options for drawing a boundary around a Domestic Dwelling system.
Because there are so many types of domestic dwelling, you should start by considering a

20
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 single, free-standing house on a block of land which is surrounded by a fence. If you have
time, consider how different the boundary would be for an apartment.

 Identify the options for a boundary around the Domestic Dwelling system.

 Remember that a boundary is essential because it allows us to understand which

elements are included as part of the system

OPERATING ENVIRONMENT

EXTERNAL
ELEMENT

EXTERNAL INTERFACE SYSTEM

SYSTEM OF INTEREST
(input/output) ELEMENT
SOI

SYSTEM INTERCONNECTION /
BOUNDARY RELATIONSHIP

 Even in a system that is relatively easy to describe (such as is the case here for the
Domestic Dwelling). the drawing of a system boundary can vary quite widely

 A formal focus on the boundary definition is therefore very important.

 Let's have a look at what options there may be for our Dwelling

21
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
  First option could be to just define the house walls as a boundary – assuming, or
course the owners own the whole house

 The first option could be to just define the house walls as a

boundaryBut. what about:

- A carport/garage?
- A veranda/porch/deck?
- The yard?
- The fence?

22
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
  A more likely solution is to extend the boundary out to include the yar using
surveyedboundary
Still, need to
consider
- The fence?

 …and we may have to extend out to the edge of the footpath

Still, need to consider
- The nature strips?
- The footpath

23
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
  Notice that out boundary will be quite different if we consider a different sort of
dwelling.
 Consider an apartment clock where there are four apartments sharing a common
foyer

 In this case we might be quite happy with the apartment walls forming the
boundaryof the system

24
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
  In this case, we might be quite happy with the apartment walls forming the
boundary of the system.
Still, need to consider:
- The foyer?
- The elevator?
- The car parks?
- Storage areas in the basement?

Exercise 2 – Draw up a table of upper-level functional and physical terms that can be used
to describe the Domestic Dwelling system. For example, one upper-level function of the
dwelling would be to “prepare food” whereas a physical element of the system would be
“kitchen”.

 Let’s now look at the physical descriptions of a Dwelling.

 Unlike the functional descriptions (which will be very similar for all types of
dwelling), the physical descriptions will be quite different depending on what sort
of dwellingyou had in mind
 Let’s use our suburban house as an example.

 Walls/Floor/Roof Pool
 Closets  Dining Room
 Bedrooms  Gym
 Power Distribution  Entertainment Area
 Bathrooms  Outside Kitchen (BBQ)
 Communications  Informal Dining Area
 Storage Rooms  Shed
 Kitchen  Garage
 Home  Air conditioning/Heating
Office/Study
 Foyer

 25
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any
 Answer the following in a short bond paper and submit it under Module 1 Formative
Assessment.

Using a Motorcycle System, create a list of functional and physical terms, develop a
functional hierarchy and a physical hierarchy for the Motorcycle System.

26
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or
transmitting in any form or by any