I85PREP
⌘ K
CSEP study materials
CSEP study resources

CSEP practice questions

One question at a time. Build your CSEP understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1General Systems Engineering

In systems engineering, which term best describes a temporary configuration of system elements assembled to satisfy a specific operational need, with its own defined interfaces and lifecycle?

  1. System-of-interest
  2. System of systems
  3. System architecture Correct answer.
  4. System boundary

Explanation

A system architecture is the fundamental organization of a system embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution. It defines the structure, interfaces, and guiding principles that persist across the system's lifecycle rather than describing a temporary assembly.

Question 2General Systems Engineering

Which lifecycle model explicitly produces a series of incremental builds, each delivering usable functionality, while allowing requirements to evolve between increments?

  1. Incremental model Correct answer.
  2. Spiral model
  3. Waterfall model
  4. V-model

Explanation

The incremental model partitions the system into increments that are designed, built, and delivered in sequence, with each increment adding usable capability. Requirements for later increments can be refined as earlier increments are validated, which is a defining trait of incremental development.

Question 3General Systems Engineering

A stakeholder requirement states that the system shall reduce average mission planning time by 30 percent. At which level of the requirements hierarchy does this statement most appropriately belong?

  1. Stakeholder requirements Correct answer.
  2. Subsystem requirements
  3. System requirements
  4. Component design specification

Explanation

Stakeholder requirements capture needs and expectations expressed in the stakeholders' terms, often as outcome-oriented goals such as reduced planning time. They are transformed into verifiable system requirements during requirements analysis rather than being allocated directly to subsystems.

Question 4General Systems Engineering

Which activity is the primary purpose of the concept of operations (ConOps) document in a systems engineering effort?

  1. Describing how the system will be used to meet stakeholder needs in its operational environment Correct answer.
  2. Documenting the detailed internal design of each subsystem
  3. Specifying the procurement schedule for system components
  4. Recording the verification results for each requirement

Explanation

A ConOps describes the system from an operational perspective, showing how users and the system interact to accomplish missions in the intended environment. It bridges stakeholder needs and system requirements by illustrating operational scenarios and usage.

Question 5General Systems Engineering

During a design review, an engineer argues that a requirement stating 'the operator interface shall be user-friendly' is acceptable. Which characteristic of a good requirement does this statement most clearly violate?

  1. Traceability
  2. Feasibility
  3. Necessity
  4. Verifiability Correct answer.

Explanation

A good requirement must be verifiable, meaning a finite and objective process exists to confirm that the system meets it. 'User-friendly' has no objective acceptance criterion, so it cannot be verified without further definition.

Question 6General Systems Engineering

Which document formally establishes the technical baseline agreed between the acquirer and the developer at the end of the system requirements phase?

  1. Interface control document
  2. Product baseline
  3. Allocated baseline
  4. Functional baseline Correct answer.

Explanation

The functional baseline is established when the system-level requirements and the concept documentation are approved, defining what the system must do. It is the first of the three classic configuration baselines and precedes allocation to lower-level items.

Question 7General Systems Engineering

In a functional analysis, which tool best supports decomposing a top-level function into subfunctions while showing the flow of inputs, outputs, and controls among them?

  1. Pareto chart
  2. Requirements traceability matrix
  3. Functional flow block diagram Correct answer.
  4. Work breakdown structure

Explanation

A functional flow block diagram decomposes system functions into a logical sequence of subfunctions and shows the inputs, outputs, and control relationships among them. It is a standard functional analysis tool for understanding functional behavior before physical allocation.

Question 8General Systems Engineering

Which statement correctly distinguishes verification from validation in systems engineering?

  1. Verification confirms the system meets its specified requirements, while validation confirms it meets stakeholder needs in the operational environment. Correct answer.
  2. Verification and validation are synonyms and may be used interchangeably in all contexts.
  3. Verification confirms stakeholder needs are met, while validation confirms requirements were correctly written.
  4. Verification is performed only after delivery, while validation is performed only during design.

Explanation

