Chartered Membership of IMechE (CEng MIMechE) Engineering Design, Development and Problem Solving Syllabus

Engineering Design, Development and Problem Solving syllabus — full chapter and topic list

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

1. 1

   Requirements and Solution Development

   3 topics

   • Defining the engineering problem
     • Stakeholder needs and design constraints
     • Functional and non-functional requirements
   • Generating and evaluating concepts
     • Ideation, morphological analysis and trade studies
     • Decision matrices and selection criteria
   • Managing technical uncertainty
     • Assumptions, sensitivity and worst-case analysis
     • Prototyping and iterative refinement
2. 2

   Implementation and Verification

   3 topics

   • Detailed engineering and analysis
     • Calculations, modelling and design margins
     • Design reviews and peer checking
   • Testing and commissioning
     • Verification, validation and acceptance testing
     • Commissioning, handover and as-built records
   • Continuous improvement
     • Root cause analysis and corrective action
     • Lessons learned and design feedback loops
3. 3

   Innovation and Technical Leadership

   3 topics

   • Driving innovation
     • Applying novel methods and technologies
     • Managing technical risk in innovation
   • Intellectual property and exploitation
     • Patents, design rights and confidentiality
     • Commercialisation and value capture
   • Whole-life engineering thinking
     • Cost, performance and through-life support
     • Design for manufacture, maintenance and disposal

Engineering Design, Development and Problem Solving flashcards for Chartered Membership of IMechE (CEng MIMechE)

20 of 73 cards from the Engineering Design, Development and Problem Solving deck — real questions with worked answers.

1. In engineering design, what is the purpose of a Product Design Specification (PDS)?

   A PDS is a formal document that captures all the requirements, constraints and performance targets a design must satisfy. It translates the problem into measurable criteria (function, environment, cost, size, life, standards) and acts as the controlling reference against which concepts are evaluated and the final design is verified.

2. Distinguish between a 'need', a 'requirement', and a 'constraint' when defining an engineering problem.

   A need is the underlying user/stakeholder want (the 'why'). A requirement is a specific, verifiable statement of what the solution must do or achieve. A constraint is a fixed boundary or limitation (e.g. budget, regulation, mass) that the solution must not violate.

3. What is the difference between functional and non-functional requirements?

   Functional requirements specify what the system must do (its functions and behaviours). Non-functional requirements specify how well it must do it or qualities it must have (reliability, safety, usability, maintainability, performance).

4. Why are well-defined requirements expressed as SMART, and what does SMART stand for?

   SMART makes requirements unambiguous and testable. It stands for Specific, Measurable, Achievable, Relevant, and Time-bound.

5. What is a 'design brief' and how does it differ from a specification?

   A design brief is a short, high-level statement of the problem, objectives, scope and context given at the start of a project. A specification is the detailed, quantified set of requirements derived from analysing the brief and stakeholder needs.

6. Define stakeholder analysis in the context of problem definition.

   Stakeholder analysis is the systematic identification of all parties affected by or influencing a project (users, clients, regulators, manufacturers, maintainers, society) and the capturing of their needs, expectations and influence so the requirements fully represent them.

7. What is the role of boundary definition (system boundary) when defining an engineering problem?

   It establishes what is inside the system being designed versus what lies in the surrounding environment, clarifying interfaces, inputs/outputs and responsibilities, and preventing scope creep or omitted interactions.

8. What is requirements traceability and why is it important?

   It is the ability to link each requirement forward to design decisions, components and tests, and backward to its originating stakeholder need. It ensures every requirement is addressed and verified, and that no design feature exists without justification.

9. In concept generation, what is the function of a morphological chart (morphological analysis)?

   A morphological chart lists the sub-functions of a product in rows and possible solution principles for each in columns. New overall concepts are generated by combining one solution per sub-function, systematically expanding the design space.

10. Name three structured idea-generation techniques used in concept generation.

    Examples include brainstorming, morphological analysis, TRIZ, SCAMPER, biomimicry, lateral thinking, and the 6-3-5 brainwriting method.

11. What is TRIZ and what core idea underpins it?

    TRIZ (Theory of Inventive Problem Solving) is a systematic innovation methodology derived from patent analysis. Its core idea is that recurring contradictions in engineering can be resolved using a set of generic inventive principles rather than ad-hoc compromise.

12. What is a weighted decision matrix (Pugh-style scoring matrix) used for in concept evaluation?

    It evaluates competing concepts against weighted criteria. Each concept is scored per criterion, scores are multiplied by criterion weights and summed, giving a total that ranks concepts objectively. $$S_j = \sum_{i} w_i \, r_{ij}$$ where $w_i$ is the weight of criterion $i$ and $r_{ij}$ the rating of concept $j$.

13. How does a Pugh matrix (controlled convergence) differ from a weighted scoring matrix?

    A Pugh matrix compares concepts against a single datum concept using relative scores of better (+), same (S) or worse (-) per criterion, rather than absolute weighted numerical scores. It is used for rapid relative comparison and concept refinement.

14. What is concept screening versus concept scoring in the selection process?

    Screening is a coarse, quick filter (often a Pugh +/S/- matrix against a reference) to eliminate weak concepts. Scoring is a finer, weighted numerical evaluation of the surviving concepts to select the best.

15. What is a function structure (function decomposition) and why use it early in design?

    It breaks the overall product function into a network of sub-functions describing flows of energy, material and signal. It enables solution-neutral thinking, ensuring concepts address the actual functions rather than fixating on one form.

16. Define 'design space' and 'solution-neutral problem statement'.

    The design space is the full set of possible solutions bounded by the requirements. A solution-neutral problem statement describes what must be achieved without implying a particular solution, keeping the design space as wide as possible.

17. What is technical (technological) uncertainty, and how does it differ from risk?

    Technical uncertainty is a lack of knowledge about whether or how something can be achieved (outcome not yet known). Risk is an uncertain event characterised by both a probability of occurrence and a defined impact, allowing it to be quantified and managed.

18. What is a Technology Readiness Level (TRL) and what does the scale span?

    TRL is a 1-to-9 scale measuring the maturity of a technology. TRL 1 is basic principles observed, TRL 5-6 is technology validated/demonstrated in relevant environment, and TRL 9 is the actual system proven in the operational environment.

19. How is a risk's severity commonly quantified in a risk register?

    As a risk priority or exposure equal to the product of likelihood and consequence (impact): $$R = P \times C$$ where $P$ is probability of occurrence and $C$ is the magnitude of the consequence.

20. Name the standard hierarchy of risk control measures from most to least effective.

    Eliminate, Substitute, Engineering controls (isolate/guard), Administrative controls (procedures/training), and Personal Protective Equipment (PPE) as the last resort.

See more Engineering Design, Development and Problem Solving flashcards →

Planning Engineering Design, Development and Problem Solving for Chartered Membership of IMechE (CEng MIMechE)

Engineering Design, Development and Problem Solving (Chartered Membership of IMechE (CEng MIMechE)) FAQ