Systems Engineering Management
Systems Engineering Management tests planning and control of technical work: how scope, cost, schedule, risk, configuration, information, and decisions are governed across the life cycle. Questions target the technical management processes of ISO/IEC/IEEE 15288, including project planning, project assessment and control, decision management, risk management, configuration management, information management, and measurement, plus reviews and tailoring.
Planning and WBS
The systems engineering management plan defines technical approach, organization, schedules, resources, and control gates. A work breakdown structure decomposes deliverables and work packages by product and task, not by organization chart. Tailoring is expected: a small upgrade may not need the same review rigor as a safety-critical new system, but the rationale must be documented.
Risk and measurement
Risk management identifies, analyzes, plans handling, monitors, and communicates. Handling options include avoid, mitigate, transfer, and accept. Each risk needs an owner, trigger, and response. Measurement uses technical performance measures and leading indicators; a good measure informs a decision, not just reports status.
Configuration and baselines
Configuration management identifies configuration items, controls changes, records status, and audits. Baselines anchor control: functional baseline at system requirements approval, allocated baseline at preliminary design, product baseline at critical design or acceptance. A change to a baselined requirement follows impact analysis and approval, not informal agreement.
Worked example
During integration, a supplier reports that an interface connector will slip six weeks, threatening a key test. The team should log the risk, assess likelihood and consequence, and select a handling option. If a qualified alternate connector exists but requires a design change, the team evaluates cost and schedule, then chooses mitigate by qualifying the alternate or accept by resequencing the test, with a decision record. Reasoning: risk handling is a documented decision with an owner and trigger, not an email escalation.
Traps that cost marks
Confusing a WBS with an organization chart; treating a risk register as a list without owners or triggers; changing a baseline without configuration control; using earned value or percent complete as the only technical measure; omitting tailoring rationale; holding reviews as status meetings rather than decision gates.