Verification answers 'did we build the system right' by confirming conformance to specified requirements, while validation answers 'did we build the right system' by confirming fitness for intended use. The two activities use different evidence and occur at different points in the lifecycle.

Question 9General Systems Engineering

A program must select a design approach for a system with high technical uncertainty and significant cost risk. Which lifecycle approach is most appropriate to manage that risk through repeated risk analysis and prototyping?

  1. V-model
  2. Incremental build with fixed requirements
  3. Spiral Correct answer.
  4. Waterfall

Explanation

The spiral model is explicitly risk-driven, structuring development into iterations that each begin with risk identification and analysis, often using prototypes to reduce uncertainty. It is suited to high-risk efforts where requirements and technology are not well understood.

Question 10General Systems Engineering

An engineer writes a requirement: 'The radar shall detect a target of 1 square meter radar cross section at a range of at least 50 kilometers with a probability of detection of 0.9.' Which pair of requirement quality characteristics does this statement best exemplify?

  1. Ambiguous and unallocated
  2. Measurable and verifiable Correct answer.
  3. Unnecessary and infeasible
  4. Vague and non-traceable

Explanation

The statement includes quantitative parameters-target size, range, and probability of detection-that allow objective testing, so it is measurable and verifiable. Good requirements specify performance in terms that support a defined verification method.

Question 11General Systems Engineering

During requirements analysis, a team identifies that two stakeholder groups have conflicting requirements for system response time. What is the most appropriate systems engineering action?

  1. Delete both requirements to avoid conflict
  2. Adopt the requirement from the group with the larger budget
  3. Allocate both requirements unchanged to the same subsystem
  4. Perform a trade study and negotiate a resolution with the stakeholders Correct answer.

Explanation

Conflicting requirements are resolved through analysis, trade studies, and negotiation with the affected stakeholders to reach an agreed, defensible position. Documenting the resolution and its rationale preserves traceability and stakeholder buy-in.

Question 12General Systems Engineering

In the systems engineering process, what is the primary role of the requirements traceability matrix?

  1. To define the physical interfaces between subsystems
  2. To schedule verification activities across the program
  3. To record the cost of each requirement change
  4. To link each requirement to its source and to downstream design, implementation, and verification artifacts Correct answer.

Explanation

A traceability matrix records bidirectional links from each requirement back to its source and forward to design elements, implementation, and verification evidence. This supports impact analysis, coverage assessment, and configuration audits.

Question 13General Systems Engineering

A system must operate in a saltwater environment. The design team specifies corrosion-resistant materials and seals. Which type of requirement does this represent?

  1. Functional requirement
  2. Performance requirement
  3. Interface requirement
  4. Constraint Correct answer.

Explanation

A constraint limits the design solution space without specifying a particular behavior, such as mandating operation in a saltwater environment or restricting material choices. Constraints shape how the system may be built rather than what function it performs.

Question 14General Systems Engineering

Which of the following best describes the purpose of a system architecture trade study?

  1. To verify that the as-built system meets its requirements
  2. To select the lowest-cost vendor for each subsystem
  3. To document the final design after all decisions are made
  4. To evaluate alternative architectures against weighted criteria and select a preferred solution Correct answer.

Explanation

A trade study systematically compares architecture alternatives against weighted evaluation criteria such as performance, cost, risk, and schedule to justify a preferred solution. The results and rationale are documented to support decision traceability.

Question 15General Systems Engineering

A system is decomposed into subsystems, and each subsystem is assigned a portion of the system-level performance budget. What is this activity called?

  1. Configuration auditing
  2. Requirement allocation Correct answer.
  3. Interface management
  4. Risk retirement

Explanation

Requirement allocation assigns system-level requirements and their associated performance budgets to lower-level elements so that, when combined, they satisfy the parent requirement. It is a key step in flowing requirements down the architecture.

Question 16General Systems Engineering

Which modeling language is standardized for describing system architecture and supports both structural and behavioral views, including requirements, blocks, and activities?

  1. Extensible Markup Language (XML)
  2. Unified Modeling Language (UML)
  3. Business Process Model and Notation (BPMN)
  4. Systems Modeling Language (SysML) Correct answer.

