0-Systems Engineering Introduction

Question 1

what is a system?

Answer 1

A set of elements interconnected in order to achieve an objective.

• Objective is the MISSION
• Deliberately DESIGNED or ENGINEERED
• Autonomy, must be managerially and operationally independent.
• Also, can be procured independently
• Operating environment
• Boundaries, interfases

Question 2

System as a capability

Answer 2

system is much more than hw+sw. It’s includes organization, personnel, training, facilities, support, etc.
-System is fully defined by all elements so SYSTEM delivers an OPERATIONAL CAPABILITY

Question 3

Logical and Physical descriptions

Answer 3

1) LOGICAL: what the system will do, how well it will do, how it will be tested, operational environment (conditions it will perform), other systems involved with its operation (whats)
2) PHYSICAL: what elements are, how they look, how they are to be manufactured, integrated and tested. (hows)
Both are a series of statements called REQUIREMENTS

Question 4

Logical

Answer 4

1-AXIOMATIC, first WHAT we WANT before to HOW!
2-Logical description changes slowly rather than physical description.
3-Logical Architecture, Requirements Breakdown Structure
4-Logical (functional) Hierarchy, mission is broken in major functions. Also called Functional Architecture.

Question 5

Physical Hierarchy

Answer 5

Usually 4 levels:

System, subsystems, assemblies and components.

Question 6

System and SOS

Answer 6

The distinction between systems as elements of an
SoS (System of Systems) and subsystems as elements of a system is
therefore that the SoS comprises elements (systems) that are optimised for their own purposes before joining the SoS, whereas the system comprises elements (subsystems) that are optimised for the system’s purpose (not necessarily for their own). Or, from the higher perspective, an SoS is most likely not optimised because the elements (the systems) are first optimised for their own purposes, whereas the system is optimised because the subsystems are designed for the system’s optimisation, not their own.

Question 7

Problem and solution domains

Answer 7

1-Problem domain is the business needs, specify what is necessary to solve a problem. Logical / Functional description.
Customer is the owner.
2-Solution domain are the requirements that describe what system can solve the problem. Physical description.
Developer is the owner.