Chartered Membership of the IET (CEng MIET) Design, Development and Problem Solving (UK-SPEC B) Syllabus

Design, Development and Problem Solving (UK-SPEC B) syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Design, Development and Problem Solving (UK-SPEC B) in Chartered Membership of the IET (CEng MIET), not a summary of it.

1. 1

   Engineering Problem Definition and Analysis

   4 topics

   • Capturing and managing requirements
     • Stakeholder elicitation and traceability
     • Functional and non-functional requirements
     • Constraint and acceptance criteria definition
   • Systems thinking and architectural decomposition
     • System boundaries and interfaces
     • Trade-off analysis and decision matrices
   • Investigating complex and open-ended problems
     • Diagnosis where information is incomplete
     • Root cause analysis techniques
   • Applying theory, modelling and simulation to inform decisions
2. 2

   Design Synthesis and Development

   5 topics

   • Conceptual and detailed design
     • Generating and evaluating design options
     • Design for manufacture, maintainability and cost
     • Design for reliability, safety and the environment
   • Prototyping, modelling and proof of concept
   • Verification and validation against requirements
     • Test planning and acceptance
     • Design reviews and gate approvals
   • Managing design change and configuration control
   • Use of standards, codes of practice and design tools
3. 3

   Innovation, Implementation and Continuous Improvement

   4 topics

   • Driving and managing innovation
     • Identifying opportunities and adopting new technology
     • Intellectual property and commercialisation awareness
   • Implementation and commissioning of solutions
   • Evaluating outcomes and feeding back lessons learned
   • Continuous improvement and operational optimisation

Design, Development and Problem Solving (UK-SPEC B) flashcards for Chartered Membership of the IET (CEng MIET)

24 of 51 cards from the Design, Development and Problem Solving (UK-SPEC B) deck — real questions with worked answers.

1. In UK-SPEC, what does Competence B ("Design, development and solving engineering problems") require a Chartered Engineer to demonstrate?

   The ability to identify, review and select techniques, procedures and methods to undertake engineering tasks; conduct/manage the design, development, manufacture, construction or commissioning of products, processes, systems and services; and lead/manage the implementation of engineering solutions while solving complex, open-ended problems.

2. What is a requirement in systems engineering?

   A statement that translates or expresses a need and its associated constraints and conditions — a documented capability or characteristic that a system must possess or a function it must perform to satisfy stakeholder needs.

3. Distinguish functional from non-functional requirements.

   Functional requirements specify WHAT the system must do (its functions/behaviours); non-functional requirements specify HOW WELL it must do it — qualities such as performance, reliability, safety, usability, maintainability and security (often called the '-ilities').

4. What does the acronym SMART stand for when writing good requirements?

   Specific, Measurable, Achievable, Relevant and Time-bound — criteria ensuring requirements are unambiguous and verifiable.

5. State the key characteristics of a well-formed individual requirement.

   It should be necessary, unambiguous, complete, consistent, singular, feasible, traceable and verifiable (testable).

6. What is requirements traceability and why does it matter?

   The ability to follow the life of a requirement both forwards and backwards — linking stakeholder needs to system requirements, to design elements, to tests. It ensures every requirement is implemented and verified, supports impact analysis of changes, and avoids orphan or gold-plated features.

7. Differentiate verification from validation.

   Verification asks 'Are we building the product right?' (does it meet its specified requirements). Validation asks 'Are we building the right product?' (does it meet the stakeholders' actual needs and intended use).

8. Name the four common verification methods used to confirm a requirement is met.

   Inspection, Analysis, Demonstration and Test (often abbreviated I, A, D, T).

9. What is systems thinking?

   A holistic approach that views a system as an integrated whole whose behaviour emerges from the interactions between its parts and its environment, rather than focusing only on individual components in isolation.

10. Define an emergent property of a system.

    A property or behaviour that arises from the interactions of the system's components and exists only at the system level — it is not possessed by any individual component on its own (e.g. reliability, safety, stability).

11. What is architectural decomposition (functional decomposition)?

    The process of breaking a complex system down into successively smaller, more manageable subsystems, modules and components, defining their functions and interfaces, so that the whole can be designed, allocated and managed.

12. In system architecture, what is an interface and why is interface definition critical?

    An interface is the shared boundary across which two components exchange information, energy or material. Defining interfaces clearly is critical because most integration failures occur at boundaries; well-specified interfaces allow modules to be developed independently and integrated reliably.

13. Distinguish coupling from cohesion in modular design.

    Coupling is the degree of interdependence between modules (low coupling is desirable); cohesion is the degree to which elements within a single module belong together (high cohesion is desirable). Good architecture seeks low coupling and high cohesion.

14. What characterises a 'complex' (as opposed to merely 'complicated') engineering problem?

    Complex problems have many interacting variables, no single correct solution, incomplete or conflicting information, emergent behaviour and uncertain outcomes — they require judgement and trade-offs rather than a deterministic procedure.

15. What is an open-ended (or 'wicked') problem?

    A problem with no definitive formulation, no clear stopping rule and no single right answer — the problem itself may only be fully understood through attempting solutions, and solutions are 'better or worse' rather than 'true or false'.

16. What is root cause analysis and name one common technique for it.

    A structured method to identify the underlying cause of a problem rather than treating symptoms. Common techniques include the '5 Whys' and the Ishikawa (fishbone/cause-and-effect) diagram.

17. In an Ishikawa (fishbone) diagram, what do the '6 Ms' categories typically represent?

    Man (people), Machine, Method, Material, Measurement and Mother Nature (environment) — categories of potential causes contributing to an effect/problem.

18. What is the purpose of modelling and simulation in engineering decision-making?

    To represent a system abstractly so that its behaviour can be predicted, explored and optimised before building it — reducing cost and risk, testing scenarios that are dangerous or impractical in reality, and informing design trade-offs with evidence.

19. Distinguish a deterministic model from a stochastic model.

    A deterministic model gives the same output for a given set of inputs (no randomness). A stochastic model incorporates random variables/probability distributions, so outputs vary and are described statistically (e.g. Monte Carlo simulation).

20. What does verification, validation and (un)certainty quantification of a model involve?

    Verifying the model is solved correctly (numerical/code correctness), validating it represents reality adequately (comparison with experimental data), and quantifying the uncertainty in its predictions so decisions account for model limitations.

21. State a key limitation engineers must remember about all models.

    'All models are wrong, but some are useful' — every model is a simplified abstraction valid only within its assumptions and operating envelope; results must be checked against those limits and never extrapolated blindly.

22. What is conceptual design?

    The early design phase that generates and evaluates broad solution concepts and architectures to satisfy requirements — establishing the principal working principles, layout and feasibility before committing to detail.

23. What is detailed (embodiment) design?

    The phase that fully specifies the chosen concept: dimensions, tolerances, materials, components, manufacturing methods and complete documentation, producing everything needed to build and verify the product.

24. What is a design trade-off study (trade study)?

    A systematic evaluation of alternative design options against weighted criteria (cost, performance, risk, weight, etc.) to select the best balanced solution, making the rationale for the decision explicit and traceable.

See more Design, Development and Problem Solving (UK-SPEC B) flashcards →

Planning Design, Development and Problem Solving (UK-SPEC B) for Chartered Membership of the IET (CEng MIET)

Design, Development and Problem Solving (UK-SPEC B) (Chartered Membership of the IET (CEng MIET)) FAQ