Explanation

SysML is a standardized general-purpose modeling language for systems engineering that extends UML with diagrams for requirements, blocks, parametric constraints, and activities. It provides both structural and behavioral views suited to multidisciplinary systems.

Question 17General Systems Engineering

An interface between two subsystems is documented in an interface control document. Which characteristic is most important for that document to be effective?

  1. It is updated only after system delivery
  2. It includes the internal design of both subsystems
  3. It defines the interface unambiguously and is configuration-controlled Correct answer.
  4. It is written by only one subsystem team

Explanation

An interface control document must define the interface characteristics unambiguously so both sides can design to it, and it must be configuration-controlled so changes are coordinated. Ambiguity or uncontrolled change at interfaces is a common source of integration failures.

Question 18General Systems Engineering

In risk management, which action represents risk mitigation rather than risk acceptance?

  1. Monitoring the risk until it materializes
  2. Transferring the risk to a subcontractor through a contract clause
  3. Documenting the risk and proceeding without changes
  4. Adding redundancy to a critical component to reduce failure probability Correct answer.

Explanation

Risk mitigation reduces the probability or consequence of a risk through design or process changes, such as adding redundancy to lower failure probability. Acceptance, transfer, and monitoring are alternative risk handling strategies that do not reduce the risk itself.

Question 19General Systems Engineering

A verification method in which the system is operated under realistic conditions to confirm it performs its intended mission is best described as which of the following?

  1. Test
  2. Demonstration Correct answer.
  3. Inspection
  4. Analysis

Explanation

Demonstration shows that the system performs a function under representative conditions without necessarily collecting detailed quantitative data, as when an operator exercises the system in a mission-like scenario. Test, by contrast, typically involves controlled conditions and precise measurement against specified limits.

Question 20General Systems Engineering

Which set of elements typically constitutes the technical baseline used for configuration control of a system under development?

  1. Requirements, risks, and issues logs
  2. Concept, prototype, and production plans
  3. Functional, allocated, and product baselines Correct answer.
  4. Cost, schedule, and performance baselines

Explanation

Configuration management recognizes three technical baselines: functional, allocated, and product. Each corresponds to an approved milestone in the lifecycle and provides a controlled reference for changes.

Question 21General Systems Engineering

A team is performing functional decomposition and needs to ensure that each subfunction's inputs and outputs are consistent with the parent function. Which principle is being applied?

  1. Functional flow consistency and conservation of inputs and outputs Correct answer.
  2. Physical integration
  3. Functional allocation
  4. Requirements prioritization

Explanation

When decomposing functions, the inputs and outputs of subfunctions must be consistent with those of the parent function so that no required input is missing and no output is unaccounted for. This consistency check preserves functional integrity across levels of decomposition.

Question 22General Systems Engineering

An architecture is described as highly modular. Which property most directly follows from high modularity?

  1. Elimination of all interface definitions
  2. Reduced ability to replace modules independently
  3. Improved ability to change or replace modules with limited impact on others Correct answer.
  4. Increased coupling between modules

Explanation

Modularity partitions a system into units with well-defined interfaces and minimal coupling, so a change to one module has limited impact on others. This supports independent evolution, reuse, and easier verification.

Question 23General Systems Engineering

A system-level requirement states that the system shall achieve a 99.9 percent availability. The architecture allocates 99.95 percent availability to a redundant subsystem and 99.95 percent to a non-redundant subsystem, assuming independence. Which conclusion is most defensible?

  1. The allocation is invalid because the combined availability of two independent series elements is the product of their availabilities, which is below the system requirement Correct answer.
  2. The allocation is valid because each subsystem exceeds the system requirement
  3. The allocation is valid because availability requirements cannot be decomposed
  4. The allocation is invalid because redundancy always reduces availability

Explanation

For independent elements in series, system availability is the product of element availabilities: 0.9995 × 0.9995 ≈ 0.99900025, which is just below 0.999. The allocation therefore does not meet the system requirement, showing why budget roll-up must be checked numerically.

Question 24General Systems Engineering

