🇬🇧 Incorporated Engineer (IEng) · subject

Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B) Syllabus

The Design, Development and Application of Solutions (UK-SPEC Competence B) syllabus for Incorporated Engineer (IEng) in full: 4 chapters, 16 topics and 6 sub-topics, every one listed below, plus 51 Design, Development and Application of Solutions (UK-SPEC Competence B) flashcards with answers.

4Chapters
16Topics
6Sub-topics
51Flashcards

Design, Development and Application of Solutions (UK-SPEC Competence B) syllabus: all 4 chapters

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

  1. Identifying and Specifying Engineering Problems

    4 topics
    • Defining the problem, constraints and stakeholder needs
      • Clarifying functional and non-functional requirements
      • Operational, statutory and commercial constraints
    • Requirements capture and specification writing
    • Establishing acceptance criteria and success measures
    • Boundary setting and scope management
  2. Applying Engineering Methods to Develop Solutions

    4 topics
    • Selecting appropriate techniques, procedures and methods
      • Reusing proven and established solutions
      • Adapting standard approaches to new contexts
    • Concept generation and option appraisal
    • Detailed design, specification and tolerancing
    • Design for manufacture, maintenance and whole-life cost
  3. Implementation, Evaluation and Improvement

    4 topics
    • Implementing design changes and modifications
    • Verification, validation and testing against specification
      • Test planning and inspection regimes
      • Commissioning and handover
    • Evaluating outcomes and proposing improvements
    • Design reviews and configuration control
  4. Maintenance, Reliability and Asset Management

    4 topics
    • Maintenance strategies (preventive, predictive, corrective)
    • Reliability, availability and maintainability (RAM) concepts
    • Fault diagnosis, root cause analysis and condition monitoring
    • Asset life-cycle and obsolescence management

Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B) flashcards — 51 questions with answers

  1. In UK-SPEC Competence B, what are the three core elements you must establish when first defining a problem?

    The problem itself (the need/objective), the constraints (limits within which a solution must work, e.g. cost, time, regulation, physical), and stakeholder needs (the requirements and expectations of all affected parties).

  2. Distinguish between a stakeholder's 'need' and a stakeholder's 'want' in problem definition.

    A need is an essential requirement that must be satisfied for the solution to be acceptable; a want is a desirable but non-essential feature. Separating them prevents scope creep and supports prioritisation.

  3. Name three common categories of design constraint.

    Technical/physical (size, weight, performance), economic (budget, whole-life cost), and regulatory/legal (standards, safety, environmental). Others include time, ethical, and resource constraints.

  4. What is the difference between a functional and a non-functional requirement?

    A functional requirement specifies what the system must do (a behaviour or function); a non-functional requirement specifies how well it must do it (quality attributes such as reliability, performance, usability, safety).

  5. State the characteristics of a well-written requirement (the 'SMART'/quality criteria).

    It should be clear/unambiguous, verifiable/testable, feasible, necessary, complete, consistent (non-conflicting), and traceable. Often summarised as Specific, Measurable, Achievable, Relevant, Traceable.

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

    Traceability is the documented link from each requirement forwards to design elements, tests and verification, and backwards to its originating stakeholder need. It ensures every requirement is met and verified, and that no unnecessary features are added.

  7. What are acceptance criteria?

    Pre-agreed, measurable conditions that a product or deliverable must satisfy to be accepted by the customer/stakeholder. They define the boundary between pass and fail for each requirement.

  8. Define a 'success measure' (key performance indicator) and how it differs from an acceptance criterion.

    A success measure/KPI quantifies how well outcomes meet objectives over time (e.g. uptime %, cost saving). An acceptance criterion is a binary pass/fail gate at handover, whereas a success measure tracks ongoing performance against the goal.

  9. In scope management, what is the project 'boundary'?

    The defined edge that separates what is inside the project (deliverables, functions, responsibilities) from what is outside it (exclusions, interfaces with other systems), establishing the limits of work and responsibility.

  10. Define 'scope creep' and give one technique to control it.

    Scope creep is the uncontrolled growth of project scope after the baseline is set, without corresponding adjustment to time, cost or resources. It is controlled by a formal change-control process that assesses and approves every proposed change.

  11. What is a scope statement expected to contain?

    The objectives, in-scope deliverables, explicit exclusions, assumptions, constraints, acceptance criteria, and the key interfaces/boundaries with adjacent systems or projects.

  12. List the main factors used to select an appropriate technique, procedure or method for a design task.

    Suitability for the problem, available resources and competence, cost and time, accuracy/reliability required, risk and safety, applicable standards/codes, and compatibility with existing systems.

  13. What is concept generation in the design process?

    The divergent, creative phase of producing multiple candidate solution ideas (concepts) before evaluation, using methods such as brainstorming, morphological analysis, TRIZ, and benchmarking, to avoid premature fixation on one solution.

  14. What is option appraisal and name one structured tool used for it.

    Option appraisal is the systematic comparison of candidate solutions against weighted criteria to select the best. A common tool is the weighted decision (Pugh) matrix; others include cost-benefit analysis and SWOT.

  15. How does a weighted decision matrix (Pugh matrix) work?

    Each option is scored against a set of evaluation criteria; each criterion has a weight reflecting its importance. The score is multiplied by the weight and summed per option: $S=\sum_{i} w_{i} r_{i}$. The highest total identifies the preferred option.

  16. What is the purpose of detailed design following concept selection?

    To convert the chosen concept into a fully specified, buildable solution: dimensions, materials, tolerances, interfaces, components and documentation sufficient for manufacture, construction or implementation.

  17. What is engineering tolerance?

    The permissible total variation in a dimension or property: the difference between the maximum and minimum acceptable limits. For a size $D$ with upper limit $U$ and lower limit $L$, tolerance $T = U - L$.

  18. Why should tolerances be specified as widely as the design allows?

    Tighter tolerances increase manufacturing cost, scrap and inspection effort. Specifying the loosest tolerance that still meets functional requirements minimises cost while ensuring fit, form and function.

  19. What is tolerance stack-up (accumulation)?

    The cumulative effect of individual part tolerances on an assembly. Worst-case stack adds them arithmetically: $T_{total}=\sum_{i=1}^{n} T_{i}$; statistical (RSS) stack uses $T_{total}=\sqrt{\sum_{i=1}^{n} T_{i}^{2}}$.

  20. What does Design for Manufacture (DFM) aim to achieve?

    To design a product so it is easy, cheap and reliable to make: minimising part count, using standard components and processes, simplifying geometry, and designing for the chosen manufacturing method to reduce cost and defects.

