Understanding Requirements Engineering

What are functional requirements?

• Functional requirements are the aesthetic aspects of a system.

• Functional requirements are optional features of a system.

• Functional requirements are specifications of what a system should do.

• Functional requirements describe how a system should look.

What are non-functional requirements?

• Non-functional requirements are the same as functional requirements.

• Non-functional requirements are only related to system performance.

• Non-functional requirements are not important for system design.

• Non-functional requirements are criteria that define the quality attributes of a system.

Describe the requirements engineering process.

• The requirements engineering process includes elicitation, analysis, specification, validation, and management of requirements.

• User interface design process

• Requirement gathering only

• Testing and deployment phases

What is requirements elicitation?

• Requirements elicitation is the process of gathering and defining stakeholder needs for a project.

• A method for testing software functionality.

• A strategy for marketing products effectively.

• A technique for managing project budgets.

List some techniques used in requirements elicitation.

• Focus groups

• User testing

• Brainstorming sessions

• Interviews, surveys, workshops, document analysis, observation.

What is the purpose of requirements specification?

• To outline the project budget and timeline.

• To create a marketing strategy for the product.

• To establish the team roles and responsibilities.

• To define and document the needs and expectations of stakeholders for a project.

How do you validate requirements?

• Requirements are validated through automated testing only.

• Requirements are validated through review, stakeholder feedback, and ensuring they are clear, testable, and consistent.

• Requirements are validated by ignoring stakeholder input.

• Validation is done solely by the project manager.

What are some common challenges in requirements validation?

• Stable requirements throughout the project

• Common challenges in requirements validation include unclear requirements, stakeholder misalignment, changing requirements, incomplete requirements, and verification difficulties.

• Full stakeholder agreement

• Clear requirements

Explain the importance of stakeholder involvement in requirements engineering.

• Stakeholder involvement is only necessary for large projects.

• Involvement of stakeholders can lead to project delays.

• Stakeholder involvement is essential for accurately capturing requirements, ensuring project alignment with user needs, and improving overall project success.

• Stakeholders should be excluded to avoid bias in requirements.

What role does documentation play in requirements specification?

• Documentation is essential for clarity, communication, and validation in requirements specification.

• Documentation complicates the requirements process.

• Documentation is only necessary for legal compliance.

• Documentation is irrelevant to project success.