During integration, a team discovers that two subsystems each meet their allocated requirements, yet the combined system fails a system-level performance requirement. Which explanation is most consistent with systems engineering principles?

  1. System-level requirements are always unachievable when subsystems are verified separately
  2. Subsystem verification must have been performed incorrectly in every case
  3. Integration testing is unnecessary if each subsystem passes its own tests
  4. The allocated requirements were incorrect or incomplete because emergent interactions were not captured in the allocation Correct answer.

Explanation

Emergent behavior arises from interactions among elements and may not be captured by individually allocated requirements. When each element passes but the integrated system fails, the allocation or interface assumptions were likely incomplete, which is why system-level verification remains essential.

Question 25General Systems Engineering

An acquirer requires an independent assessment that the developer's configuration management process provides adequate control of baselines and changes. Which activity most directly satisfies this need?

  1. A configuration management process audit Correct answer.
  2. A requirements validation review
  3. A physical configuration audit
  4. A functional configuration audit

Explanation

A configuration management process audit evaluates whether the implemented configuration management process complies with approved procedures and contractual requirements. Functional and physical configuration audits instead examine the product's performance and as-built conformity.

Question 26General Systems Engineering

In the systems engineering life-cycle model, what distinguishes the concept definition stage from the subsequent development stage?

  1. Concept definition explores stakeholder needs, feasible concepts, and top-level requirements before major resources are committed Correct answer.
  2. Concept definition produces the fully detailed design drawings and manufacturing specifications
  3. Concept definition is the phase in which the system is operated and then retired
  4. Concept definition is where the system is integrated and verified against its technical baseline

Explanation

Concept definition is the front-end stage in which stakeholder needs are elicited, alternative concepts are examined, and top-level requirements and constraints are established so a sound decision to proceed can be made. Detailed design, integration, verification, operation, and retirement belong to later stages and depend on the outputs of this early analysis.

Question 27General Systems Engineering

Which statement best captures the purpose of the systems engineering management plan (SEMP) on a development program?

  1. It records the negotiated contract price and payment schedule for each deliverable
  2. It defines how the technical effort will be organized, controlled, and integrated across the program Correct answer.
  3. It provides the as-built configuration record of every installed component
  4. It lists the acceptance test procedures that will be run on the delivered system

Explanation

The SEMP is the program's technical management framework: it describes the technical organization, processes, reviews, integration approach, and how systems engineering will be planned and controlled. It is a management and process document rather than a cost record, a test procedure, or an as-built configuration listing.

Question 28General Systems Engineering

A review board wants to confirm that a system's design satisfies its baselined requirements before committing to production. Which review is intended primarily for that purpose?

  1. A physical configuration audit that compares as-built hardware to documentation
  2. A preliminary design review focused on subsystem trade studies
  3. A critical design review that evaluates the complete design against the allocated baseline Correct answer.
  4. A functional configuration audit that examines verification evidence for each requirement

Explanation

The critical design review assesses whether the detailed design, as documented, can meet the performance and other requirements in the allocated baseline and is ready to proceed toward production. It is the design-maturity gate where the complete design is evaluated against requirements.

Question 29General Systems Engineering

Which term describes the process of examining a proposed design change to determine its effects on cost, schedule, performance, and risk before approval?

  1. Baseline freeze
  2. Change impact assessment Correct answer.
  3. Configuration status accounting
  4. Configuration identification

Explanation

Change impact assessment evaluates a proposed change against performance, cost, schedule, interfaces, and risk so that the change control board can make an informed decision. It is the analytical step that precedes approval or rejection of a change.

Question 30General Systems Engineering

Which characteristic is essential for a well-formed requirement in a system specification?

  1. It is written in general terms so that it remains valid for any future design
  2. It is stated so that a single verification method can objectively confirm satisfaction Correct answer.
  3. It describes the design solution the developer must implement
  4. It combines several related performance goals into one consolidated statement

Explanation

A well-formed requirement must be verifiable, meaning its satisfaction can be objectively confirmed by an identified method such as test, analysis, inspection, or demonstration. Combining goals, prescribing design, or remaining vague all undermine verifiability and traceability.

