Systems Engineering

The Evolution of Systems Engineering

Systems engineering is concerned with the engineering of a set of parts that interact together to create a whole.

A life cycle is the general phases a system goes through. For example, the DoD has the following phases: material solution analysis, technology development, engineering, and manufacturing development, production and deployment, and operations and support.

There are fundamental elements between them all.

Model of systems engineering is based on a “V” representation with the left side reprsenting concept development, and the decomposition of requirements into functions and physical entities that can be architected, designed and developed.

Right side is the integration of those entites (w/ testing) into the field where they’re operated and maintained.

However, it’s rarely as linear as “modeled”, and there are variations.

Systems engineering works best when system requirements are already established, the user community is relatively homogenous, and a single individual has management and funding of the program. But they’re rarely sufficient for success.

System of Systems (SoS)

A system of systems is what results when independant and useful systems are integrated into a larger one.

Types of SoS:

Virtual

Virtual SoS lack central management authority and a centrally agreed on purpose for the system of systems. Relies on relatively invisible mechanisms to maintain it.

Collaborative

Component systemsinteract voluntarily to fulfill agreed-on central purposes. The Internet is a collaborative system. There are standards, but no power to enforce it, and central players simply decide to provide or deny services to enforce it.

Acknowledged

Have recognized obectives. Designateed manager and resources, but systems retain their independant ownership, objectives, etc. Changes in the systems are collaborated between the SoS and the system.

Directed

SoS is built and managed for a specific purpose. Centrally managed in long-term operations, component systems can operate independently but normal operational mode is subordinated to the central managed purpose.

SE Life-Cycle Building Blocks

1. Concept Development

   Transforms user expression of operational needs into well-defined concept of operations, high-level conceptual definition, and a set of initial operational requirements.

2. Requirements Engineering

   Detailed system requirements are taken from stakeholders, where they’re further analyzed and refined. From them, processes for managing requirements through the rest of the system life cycle are developed. Uncertainty and instability of requirements are accomodated and planned for.

3. System Architecture Once requirements are expressed and folded into a management process (whatever the fuck that means), a system architecture can be described. It provdes the foundation for further development, integration, testing, operation, interfacing, and improvement of the system.

4. System Design and Development