SystemHierarchyModule-SpaceSystemsEngineering.pptVIP

date Presentation name  Module Purpose: System Hierarchy To show how one view of the system architecture is captured by the product breakdown structure (PBS). To describe the benefits and costs of creating a system hierarchy. To show how to capture all of the work necessary for a project by adding the non-product work to the PBS to create the work breakdown structure (WBS). Why Break a Product Down? Breaking a large complex problem (project) into smaller pieces makes them easier to solve since the problems are smaller and specialists can focus on their functional areas. But this process of reductionism creates some new problems. Namely, New interfaces are created between the pieces (subsystems), so they must be defined and managed. System resources (e.g., mass or power) must be allocated to the subsystems and these allocations must be accounted for; and System performance is also allocated to subsystems, so confidence must be established that if all of the subsystems perform as desired, then the system will perform as desired. The creation of the system architecture, the description and management of interfaces, the allocation of resources and performances, and establishing confidence that these allocations are appropriate are all systems engineering responsibilities. More Value to Creating A System Hierarchy Organizes the work required to complete a flight project. Contains all hardware items, software items, and information items (e.g., documents, databases). Provides the basis for functional analysis. Characteristics: Top-down, Product-based, Lowest level maps to cognizant engineer or manager, Branch points in hierarchy show how elements will be integrated. Hierarchical Level Names and Examples System Hierarchy (1/2) Hierarchy/Hierarchical Levels - The relationship of one item of hardware/software with respect to items above and below in the relative order of things. Mission - An individual system or groups of systems operated to meet a specific set of o