Question 31General Systems Engineering

What is the principal reason for establishing a functional baseline before beginning detailed design?

  1. It specifies the exact part numbers that must be procured for each subsystem
  2. It documents the test results that demonstrate the system meets its requirements
  3. It records the manufacturing tolerances that will be used on the production line
  4. It fixes the approved functional and performance requirements against which design changes will be judged Correct answer.

Explanation

The functional baseline captures the approved system-level functional and performance requirements and the verification approach, providing the controlled reference against which later changes are evaluated. It is a requirements baseline, not a parts list, a test report, or a manufacturing specification.

Question 32General Systems Engineering

Which activity is performed during the systems engineering technical reviews to confirm that a design is ready to enter the next phase?

  1. Replacing the technical baseline with the contractor's preferred design
  2. Closing out action items and assessing entry and exit criteria for the phase Correct answer.
  3. Deleting requirements that proved difficult to verify
  4. Releasing the system for operational use regardless of open findings

Explanation

Technical reviews use defined entry and exit criteria, and the review board confirms that action items are resolved or dispositioned before the program proceeds to the next phase. This disciplined gatekeeping is what makes the review meaningful.

Question 33General Systems Engineering

In systems engineering, what does the term 'interface' most precisely refer to?

  1. The schedule milestone at which integration testing begins
  2. The organizational chart showing which team owns each subsystem
  3. The internal circuitry contained within a single replaceable module
  4. A shared boundary across which two system elements exchange matter, energy, or information Correct answer.

Explanation

An interface is the shared boundary between two elements through which they exchange matter, energy, or information, and it must be defined and controlled on both sides. Internal circuitry, organizational structure, and schedule milestones are not interfaces in this sense.

Question 34General Systems Engineering

A team is allocating a system-level reliability target among three subsystems. Which approach best supports a defensible allocation?

  1. Assign an equal share of the target to each subsystem regardless of its complexity
  2. Assign the entire target to the subsystem with the highest part count
  3. Defer allocation until integration testing reveals the actual failure rates
  4. Use a documented allocation method, such as apportionment based on predicted failure rates or criticality, and record the rationale Correct answer.

Explanation

Allocation should follow a documented, repeatable method such as reliability apportionment based on predicted failure rates, complexity, or criticality, with the rationale recorded for traceability. Arbitrary or deferred allocation leaves the design without a coherent budget to meet.

Question 35General Systems Engineering

During concept exploration, a team must compare three candidate architectures against stakeholder priorities. Which technique most directly supports a transparent, traceable comparison?

  1. Using a weighted decision matrix with criteria derived from stakeholder needs and documented scoring Correct answer.
  2. Selecting the architecture with the lowest projected unit cost alone
  3. Adopting the architecture used on the previous program without further analysis
  4. Choosing the architecture preferred by the most senior engineer

Explanation

A weighted decision matrix ties evaluation criteria to stakeholder needs, makes weights and scores explicit, and documents the rationale so the decision is traceable and reviewable. Single-criterion or authority-based selection lacks the transparency and traceability a trade study requires.

Question 36General Systems Engineering

An engineer discovers that a subsystem cannot meet its allocated mass budget. What is the most appropriate systems engineering response?

  1. Reduce the allocated mass of an unrelated subsystem without analysis to keep the total constant
  2. Direct the subsystem team to ignore the budget because integration will resolve it
  3. Perform a trade study on the allocation across affected subsystems and process any baseline change through configuration control Correct answer.
  4. Quietly increase the subsystem's mass allocation and proceed with design

Explanation

A budget shortfall is a system-level issue, so the engineer should analyze options across the affected elements and, if the allocation must change, route the change through configuration control with documented rationale. Unilateral or arbitrary adjustments break the integrity of the allocation baseline.

Question 37General Systems Engineering

A program wants to reduce the risk that late-discovered interface mismatches will delay integration. Which action most directly addresses this risk?

  1. Postponing all interface definition until the subsystems are built
  2. Reducing the number of verification activities planned for each subsystem
  3. Increasing the integration team's overtime budget
  4. Defining and controlling interfaces early through interface control documentation and interface reviews Correct answer.

Explanation

Interface mismatches are best prevented by defining interfaces early, documenting them in controlled interface documentation, and reviewing them with both sides before build. Early definition and control let incompatible assumptions surface while they are still cheap to correct.

Question 38General Systems Engineering

A stakeholder requirement states a need in vague terms. Which action best moves the program toward a verifiable requirement?

  1. Elicit clarification from the stakeholder to define measurable conditions and then document the refined requirement Correct answer.
  2. Remove the requirement because it cannot be verified as stated
  3. Rewrite the statement as a design constraint specifying a particular component
  4. Accept the statement as written and let the design team interpret it during implementation

Explanation

Vague needs are resolved by working with the stakeholder to establish measurable conditions and criteria, then documenting the refined requirement with traceability to the original need. This preserves the intent while making the requirement verifiable.

Question 39General Systems Engineering

Which practice best supports bidirectional traceability between stakeholder needs and verification activities?

  1. Relying on the memory of the lead engineer to recall which tests cover which needs
  2. Tracking only the forward links from needs to requirements
  3. Maintaining a traceability matrix that links each need to requirements, design elements, and verification methods Correct answer.
  4. Recording verification results in a separate system with no cross-references

Explanation

Bidirectional traceability requires a maintained matrix or tool that links needs to derived requirements, design elements, and verification methods in both directions. This lets the team confirm every need is covered and every requirement is justified.

Question 40General Systems Engineering

A team is defining the operational scenarios the system must support. Which artifact most appropriately captures how the system interacts with external actors over time?

  1. A bill of materials for the delivered hardware
  2. A static block diagram of internal subsystem composition
  3. A use case or sequence model showing external actors and the flow of interactions Correct answer.
  4. A staffing plan for the integration team

Explanation

Operational scenarios are behavioral descriptions of how external actors interact with the system over time, which use case or sequence models capture well. Static structure diagrams, bills of materials, and staffing plans do not express temporal interaction with external actors.

Question 41General Systems Engineering

A project faces a risk that a key supplier may deliver a component late. Which response is a risk mitigation rather than a risk transfer?

  1. Purchasing insurance that covers schedule losses from late delivery
  2. Documenting the risk in the register without any further action
  3. Accepting the delay and adjusting the schedule after it occurs
  4. Qualifying a second supplier and holding buffer stock to reduce the impact of a late delivery Correct answer.

Explanation

Mitigation reduces the likelihood or impact of the risk through actions the program controls, such as qualifying an alternate supplier and holding buffer stock. Transfer shifts the financial consequence to another party, and acceptance simply acknowledges the risk without reducing it.

Question 42General Systems Engineering

A review finds that a requirement cannot be verified with any practical method. What is the most appropriate systems engineering action?

  1. Mark the requirement as verified by inspection without evidence
  2. Waive the requirement permanently and proceed to production
  3. Delete the requirement and note the gap in the review minutes
  4. Revisit the requirement with the stakeholder to restate it in verifiable terms or agree on an acceptable verification approach Correct answer.

Explanation

An unverifiable requirement is a requirements-quality defect, so the correct action is to refine it with the stakeholder or agree on a practical verification method, then update the baseline through configuration control. Falsifying verification, deleting the need, or permanently waiving it all leave the program without justified confidence.

Question 43General Systems Engineering

Two subsystems are developed by different suppliers and must exchange data over a shared bus. Which document is most appropriate to control the agreed bus protocol, timing, and data formats?

  1. An interface control document for the shared bus Correct answer.
  2. The program's risk management plan
  3. The system-level concept of operations
  4. The supplier's internal quality manual

Explanation

The interface control document defines and controls the agreed characteristics of a shared boundary, including protocol, timing, and data formats, so both suppliers build to the same definition. The concept of operations, risk plan, and quality manual do not control interface specifics.

Question 44General Systems Engineering