Show the other 31 Design, Development and Application of Solutions (UK-SPEC Competence B) flashcards
  1. What is Design for Maintainability (DfM/maintenance)?

    Designing equipment so it can be inspected, serviced and repaired quickly and safely: good access, modularity, standard fasteners, diagnostic features and easily replaceable components, reducing mean time to repair.

  2. Define whole-life cost (life-cycle cost).

    The total cost of an asset over its entire life: acquisition (capital) plus operation, maintenance, downtime, and disposal costs. $LCC = C_{acq} + C_{op} + C_{maint} + C_{disposal}$ (often discounted to present value).

  3. Why is whole-life cost preferred over purchase price when appraising designs?

    Because the largest share of cost is often incurred during operation and maintenance, not purchase. A cheaper item to buy may have higher running, energy or disposal costs, making it more expensive over its life.

  4. What is the recommended process for implementing a design change or modification?

    Raise a change request, assess impact (cost, safety, schedule, interfaces), obtain approval through change/configuration control, update documentation and baselines, implement, then verify and validate the change.

  5. Distinguish verification from validation.

    Verification asks 'did we build the product right?' — does it meet the specification. Validation asks 'did we build the right product?' — does it meet the user's actual needs in the operating environment.

  6. List four common testing types used to confirm a design meets specification.

    Unit/component testing, integration testing, system testing, and acceptance testing. Others include functional, performance, environmental, and regression testing.

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

    A FAT verifies the equipment against specification at the manufacturer's premises before shipment; a SAT verifies it again after installation at the operating site to confirm correct integration and on-site performance.

  8. What is the purpose of evaluating outcomes after implementation?

    To compare actual performance against the original objectives, success measures and acceptance criteria, identify shortfalls and lessons learned, and propose improvements for the current and future designs (continuous improvement).

  9. Name a structured continuous-improvement cycle used to drive design improvements.

    The PDCA (Plan-Do-Check-Act) Deming cycle; also DMAIC (Define, Measure, Analyse, Improve, Control) from Six Sigma.

  10. What is a design review?

    A formal, documented, systematic examination of a design by competent reviewers at defined stages (gates) to evaluate whether it meets requirements, identify problems early, and authorise progression to the next phase.

  11. List typical formal design-review stages (gates) in a project.

    Requirements/System Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), and Production/Final Design Review. They act as go/no-go decision gates.

  12. What is configuration management?

    The discipline of identifying, controlling, recording the status of, and auditing the configuration items of a product throughout its life, ensuring consistency between the product, its requirements, and its documentation.

  13. State the four main functions of configuration management.

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

  14. What is a configuration baseline?

    A formally reviewed and agreed reference version of a configuration item (e.g. requirements, design, build) that serves as the basis for further work and can only be changed through formal change control.

  15. Name and distinguish the three principal maintenance strategies.

    Corrective (reactive) — repair after failure; Preventive — scheduled at fixed time/usage intervals to prevent failure; Predictive (condition-based) — maintenance triggered by monitored condition indicating impending failure.

  16. What is the main disadvantage of a purely corrective (run-to-failure) maintenance strategy?

    Unplanned downtime, potential safety/consequential damage, higher repair costs and disruption, because failures occur without warning. It is acceptable only for non-critical, low-cost items.

  17. What is the difference between preventive and predictive maintenance triggers?

    Preventive is triggered by elapsed time or usage (calendar/hours/cycles) regardless of actual condition; predictive is triggered by the measured condition of the asset, performing maintenance only when data indicates it is needed.

  18. What is Reliability-Centred Maintenance (RCM)?

    A structured method that determines the most effective maintenance strategy for each asset based on its functions, failure modes and consequences, selecting corrective, preventive, predictive or redesign as appropriate to preserve function at least cost.

  19. Define reliability in the RAM context.

    The probability that an item performs its required function under stated conditions for a specified period of time without failure. It is concerned with avoiding failure.

  20. Define maintainability in the RAM context.

    The ease and speed with which an item can be restored to operating condition after failure, usually measured by the Mean Time To Repair (MTTR). It reflects how quickly maintenance can be performed.

  21. Define availability and give its steady-state formula in terms of MTBF and MTTR.

    Availability is the proportion of time an item is in a functioning, ready-to-use state. $$A = \frac{MTBF}{MTBF + MTTR}$$

  22. What does MTBF stand for and how is it defined?

    Mean Time Between Failures — the average operating time between failures of a repairable item: $MTBF = \frac{\text{total operating time}}{\text{number of failures}}$.

  23. What is the difference between MTBF and MTTF?

    MTBF (Mean Time Between Failures) applies to repairable items and measures time between successive failures; MTTF (Mean Time To Failure) applies to non-repairable items and measures the average time to the single failure that ends life.

  24. State the relationship between failure rate $\lambda$ and MTBF for a constant failure rate.

    For a constant (random) failure rate, MTBF is the reciprocal of the failure rate: $$MTBF = \frac{1}{\lambda}.$$

  25. Give the reliability function for an item with a constant failure rate $\lambda$.

    The reliability at time $t$ follows the exponential law: $$R(t) = e^{-\lambda t}.$$

  26. Describe the three regions of the bathtub curve.

    1) Infant mortality / early life — decreasing failure rate (manufacturing/installation defects); 2) Useful life — constant, low random failure rate; 3) Wear-out — increasing failure rate as the item ages and degrades.

  27. How does reliability combine for components in series versus in parallel?

    Series (all must work): $R_{s}=\prod_{i=1}^{n} R_{i}$. Parallel/redundant (one must work): $R_{p}=1-\prod_{i=1}^{n}(1-R_{i})$.

  28. What is root cause analysis and name two common techniques.

    A systematic process to identify the underlying cause of a failure (not just symptoms) so it can be permanently eliminated. Techniques include the '5 Whys' and the Ishikawa (fishbone/cause-and-effect) diagram; also Fault Tree Analysis and FMEA.

  29. What is FMEA and what is the Risk Priority Number?

    Failure Mode and Effects Analysis systematically identifies potential failure modes and their effects. The Risk Priority Number ranks them: $RPN = S \times O \times D$ (Severity × Occurrence × Detection), prioritising actions on the highest values.

  30. What is condition monitoring and give three example techniques?

    Condition monitoring measures parameters that indicate machine health to detect developing faults. Examples: vibration analysis, oil/lubricant (tribology) analysis, thermography, and acoustic emission. It underpins predictive maintenance.

  31. What is asset obsolescence management and why is it important?

    The proactive identification and mitigation of components, software or technology becoming unavailable or unsupported over an asset's life. It is important to avoid forced downtime, costly redesign and loss of support, planning last-time buys, redesign or substitution in advance.

Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B) FAQ

What is in the Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B) syllabus?

Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B) is split into 4 chapters: Identifying and Specifying Engineering Problems, Applying Engineering Methods to Develop Solutions, Implementation, Evaluation and Improvement and Maintenance, Reliability and Asset Management. Together they contain 16 topics and 6 sub-topics.

How many chapters are in Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B)?

4 chapters, containing 16 topics and 6 sub-topics. The largest chapter is Identifying and Specifying Engineering Problems, with 4 topics.

Are there flashcards for Incorporated Engineer (IEng) Design, Development and Application of Solutions (UK-SPEC Competence B)?

Yes — a 51-card Design, Development and Application of Solutions (UK-SPEC Competence B) 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.