🇬🇧 Chartered Engineer (CEng) · subject

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

The Competence B: Design, Development and Solution of Engineering Problems syllabus for Chartered Engineer (CEng) in full: 3 chapters, 11 topics and 19 sub-topics, every one listed below, plus 56 Competence B: Design, Development and Solution of Engineering Problems flashcards with answers.

3Chapters
11Topics
19Sub-topics
56Flashcards

Competence B: Design, Development and Solution of Engineering Problems syllabus: all 3 chapters

Expand any chapter to see its topics and sub-topics.

  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. 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. 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

Chartered Engineer (CEng) Competence B: Design, Development and Solution of Engineering Problems flashcards — 56 questions with 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.

Show the other 36 Competence B: Design, Development and Solution of Engineering Problems flashcards
  1. 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).

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

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

  3. 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.

  4. In a weighted decision matrix, how is each concept's total score calculated?

    By summing the products of each criterion weight and the concept's score on that criterion: $S = \sum_{i=1}^{n} w_i \, s_i$.

  5. What is the purpose of building a prototype during concept evaluation?

    To test, demonstrate and de-risk a concept early, validate assumptions, gather stakeholder feedback and reduce uncertainty before committing to full development.

  6. What is the difference between verification and validation of a concept?

    Verification asks 'are we building the product right?' (meets specification); validation asks 'are we building the right product?' (meets the actual user need).

  7. What is a 'code of practice' versus a 'standard'?

    A standard is an agreed technical specification giving requirements/criteria; a code of practice gives recommended methods and good practice for design or operation. Both promote safety, quality and interoperability.

  8. Name the bodies behind BS, ISO, IEC and Eurocodes.

    BS = British Standards Institution (BSI); ISO = International Organization for Standardization; IEC = International Electrotechnical Commission; Eurocodes = CEN (European Committee for Standardization).

  9. What is a factor of safety (FoS) and how is it defined?

    A multiplier accounting for uncertainty, ensuring capacity exceeds demand: $FoS = \dfrac{\text{material/ultimate strength}}{\text{applied (working) stress}}$, with $FoS > 1$ required.

  10. State the simple stress formula used in design verification against a material limit.

    $\sigma = \dfrac{F}{A}$, where $\sigma$ is direct stress, $F$ the applied force and $A$ the cross-sectional area; this is compared against the allowable stress.

  11. What is 'design for X' (DfX), and give three examples of X.

    A family of design methodologies optimising a product for a specific lifecycle attribute. Examples: Design for Manufacture, Design for Assembly, Design for Maintainability, Design for Sustainability, Design for Safety.

  12. What does CE/UKCA marking signify on an engineered product?

    That the product conforms to the relevant legal (essential health, safety and environmental) requirements; UKCA is the UK conformity mark, CE the EU equivalent.

  13. What is whole-life (life-cycle) thinking in design?

    Considering all stages of a system's life — concept, design, manufacture, operation, maintenance, and decommissioning/disposal — when making design decisions, not just initial build.

  14. Define whole-life cost (WLC / life-cycle cost).

    The total cost of ownership over the asset's life: $LCC = C_{capital} + C_{operation} + C_{maintenance} + C_{disposal}$ (often discounted to present value).

  15. What is the formula for Net Present Value (NPV) used in whole-life appraisal?

    $NPV = \sum_{t=0}^{n} \dfrac{C_t}{(1+r)^{t}}$, where $C_t$ is the net cash flow in year $t$ and $r$ is the discount rate; a positive NPV indicates a worthwhile investment.

  16. What is a Life Cycle Assessment (LCA) and what does it evaluate?

    A systematic 'cradle-to-grave' analysis of the environmental impacts (energy, emissions, resources, waste) of a product across all life-cycle stages, per ISO 14040/14044.

  17. What is 'embodied carbon' versus 'operational carbon' in sustainable design?

    Embodied carbon is the CO₂e from materials, manufacture, transport and construction; operational carbon is the CO₂e from energy used while the asset is in service.

  18. What is the purpose of a design review?

    A formal, documented, multidisciplinary check at a defined milestone to confirm the design meets requirements, identify risks/errors early, and authorise progression to the next stage.

  19. Distinguish a Preliminary Design Review (PDR) from a Critical Design Review (CDR).

    PDR confirms the overall design approach meets requirements before detailed design begins; CDR confirms the detailed design is complete and ready to proceed to manufacture/build.

  20. What is configuration management (configuration control)?

    The discipline of identifying, documenting, controlling changes to, and auditing the functional and physical characteristics of a system throughout its life, ensuring integrity and traceability of the current baseline.

  21. Name the four main activities/functions of configuration management.

    Configuration identification, configuration control (change control), configuration status accounting, and configuration audit/verification.

  22. What is a 'baseline' in configuration control?

    A formally agreed, fixed reference version of a configuration item or document against which changes are managed and progress is measured.

  23. What is the role of a Change Control Board (CCB)?

    To formally review, assess the impact of, and approve or reject proposed changes to a baseline, ensuring changes are controlled, traceable and justified.

  24. What is a method statement in implementing an engineering solution?

    A document detailing the safe, step-by-step working procedure for a task, including sequence, resources, hazards and controls, ensuring work is carried out correctly and safely.

  25. What is the difference between verification and validation in the V-model?

    Verification (left-to-right checks at each level) confirms each output meets its specification; validation (right side) confirms the finished system meets the original user requirements and operates correctly in context.

  26. Define commissioning of an engineered system.

    The structured process of bringing a newly installed system into operational service — checking, testing, adjusting and verifying that it performs to its design intent and requirements before handover.

  27. State the formulas linking reliability, MTBF and failure rate for verification of dependability.

    $MTBF = \dfrac{1}{\lambda}$ and $R(t) = e^{-\lambda t}$, where $\lambda$ is the constant failure rate; availability $A = \dfrac{MTBF}{MTBF + MTTR}$.

  28. What is a Factory Acceptance Test (FAT) versus a Site Acceptance Test (SAT)?

    A FAT verifies equipment meets specification at the manufacturer's facility before shipment; a SAT verifies correct installation and performance after it is installed on site.

  29. What is the PDCA (Plan-Do-Check-Act) cycle used for in evaluating outcomes?

    A continuous-improvement loop: Plan a change, Do (implement/trial) it, Check the results against expectations, and Act to standardise or revise; it drives iterative refinement.

  30. What is a post-implementation review (lessons learned) and why is it valuable?

    A structured evaluation after delivery comparing actual outcomes against objectives, capturing what worked and what did not, so improvements feed forward into future designs and processes.

  31. What is root cause analysis, and name one technique used.

    A method to identify the underlying cause of a problem rather than its symptoms, enabling lasting corrective action. Techniques include the '5 Whys', Fishbone (Ishikawa) diagram and Fault Tree Analysis.

  32. Distinguish continuous improvement (Kaizen) from innovation.

    Kaizen/continuous improvement makes small, incremental refinements to existing processes; innovation introduces step-change, novel solutions, products or methods that transform performance or create new value.

  33. Compare the four main types of intellectual property protection.

    Patents protect novel inventions/technical solutions (up to 20 years); trademarks protect brand identifiers; registered designs protect appearance/aesthetics; copyright protects original creative/literary works automatically.

  34. What three criteria must an invention satisfy to be patentable?

    It must be novel, involve an inventive step (non-obvious), and be capable of industrial application; it must not be excluded subject matter.

  35. What is commercial exploitation of an engineering innovation, and name two routes.

    Turning innovation into commercial value/revenue. Routes include manufacturing and direct sale, licensing the IP to others, forming a joint venture, or selling/assigning the IP (spin-out).

  36. What is a Technology Readiness Level (TRL) scale used for?

    A 1-9 scale assessing the maturity of a technology, from TRL 1 (basic principles observed) to TRL 9 (proven in operational environment), used to manage innovation risk and investment decisions.

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

What is in the Chartered Engineer (CEng) Competence B: Design, Development and Solution of Engineering Problems syllabus?

Chartered Engineer (CEng) Competence B: Design, Development and Solution of Engineering Problems is split into 3 chapters: Identifying and Defining Engineering Problems, Design Synthesis and Conceptual Development and Implementation, Testing and Continuous Improvement. Together they contain 11 topics and 19 sub-topics.

How many chapters are in Chartered Engineer (CEng) Competence B: Design, Development and Solution of Engineering Problems?

3 chapters, containing 11 topics and 19 sub-topics. The largest chapter is Design Synthesis and Conceptual Development, with 4 topics.

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

Yes — a 56-card Competence B: Design, Development and Solution of Engineering Problems deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.