Answer in ALL CAPS, remove the space after your answer. The first activity in software engineering is Requirements -----------.

This defines what the system will do in preparation to the design activity

This refers to requirements being described in a natural language, and possibly with the addition of simple tables and diagrams without using formal modeling languages.

This define exactly what will be implemented in the system. This is a document contains the models that describe the system’s services, use cases, behavior, constraints, high-level business processes,

Group the ff which are Levels of Abstraction, and which are Categories of Requirements

Category of requirements that define the external behavior of the system, how the system interacts with its environment, how it responds to inputs, what output to generate and how to behave under certain conditions.

Category of requirements that  are either quality attributes of the system or constraints on the system or the supporting infrastructure.

Which of the ff are samples of quality attributes?

Category of requirements that means what the system does and what the system must not do

Transforming qualitative requirements to quantitative ones are done thru requirements engineering process

Without being quantitative, requirements can be properly designed and later measured.

Between analysts and designers, who would work with customers to quantify nonfunctional requirements? Sample customers says the system should be fast, these people will convert it to terms like: the system while having 100 simultaneous users should respond in 2 seconds max. 

Between analysts and designers, who would validate feasibility requirements? Sample, the customer wants a secure system, this person will create a user registration and log in module

For important roles, these are the ones asking for the system to be built

For important roles, these are the ones that will be using and interacting with the system

For important roles, these are the ones that define a system’s functional and nonfunctional requirements and then creates models for these requirements in a system requirement documents

For important roles, these are the ones that are any entities that have an interest in a project, in other words that either affect project outcome or are themselves affected by the project outcome.

Stakeholders are entities that are only existing inside an organization, never outside an organization

This step in Requirements Engineering is all about information discovery and collection

This step in Requirements Engineering where customer and user needs are deeply understood

This step in Requirements Engineering where it is about the production, review, evaluation, and approved of the system requirements specification document.

This step in Requirements Engineering where it is about finding potential problems with the requirements.

Order these requirements engineering processes into the proper order

What do we mean when we say that requirements should be unambiguous?