Systems Engineering (SE) is a necessary process to successfully design and operate a complex system, however the process can

also be applied to the design of a simple system.

The process evolved to reduce risk, reduce development time and to enhance product quality. In an SE project a clearly stated mission objective (as composed from the stakeholder expectations) is always at the forefront of the design efforts. The total effort is called the life cycle and is divided into a sequence of phases. In each phase the 11 Systems Engineering Functions can be applied Whereas a systems engineering team creates an architectural design, systems engineering hands off the task of full-blow subsystems detailed design (including design of components and parts) to specialty teams of design engineers who apply the Engineering Design Process (EDP). This is followed by application of the implementation phases up the right leg of the Vee, where physical parts are assembled and integrated into components, components into subsystems, and subsystems into the system. Each component, each subsystem and the system had requirements defined during the top-down implementation phases, and these are verified through testing during the implementation phases. At the top of the Vee the system is validated, i.e. testing of the system to make sure that it does accomplish the mission objective that was the original impetus of the project. If properly practiced, systems engineering leads to an optimized final product, and increases the chance of successfully creating a product that meets customer expectations.

Sytem architech A System can be broadly defined as an integrated set of elements that accomplish a defined objective [5] A system is made up of combinations of elements. A system can be divided into a hierarchy of sets of elements that include subsystems, components, subcomponents and parts. A Subsystem is a system in its own right, except it normally will not provide a useful function on its own, it must be integrated with other subsystems to make a system. Therefore, interfaced or connecting subsystems are required to make-up the system

Components are elements that make up a subsystem or system, may be Commercial Off-TheShelf (COTS) and are adaptable to a particular set of specifications. COTS motors, microcontrollers, solenoids and gearboxes are components. Parts are elements on the lowest level of the hierarchy, and are often COTS, but may need to be designed and manufactured for special applications. Bolts, gears, clamps, resistors, shafts, bearings, etc. fall into this category, as could software that is a "part" in a microcontroller (a

component) in a Command and Data Handling System. (Note: The software development process is not considered in this presentation).

The Engineering Design Process (EDP) for Design of a Subsystem, Component or Part, and its Relationship to SE
EDP is the process used for in-depth, detailed design of parts, components and subsystems. Concurrent Engineering
Pre-Phase A: Concept Studies Phase A: Concept & Technology Development Phase B: Preliminary Design & Technology Completion Phase C: Final Design & Fabrication Phase D: System Assembly, Integration & Test, Launch Formulation

Approval Implementatio n

Phase E: Operations & Sustainment Phase F: Closeout