Chartered Engineer (CEng) Competence B: Design, Development and Solution of Engineering Problems Syllabus

Competence B: Design, Development and Solution of Engineering Problems syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Competence B: Design, Development and Solution of Engineering Problems in Chartered Engineer (CEng), not a summary of it.

1. 1

   Identifying and Defining Engineering Problems

   3 topics

   • Eliciting and Establishing Requirements
     • Stakeholder needs analysis
     • Functional and non-functional requirements
     • Requirements traceability
   • Defining Constraints and Success Criteria
     • Technical, commercial, regulatory and environmental constraints
     • Specifications and acceptance criteria
   • Problem Framing and Scoping for Complex Systems
2. 2

   Design Synthesis and Conceptual Development

   4 topics

   • Generating and Evaluating Design Concepts
     • Concept generation and creativity techniques
     • Trade-off analysis and decision matrices
   • Applying Design Theory, Codes and Standards
     • Relevant British, European and international standards
     • Design for manufacture, assembly and maintainability
   • Whole-Life and Systems-Level Design Thinking
     • Lifecycle cost and through-life engineering
     • Design for reliability, availability and resilience
   • Design Reviews and Configuration Control
3. 3

   Implementation, Testing and Continuous Improvement

   4 topics

   • Implementing Engineering Solutions
     • Prototyping and proof of concept
     • Production, construction or deployment readiness
   • Verification, Validation and Commissioning
     • Test planning and acceptance testing
     • Performance evaluation against requirements
   • Evaluating Outcomes and Implementing Improvements
     • Lessons learned and feedback loops
     • Root cause analysis of failures
   • Innovation, Intellectual Property and Commercial Exploitation
     • Protecting IP and patents
     • Routes to market and value creation

Competence B: Design, Development and Solution of Engineering Problems flashcards for Chartered Engineer (CEng)

23 of 56 cards from the Competence B: Design, Development and Solution of Engineering Problems deck — real questions with worked answers.

1. What are 'requirements' in the engineering design context?

   Documented statements that define what a system, product or process must do (functional) and how well it must do it (non-functional), forming the agreed basis for design, verification and acceptance.

2. Distinguish functional requirements from non-functional requirements.

   Functional requirements specify what the system must do (its behaviours and functions); non-functional requirements specify qualities or constraints on how it performs (e.g. reliability, safety, usability, maintainability, performance).

3. Name four common techniques for eliciting requirements from stakeholders.

   Interviews, workshops, questionnaires/surveys, observation, document analysis, prototyping and use-case/scenario development (any four).

4. What does the acronym SMART stand for when writing requirements or success criteria?

   Specific, Measurable, Achievable, Relevant and Time-bound.

5. What is a stakeholder, and why is stakeholder identification critical to requirements elicitation?

   A stakeholder is any party affected by or able to influence the project (clients, users, regulators, operators, suppliers). Identifying all of them ensures requirements capture every legitimate need and avoid costly late-stage changes.

6. What is requirements traceability and what tool supports it?

   Traceability is the ability to link each requirement forward to its design, implementation and verification, and back to its originating need. It is supported by a Requirements Traceability Matrix (RTM).

7. State the characteristics of a 'good' requirement.

   Clear/unambiguous, complete, consistent, verifiable/testable, feasible, necessary, traceable and atomic (single requirement per statement).

8. Differentiate a 'need', a 'requirement' and a 'specification'.

   A need is the underlying problem or desire; a requirement is a formal, agreed statement of that need; a specification is the detailed technical document defining how the requirement will be met.

9. What is the MoSCoW method used for in requirements management?

   Prioritising requirements into Must have, Should have, Could have and Won't have (this time), to manage scope and trade-offs.

10. What is a constraint in engineering design?

    A fixed restriction or boundary condition that the solution must satisfy and cannot be traded off, e.g. budget cap, legal limit, physical space, material availability or interface compatibility.

11. Contrast a constraint with a success criterion (objective).

    A constraint is a hard limit that must be met (pass/fail); a success criterion/objective is a desired outcome to be maximised or optimised and can be traded against others.

12. List the classic triple constraint (iron triangle) of project/engineering delivery.

    Scope, time (schedule) and cost, with quality typically at the centre; changing one affects the others.

13. What is a Key Performance Indicator (KPI) and how does it relate to success criteria?

    A KPI is a quantifiable measure used to track progress toward a success criterion or objective, providing the evidence that a target has been met.

14. Give examples of the main categories of design constraints.

    Technical/physical, economic/budgetary, legal/regulatory, environmental, safety, time/schedule, ethical and social, and resource/skills constraints.

15. What is 'problem framing' in complex systems engineering?

    The process of defining the problem boundary, context, stakeholders and the question to be solved before generating solutions, ensuring the right problem is addressed rather than just a symptom.

16. Define a 'system boundary' and why scoping it correctly matters.

    The conceptual line separating the system of interest from its external environment. Correct scoping determines what is designed, what interfaces must be managed, and prevents scope creep or missing interactions.

17. What distinguishes a 'complicated' system from a 'complex' system?

    A complicated system has many parts but predictable, decomposable behaviour; a complex system exhibits emergent, non-linear behaviour from interacting components that cannot be fully predicted by analysing parts alone.

18. What is 'emergence' in systems thinking?

    System-level properties or behaviours that arise from the interactions between components and are not present in any individual component (e.g. reliability, safety, performance of the whole).

19. What is a 'wicked problem'?

    A problem that is ill-defined, has no definitive formulation or stopping rule, no true/false solution (only better/worse), and where every attempt at a solution changes the problem (Rittel & Webber).

20. What is the purpose of a Concept of Operations (ConOps)?

    To describe, from the user's viewpoint, how a system will be operated and used in its intended environment, framing the problem and guiding requirements and scope.

21. What is divergent vs convergent thinking in concept generation?

    Divergent thinking generates many varied ideas/options (breadth); convergent thinking narrows and evaluates them to select the best (depth/decision).

22. Name three structured idea-generation techniques for design concepts.

    Brainstorming, morphological analysis, TRIZ, SCAMPER, biomimicry, mind-mapping and lateral thinking (any three).

23. What is a weighted decision (Pugh) matrix used for in concept evaluation?

    To systematically compare design concepts against weighted selection criteria, scoring each option to objectively identify the strongest concept relative to a datum/baseline.

See more Competence B: Design, Development and Solution of Engineering Problems flashcards →

Planning Competence B: Design, Development and Solution of Engineering Problems for Chartered Engineer (CEng)

Competence B: Design, Development and Solution of Engineering Problems (Chartered Engineer (CEng)) FAQ