Wayground logo

Free Printable Worksheets

Font size

S
M
L
XL
Worksheets

Section A - Unit 1 Requirement Engineering

Total questions: 30

Worksheet time: 22mins

Name
Class
Date
1.

Which philosopher is quoted at the beginning of the introduction to requirements?

a)

Plato

b)

Socrates

c)

Lucius Annaeus Seneca

d)

Marcus Aurelius

2.

Requirements (a)   is crucial because fixing requirements errors after delivery is very costly.

3.

What is the main pressure on the development process in Requirement Engineering?

a)

Decreased funding

b)
  • Fast-changing technology

c)

High employee turnover

d)

Increased regulatory requirements

4.

What are the three key factors driving software as a dominant force of change in new products?

a)

Cost, speed, scalability

b)

Arbitrary complexity, instant distribution, off-the-shelf components

c)

Innovation, usability, efficiency

d)

Customization, flexibility, security

5.

Business requirements are typically outlined in a (a)   requirements document (BRD).

6.

What is the real goal according to the document, beyond just 'time to market'?

a)

Time to market with high quality

b)

Time to market with low cost

c)

Time to market with the right product

d)

Time to market with maximum profit

7.

Which of the following is NOT one of the most common reasons for project failures in Requirement Engineering?

a)

Incomplete requirements

b)

Unrealistic expectations

c)

Lack of user involvement

d)

Advanced technology

8.

According to the Scientific American (Sept. 1994), what increases the chance of project failure?

a)

Larger projects with longer schedules

b)

Smaller projects with shorter schedules

c)

High user involvement

d)

High-quality management support

9.

Which approach does the document mention as encompassing the entire technical effort?

a)

Project Management

b)

Systems Engineering

c)

Agile Development

d)

Waterfall Method

10.

Which type of requirement specifies what the system should do overall?

a)

User requirements

b)
  • Functional requirements

c)

Business requirements

d)

Non-functional requirements

11.

What is the key goal of requirements validation?

a)

To gather user requirements

b)

To demonstrate that the requirements define the system that the customer really wants

c)

To create prototypes

d)

To write user manuals

12.

What does the process of requirements elicitation involve?

a)

Only technical staff working alone

b)
  • Technical staff working with customers and stakeholders to gather requirements

c)

Automated software tools gathering requirements

d)

Management drafting requirements

13.

What is the main focus of requirements specification?

a)

Implementing the system

b)

Documenting the user and system requirements

c)

Conducting market research

d)

Designing the system architecture

14.

A (a)   Analyst is responsible for gathering, analyzing, and documenting business requirements.

15.

Which method is commonly used for documenting requirements in a way that customers can understand?

a)

Design description languages

b)

Natural language

c)

Mathematical specifications

d)

UML diagrams

16.

In requirements elicitation, what is a common challenge when interacting with stakeholders?

a)

Stakeholders always provide clear requirements

b)

Stakeholders have conflicting requirements

c)

Stakeholders do not need to be involved

d)

Stakeholders only need to be involved during testing

17.

What does 'requirements change management' involve?

a)

Avoiding any changes to the system requirements

b)

Implementing all suggested changes immediately

c)

Managing changing requirements during the requirements engineering process and system development

d)

Developing new system features without documenting changes

18.

What is one reason for conducting requirements reviews?

a)

To increase project costs

b)

To delay project timelines

c)

To finalize the system code

d)

To ensure both client and contractor understand and agree on requirements

19.

Which requirement type focuses on the 'how' of a system's performance?

a)

Business requirements

b)

Functional requirements

c)

User requirements

d)

Non-functional requirements

20.

What is the purpose of using prototyping in requirements validation?

a)

To check requirements through an executable model

b)

To increase development speed

c)

To finalize system design

d)

To implement the final system

21.

Why is it important to gather user requirements early in the software development process?

a)

To ensure the system meets the users' needs and expectations

b)

To ensure the system is completed on time

c)

To reduce the overall cost of development

d)

To finalize the project budget

22.

Which technique is commonly used to gather user requirements?

a)

Code reviews

b)

User interviews and surveys

c)

System testing

d)

Budget analysis

23.

When documenting user requirements, why is it important to use natural language?

a)
  • To ensure that developers understand the technical details

b)

To make the document legally binding

c)

To ensure that non-technical stakeholders can understand the requirements

d)

To comply with industry standards

24.

What is the primary focus of business requirements?

a)

To specify the system's user interface design

b)

To outline the business objectives and goals that the system must achieve

c)

To detail the software's coding standards

d)

To define the project's timeline and budget

25.

Why is it critical to align system development with business requirements?

a)

To ensure the system is technically superior

b)

To ensure the system supports the business’s strategic goals and delivers value

c)

To minimize the use of advanced technologies

d)

To speed up the development process

26.

Why is it important to document both user and business requirements?

a)
  • To provide a clear guide for what the system should achieve and how it aligns with business goals

b)

To ensure developers have complete control over the project

c)

To comply with legal standards

d)
  • To create a backup plan for system failures

27.

Aligning system features with business requirements ensures that the system supports the strategic goals and objectives of the organization. It helps in delivering value by addressing the specific needs and challenges faced by the business. For example, if a business requirement is to improve customer satisfaction, a corresponding system feature could be the implementation of a customer feedback system, which allows the business to gather and analyze customer opinions and make improvements based on that feedback.

27.

Explain the importance of aligning system features with business requirements and provide an example.

4 lines
28.

The primary goal of user requirements is to describe the (a)   needed by the end users.

29.

In requirements validation, (a)   is used to check requirements through an executable model.

30.

Which technique can be used to validate that business requirements have been correctly understood?

a)

Code reviews

b)

Prototyping and feedback sessions with stakeholders

c)

System performance testing

d)

Unit testing