Requirements Engineering

Flashcards about requirements engineering, including types of requirements, the requirements engineering process, and elicitation methods.

What is a requirement in software development?

A statement about an intended product that specifies what it should do or how it should perform.

Name four different types of requirements.

Business, User, Functional, and Non-Functional requirements.

What are Functional Requirements?

What the system must do and how the system will be implemented, including functions and data requirements.

What are Non-Functional Requirements?

Qualities or characteristics that the system must have, such as usability, performance, and security.

Name three categories of Non-Functional Requirements.

Product, Organisational, and External requirements.

Give examples of product requirements related to Non-Functional requirements.

Efficiency, reliability, portability and usability

Define Requirements Engineering.

Establishing user requirements, i.e., what people want from a computer system.

List the stages of Requirements Engineering.

Requirements elicitation (gathering), Requirements analysis, Requirements documentation, and Requirements verification and validation.

What is Requirements Elicitation?

Articulating and understanding users’ needs, as well as any constraints and any processes that need to be followed.

Name some methods for Requirements Elicitation.

Questionnaires, Interviews, Brainstorming, Observations, Workshops and Focus groups, and Prototyping.

What are some challenges of Requirements Elicitation?

Users may not know what they want, or struggle to articulate it. Also, difficulties communicating between users and designers due to different backgrounds, knowledges, vocabularies and goals

What two properties should requirements ideally possess?

Completeness and consistency.