Chapter 2 SA

Question 1

What is the primary goal of system analysis?

Answer 1

To understand and specify the requirements for a system.

Question 2

True or False: System requirements are only technical specifications.

Answer 2

False

Question 3

What are the two main types of system requirements?

Answer 3

Functional and non-functional requirements.

Question 4

Fill in the blank: Functional requirements describe what a system should _______.

Answer 4

do

Question 5

What is meant by non-functional requirements?

Answer 5

Requirements that define the quality attributes of a system.

Question 6

Which technique is commonly used to gather system requirements?

Answer 6

Interviews

Question 7

True or False: Stakeholders are not important in the requirements gathering process.

Answer 7

False

Question 8

What is a use case in system analysis?

Answer 8

A description of how users will interact with the system.

Question 9

What type of diagram is often used to visualize system requirements?

Answer 9

Use case diagram

Question 10

Multiple Choice: Which of the following is NOT a method for gathering requirements?
A) Surveys
B) Prototyping
C) Programming

Answer 10

C) Programming

Question 11

What does the acronym SRS stand for?

Answer 11

Software Requirements Specification

Question 12

True or False: Requirements should be documented and validated.

Answer 12

True

Question 13

What is the purpose of requirement validation?

Answer 13

To ensure that the requirements meet the needs of stakeholders.

Question 14

Fill in the blank: _______ requirements can include performance, security, and usability.

Answer 14

Non-functional

Question 15

What is a requirement traceability matrix?

Answer 15

A tool used to track the relationship between requirements and other project artifacts.

Question 16

Multiple Choice: Which is a common challenge in gathering requirements? A) Lack of stakeholder involvement B) Clear communication C) Defined goals

Answer 16

A) Lack of stakeholder involvement

Question 17

What is the role of a business analyst in system analysis?

Answer 17

To facilitate communication between stakeholders and the development team.

Question 18

True or False: Requirements can change throughout the development process.

Answer 18

True

Question 19

What is the significance of prioritizing requirements?

Answer 19

To ensure that the most critical needs are addressed first.

Question 20

Fill in the blank: _______ analysis helps in understanding the feasibility of requirements.

Answer 20

Feasibility

Question 21

What is a prototype in the context of system requirements?

Answer 21

A preliminary version of a system used to visualize and test requirements.

Question 22

Multiple Choice: Which of the following is a benefit of prototyping? A) Reduces risk B) Increases cost C) Delays project

Answer 22

A) Reduces risk

Question 23

What are the components of a typical requirements document?

Answer 23

Introduction, scope, functional requirements, non-functional requirements, and appendices.

Question 24

True or False: All requirements must be measurable.

Answer 24

True

Question 25

What is the difference between high-level and detailed requirements?

Answer 25

High-level requirements provide an overview, while detailed requirements specify exact functionalities.

Question 26

Fill in the blank: _______ is the process of determining what the system should do.

Answer 26

Requirements elicitation

Question 27

What does the term 'stakeholder' refer to?

Answer 27

Any individual or group with an interest in the outcome of a project.

Question 28

Multiple Choice: Which of the following is an example of a non-functional requirement? A) User authentication B) Page load time C) Data storage

Answer 28

B) Page load time

Question 29

What is the purpose of a stakeholder interview?

Answer 29

To gather insights and expectations related to system requirements.

Question 30

True or False: Requirements should be ambiguous to allow flexibility.

Answer 30

False

Question 31

What is a user story?

Answer 31

A brief description of a feature from the perspective of the end user.

Question 32

Fill in the blank: _______ is a technique to identify and document the needs of users.

Answer 32

Requirements gathering

Question 33

What are acceptance criteria?

Answer 33

Conditions that must be met for a requirement to be considered fulfilled.

Question 34

Multiple Choice: Which of the following is a key principle of effective requirements gathering? A) Avoiding feedback B) Engaging stakeholders C) Ignoring user needs

Answer 34

B) Engaging stakeholders

Question 35

What is a functional specification?

Answer 35

A document that describes the functionalities of a system in detail.

Question 36

True or False: System requirements should only focus on current needs.

Answer 36

False

Question 37

What does 'scope creep' refer to?

Answer 37

The uncontrolled expansion of project scope without adjustments to time, cost, and resources.

Question 38

Fill in the blank: The _______ phase involves analyzing the gathered requirements for consistency and completeness.

Answer 38

analysis

Question 39

What is the benefit of using scenarios in requirements analysis?

Answer 39

They help to visualize user interactions and identify potential issues.

Question 40

Multiple Choice: Which of the following is a method for validating requirements? A) Review sessions B) Random sampling C) Ignoring feedback

Answer 40

A) Review sessions

Question 41

What is the role of a requirements analyst?

Answer 41

To collect, analyze, and manage requirements throughout the project lifecycle.

Question 42

True or False: Requirements should be documented only at the beginning of a project.

Answer 42

False

Question 43

What is a user acceptance test?

Answer 43

A test conducted to determine if the system meets the acceptance criteria defined in the requirements.

Question 44

Fill in the blank: _______ requirements are often subjective and relate to user satisfaction.

Answer 44

Quality

Question 45

What is the importance of clear requirements in system development?

Answer 45

They help prevent misunderstandings and ensure the system meets user needs.