SWR302 FPT Final / Software
Requirement
A key tool for software designer, developer and their test team is to carry out their respective
tasks is defined by:
Select one:
a. Technical documentation
b. Requirements documentation
c. Software design documentation
d. Users document -
B
A key tool for software designer, developer and their test team is to carry out their respective
tasks is defined by:
Select one:
a. Technical documentation
b. Requirements documentation
c. Software design documentation
d. Users document -
B
Why reuse requirements?
Select one or more:
a. Faster delivery, lower development costs, consistency both within and across applications,
higher team productivity, fewer defects, and reduced rework.
b. to estimate implementation effort if you have data available from implementing the same
requirements on a previous project.
c. save review time, accelerate the approval cycle, and speed up other project activities, such
as testing
d. improve functional consistency across related members of a product line or among a set of
business applications -
a, b, c, d
Why reuse requirements?
Select one or more:
a. Faster delivery, lower development costs, consistency both within and across applications,
higher team productivity, fewer defects, and reduced rework.
b. to estimate implementation effort if you have data available from implementing the same
requirements on a previous project.
c. save review time, accelerate the approval cycle, and speed up other project activities, such
as testing
d. improve functional consistency across related members of a product line or among a set of
business applications -
a, b, c, d
1|Page
,Why should we prioritize the requirements?
Select one or more:
a. To provide the highest value at the lowest cost.
b. To deal with competing demands for limited resources
c. Develop products through a series of fixed-schedule timeboxes for agile or other projects
d. Help the project deliver the maximum business value as quickly as possible within the
project constraints -
a, b, c, d
Why should we prioritize the requirements?
Select one or more:
a. To provide the highest value at the lowest cost.
b. To deal with competing demands for limited resources
c. Develop products through a series of fixed-schedule timeboxes for agile or other projects
d. Help the project deliver the maximum business value as quickly as possible within the
project constraints -
a, b, c, d
Performance is an external quality attribute which could be described:
Select one:
a. How easily the system can interconnect and exchange data with other systems or
components
b. How well the system protects against unauthorized access to the application and its data
c. How easy it is for people to learn, remember, and use the system
d. How easily the system can grow to handle more users, transactions, servers, or other
extensions
e. How quickly and predictably the system responds to user inputs or other events -
e
Performance is an external quality attribute which could be described:
Select one:
a. How easily the system can interconnect and exchange data with other systems or
components
b. How well the system protects against unauthorized access to the application and its data
c. How easy it is for people to learn, remember, and use the system
d. How easily the system can grow to handle more users, transactions, servers, or other
extensions
e. How quickly and predictably the system responds to user inputs or other events -
e
To depict the complex logic, which representation technique should be used?
Select one:
a. Data dictionary
b. Decision tree
c. Swimlane diagram
d. State-transition diagram
e. Data flow diagram -
2|Page
, b
To depict the complex logic, which representation technique should be used?
Select one:
a. Data dictionary
b. Decision tree
c. Swimlane diagram
d. State-transition diagram
e. Data flow diagram -
b
Which of the following is NOT the purpose of software verification and validation?
Select one:
a. To make sure that there are no programming errors in the software
b. To make sure that the users are correctly using the program
c. To make sure there are no errors when running the program
d. To make sure that all software requirements have been implemented -
c
Which of the following is NOT the purpose of software verification and validation?
Select one:
a. To make sure that there are no programming errors in the software
b. To make sure that the users are correctly using the program
c. To make sure there are no errors when running the program
d. To make sure that all software requirements have been implemented -
c
What happens during static testing?
Select one:
a. The programmers monitor the data entry screens as data is entered
b. The software is installed and tested for any logic errors
c. The code is examined for quality and efficiency
d. The users report missing functionality to the programmers -
c
What happens during static testing?
Select one:
a. The programmers monitor the data entry screens as data is entered
b. The software is installed and tested for any logic errors
c. The code is examined for quality and efficiency
d. The users report missing functionality to the programmers -
c
In the V model, the user requirements are detected by ___________
3|Page
, Select one:
a. System testing
b. Integration testing
c. Acceptance testing
d. Unit testing -
c
In the V model, the user requirements are detected by ___________
Select one:
a. System testing
b. Integration testing
c. Acceptance testing
d. Unit testing -
c
How about estimating project size and effort from requirements? Based on
Select one or more:
a. function points (Jones 1996b; IFPUG 2010)
b. the number, type, and complexity of user interface elements
c. the number of individually testable requirements (Wilson 1995)
d. story points (Cohn 2005; McConnell 2006) or use case points (Wiegers 2006)
e. estimated lines of code needed to implement specific requirements -
a , b, c, d, e
How about estimating project size and effort from requirements? Based on
Select one or more:
a. function points (Jones 1996b; IFPUG 2010)
b. the number, type, and complexity of user interface elements
c. the number of individually testable requirements (Wilson 1995)
d. story points (Cohn 2005; McConnell 2006) or use case points (Wiegers 2006)
e. estimated lines of code needed to implement specific requirements -
a , b, c, d, e
The MoSCoW prioritization scheme stand for four possible priority classifications for the
requirements in a set (IIBA 2009):
Select one:
a. May, Should, Could, Won't
b. May, Should, Can, Won't
c. Must, Should, Can, Will
d. Must, Should, Could, Won't -
d
The MoSCoW prioritization scheme stand for four possible priority classifications for the
requirements in a set (IIBA 2009):
Select one:
4|Page
Requirement
A key tool for software designer, developer and their test team is to carry out their respective
tasks is defined by:
Select one:
a. Technical documentation
b. Requirements documentation
c. Software design documentation
d. Users document -
B
A key tool for software designer, developer and their test team is to carry out their respective
tasks is defined by:
Select one:
a. Technical documentation
b. Requirements documentation
c. Software design documentation
d. Users document -
B
Why reuse requirements?
Select one or more:
a. Faster delivery, lower development costs, consistency both within and across applications,
higher team productivity, fewer defects, and reduced rework.
b. to estimate implementation effort if you have data available from implementing the same
requirements on a previous project.
c. save review time, accelerate the approval cycle, and speed up other project activities, such
as testing
d. improve functional consistency across related members of a product line or among a set of
business applications -
a, b, c, d
Why reuse requirements?
Select one or more:
a. Faster delivery, lower development costs, consistency both within and across applications,
higher team productivity, fewer defects, and reduced rework.
b. to estimate implementation effort if you have data available from implementing the same
requirements on a previous project.
c. save review time, accelerate the approval cycle, and speed up other project activities, such
as testing
d. improve functional consistency across related members of a product line or among a set of
business applications -
a, b, c, d
1|Page
,Why should we prioritize the requirements?
Select one or more:
a. To provide the highest value at the lowest cost.
b. To deal with competing demands for limited resources
c. Develop products through a series of fixed-schedule timeboxes for agile or other projects
d. Help the project deliver the maximum business value as quickly as possible within the
project constraints -
a, b, c, d
Why should we prioritize the requirements?
Select one or more:
a. To provide the highest value at the lowest cost.
b. To deal with competing demands for limited resources
c. Develop products through a series of fixed-schedule timeboxes for agile or other projects
d. Help the project deliver the maximum business value as quickly as possible within the
project constraints -
a, b, c, d
Performance is an external quality attribute which could be described:
Select one:
a. How easily the system can interconnect and exchange data with other systems or
components
b. How well the system protects against unauthorized access to the application and its data
c. How easy it is for people to learn, remember, and use the system
d. How easily the system can grow to handle more users, transactions, servers, or other
extensions
e. How quickly and predictably the system responds to user inputs or other events -
e
Performance is an external quality attribute which could be described:
Select one:
a. How easily the system can interconnect and exchange data with other systems or
components
b. How well the system protects against unauthorized access to the application and its data
c. How easy it is for people to learn, remember, and use the system
d. How easily the system can grow to handle more users, transactions, servers, or other
extensions
e. How quickly and predictably the system responds to user inputs or other events -
e
To depict the complex logic, which representation technique should be used?
Select one:
a. Data dictionary
b. Decision tree
c. Swimlane diagram
d. State-transition diagram
e. Data flow diagram -
2|Page
, b
To depict the complex logic, which representation technique should be used?
Select one:
a. Data dictionary
b. Decision tree
c. Swimlane diagram
d. State-transition diagram
e. Data flow diagram -
b
Which of the following is NOT the purpose of software verification and validation?
Select one:
a. To make sure that there are no programming errors in the software
b. To make sure that the users are correctly using the program
c. To make sure there are no errors when running the program
d. To make sure that all software requirements have been implemented -
c
Which of the following is NOT the purpose of software verification and validation?
Select one:
a. To make sure that there are no programming errors in the software
b. To make sure that the users are correctly using the program
c. To make sure there are no errors when running the program
d. To make sure that all software requirements have been implemented -
c
What happens during static testing?
Select one:
a. The programmers monitor the data entry screens as data is entered
b. The software is installed and tested for any logic errors
c. The code is examined for quality and efficiency
d. The users report missing functionality to the programmers -
c
What happens during static testing?
Select one:
a. The programmers monitor the data entry screens as data is entered
b. The software is installed and tested for any logic errors
c. The code is examined for quality and efficiency
d. The users report missing functionality to the programmers -
c
In the V model, the user requirements are detected by ___________
3|Page
, Select one:
a. System testing
b. Integration testing
c. Acceptance testing
d. Unit testing -
c
In the V model, the user requirements are detected by ___________
Select one:
a. System testing
b. Integration testing
c. Acceptance testing
d. Unit testing -
c
How about estimating project size and effort from requirements? Based on
Select one or more:
a. function points (Jones 1996b; IFPUG 2010)
b. the number, type, and complexity of user interface elements
c. the number of individually testable requirements (Wilson 1995)
d. story points (Cohn 2005; McConnell 2006) or use case points (Wiegers 2006)
e. estimated lines of code needed to implement specific requirements -
a , b, c, d, e
How about estimating project size and effort from requirements? Based on
Select one or more:
a. function points (Jones 1996b; IFPUG 2010)
b. the number, type, and complexity of user interface elements
c. the number of individually testable requirements (Wilson 1995)
d. story points (Cohn 2005; McConnell 2006) or use case points (Wiegers 2006)
e. estimated lines of code needed to implement specific requirements -
a , b, c, d, e
The MoSCoW prioritization scheme stand for four possible priority classifications for the
requirements in a set (IIBA 2009):
Select one:
a. May, Should, Could, Won't
b. May, Should, Can, Won't
c. Must, Should, Can, Will
d. Must, Should, Could, Won't -
d
The MoSCoW prioritization scheme stand for four possible priority classifications for the
requirements in a set (IIBA 2009):
Select one:
4|Page
