Functional and Non-Functional Requirements

This quiz covers the distinction between functional and non-functional requirements, the three categories of non-functional requirements (product, organizational, external), how to write testable non-functional requirements, metrics for measuring system properties, and the concept of requirements completeness and consistency

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 244

Questions #: 16

Time: 15 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Definition of Functional Requirements

1 pts

volume_mute

Which of the following best describes functional requirements?

Emergent system properties such as reliability, performance, and availability

Requirements derived from the application domain that constrain how computations must be carried out

Statements of services the system should provide, how it should react to particular inputs, and how it should behave in particular situations

Constraints on the development process imposed by the client organization

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Functional Requirements — MHC-PMS Examples

2 pts

volume_mute

Which of the following are functional requirements for the MHC-PMS (mental health care patient management system)? Select all that apply.

Users of the MHC-PMS system shall authenticate themselves using their health authority identity card.

The system shall generate each day, for each clinic, a list of patients who are expected to attend appointments that day.

A user shall be able to search the appointments lists for all clinics.

The system shall be available to all clinics during normal working hours (Mon–Fri, 08:30–17:30).

Each staff member using the system shall be uniquely identified by his or her eight-digit employee number.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Imprecision in Functional Requirements

1 pts

volume_mute

The requirement 'A user shall be able to search the appointments lists for all clinics' is considered ambiguous. What is the key ambiguity?

It is unclear what 'appointments' means in a clinical context

It is unclear who is allowed to perform the search

It does not specify how many clinics the system supports

The word 'search' is ambiguous — it could mean a global cross-clinic search by patient name, or it could mean the user must first select a clinic and then search within it

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Completeness and Consistency

1 pts

volume_mute

In principle, a functional requirements specification should be both complete and consistent. Fill in the blanks:

"(1) means that all services required by the user should be defined. (2) means that requirements should not have contradictory definitions of the same system function."

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Why Complete and Consistent Requirements Are Hard

1 pts

volume_mute

True or False: For large, complex systems it is practically impossible to achieve requirements that are fully complete and consistent.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Definition of Non-Functional Requirements

1 pts

volume_mute

Non-functional requirements are best described as:

Detailed descriptions of specific services the system must deliver

Constraints on the services or functions offered by the system, including timing constraints, development process constraints, and standards constraints

Requirements that only apply to the user interface of the system

High-level natural language statements of what the system should do for end-users

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Non-Functional Requirements — System vs. Component Level

1 pts

volume_mute

True or False: Non-functional requirements often apply to the system as a whole, rather than to individual system features or services.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Criticality of Non-Functional Requirements

1 pts

volume_mute

True or False: Non-functional requirements are often more critical than individual functional requirements because failing to meet a non-functional requirement can make the whole system unusable.

False

True

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Categories of Non-Functional Requirements

2 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Description

Broad system requirements derived from policies and procedures in the customer's and developer's organization (e.g., development process requirements, operational requirements)

Requirements that specify or constrain the behavior of the software itself (e.g., performance, reliability, security, usability)

Requirements derived from factors external to the system and its development process (e.g., regulatory, legislative, ethical requirements)

Non-functional requirements are classified into three main categories. Match each category to its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Classifying NFR Examples

2 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

NFR

The MHC-PMS shall be available to all clinics during normal working hours (Mon–Fri, 08:30–17:30). Downtime within normal working hours shall not exceed five seconds in any one day.

Users of the MHC-PMS system shall authenticate themselves using their health authority identity card.

The system shall implement patient privacy provisions as set out in HStan-03-2006-priv.

Correct Answer

Explanation

NFR Metrics — Matching Properties to Measures

3 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Property

Speed

Size

Ease of Use

Reliability

Robustness

Portability

Measure

Percentage of target-dependent statements; Number of target systems

Processed transactions/second; User/event response time; Screen refresh time

Mbytes; Number of ROM chips

Time to restart after failure; Percentage of events causing failure

Mean time to failure; Probability of unavailability; Rate of failure occurrence

Training time; Number of help frames

Match each system property to the correct metric used to measure it for non-functional requirements specification.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Goal vs. Testable NFR

1 pts

volume_mute

Consider these two statements about system usability:

Goal: The system should be easy to use by medical staff and should be organized in such a way that user errors are minimized.

Testable NFR: Medical staff shall be able to use all the system functions after four hours of training. After this training, the average number of errors made by experienced users shall not exceed two per hour of system use.

Why is the Testable NFR preferred over the goal?

The testable NFR focuses on training time, which is always the most important usability metric

The testable NFR provides measurable, objectively verifiable criteria; the goal is vague and cannot be tested

The testable NFR is shorter and therefore clearer

The testable NFR was written by an engineer, while the goal was written by a user

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Challenges in Measuring NFRs

2 pts

volume_mute

Which of the following are genuine difficulties in specifying non-functional requirements quantitatively? Select all that apply.

Customers may not be able to relate measurable specifications to their everyday experience of computer systems

Customers always prefer vague goals because they are easier to write

The cost of objectively verifying measurable NFRs can be very high

Non-functional requirements can never be measured by any means

For some properties like maintainability, there are no usable metrics

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

NFR Conflicts and Interactions

1 pts

volume_mute

True or False: Non-functional requirements never conflict or interact with other functional or non-functional requirements.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

NFRs and System Architecture

2 pts

volume_mute

Why can non-functional requirements affect the overall system architecture rather than just individual components? Select all that apply.

Reliability NFRs may require redundant components spread across the entire system

To meet a performance NFR, you may have to organize the system to minimize communications between components

Non-functional requirements always map directly to a single identifiable component in the system

A single security NFR may generate multiple related functional requirements that define new system services and restrict existing ones

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Separating Functional and Non-Functional Requirements

1 pts

volume_mute

True or False: It is always straightforward to separate functional requirements from non-functional requirements in a requirements document, and they should always be kept in completely separate sections.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Definition of Functional Requirements

Correct Answer

Explanation

Functional Requirements — MHC-PMS Examples

Correct Answer

Explanation

Imprecision in Functional Requirements

Correct Answer

Explanation

Completeness and Consistency

Correct Answer

Explanation

Why Complete and Consistent Requirements Are Hard

Correct Answer

Explanation

Definition of Non-Functional Requirements

Correct Answer

Explanation

Non-Functional Requirements — System vs. Component Level

Correct Answer

Explanation

Criticality of Non-Functional Requirements

Correct Answer

Explanation

Three Categories of Non-Functional Requirements

Category

Description

Correct Answer

Explanation

Classifying NFR Examples

NFR

Category

Correct Answer

Explanation

NFR Metrics — Matching Properties to Measures

Property

Measure

Correct Answer

Explanation

Goal vs. Testable NFR

Correct Answer

Explanation

Challenges in Measuring NFRs

Correct Answer

Explanation

NFR Conflicts and Interactions

Correct Answer

Explanation

NFRs and System Architecture

Correct Answer

Explanation

Separating Functional and Non-Functional Requirements

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: