General Systems Engineering
General Systems Engineering tests whether you can define and reason about a whole system, not just a collection of components. Questions in this domain draw on ISO/IEC/IEEE 15288 life-cycle process concepts, system boundary and context, emergence, recursion, iteration, and the distinction between the system of interest and its enabling systems. The exam rewards candidates who can identify the system boundary that matches authority, responsibility, and life-cycle scope.
Systems, boundaries, and context
A system is an integrated set of elements that accomplishes a defined objective. The system of interest (SOI) is the one being engineered; enabling systems support the SOI across its life cycle, such as production, test, deployment, support, and disposal systems. Boundary selection changes the requirement set: too narrow and external interfaces are missed; too wide and the project absorbs problems it does not control. Context diagrams, interface lists, and explicit external actors make the boundary visible.
Life-cycle processes
15288 organizes processes into agreement, organizational project-enabling, technical management, and technical processes. The technical processes run from business or mission analysis through stakeholder needs, system requirements, architecture definition, design definition, integration, verification, transition, validation, operation, maintenance, and disposal. They are recursive: the same set can apply at system, subsystem, and component levels. Iteration is normal when knowledge improves, provided baselines and decision gates control change.
Emergence and holism
Emergent properties appear only at the system level, such as end-to-end latency, throughput, safety, and security posture. They cannot be proven by inspecting components alone, so integration and verification must exercise interfaces and operational threads.
Worked example
A city plans a congestion-charging service. If the SOI is roadside cameras and payment processing, then enforcement, appeals, and privacy compliance fall outside, and the transport authority back office is an enabling system. If the SOI is the charging service, cameras, payment gateway, appeals workflow, and customer account management are inside, while the authority finance system may remain enabling. The defensible answer is not the widest boundary; it is the boundary aligned with decision authority and life-cycle responsibility. Reasoning: the exam tests whether you can name what is being engineered, what supports it, and who accepts the resulting risk.
Traps that cost marks
Treating the V-model as a mandatory waterfall sequence; calling enabling systems subsystems; assuming component tests demonstrate emergent system behavior; omitting disposal and support from life-cycle thinking; drawing a context boundary without external interfaces.