This item tests how models are distinguished by what they use to represent the system. A model that uses real parts is a physical model: it is built with tangible components that resemble the actual hardware, so you can observe real physical interactions, tolerances, and interfaces. This kind of model is useful for hands-on testing, hardware-in-the-loop validation, and understanding how the system behaves in the real world. In contrast, a digital model relies on software or numerical simulations, not physical components; an informal model is a rough, non-rigorous representation such as sketches or simple diagrams; and a formal model uses precise mathematical or logical descriptions. Since the question emphasizes real parts, the physical model is the best fit.

Requirements engineering focuses on capturing what the system must do and how its needs will be verified and tracked over time. The System Requirements Definition Process is the stage where stakeholders’ needs are elicited, turned into defined requirements, analyzed for feasibility and consistency, and actively managed through baselines and traceability. This process outputs a clear, verifiable set of system requirements that guide design and later verification, and it provides the ongoing management needed as needs evolve. In contrast, System Analysis Process emphasizes understanding problems and constraints, Design Definition Process focuses on turning requirements into architectural and detailed design, and Implementation is about actually building the system.

Technical Performance Measures are the metrics tied directly to system requirements that quantify how well the evolving design is meeting those requirements and what risks remain. They give a numerical way to track design progress, show whether the design is on track to satisfy performance targets, and illuminate technical risks early so you can plan mitigations. As you gather design data across iterations, TPMs reveal trends and inform design reviews and decision points, ensuring choices are based on evidence about capability and risk. Other terms describe different ideas—for example, TRLs assess how mature a technology is, not how well the design meets performance requirements; quality assurance focuses on the quality of processes and final products rather than on tracking progress against requirements and associated risks; and WPA is not the standard term used to capture this specific combination of progress, performance compliance, and risk tracking.

The main idea here is that the Measurement Process is the one responsible for turning information needs into concrete, objective data. It does this by defining what to measure, selecting appropriate metrics, and specifying how data will be collected, analyzed, and reported. This makes the information gathered reliable and comparable, so decisions about the system can be evidence-based. For example, if you need to know whether the system meets a reliability target, the measurement process would establish the relevant metrics (like mean time between failures), determine data sources and collection methods, collect the data, analyze it, and present the results to stakeholders. The other processes serve different roles. The Information Management Process is about how information is stored, shared, and governed across the project lifecycle. The Configuration Management Process focuses on controlling changes to system artifacts and maintaining baselines. MBSE (model-based systems engineering) emphasizes using models to represent and analyze the system, not specifically the activity of gathering objective data.