Download EXPERT SYSTEMS ENGINEERING PROFESSIONAL EXAMINATION PRACTICE EXAM QUESTIONS and more Exams Systems Engineering in PDF only on Docsity!
EXPERT SYSTEMS ENGINEERING
PROFESSIONAL EXAMINATION
PRACTICE EXAM QUESTIONS AND
CORRECT ANSWERS (VERIFIED
ANSWERS) PLUS RATIONALES 2026 Q&A
| INSTANT DOWNLOAD PDF
A key purpose of systems engineering is to: A. Write software code faster B. Manage complexity across the system lifecycle C. Replace project management D. Eliminate testing activities Rationale: Systems engineering focuses on managing complexity by integrating all technical and managerial processes across the system lifecycle. It ensures that requirements, design, verification, and validation are aligned, rather than focusing on a single discipline like coding or testing.
Which model best represents iterative development with verification at each stage? A. Waterfall model B. V-model
C. Spiral model only D. Incremental funding model Rationale: The V-model emphasizes verification and validation activities corresponding to each development phase. It ensures that each design stage has a matching testing stage, making it ideal for structured systems engineering processes.
Requirements traceability ensures: A. Faster coding B. Requirements can be tracked from origin to implementation C. Elimination of documentation D. Reduced stakeholder involvement Rationale: Traceability links requirements throughout the lifecycle, ensuring each requirement is implemented, verified, and validated. It improves accountability and reduces risk of missing critical system functions.
Which is an example of a functional requirement? A. System must be lightweight B. System shall process transactions within 2 seconds C. System should look modern D. System must use aluminum casing Rationale: Functional requirements define system behavior or functions, such as processing time. Physical or aesthetic attributes are non-functional requirements.
Which tool is commonly used in Model-Based Systems Engineering (MBSE)? A. Excel B. SysML C. HTML D. SQL Rationale: SysML is a standardized modeling language used in MBSE to represent system structure, behavior, and requirements in a formalized way.
A system boundary defines: A. Software code limits B. What is inside and outside the system scope C. Project budget limits D. Team responsibilities Rationale: System boundary distinguishes system components from external environment, helping define interfaces and interactions.
Which is a non-functional requirement? A. System shall store user data B. System shall have 99.9% availability C. System shall generate reports D. System shall process payments Rationale: Non-functional requirements describe system qualities such as reliability, availability, performance, and usability rather than functions.
Trade studies are used to: A. Eliminate requirements B. Compare alternative solutions objectively C. Increase project scope D. Reduce stakeholder input Rationale: Trade studies evaluate multiple design options using criteria such as cost, performance, and risk to select the most suitable solution.
Risk in systems engineering is defined as: A. A guaranteed failure B. Probability of an event and its consequence C. Project delay only D. Budget overrun only Rationale: Risk combines likelihood and impact of uncertain events that may affect system objectives.
Which lifecycle phase comes first? A. Design B. Requirements definition C. Testing D. Deployment Rationale: Systems engineering begins with defining stakeholder needs and requirements before moving to design and implementation phases.
What does MBSE primarily replace? A. Testing B. Document-based systems engineering C. Coding D. Project management Rationale: MBSE replaces traditional document-heavy approaches with model- centric approaches to improve consistency and communication.
A baseline in configuration management is: A. A risk register B. Approved version of a configuration item C. A test plan D. A cost estimate Rationale: A baseline is a formally approved configuration state used as a reference for future changes.
Which best describes emergent behavior? A. Planned behavior B. System behavior arising from interaction of components C. Software bugs D. Hardware failure Rationale: Emergent behavior occurs when system-level properties arise that cannot be predicted from individual components alone.
Verification methods include: A. Interviews only B. Inspection, analysis, demonstration, testing C. Marketing surveys D. Financial audits Rationale: Verification uses structured technical methods to confirm requirements are met.
A use case describes: A. System cost B. Interaction between user and system to achieve a goal C. Hardware layout D. Budget allocation Rationale: Use cases capture functional requirements through user-system interaction scenarios.
Which is NOT part of systems engineering? A. Requirements management B. Random coding without design C. System integration D. Verification Rationale: Systems engineering requires structured processes; unplanned coding contradicts disciplined system design.
What is the purpose of validation testing? A. Check code syntax B. Ensure system meets user expectations C. Reduce documentation D. Increase coding speed Rationale: Validation confirms the system solves the intended problem for stakeholders.
A system architecture defines: A. Budget structure B. High-level structure and interactions of system components C. Employee roles D. Marketing strategy Rationale: Architecture defines structure, behavior, and relationships among system elements.
Which best describes interface compatibility? A. System aesthetics B. Ability of components to exchange information correctly C. Code performance D. User satisfaction Rationale: Interface compatibility ensures subsystems communicate without errors or mismatches.
Stakeholders include: A. Only engineers B. Anyone affected by or influencing the system C. Only customers D. Only managers Rationale: Stakeholders include users, engineers, managers, regulators, and others impacted by the system.
The spiral model emphasizes: A. Fixed requirements B. Iterative development with risk analysis C. No documentation D. Linear design only Rationale: Spiral model integrates risk assessment and iterative refinement throughout development.
System requirements should be: A. Vague B. Clear, measurable, and testable C. Optional D. Changing daily without control Rationale: Good requirements must be unambiguous and verifiable to support design and testing.
B. Improved consistency and traceability C. Reduced modeling D. Less communication Rationale: MBSE improves system understanding through integrated models and reduces inconsistencies.
System validation ensures: A. Design correctness B. User needs satisfaction C. Code efficiency D. Hardware speed Rationale: Validation confirms that the system fulfills intended operational needs.
Which is an example of system interface? A. Budget report B. Data exchange between software modules C. Marketing plan D. User survey Rationale: Interfaces define how components communicate and interact.
Requirements engineering includes: A. Marketing analysis B. Elicitation, analysis, specification, validation
C. Sales forecasting D. Accounting Rationale: Requirements engineering systematically defines what the system must do.
A system lifecycle ends with: A. Design B. Retirement/disposal C. Testing D. Coding Rationale: Systems are eventually decommissioned when they are no longer useful.
Modularity improves: A. System confusion B. Maintainability and scalability C. System failure D. Cost only increase Rationale: Modular systems are easier to modify and maintain.
Which reduces system risk most effectively? A. Ignoring requirements B. Early validation and risk analysis C. Increasing complexity D. Skipping testing
Which is NOT a system engineering objective? A. Integration B. Random development without structure C. Verification D. Lifecycle management Rationale: Systems engineering relies on structured and controlled processes.
System performance measures include: A. Color scheme B. Throughput and response time C. Logo design D. Employee count Rationale: Performance measures evaluate system efficiency and speed.
Traceability matrix is used to: A. Track employees B. Map requirements to design and test cases C. Increase coding speed D. Manage finances Rationale: It ensures every requirement is linked to implementation and verification.
A stakeholder requirement is: A. Internal code rule B. Expression of need from users or stakeholders C. System bug D. Design constraint only Rationale: Stakeholder requirements capture user needs and expectations.
System reliability improvement includes: A. Ignoring failures B. Redundancy and fault tolerance C. Reducing testing D. Increasing complexity Rationale: Redundancy and fault-tolerant design increase system dependability.
Which best describes system thinking? A. Focusing only on parts B. Understanding interactions within the whole system C. Ignoring interfaces D. Coding without design Rationale: Systems thinking considers relationships and interactions between components to understand overall behavior.
System architecture trade-offs are important because they: A. Remove requirements B. Balance conflicting system goals such as cost, performance, and reliability
C. Financial model D. Hardware blueprint Rationale: CONOPS describes system usage scenarios, helping align design with user expectations and operational needs.
Requirements prioritization is important because it: A. Eliminates documentation B. Helps manage limited resources by ranking requirements by importance C. Removes testing D. Increases system size Rationale: Prioritization ensures critical requirements are addressed first when time or budget is limited.
Which is a key characteristic of a well-formed requirement? A. Ambiguous wording B. Testable and verifiable statement C. Optional feature D. Marketing slogan Rationale: Requirements must be testable so engineers can confirm system compliance through verification methods.
What is the purpose of system decomposition diagrams? A. Show financial flow B. Represent hierarchical breakdown of system components
C. Replace testing D. Eliminate interfaces Rationale: Decomposition diagrams help visualize system structure and simplify complexity by breaking it into parts.
What is interface risk? A. User dissatisfaction B. Failure in communication between system components C. Marketing failure D. Budget overrun Rationale: Interface risk occurs when data, signals, or physical connections between subsystems fail or mismatch.
System robustness refers to: A. System speed B. Ability to function under unexpected conditions or stress C. Code efficiency D. Cost reduction Rationale: Robust systems continue operating even when conditions deviate from expected operating ranges.
What is configuration item (CI)? A. Marketing document B. Any component or artifact under configuration control
