Engineering Design & Requirements

← Back to Domain-Specific Families

Abstractions about turning needs and constraints into engineered products, services, and systems. They cover requirements capture, conceptual and model-based design, prototyping, evaluation, logistics, user participation, integration, and the organizational methods that coordinate design work.

47 abstractions in this family — domain-specific abstractions that sit near one another in structural-signature space (k-means over structural-signature embeddings). Each is shown with its short description.

• Bond graph — A domain-independent graphical model of power exchange in dynamic physical systems using effort–flow variable pairs and energy-conserving junctions.
• Conceptual design — The early design phase that establishes a solution's governing functions, architecture, interactions and form before detailed specification.
• Conditional Design Manifesto — A collaborative design method that treats explicit rules, conditions and participant interactions as the design, allowing the final form to emerge unpredictably from execution.
• Constraint (computer-aided design) — A declared geometric or dimensional relation that a parametric CAD model must preserve during editing.
• Continuous design — An evolutionary design practice that revises a modular system throughout development using fast feedback, tests, refactoring, and delayed reversible decisions.
• Dematerialization (products) — Reducing the material throughput required to deliver a product’s function, including substitution of access or service systems for individual ownership.
• Design for logistics — The product-development practice of shaping product architecture, packaging and process so transport, storage, handling and replenishment costs and service constraints are controlled.
• Design thinking — A family of human-centered design approaches that iteratively frame ambiguous problems, study users, generate alternatives, prototype and learn from testing.
• Digital prototyping — The construction and iterative evaluation of a virtual product model before committing to a physical prototype or production tooling.
• Easy Approach to Requirements Syntax — A small family of structured natural-language templates for writing clear system requirements.
• Ecological interface design — An interface-design approach that visually exposes the invariant constraints and affordances of a complex work domain so operators can adapt across familiar and unforeseen situations.
• EDA database — A specialized design database representing electronic-circuit objects, geometry, connectivity, hierarchy and constraints for interoperating automation tools.
• Empirical algorithmics — The systematic experimental study of algorithm behavior through implemented instances, controlled benchmarks and statistical analysis.
• End user — The person who ultimately operates or directly experiences a product, distinct from its purchaser, administrator, maintainer, or intermediary.
• Engineering analysis — Systematic decomposition and model-based evaluation of an engineered system to infer performance, state, margins or failure behavior.
• Engineering design process — An iterative, evidence-driven process that translates needs into a verified and realizable engineering design across its lifecycle.
• Form, fit and function — An engineering equivalence test asking whether a replacement preserves a component’s physical characteristics, interfaces and required behavior.
• Gajski–Kuhn chart — A Y-shaped framework organizing hardware-system representations across behavioral, structural, and physical domains and across successive abstraction levels.
• Generative design — An iterative design process in which algorithms generate and evaluate many candidate forms under designer-specified goals and constraints.
• Holacracy — A branded organizational-governance method distributing authority through nested circles, explicit roles and rule-governed governance meetings.
• Industrial design rights in the European Union — The layered EU legal regime protecting a product’s appearance through unitary registered or unregistered design rights alongside harmonized national rights.
• Knowledge acquisition — The elicitation, extraction and formal encoding of domain knowledge needed to build or maintain a knowledge-based system.
• Knowledge Acquisition and Documentation Structuring — The KADS methodology for developing knowledge-based systems through explicit models of organization, tasks, expertise, communication and design rather than direct rule extraction into code.
• Knowledge-based engineering — An engineering approach that encodes reusable design knowledge, constraints and reasoning in software to automate or assist product and process design.
• Liner shipping network design and scheduling problem — A maritime-operations optimization problem jointly choosing liner services, schedules, vessel deployment, and container flows.
• Linking pin model — An organizational design of overlapping work groups in which each group's leader is simultaneously a member of the next higher group.
• Main effect — The marginal effect of one factor on a response averaged over the levels or distribution of the other factors in a factorial model.
• Model-based design — A development process in which an explicit executable system model serves as the central specification for analysis, simulation, design decisions, implementation generation and verification.
• Morphological analysis (problem-solving) — A method for enumerating and testing combinations of discrete dimensions in a complex nonquantified problem space.
• Object Process Methodology — A systems-modeling language and methodology that represents stateful objects and the processes that create, transform or consume them in one integrated model.
• Product design — The process of defining a product’s form, function, interaction, manufacturability and lifecycle so it meets user and business needs.
• Product-family engineering — An engineering discipline that builds a shared product-line platform with explicitly modeled common features and planned variability from which related products are derived.
• Requirement — An engineering condition that a product, service, process, or work result must satisfy to be acceptable to a declared stakeholder, contract, standard, or verification regime.
• Science fiction prototyping — A futures and design method that uses a science-fiction narrative to explore a proposed technology’s operation, users and social consequences before it exists.
• Semiconductor process simulation — A technology-CAD method that numerically predicts device geometry, materials, dopant profiles, stress, and defects produced by a proposed semiconductor fabrication sequence.
• Service design sprint — A time-boxed collaborative process for framing, prototyping, and testing a service concept or improvement.
• Ship class — A group of ships built from substantially the same design, distinguished from broader functional ship types.
• Signage — A coordinated system of displayed signs and visual cues that identifies places, communicates rules or hazards and supports orientation and wayfinding in a physical or digital environment.
• Specialty engineering — The integration of cross-cutting engineering disciplines needed for system qualities or environments not owned by the main hardware, software or human-factors design streams.
• Structured analysis and design technique — A hierarchical functional modeling methodology using box-and-arrow activity and data diagrams to describe system inputs, controls, outputs and mechanisms.
• Systems integrator — A functional engineering role responsible for combining independently developed subsystems and verifying that their interfaces produce the required whole-system behavior.
• Systems modeling — The interdisciplinary practice of constructing purpose-specific representations of a system’s structure, functions, behavior, requirements and environment.
• Technology support net — The interdependent physical, energy, information, legal and cultural infrastructure that enables a technology core to develop and operate.
• Test and evaluation master plan — A governing program document that integrates test objectives, resources, responsibilities, schedules, environments, and decision evidence across a system lifecycle.
• Toolkits for user innovation — Coordinated design environments that let users translate their own need information into feasible customized products or services through bounded choices, simulation and rapid feedback.
• Transformation design — A human-centered iterative design practice for producing durable change in the behavior and form of complex organizations or social systems.
• Transgenerational design — A design approach creating products and environments usable and appealing across age groups, including changes in ability associated with aging, without stigmatizing adaptations.