Systems Engineering

← Back to Domain-Specific Abstractions by Domain

12 domain-specific abstractions whose origin domain is Systems Engineering.

• Bond graph — A domain-independent graphical model of power exchange in dynamic physical systems using effort–flow variable pairs and energy-conserving junctions.
• Capacitor-spring analogy — Map an ideal electrical capacitor to a mechanical spring by preserving constitutive integral form, with voltage corresponding to force, current to velocity, charge to displacement, and capacitance to compliance.
• Function model — A structured representation of what a system does, decomposing required functions and their flows independently enough from implementation to support analysis and design.
• IDEF0 — Model a system's functions as hierarchically decomposed activity boxes with Input, Control, Output, and Mechanism arrows, preserving parent-child boundary interfaces across levels of detail.
• Model-based design — A development process in which an explicit executable system model serves as the central specification for analysis, simulation, design decisions, implementation generation and verification.
• Object Process Methodology — A systems-modeling language and methodology that represents stateful objects and the processes that create, transform or consume them in one integrated model.
• Redundancy (engineering) — Intentional duplication or diversification of components, information or functions so a system can tolerate failures or improve performance.
• Requirement Diagram — The SysML v1.x graphical view that presents requirements and selected hierarchy, derivation, satisfaction, verification, refinement, copy, trace, or containment links to other model elements.
• Structured analysis and design technique — A hierarchical functional modeling methodology using box-and-arrow activity and data diagrams to describe system inputs, controls, outputs and mechanisms.
• Systems integrator — A functional engineering role responsible for combining independently developed subsystems and verifying that their interfaces produce the required whole-system behavior.
• Systems modeling — The interdisciplinary practice of constructing purpose-specific representations of a system’s structure, functions, behavior, requirements and environment.
• Test and evaluation master plan — A governing program document that integrates test objectives, resources, responsibilities, schedules, environments, and decision evidence across a system lifecycle.