A program is deciding how much verification to perform on a low-criticality, commercially available component. Which consideration most appropriately guides the decision?

  1. The component's physical size relative to other items
  2. The criticality of the component's function, the maturity of the item, and the risk that an undetected failure would pose Correct answer.
  3. The number of pages in the supplier's datasheet
  4. The personal preference of the integration lead

Explanation

Verification rigor should be risk-based, weighing the criticality of the function, the maturity and heritage of the item, and the consequences of an undetected failure. Datasheet length, personal preference, and physical size are not sound bases for verification depth.

Question 45General Systems Engineering

An architecture team wants to reduce the propagation of a failure from one subsystem to another. Which architectural approach most directly supports this goal?

  1. Introducing isolation and fault-containment boundaries between subsystems Correct answer.
  2. Combining all functions into a single monolithic module
  3. Removing all redundancy to simplify the design
  4. Increasing the coupling between subsystems so failures are shared

Explanation

Fault containment depends on isolation boundaries that limit how a failure in one element can affect others, often combined with redundancy and defined failure modes. Higher coupling or a monolithic design allows failures to propagate more easily.

Question 46General Systems Engineering

A program must demonstrate that a system meets its requirements while also confirming that it satisfies the users' operational needs in the intended environment. Which pairing of activities addresses these two aims?

  1. Verification and validation are interchangeable terms for the same acceptance test
  2. Verification is performed only by the customer; validation only by the developer
  3. Verification confirms the system meets specified requirements; validation confirms it satisfies intended use in the operational environment Correct answer.
  4. Verification confirms stakeholder satisfaction; validation confirms compliance with specifications

Explanation

Verification builds objective evidence of compliance with specified requirements, while validation establishes that the system fulfills its intended purpose in the operational environment. The two answer different questions and are both needed for confidence.

Question 47General Systems Engineering

A system must be maintainable over a 20-year life with periodic technology refresh of its processing units. Which architectural property most directly enables this?

  1. A single proprietary processor with no documented interface
  2. Hard-coding hardware-specific assumptions throughout the software
  3. Tight coupling of processing units to the application logic
  4. Well-defined interfaces and modular replacement of processing elements Correct answer.

Explanation

Long-life systems support technology refresh when processing elements are modular and accessed through well-defined, documented interfaces, so they can be replaced without redesigning the rest of the system. Tight coupling, proprietary undocumented interfaces, and hard-coded assumptions make replacement costly and risky.

Question 48General Systems Engineering

A program has a fixed budget and schedule, and a proposed change would improve performance but exceed both. Which decision process is most appropriate?

  1. Let each subsystem team decide independently whether to adopt the change
  2. Reject all changes automatically to protect the baseline
  3. Approve the change immediately because performance improvement is always desirable
  4. Evaluate the change against performance, cost, schedule, and risk, and decide through the change control board with documented rationale Correct answer.

Explanation

Change decisions should weigh the full set of impacts and be made by the change control board with documented rationale, so the baseline is altered only deliberately. Automatic approval or rejection, or decentralized adoption, undermines configuration control.

Question 49General Systems Engineering

A team is selecting measures of effectiveness for a system that must balance speed, coverage, and cost. Which set of measures is most appropriate?

  1. A single subjective rating provided by the program manager
  2. Only the acquisition cost of the system
  3. A balanced set of quantifiable measures tied to stakeholder priorities, with defined units and thresholds Correct answer.
  4. Measures chosen after the design is complete to match its achieved performance

Explanation

Measures of effectiveness should be quantifiable, tied to stakeholder priorities, and defined with units and thresholds so alternatives can be compared objectively. Single or subjective measures, or measures chosen after the fact, cannot guide a fair trade.

Question 50General Systems Engineering

An architecture has high cohesion within modules and low coupling between them. Which consequence is most consistent with these properties?

  1. Every module must be redesigned whenever any requirement changes
  2. Changes to one module are less likely to require changes in unrelated modules Correct answer.
  3. The system becomes harder to test because modules cannot be isolated
  4. Interfaces between modules become unnecessary

Explanation

High cohesion concentrates related functionality within a module, and low coupling minimizes dependencies between modules, so a change in one module tends to stay local. This improves maintainability and testability rather than making redesign or testing harder.