Requirements Definition and Analysis Flashcards

A systems engineer is analyzing a requirement that states: 'The system shall be user-friendly.' Which of the following characteristics of a good requirement is this statement primarily violating?

Answer: Verifiable

The term 'user-friendly' is subjective and cannot be objectively measured or tested. A good requirement must be verifiable, meaning there is a definitive way to determine if the system meets the requirement through inspection, analysis, demonstration, or test. To improve this, the requirement should be broken down into specific, measurable criteria, such as 'The system shall respond to user input within 0.5 seconds' or 'A new user shall be able to complete Task X within 5 minutes with no more than 1 error.'

Which of the following activities is central to the Requirements Definition process, transforming stakeholder needs into a technical view of the solution?

Answer: Creating a set of verifiable system requirements

The core purpose of the Requirements Definition process is to translate the stakeholder-oriented view of desired capabilities into a detailed, technical set of system requirements that the development team can build and verify against. Trade-off studies, coding, and testing are all crucial later-stage activities that are guided by the outputs of the requirements definition process.

During a requirements elicitation workshop for a new emergency response system, a firefighter requests a feature to 'quickly access incident data,' while a paramedic asks for a feature to 'rapidly view patient history.' What is the most effective initial action for the systems engineer?

Answer: Analyze and synthesize the underlying needs to create a single, well-defined requirement.

The systems engineer's role is not just to collect stated wants, but to analyze and understand the underlying needs. Both stakeholders are expressing a need for fast access to critical information. The best approach is to analyze this common need and synthesize it into a clear, unambiguous, and verifiable requirement, such as 'The system shall display critical incident and patient data within 3 seconds of a user query.' This avoids redundant or conflicting requirements and focuses on the essential capability.

A requirement for a satellite communication system states: 'The system shall store tracking data in a SQL database on a solid-state drive.' This requirement violates which key characteristic of a well-written requirement?

Answer: It is not implementation-free.

This requirement specifies *how* the system should meet the need (using a SQL database on an SSD), rather than *what* the system must do. Good requirements should be implementation-free, focusing on the functional and performance needs, which allows designers the flexibility to choose the best technical solution. A better requirement would be: 'The system shall store up to 10 TB of tracking data and retrieve any data point within 500 milliseconds.'

What is the primary distinction between requirements validation and requirements verification in the context of systems engineering?

Answer: Validation confirms the right system is being built (meets stakeholder needs), while verification confirms the system is built right (meets requirements).

This is a fundamental concept in systems engineering. Validation is the process of ensuring that the defined requirements accurately reflect the true needs and expectations of the stakeholders – are we building the right thing? Verification is the process of ensuring that the developed system or component meets the specified requirements – are we building the thing right?

Which of the following is an example of a well-written, atomic requirement?

Answer: The system shall authenticate users against the corporate LDAP directory.

An atomic requirement is one that specifies a single, complete capability and cannot be broken down further without losing its meaning. 'The system shall authenticate users against the corporate LDAP directory' is a single, verifiable function. The other options are either not verifiable ('fast and reliable') or combine multiple actions ('log in and display dashboard', 'process payments and generate email'), which should be specified as separate, atomic requirements for proper traceability and testing.