Requirement Engineering

_______ is the process of identifying, eliciting, analyzing, specifying, validating, and managing the needs and expectations of stakeholders for a software system.

• Requirement Engineering

• Planning

• Designing

• Coding

_______ Feasibility current resources both hardware software along required technology are analyzed to develop the project

• Operational

• Technical

• Economic

• Design

______ Feasibility study cost and benefit of the project are analyzed.

• Economic

• Operational

• Technical

• Design

______ is the various way used to gain knowledge about the project domain and requirements.

• Feasibility Study

• Requirement Elicitation

• Specification

• Verification

__________ is the process of documenting the requirements identified in the analysis step in a clear, consistent and unambiguous manner,

• Requirement Specification

• Feasibility Study

• Elicitation

• Verification

________ refers to the set of task that ensures that the software correctly implemented a specific function.

• Verification

• Validation

_______ refers to a different set of tasks that ensures that the software has been built is traceable to customer requirements.

• Verification

• Validation

_______ is the process of analyzing, documenting, tracking, prioritizing, and agreeing on the requirement and controlling the communication with relevant stakeholders.

• Functional Requirements

• Non-Functional Requirements

• Requirement Management

• Validation

_____ are all persons or organizations that are directly or indirectly affected by the activities of a company or have an interest in these activities.

• Developers

• Testers

• Stakeholders

• Clients

______ describe what the software should do. They define the functions or features that the system must have.

• Functional Requirements

• Non-Functional Requirements

• Domain Requirements

• SRS