SWR302 - Final - King
a-
Question 1 Which of the following statements belong to WHY dimension?
a. Identify, analyze, refine the system-to-be's objectives
b. None of the others
c. Assign responsibilities for objectives, services, constraints among system-to-be
components
d. Identify & define the system-to-be's functional services
D-
Arrange the given sequence to form a SRS Prototype outline as per IEEE SRS
Standard.
i. General description
ii. Introduction
iii. Index
iv. Appendices
v. Specific Requirements
Select one:
a. iii, i, ii,v, iv
b. iii, i, ii
c. iii, ii, i, v, iv
d. ii, i, v, iv, iii
a-
Giving an example of quality requirements: "Authorization of an ATM withdrawal
request shall take no more than 2.0 seconds". This is a__________
Select one:
a. performance requirement
b. interoperability requirement
c. reliability requirement
d. robustness requirement
b-
Which is the definition of functional requirement?
Select one:
a. A restriction that is imposed on the choices available to the developer for the design and
construction of a product
b. A description of a behavior that a system will exhibit under specific conditions
c. A top-level requirement for a product that contains multiple subsystems, which could be all
software or software and hardware
d. A description of a property or characteristic that a system must exhibit or a constraint that
it must respect
e. A goal or task that specific classes of users must be able to perform with a system, or a
desired product attribute
f. A policy, guideline, standard, or regulation that defines or constrains some aspect of the
business. Not a software requirement in itself, but the origin of several types of software
requirements
1|Page
,D-
Which of the following is not a diagram studied in Requirement Analysis ?
Select one:
a. State Transition Diagram
b. Use Cases
c. Entity Relationship Diagram
d. Activity Diagram
a-
Which of the following option is not tracked by configuration management tools?
Select one:
a. None of the mentioned
b. Storing versions of system components
c. Tracking of change proposals
d. Tracking the releases of system versions to customers
a-
How are the requirements validated?
Select one:
a. We inspect our requirements documents and models, with participants that include
customers, developers, and testers. We write tests against the requirements and use them to
validate the requirements and models.
b. The BA and some stakeholders hold informal reviews when they have time.
c. We pass the specified requirements around to people to get their feedback.
d. We think our requirements are pretty good when we first write them
B-
How well trained and how experienced are your business analysts?
a. The BAs have had several days of training and considerable experience in collaborating
with users.
b. We have professional business analysts or requirements engineers who are trained and
proficient in interviewing techniques, the facilitation of group sessions, technical writing, and
modeling. They understand both the application domain and the software development
process.
c. They are developers or former users who have little experience and no specific training in
software requirements engineering.
d. Developers, experienced users, or project managers who have had some previous exposure
to requirements engineering perform the BA role.
e-
Question 5
Quiz 1 Which of the followings belong to System requirement statements
Select one:
a. Descriptive statement about problem world phenomena (holds regardless of any software-
to-be)
b. Statements to be satisfied by the environment of the software-to-be
c. None of the others
d. Statement providing a precise meaning to system concepts or auxiliary terms
e. Prescriptive statement referring to environment phenomena (not necessarily shared)
2|Page
, C-
How many feasibility studies is conducted in Requirement Analysis ?
Select one:
a. Two
b. None of the mentioned
c. Three
d. Four
d-
How are the individual functional requirements labeled?
Select one:
a. We use a hierarchical numbering scheme, such as "3.1.2.4."
b. We write paragraphs of narrative text or short user stories; specific requirements are not
explicitly identified.
c. We use bulleted or numbered lists.
d. Each discrete requirement has a unique, meaningful label that is not disrupted when other
requirements are added, moved, or deleted.
C-
What approaches are used when working with stakeholders to identify the specific
software requirements?
a.
Management or marketing provides a product concept, and the developers write the
requirements. Customer stakeholders tell the development team if they've missed anything.
b.
We begin with a general understanding, write some code, show the software to some
users, and modify the code until they're happy.
c.
We hold structured requirements elicitation interviews or workshops with representatives
from the different user classes for the product. We employ use cases or user stories to
understand the users' goals, and we create analysis models to help
ensure we identify all the functional requirements. We flesh out the requirements
incrementally
and iteratively, giving the customers numerous opportunities to improve them.
d.
Marketing or customer representatives tell the development team what features and functions
the product should contain. Sometimes marketing tells the development team when the
product direction changes.
a-
Which of the following process is concerned with analyzing the costs and benefits
of
proposed changes?
Select one:
a. Change management
b. Version management
c. Release management
d. System building
3|Page
a-
Question 1 Which of the following statements belong to WHY dimension?
a. Identify, analyze, refine the system-to-be's objectives
b. None of the others
c. Assign responsibilities for objectives, services, constraints among system-to-be
components
d. Identify & define the system-to-be's functional services
D-
Arrange the given sequence to form a SRS Prototype outline as per IEEE SRS
Standard.
i. General description
ii. Introduction
iii. Index
iv. Appendices
v. Specific Requirements
Select one:
a. iii, i, ii,v, iv
b. iii, i, ii
c. iii, ii, i, v, iv
d. ii, i, v, iv, iii
a-
Giving an example of quality requirements: "Authorization of an ATM withdrawal
request shall take no more than 2.0 seconds". This is a__________
Select one:
a. performance requirement
b. interoperability requirement
c. reliability requirement
d. robustness requirement
b-
Which is the definition of functional requirement?
Select one:
a. A restriction that is imposed on the choices available to the developer for the design and
construction of a product
b. A description of a behavior that a system will exhibit under specific conditions
c. A top-level requirement for a product that contains multiple subsystems, which could be all
software or software and hardware
d. A description of a property or characteristic that a system must exhibit or a constraint that
it must respect
e. A goal or task that specific classes of users must be able to perform with a system, or a
desired product attribute
f. A policy, guideline, standard, or regulation that defines or constrains some aspect of the
business. Not a software requirement in itself, but the origin of several types of software
requirements
1|Page
,D-
Which of the following is not a diagram studied in Requirement Analysis ?
Select one:
a. State Transition Diagram
b. Use Cases
c. Entity Relationship Diagram
d. Activity Diagram
a-
Which of the following option is not tracked by configuration management tools?
Select one:
a. None of the mentioned
b. Storing versions of system components
c. Tracking of change proposals
d. Tracking the releases of system versions to customers
a-
How are the requirements validated?
Select one:
a. We inspect our requirements documents and models, with participants that include
customers, developers, and testers. We write tests against the requirements and use them to
validate the requirements and models.
b. The BA and some stakeholders hold informal reviews when they have time.
c. We pass the specified requirements around to people to get their feedback.
d. We think our requirements are pretty good when we first write them
B-
How well trained and how experienced are your business analysts?
a. The BAs have had several days of training and considerable experience in collaborating
with users.
b. We have professional business analysts or requirements engineers who are trained and
proficient in interviewing techniques, the facilitation of group sessions, technical writing, and
modeling. They understand both the application domain and the software development
process.
c. They are developers or former users who have little experience and no specific training in
software requirements engineering.
d. Developers, experienced users, or project managers who have had some previous exposure
to requirements engineering perform the BA role.
e-
Question 5
Quiz 1 Which of the followings belong to System requirement statements
Select one:
a. Descriptive statement about problem world phenomena (holds regardless of any software-
to-be)
b. Statements to be satisfied by the environment of the software-to-be
c. None of the others
d. Statement providing a precise meaning to system concepts or auxiliary terms
e. Prescriptive statement referring to environment phenomena (not necessarily shared)
2|Page
, C-
How many feasibility studies is conducted in Requirement Analysis ?
Select one:
a. Two
b. None of the mentioned
c. Three
d. Four
d-
How are the individual functional requirements labeled?
Select one:
a. We use a hierarchical numbering scheme, such as "3.1.2.4."
b. We write paragraphs of narrative text or short user stories; specific requirements are not
explicitly identified.
c. We use bulleted or numbered lists.
d. Each discrete requirement has a unique, meaningful label that is not disrupted when other
requirements are added, moved, or deleted.
C-
What approaches are used when working with stakeholders to identify the specific
software requirements?
a.
Management or marketing provides a product concept, and the developers write the
requirements. Customer stakeholders tell the development team if they've missed anything.
b.
We begin with a general understanding, write some code, show the software to some
users, and modify the code until they're happy.
c.
We hold structured requirements elicitation interviews or workshops with representatives
from the different user classes for the product. We employ use cases or user stories to
understand the users' goals, and we create analysis models to help
ensure we identify all the functional requirements. We flesh out the requirements
incrementally
and iteratively, giving the customers numerous opportunities to improve them.
d.
Marketing or customer representatives tell the development team what features and functions
the product should contain. Sometimes marketing tells the development team when the
product direction changes.
a-
Which of the following process is concerned with analyzing the costs and benefits
of
proposed changes?
Select one:
a. Change management
b. Version management
c. Release management
d. System building
3|Page
