Professional Documents
Culture Documents
Chúc may mắn!: A. Business Rules
Chúc may mắn!: A. Business Rules
hấn Ctrl + F để
vào mục tìm kiếm, sau đó copy câu hỏi ở trên bài test về và paste vào ô tìm kiếm.
- Để lấy đáp án câu hỏi mới mà không có trong tài liệu này, các bạn LH 01236332429.
- Để đăng kí lấy tài liệu các phần khác trong chương trình Fresher của FPT các bạn liên hệ email:
canhbuomphieudutk111@gmail.com
- Để đăng kí Mock Project các bạn cũng liên hệ email trên.
- Tài liệu này chỉ để tham khảo, học phải hiểu mới có thể làm việc được sau khi ra trường.
Chúc may mắn!
1. Select the most corect answer given the below use-case diagram. A. There may be an error occurring when validating user.
2. Which of the following is not an objective for building a requirements model? B. define set of software requirements that can
be validated
3. Which of the following is not an objective for building a requirements model? C. develop an abbreviated solution for the
problem
4. Which of following item should you choose to reduce users' memory load when design user interface?
6. Which control will you use to design for following screen? A. List box
7. Which control will you use to design highlighted item of following screen? D. Static text
8. Which control can be used to put some related controls in a group? C. Group box
11. Which of following is not belonged to Product level of Requirement? C. Business Requirements
12. Which of following is non-functional Requirement? B. ATM system have a touch screen that user can operate on it
15. Which of following best describes Requirement Specification? B. Requirement Specification is a document that describes all
information about requirement including functional requirements, non-functional requirements, data requirements,
external requirements and even constraints.
21. When should we use Radio button on screen design? A. - The number of choices should be less than or equal to eight. -
There is only 1 selection accepted.
22. What is purpose of using use case diagram in requirement modeling? D. All of these
23. Which of following is not belonged to Product level of Requirement? C. Business Requirements
24. What is Nonfunctional requirement? A. A constraints the system must satisfy.
25. UML activity diagrams are useful in representing which analysis model elements? D. Scenario-based element
26. Select the most corect answer given the below use-case diagram? A. There may be an error occurring when validating user.
27.Interface design focuses on:? B. how information is provided and captured from users
28. In which document where the plan for implementing non-functional requirements is described? B. System Architecture
29. Which of the following is not an objective for building a requirements model? C. develop an abbreviated solution for the
problem
30. Which of following shows a good UI design?A. Controls are grouped and arranged from left to right or top to bottom.
33. Which statement is true about Funcitonal Requirement and Non-functional Requirement? C. Functional requirements define
what a system is supposed to do and non-functional requirements define how a system is supposed to be
34.What is purpose of using use case diagram in requirement modeling? D. All of these
Question 1 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Make sure that the requirements define the system that the customer really wants ?
A. Elicit & Analyze Requirements
B. Develop SRS
C. Manage Requirement Changes
D. Validate Requirements
Question 2 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ?
A. Elicit & Analyze Requirements
B. Manage Requirement Changes
C. Validate Requirements
D. Develop SRS
Question 3 of 20
5.0/ 5.0 Points
Requirements elicitation means
A. Gathering of requirements
B. Capturing of requirements
C. Understanding of requirements
D. All of the above
Question 4 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Detect and resolve conflicts between requirements ?
A. Validate Requirements
B. Manage Requirement Changes
C. Develop SRS
D. Elicit & Analyze Requirements
Question 5 of 20
5.0/ 5.0 Points
What is purpose of SRS Review check list ?
A.To describe the system
B.To make sure you understood completely the requirements.
C.To review the requirements by yourself
D.To ensure you comply with processes.
Question 6 of 20
5.0/ 5.0 Points
What type of documents address what users need to do their jobs?
A. ADD - Architecture Design Document
B. SRS – Software requirement specification
C. DDD - Detail Design Document
D. URD - User Requirement Definition
Question 7 of 20
5.0/ 5.0 Points
Requirements models depict software in which three domains?
A. architecture, interface, component
B. cost, risk, schedule
C. information, function, behavior
D. None of the above
Question 8 of 20
5.0/ 5.0 Points
Which of the following are valid reasons for collecting customer feedback concerning delivered software?
A. Allows developers to make changes to the delivered increment
B. Delivery schedule can be revised to reflect changes
C. Developers can identify changes to incorporate into next increment
D. All of the above
Question 9 of 20
5.0/ 5.0 Points
Requirements review process is carried out to
A. Spend time in requirements gathering
B. Improve the quality of SRS
C. Document the requirements
D. None of the above
Question 10 of 20
5.0/ 5.0 Points
To check whether we have developed the product according to the customer requirements or not. It is a Dynamic process.
A. Verification
B. Quality Assurance
C. Quality Control
D. Validation
Question 11 of 20
5.0/ 5.0 Points
Six important characteristics of good SRS are
A. Correct, Ambiguous, Complete,
Consistent, Verifiable, Traceable.
B. Correct, Unambiguous, Complete,
Consistent, Verifiable, Traceable.
C. Correct, Unambiguous, Complete,
Consistent, Verifiable, Usability.
D. Correct, Ambiguous, Complete,
Consistent, Maintainability, Traceable.
Question 12 of 20
5.0/ 5.0 Points
Which of the following order stage is compatible with requirement process?
A. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Traceability ->
Manage Requirement Status -> Manage Requirement Changes.
B. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Requirement Changes ->
Manage Traceability ->
Manage Requirement Status.
C. Elicit & Analyze Requirements -> Develop SRS ->
Manage Traceability ->
Manage Requirement Status -> Manage Requirement Changes ->
Validate Requirements.
D. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Requirement Status ->
Manage Traceability ->
Manage Requirement Changes.
Question 13 of 20
5.0/ 5.0 Points
One reason to involve everyone on the software team in the planning activity is to
A. get all team members to "sign up" to the plan
B. control feature creep
C. understand the problem scope
D. adjust the granularity of the plan
Question 14 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it uses an executable model of the system to check
requirements?
A. Test-case generation
B. Prototyping
C. Model Validation
D. Requirements Review
Question 15 of 20
5.0/ 5.0 Points
Which of the following role uses requirement documents to:
- plan a bid for the system and to plan the system development process ?
A. System test engineers
B. System engineers
C. System customer
D. Manager
Question 16 of 20
5.0/ 5.0 Points
What type of documents used to track the status, relationship and change of requirements during the whole project?
A. Requirement Management Sheet
B. SRS – Software requirement specification
C. URD - User Requirement Definition
D. DDD - Detail Design Document
Question 17 of 20
5.0/ 5.0 Points
Verification is to check
A. the methodology of software development
B. whether we are building the product right
C. ensure you comply with processes.
D. whether we are building the right product
Question 18 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it develops tests for requirements to check testability?
A. Prototyping
B. Test-case generation
C. Model Validation
D. Requirements Review
Question 19 of 20
5.0/ 5.0 Points
Three things that make requirements elicitation difficult are problems of
A.volatility
B.understanding
C.scope
D.budgeting
Question 20 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be TESTED?
A. Validity check
B. Realism check
C. Verifiability check
D. Completeness check
Question 1 of 20
5.0/ 5.0 Points
The work products produced during requirement elicitation will vary depending on the
A. size of the product being built
B. software process being used
C. size of the budget
D. stakeholders needs
Question 2 of 20
5.0/ 5.0 Points
Which of the following is not an objective for building a requirements model?
A. define set of software requirements that can be validated
B. describe customer requirements
C. establish basis for software design
D. develop an abbreviated solution for the problem
Question 3 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ?
A. Elicit & Analyze Requirements
B. Manage Requirement Changes
C. Validate Requirements
D. Develop SRS
Question 4 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Detect and resolve conflicts between requirements ?
A. Elicit & Analyze Requirements
B. Manage Requirement Changes
C. Develop SRS
D. Validate Requirements
Question 5 of 20
5.0/ 5.0 Points
The result of the requirements engineering task is an analysis model that defines which of the following problem domain(s)?
A. information
B. functional
C. behavioral
D. all of the above
Question 6 of 20
5.0/ 5.0 Points
How to requirement clarifying?
A.Clarify unclear item(s) using Q&A
B.Self study related materials.
C.Discuss with other members to clarify or confirm your understanding.
D.Using SRS review checklist
Question 7 of 20
5.0/ 5.0 Points
A Non-Functional Software testing done to check if the user interface is easy to use and understand
A. Block Box Testing
B. Security Testing
C. Usability Testing
D. Unit testing
Question 8 of 20
5.0/ 5.0 Points
Prototyping allows the users to clarify their information requirements as they use the prototype.
A. Yes
B. No
Question 9 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Develop use cases, system requirement ?
A. Validate Requirements
B. Manage Requirement Changes
C. Elicit & Analyze Requirements
Question 10 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that it should has only one interpretation (to both creator & user)?
A. Unambiguous
B. Traceable
C. Correct
D. Verifiable
Question 11 of 20
5.0/ 5.0 Points
Which of the following role uses requirement documents to:
- develop validation tests for the system ?
A. Manager
B. System customer
C. System test engineers
D. System engineers
Question 12 of 20
5.0/ 5.0 Points
Which of the following order stage is compatible with requirement process?
A. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Traceability ->
Manage Requirement Status -> Manage Requirement Changes.
B. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Requirement Changes ->
Manage Traceability ->
Manage Requirement Status.
C. Elicit & Analyze Requirements -> Develop SRS ->
Manage Traceability ->
Manage Requirement Status -> Manage Requirement Changes ->
Validate Requirements.
D. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Requirement Status ->
Manage Traceability ->
Manage Requirement Changes.
Question 13 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that it is good reference for future dev/enhance documents ?
A. Complete
B. Unambiguous
C. Traceable
D. Correct
Question 14 of 20
5.0/ 5.0 Points
It includes a set of ________ that describe all the interactions the users will have with the software.
A. Ivar Jacobson
B. Unified Modeling Language
C. Use case
D. IBM Rational Unified Process
Question 15 of 20
5.0/ 5.0 Points
What is purpose of SRS Review check list ?
A.To review the requirements by yourself
B.To describe the system
C.To make sure you understood completely the requirements.
D.To ensure you comply with processes.
Question 16 of 20
5.0/ 5.0 Points
To validate requirement, what type of the following checking action that
answers the question "Is there any requirement CONFLICT?"
A. Consistency check
B. Realism check
C. Verifiability check
Question 17 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be IMPLEMENTED with given available budget and technology?
A. Completeness check
B. Validity check
C. Consistency check
D. Realism check
Question 18 of 20
5.0/ 5.0 Points
Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop, what is considered a
typical task in this phase ?
A.You ask the clients what functionality should the website provide to its customers
B.Technical Information like hardware used would be gathered
C.You ask the clients how the web interface should look like in style and colors
D.Study whether the client requirements are possible to implement
Question 19 of 20
5.0/ 5.0 Points
What type of documents used to track the status, relationship and change of requirements during the whole project?
A. URD - User Requirement Definition
B. Requirement Management Sheet
C. DDD - Detail Design Document
D. SRS – Software requirement specification
Question 20 of 20
5.0/ 5.0 Points
Six important characteristics of good SRS are
A. Correct, Unambiguous, Complete,
Consistent, Verifiable, Traceable.
B. Correct, Ambiguous, Complete,
Consistent, Verifiable, Traceable.
C. Correct, Unambiguous, Complete,
Consistent, Verifiable, Usability.
D. Correct, Ambiguous, Complete,
Consistent, Maintainability, Traceable.
What is purpose of using use case diagram in requirement modeling?------ D. All of these
Select the most corect answer given the below use-case dia========
gram-
-------------------------C . Requirement Specification is a document that describes all information about requirement including functional
requirements, non-functional requirements, data requirements, external requirements and even constraints.
------------------------ C. Functional requirements define what a system is supposed to do and non-functional requirements define how a system
is supposed to be
Which diagram is used in Requirement modeling?
--------------------- D. Generalization
---------------------- C. - The number of choices should be less than or equal to eight.
- There is only 1 selection accepted.
In which document where the plan for implementing non-functional requirements is described?
UML activity diagrams are useful in representing which analysis model elements?
------------------------------------- A. Controls are grouped and arranged from left to right or top to bottom.
----------------------------------------- B. Checkbox
Which of following item should you choose to reduce users' memory load when design user interface?
Question 2 of 20
5.0/ 5.0 Points
What is Nonfunctional requirement?
A. A constraints the system must satisfy.
B. A service the system has to perform.
C. A requirement that is no need to be implemented.
D. All of these
Question 3 of 20
5.0/ 5.0 Points
In which document where the plan for implementing non-functional requirements is described?
A. System Design
B. System Architecture
C. Detail Design
D. Requirement specification
Question 4 of 20
5.0/ 5.0 Points
Which statement is true about Funcitonal Requirement and Non-functional Requirement?
A. A functional requirement is a requirement that specifies criteria that can be used to judge the operation of a
system, rather than specific behaviors
B. Functional requirements are often called qualities of a system
C. Functional requirements define what a system is supposed to do and non-functional requirements define how a
system is supposed to be
D. All of these
Question 5 of 20
5.0/ 5.0 Points
What is purpose of using use case diagram in requirement modeling?
A. To capture requirement
B. To show who do something in system
C. To describe the series of steps that take place during the interaction and include different ways that this
interaction could play out
D. All of these
Question 6 of 20
5.0/ 5.0 Points
Which of following doesn't described Requirement Level
A. Product level
B. User level
C. Business level
D. Software level
Question 7 of 20
5.0/ 5.0 Points
Which of following is not belonged to User level of Requirement?
A. Quality Attributes
B. User Requirements
C. Business Requirements
D. Business Rules
Question 8 of 20
5.0/ 5.0 Points
Which of these is not an element of a requirements model?
A. Behavioral elements
B. Scenario-based elements
C. Data elements
D. Class-based elements
Question 9 of 20
5.0/ 5.0 Points
Which item below decides Nonfunctional requirement?
A. Business Requirements
B. User Requirements
C. Quality Attributes
D. Business Rules
Question 10 of 20
5.0/ 5.0 Points
Which of following best describes Requirement Specification?
A. Requirement specification is a document that software engineer writes all input request that need to be
implemented.
B. Requirement specification is of a document that user specify all information about their requirement.
C. Requirement Specification is a document that describes all information about requirement including functional
requirements, non-functional requirements, data requirements, external requirements and even constraints.
D. Requirement Specification is a collection of all requirement that needed to be implemented.
Question 11 of 20
5.0/ 5.0 Points
UML activity diagrams are useful in representing which analysis model elements?
A. Class-based elements
B. Scenario-based elements
C. Flow-based elements
D. Behavioral elements
Question 12 of 20
5.0/ 5.0 Points
Select the most corect answer given the below use-case diagram
Question 13 of 20
0.0/ 5.0 Points
Which diagram is used in Requirement modeling?
A. Use case diagram
B. Data Flow Diagram
C. Sequence diagram
D. All of these
Question 14 of 20
5.0/ 5.0 Points
Which of following contributes to Functional Requirements?
A. User Requirements
B. Business Rules
C. Quality Attributes
D. All of these
Question 15 of 20
5.0/ 5.0 Points
When should we use Radio button on screen design?
A. - The number of choices should be less than or equal to eight.
- There are multiple selections can be selected.
B. - The number of choices should be less than or equal to ten.
- There are multiple selections can be selected.
C. - The number of choices should be less than or equal to eight.
- There is only 1 selection accepted.
Question 16 of 20
5.0/ 5.0 Points
Which of following item should you choose to reduce users' memory load when design user interface?
A. Make the user interface transparent
B. Allow users to use either the keyboard or mouse
C. Provide defaults, undo, and redo
D. Allow users to customize the interface
Question 17 of 20
5.0/ 5.0 Points
Which of following shows a good UI design?
A. Controls are grouped and arranged from left to right or top to bottom.
B. Controls are grouped and arranged from right to left or bottom to top
C. Both of the answers
D. None of the answer
Question 18 of 20
5.0/ 5.0 Points
Which control will you use to design for following screen?
A. Tab
B. List box
C. Group box
Question 19 of 20
5.0/ 5.0 Points
Which of following shows a bad UI design?
A. The radio buttons and check boxes are not grouped.
B. Push button are distributed horizontally.
C. Combo box controls more than 10 items
D. All of these
Question 20 of 20
5.0/ 5.0 Points
How to make the user interface consistent?
A. Maintain consistency within and across products (experience)
B. Keep interaction results the same (expectations)
C. Sustain the context of users’ tasks (continuity)
D. All of these
Part 1 of 1 - 95.0/ 100.0 Points
Question 1 of 20
5.0/ 5.0 Points
Which of the following is not an objective for building a requirements model?
A. describe customer requirements
B. develop an abbreviated solution for the problem
C. establish basis for software design
D. define set of software requirements that can be validated
Question 2 of 20
5.0/ 5.0 Points
Which of the following role uses requirement documents to:
- check that they meet their needs ?
A. System maintenance engineers
B. System engineers
C. System customer
D. System test engineers
Question 3 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that it should reviewable & testable in finite cost-effective process ?
A. Verifiable
B. Unambiguous
C. Correct
D. Traceable
Question 4 of 20
5.0/ 5.0 Points
What type of documents address what users need to do their jobs?
A. ADD - Architecture Design Document
B. DDD - Detail Design Document
C. SRS – Software requirement specification
D. URD - User Requirement Definition
Question 5 of 20
5.0/ 5.0 Points
Which of the following is not one of the context-free questions that would be used during project inception?
A. Who will use the solution?
B. What will be the economic benefit from a good solution?
C. Who is behind the request for work?
D. Who will pay for the work?
Question 6 of 20
5.0/ 5.0 Points
Outcome of requirements specification phase is
A. Design Document
B. Software requirements specification
C. Test Document
D. None of the above
Question 7 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ?
A. Validate Requirements
B. Develop SRS
C. Elicit & Analyze Requirements
D. Manage Requirement Changes
Question 8 of 20
5.0/ 5.0 Points
It includes a set of ________ that describe all the interactions the users will have with the software.
A. Unified Modeling Language
B. Ivar Jacobson
C. Use case
D. IBM Rational Unified Process
Question 9 of 20
5.0/ 5.0 Points
Six important characteristics of good SRS are
A. Correct, Ambiguous, Complete,
Consistent, Verifiable, Traceable.
B. Correct, Unambiguous, Complete,
Consistent, Verifiable, Usability.
C. Correct, Unambiguous, Complete,
Consistent, Verifiable, Traceable.
D. Correct, Ambiguous, Complete,
Consistent, Maintainability, Traceable.
Question 10 of 20
5.0/ 5.0 Points
Which of the following order stage is compatible with requirement change process?
A. Change analysis and costing ->
Problem analysis and change specification ->
Change implementation.
B. Problem analysis and change specification ->
Change implementation ->
Change analysis and costing.
C. Change implementation ->
Problem analysis and change specification ->
Change analysis and costing.
D. Problem analysis and change specification ->
Change analysis and costing ->
Change implementation.
Question 11 of 20
5.0/ 5.0 Points
Which of the following role uses requirement documents to:
- develop validation tests for the system ?
A. System engineers
B. System test engineers
C. System customer
D. Manager
Question 12 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
-Are all functions required by customer INCLUDED?
A. Consistency check
B. Verifiability check
C. Completeness check
D. Realism check
Question 13 of 20
5.0/ 5.0 Points
Product features are related to:
A. Functional requirements
B. Non functional requirements
C. Interface requirement
D. None of the above
Question 14 of 20
5.0/ 5.0 Points
Requirements models depict software in which three domains?
A. architecture, interface, component
B. cost, risk, schedule
C. information, function, behavior
D. None of the above
Question 15 of 20
5.0/ 5.0 Points
How to requirement clarifying?
A.Using SRS review checklist
B.Clarify unclear item(s) using Q&A
C.Self study related materials.
D.Discuss with other members to clarify or confirm your understanding.
Question 16 of 20
5.0/ 5.0 Points
Which of the following are valid reasons for collecting customer feedback concerning delivered software?
A. Allows developers to make changes to the delivered increment
B. Delivery schedule can be revised to reflect changes
C. Developers can identify changes to incorporate into next increment
D. All of the above
Question 17 of 20
5.0/ 5.0 Points
Which of the following should be considered as candidate objects in a problem space?
A. events
B. people
C. structures
D. all of the above
Question 18 of 20
5.0/ 5.0 Points
Non-functional requirements are requirements which impose constraints on the design or implementation (such as
________ requirements, quality standards, or design constraints).
A. Requirements analysis
B. Performance engineering
C. Functional specification
D. Systems Development Life Cycle
Question 19 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be TESTED?
A. Validity check
B. Realism check
C. Verifiability check
D. Completeness check
Question 20 of 20
0.0/ 5.0 Points
Validation is to check
A. whether we are building the product right
B. the methodology of software development
C. whether we are building the right product
D. ensure you comply with processes.
Part 1 of 1 - 95.0/ 100.0 Points
Question 1 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be IMPLEMENTED with given available budget and technology?
A. Realism check
B. Consistency check
C. Validity check
D. Completeness check
Question 2 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Does the system provide RIGHT functionalities as customer’s NEED?
A. Realism check
B. Validity check
C. Consistency check
D. Completeness check
Question 3 of 20
5.0/ 5.0 Points
Which of the following are valid reasons for collecting customer feedback concerning delivered software?
A. Allows developers to make changes to the delivered increment
B. Delivery schedule can be revised to reflect changes
C. Developers can identify changes to incorporate into next increment
D. All of the above
Question 4 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ?
A. Develop SRS
B. Elicit & Analyze Requirements
C. Manage Requirement Changes
D. Validate Requirements
Question 5 of 20
5.0/ 5.0 Points
SRS stands for ?
A. Software Requirement Specification
B. Software Requirement Solution
C. System Requirement Solution
D. None of the above
Question 6 of 20
5.0/ 5.0 Points
Three things that make requirements elicitation difficult are problems of
A.scope
B.volatility
C.understanding
D.budgeting
Question 7 of 20
5.0/ 5.0 Points
Which of the following order stage is compatible with requirement change process?
A. Change analysis and costing ->
Problem analysis and change specification ->
Change implementation.
B. Change implementation ->
Problem analysis and change specification ->
Change analysis and costing.
C. Problem analysis and change specification ->
Change implementation ->
Change analysis and costing.
D. Problem analysis and change specification ->
Change analysis and costing ->
Change implementation.
Question 8 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it uses an executable model of the system to check
requirements?
A. Requirements Review
B. Test-case generation
C. Model Validation
D. Prototyping
Question 9 of 20
5.0/ 5.0 Points
What is purpose of SRS Review check list ?
A.To ensure you comply with processes.
B.To review the requirements by yourself
C.To describe the system
D.To make sure you understood completely the requirements.
Question 10 of 20
0.0/ 5.0 Points
Which of the following role uses requirement documents to:
- check that they meet their needs ?
A. System customer
B. System engineers
C. System maintenance engineers
D. System test engineers
Question 11 of 20
5.0/ 5.0 Points
SRS document is for
A. “What”of a system?
B. Costing and scheduling of a system
C. How to design the system?
D. System’s requirement.
Question 12 of 20
5.0/ 5.0 Points
Who we must work with to elicit:
- the services that the system should provide.
- the constraints that the system should satisfy.
A. Software Programmer
B. Software tester
C. Software Project Manager
D. Customers
Question 13 of 20
5.0/ 5.0 Points
In collaborative requirements gathering the facilitator
A. controls the meeting
B. must be an outsider
C. arranges the meeting place
D. can not be a customer
Question 14 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Develop use cases, system requirement ?
A. Elicit & Analyze Requirements
B. Manage Requirement Changes
C. Validate Requirements
Question 15 of 20
5.0/ 5.0 Points
During program development, software requirements specify
A. how to divide the task into subtasks
B. how to test the program when it is done
C. what the task is that the program must perform
D. how the program will accomplish the task
Question 16 of 20
5.0/ 5.0 Points
The work products produced during requirement elicitation will vary depending on the
A. stakeholders needs
B. software process being used
C. size of the budget
D. size of the product being built
Question 17 of 20
5.0/ 5.0 Points
Which of the following is not an objective for building a requirements model?
A. describe customer requirements
B. define set of software requirements that can be validated
C. develop an abbreviated solution for the problem
D. establish basis for software design
Question 18 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it develops tests for requirements to check testability?
A. Model Validation
B. Test-case generation
C. Prototyping
D. Requirements Review
Question 19 of 20
5.0/ 5.0 Points
One reason to involve everyone on the software team in the planning activity is to
A. control feature creep
B. adjust the granularity of the plan
C. get all team members to "sign up" to the plan
D. understand the problem scope
Question 20 of 20
5.0/ 5.0 Points
Outcome of requirements specification phase is
A. Design Document
B. Software requirements specification
C. Test Document
D. None of the above
1 Requirements models depict software in which three domains? information, function, behavior
2 SRS stands for ? Software Requirement Specification
3 The work products produced during requirement elicitation will vary depending on the size of the
product being built
4 Outcome of requirements specification phase is Software requirements specification
5 Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop,
what is considered a typical task in this phase ? You ask the clients what functionality should the website
provide to its customers You ask the clients how the web interface should look like in style and colors
6 To validate requirement, what type of checking answers the question of -Are all functions required by
customer INCLUDED? Completeness check
7 Three things that make requirements elicitation difficult are problems of scope .volatility .understanding
8 A Non-Functional Software testing done to check if the user interface is easy to use and Understand
Usability Testing
9 During program development, software requirements specify what the task is that the program must
perform
answers the question "Is there any requirement CONFLICT?" Consistency check
13 One reason to involve everyone on the software team in the planning activity is to get all team
members to "sign up" to the plan
14 Software requirement should not be It includes a set of ________ that describe all the interactions the
users will have with the software. Use case
15 The approach/document used to make sure all the requirements are covered when writing test cases
Traceablity Matrix
16 To validate requirement, what type of techniques describes that it uses an executable model of the
system to check requirements? Prototyping
17 The result of the requirements engineering task is an analysis model that defines which of the following
problem domain(s)? all of the above
18 Six important characteristics of good SRS are Correct, Unambiguous, Complete, Consistent, Verifiable,
Traceable
19 Non-functional requirements are requirements which impose constraints on the design or
implementation Performance engineering
20 Verification is to check whether we are building the product right
21 To check whether we are developing the right product according to the customer requirements are
not. It is a static process Verification
22 To validate requirement, what type of checking answers the question of - Can requirement be TESTED?
Verifiability check
23 Prototyping allows the users to clarify their information requirements as they use the Yes
24 To validate requirement, what type of checking answers the question of - Can requirement be
IMPLEMENTED with given available budget and technology? Realism check
25 Requirements review process is carried out to Improve the quality of SRS
26 SRS document is for System’s requirement
29One reason to involve everyone on the software team in the planning activity is to get all team members
to "sign up" to the plan
1. Requirements models depict software in which three domains? information, function, behavior
2. SRS stands for ? Software Requirement Specification
3. The work products produced during requirement elicitation will vary depending on the size of the
product being built
4. Outcome of requirements specification phase is Software requirements specification
5. Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop,
what is considered a typical task in this phase ? You ask the clients what functionality should the
website provide to its customers You ask the clients how the web interface should look like in style
and colors
6. To validate requirement, what type of checking answers the question of -Are all functions required by
customer INCLUDED? Completeness check
7. Three things that make requirements elicitation difficult are problems of scope .volatility .understanding
8. A Non-Functional Software testing done to check if the user interface is easy to use and Understand
Usability Testing
9. During program development, software requirements specify what the task is that the program must
perform
12.To validate requirement, what type of the following checking action that
answers the question "Is there any requirement CONFLICT?" Consistency check
24.To validate requirement, what type of checking answers the question of - Can requirement be TESTED?
Verifiability check
25.Prototyping allows the users to clarify their information requirements as they use the Yes
26.To validate requirement, what type of checking answers the question of - Can requirement be
IMPLEMENTED with given available budget and technology? Realism check
Question 1 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Detect and resolve conflicts between requirements ?
A. Manage Requirement Changes
B. Elicit & Analyze Requirements
C. Validate Requirements
D. Develop SRS
Question 2 of 20
5.0/ 5.0 Points
Non-functional requirements are requirements which impose constraints on the design or implementation (such as
________ requirements, quality standards, or design constraints).
A. Functional specification
B. Performance engineering
C. Systems Development Life Cycle
D. Requirements analysis
Question 3 of 20
5.0/ 5.0 Points
Requirements models depict software in which three domains?
A. architecture, interface, component
B. cost, risk, schedule
C. information, function, behavior
D. None of the above
Question 4 of 20
5.0/ 5.0 Points
To check whether we are developing the right product according to the customer requirements are not. It is a static process
A. Validation
B. Quality Assurance
C. Quality Control
D. Verification
Question 5 of 20
5.0/ 5.0 Points
What type of documents includes:
- A set of software requirements as complete, consistent, and correct as possible, from the developer's point of view ?
A. SRS – Software requirement specification
B. ADD - Architecture Design Document
C. URD - User Requirement Definition
D. DDD - Detail Design Document
Question 6 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Develop use cases, system requirement ?
A. Elicit & Analyze Requirements
B. Validate Requirements
C. Manage Requirement Changes
Question 7 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be TESTED?
A. Completeness check
B. Verifiability check
C. Realism check
D. Validity check
Question 8 of 20
5.0/ 5.0 Points
Which of the following is not one of the context-free questions that would be used during project inception?
A. What will be the economic benefit from a good solution?
B. Who will use the solution?
C. Who will pay for the work?
D. Who is behind the request for work?
Question 9 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that it is good reference for future dev/enhance documents ?
A. Complete
B. Traceable
C. Unambiguous
D. Correct
Question 10 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
-Are all functions required by customer INCLUDED?
A. Realism check
B. Verifiability check
C. Consistency check
D. Completeness check
Question 11 of 20
5.0/ 5.0 Points
Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop, what is considered
a typical task in this phase ?
A.You ask the clients how the web interface should look like in style and colors
B.Study whether the client requirements are possible to implement
C.You ask the clients what functionality should the website provide to its customers
D.Technical Information like hardware used would be gathered
Question 12 of 20
5.0/ 5.0 Points
Which of the following are valid reasons for collecting customer feedback concerning delivered software?
A. Allows developers to make changes to the delivered increment
B. Delivery schedule can be revised to reflect changes
C. Developers can identify changes to incorporate into next increment
D. All of the above
Question 13 of 20
5.0/ 5.0 Points
Prototyping allows the users to clarify their information requirements as they use the prototype.
A. No
B. Yes
Question 14 of 20
5.0/ 5.0 Points
Six important characteristics of good SRS are
A. Correct, Unambiguous, Complete,
Consistent, Verifiable, Traceable.
B. Correct, Ambiguous, Complete,
Consistent, Maintainability, Traceable.
C. Correct, Unambiguous, Complete,
Consistent, Verifiable, Usability.
D. Correct, Ambiguous, Complete,
Consistent, Verifiable, Traceable.
Question 15 of 20
5.0/ 5.0 Points
Requirements review process is carried out to
A. Spend time in requirements gathering
B. Improve the quality of SRS
C. Document the requirements
D. None of the above
Question 16 of 20
5.0/ 5.0 Points
Which is not a characteristic of a good SRS?
A. Correct
B. Complete
C. Consistent
D. Brief
Question 17 of 20
5.0/ 5.0 Points
One reason to involve everyone on the software team in the planning activity is to
A. control feature creep
B. adjust the granularity of the plan
C. understand the problem scope
D. get all team members to "sign up" to the plan
Question 18 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Make sure that the requirements define the system that the customer really wants ?
A. Elicit & Analyze Requirements
B. Validate Requirements
C. Develop SRS
D. Manage Requirement Changes
Question 19 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be IMPLEMENTED with given available budget and technology?
A. Consistency check
B. Completeness check
C. Realism check
D. Validity check
Question 20 of 20
5.0/ 5.0 Points
A Non-Functional Software testing done to check if the user interface is easy to use and understand
A. Unit testing
B. Security Testing
C. Usability Testing
D. Block Box Testing
Question 1 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ?
A. Develop SRS
B. Elicit & Analyze Requirements
C. Manage Requirement Changes
D. Validate Requirements
Question 2 of 20
0.0/ 5.0 Points
Requirements models depict software in which three domains?
Question 3 of 20
5.0/ 5.0 Points
Which of the following are valid reasons for collecting customer feedback concerning delivered software?
Question 4 of 20
5.0/ 5.0 Points
Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop, what is considered a typical task in
this phase ?
Question 5 of 20
5.0/ 5.0 Points
Who we must work with to elicit:
- the services that the system should provide.
- the constraints that the system should satisfy.
A. Software tester
B. Software Programmer
C. Customers
D. Software Project Manager
Question 6 of 20
5.0/ 5.0 Points
What type of documents used to track the status, relationship and change of requirements during the whole project?
Question 7 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it uses an executable model of the system to check requirements?
A. Prototyping
B. Model Validation
C. Test-case generation
D. Requirements Review
Question 8 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Detect and resolve conflicts between requirements ?
Question 9 of 20
5.0/ 5.0 Points
Software requirement should not be
A. ambiguous
B. complete
C. consistent
D. functional
Question 10 of 20
5.0/ 5.0 Points
It includes a set of ________ that describe all the interactions the users will have with the software.
Question 11 of 20
5.0/ 5.0 Points
Product features are related to:
A. Functional requirements
B. Non functional requirements
C. Interface requirement
D. None of the above
Question 12 of 20
5.0/ 5.0 Points
Outcome of requirements specification phase is
A. Design Document
B. Software requirements specification
C. Test Document
D. None of the above
Question 13 of 20
5.0/ 5.0 Points
Which of the following is not an objective for building a requirements model?
Question 14 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it develops tests for requirements to check testability?
A. Requirements Review
B. Model Validation
C. Prototyping
D. Test-case generation
Question 15 of 20
5.0/ 5.0 Points
Which of the following order stage is compatible with requirement change process?
Question 16 of 20
0.0/ 5.0 Points
Requirements elicitation means
A. Gathering of requirements
B. Capturing of requirements
C. Understanding of requirements
D. All of the above
Question 17 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that it is good reference for future dev/enhance documents ?
A. Complete
B. Correct
C. Unambiguous
D. Traceable
Question 18 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Develop use cases, system requirement ?
A. Validate Requirements
B. Elicit & Analyze Requirements
C. Manage Requirement Changes
Question 19 of 20
0.0/ 5.0 Points
Which of the following role uses requirement documents to:
- help understand the system and the relationships between its part ?
A. System customer
B. System maintenance engineers
C. Manager
D. System test engineers
Question 20 of 20
5.0/ 5.0 Points
Verification is to check
Question 1 of 20
5.0/ 5.0 Points
What is purpose of using use case diagram in requirement modeling?
A. To capture requirement
B. To show who do something in system
C. To describe the series of steps that take place during the interaction and include different ways that this interaction
could play out
D. All of these
Question 2 of 20
5.0/ 5.0 Points
Select the most corect answer given the below use-case diagram
Question 3 of 20
5.0/ 5.0 Points
Which is relationship between User and Client actor?
A. Extension
B. Association
C. Specification
D. Generalization
Question 4 of 20
5.0/ 5.0 Points
UML activity diagrams are useful in representing which analysis model elements?
A. Scenario-based elements
B. Behavioral elements
C. Class-based elements
D. Flow-based elements
Question 5 of 20
5.0/ 5.0 Points
Which statement is true about Funcitonal Requirement and Non-functional Requirement?
A. A functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system,
rather than specific behaviors
B. Functional requirements are often called qualities of a system
C. Functional requirements define what a system is supposed to do and non-functional requirements define how a system
is supposed to be
D. All of these
Question 6 of 20
5.0/ 5.0 Points
Which of following contributes to Functional Requirements?
A. User Requirements
B. Business Rules
C. Quality Attributes
D. All of these
Question 7 of 20
5.0/ 5.0 Points
Which of following is not belonged to Product level of Requirement?
A. Functional Requirements
B. Data Requirements
C. External Interface Requirements
D. Business Requirements
Question 8 of 20
5.0/ 5.0 Points
Which of the following is not an objective for building a requirements model?
A. describe customer requirements
B. establish basic for software design
C. define set of software requirements that can be validated
D. develop an abbreviated solution for the problem
Question 9 of 20
5.0/ 5.0 Points
What is Nonfunctional requirement?
A. A constraints the system must satisfy.
B. A service the system has to perform.
C. A requirement that is no need to be implemented.
D. All of these
Question 10 of 20
5.0/ 5.0 Points
Which diagram is used in Requirement modeling?
A. Use case diagram
B. Data Flow Diagram
C. Sequence diagram
D. All of these
Question 11 of 20
5.0/ 5.0 Points
Which of following best describes Requirement Specification?
A. Requirement Specification is a document that describes all information about requirement including functional
requirements, non-functional requirements, data requirements, external requirements and even constraints.
B. Requirement specification is of a document that user specify all information about their requirement.
C. Requirement specification is a document that software engineer writes all input request that need to be implemented.
D. Requirement Specification is a collection of all requirement that needed to be implemented.
Question 12 of 20
5.0/ 5.0 Points
In which document where the plan for implementing non-functional requirements is described?
A. System Design
B. System Architecture
C. Detail Design
D. Requirement specification
Question 13 of 20
5.0/ 5.0 Points
Which of following is non-functional Requirement?
A. ATM system use common database.
B. ATM system must following rule of National Banking.
C. ATM system have a touch screen that user can operate on it
D. ATM system must have 3 functions including cash withdrawing, history viewing, cash transferring.
Question 14 of 20
5.0/ 5.0 Points
Which of following is not belonged to User level of Requirement?
A. User Requirements
B. Business Requirements
C. Business Rules
D. Quality Attributes
Question 15 of 20
5.0/ 5.0 Points
When should we use Radio button on screen design?
A. - The number of choices should be less than or equal to ten.
- There are multiple selections can be selected.
B. - The number of choices should be less than or equal to eight.
- There are multiple selections can be selected.
C. - The number of choices should be less than or equal to eight.
- There are multiple selections can be selected.
D. - The number of choices should be less than or equal to eight.
- There is only 1 selection accepted.
Question 16 of 20
5.0/ 5.0 Points
Which control can be used to provide multiple choices of selection?
A. Checkbox
B. Group box
C. Radio button
D. Combo box
Question 17 of 20
5.0/ 5.0 Points
Choose the answer that you think it's a good choice for layout RADIO button on a Dialog.
A. Radio buttons are grouped and arrayed horizontally
B. Radio buttons are grouped and arrayed vertically.
C. Radio buttons are arrayed vertically
D. Radio buttons are arrayed horizontally
Question 18 of 20
5.0/ 5.0 Points
How to make the user interface consistent?
A. Maintain consistency within and across products (experience)
B. Keep interaction results the same (expectations)
C. Sustain the context of users’ tasks (continuity)
D. All of these
Question 19 of 20
5.0/ 5.0 Points
Which control will you use to design for following screen?
A. Tab
B. List box
C. Group box
Question 20 of 20
5.0/ 5.0 Points
Which of following item should you choose to reduce users' memory load when design user interface?
A. Allow users to customize the interface
B. Make the user interface transparent
C. Allow users to use either the keyboard or mouse
D. Provide defaults, undo, and redo
1. Which of the following order stage is compatible with requirement change process? . Problem
analysis and change specification -> Change analysis and costing -> Change implementation.
2. Which of the following is not one of the context-free questions that would be used during project
inception? Who will pay for the work?
3. Requirements models depict software in which three domains? information, function, behavior
4. SRS stands for ? Software Requirement Specification
5. The work products produced during requirement elicitation will vary depending on the size of the
product being built
6. Outcome of requirements specification phase is Software requirements specification
7. Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop,
what is considered a typical task in this phase ? You ask the clients what functionality should the
website provide to its customers You ask the clients how the web interface should look like in
style and colors
8. To validate requirement, what type of checking answers the question of -Are all functions required by
customer INCLUDED? Completeness check
9. Which of the following stage is done to: Make sure that the requirements define the system that the
customer really wants Validate Requirements
10.Three things that make requirements elicitation difficult are problems of scope .volatility
.understanding
12.A Non-Functional Software testing done to check if the user interface is easy to use and Understand
Usability Testing
13.During program development, software requirements specify what the task is that the program must
perform
17.To validate requirement, what type of the following checking action that
answers the question "Is there any requirement CONFLICT?" Consistency check
38.Which of the following stage is done to: Develop use cases, system requirement ? Elicit & Analyze
Requirements
39.To validate requirement, what type of checking answers the question of - Can requirement be
TESTED? Verifiability check
40.Prototyping allows the users to clarify their information requirements as they use the Yes
42.To validate requirement, what type of checking answers the question of - Can requirement be
IMPLEMENTED with given available budget and technology? Realism check
1. What type of characteristics of good SRS describes that it is good reference for future dev/enhance
documents ? Traceable
2. One reason to involve everyone on the software team in the planning activity is to get all team members
to "sign up" to the plan
3. Requirements review process is carried out to Improve the quality of SRS
4. SRS document is for System’s requirement
5. Six important characteristics of good SRS are Correct, Unambiguous, Complete, Consistent,
Verifiable, Traceable.
6. Software requirement should not be ambiguous
7. Which of the following is not one of the context-free questions that would be used during project inception?
Who will pay for the work?
8. Which of the following are valid reasons for collecting customer feedback concerning delivered software?
All of the above
9. What type of characteristics of good SRS describes that it should has only one interpretation (to both creator
& user)? Unambiguous
10. A Non-Functional Software testing done to check if the user interface is easy to use and understand
Usability Testing
11. What type of documents includes:
- A set of software requirements as complete, consistent, and correct as possible, from the developer's point
of view ? SRS – Software requirement specification
12. Requirements elicitation means All of the above
13. It includes a set of ________ that describe all the interactions the users will have with the software. Use
case
14. The approach/document used to make sure all the requirements are covered when writing test cases
Traceablity Matrix
15. To validate requirement, what type of techniques describes that it uses an executable model of the system to
check requirements? Prototyping
16. During program development, software requirements specify what the task is that the program must
perform
17. To validate requirement, what type of checking answers the question of
-Are all functions required by customer INCLUDED? Completeness check
18. What type of characteristics of good SRS describes that no conflict between individual requirements ?
Consistent
19. Which of the following should be considered as candidate objects in a problem space? all of the above
20. The result of the requirements engineering task is an analysis model that defines which of the following
problem domain(s)? all of the above
21. Which of the following role uses requirement documents to:
- plan a bid for the system and to plan the system development process ? Manager
22. To validate requirement, what type of techniques describes that it develops tests for requirements to check
testability? Test-case generation
23. Non-functional requirements are requirements which impose constraints on the design or implementation
(such as ________ requirements, quality standards, or design constraints). Performance engineering
24. Verification is to check whether we are building the product right
25. SRS stands for ? Software Requirement Specification
26. What type of documents used to track the status, relationship and change of requirements during the whole
project? Requirement Management Sheet
27. Three things that make requirements elicitation difficult are problems of
A.volatility
C.scope
D.understanding
28. Which of the following order stage is compatible with requirement change process? Problem analysis
and change specification ->
Change analysis and costing ->
Change implementation.
29. In collaborative requirements gathering the facilitator controls the meeting
30. Which of the following role uses requirement documents to:
- check that they meet their needs ? System customer
31. Which of the following role uses requirement documents to:
- develop validation tests for the system ? System test engineers
32. Which of the following stage is done to:
- Develop use cases, system requirement ? Elicit & Analyze Requirements
33. Which of the following is not an objective for building a requirements model? develop an abbreviated
solution for the problem
34. Outcome of requirements specification phase is Software requirements specification
35. Product features are related to: Functional requirements
36. Who we must work with to elicit:
- the services that the system should provide.
- the constraints that the system should satisfy. Customers
37. Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop, what
is considered a typical task in this phase ?
You ask the clients how the web interface should look like in style and colors
You ask the clients what functionality should the website provide to its customers
38. Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ? Elicit & Analyze Requirements
Part 1 of 1 -
Question 1 of 20
5.0 Points
To check whether we have developed the product according to the customer requirements or not. It is a Dynamic process.
A. Quality Assurance
B. Validation
C. Verification
D. Quality Control
Reset Selection
Question 2 of 20
5.0 Points
Non-functional requirements are requirements which impose constraints on the design or implementation (such as
________ requirements, quality standards, or design constraints).
A. Systems Development Life Cycle
B. Performance engineering
C. Requirements analysis
D. Functional specification
Reset Selection
Question 3 of 20
5.0 Points
What type of documents used to track the status, relationship and change of requirements during the whole project?
A. SRS – Software requirement specification
B. Requirement Management Sheet
C. URD - User Requirement Definition
D. DDD - Detail Design Document
Reset Selection
Question 4 of 20
5.0 Points
Software requirement should not be
A. functional
B. ambiguous
C. complete
D. consistent
Reset Selection
Question 5 of 20
5.0 Points
Requirements elicitation means
A. Gathering of requirements
B. Capturing of requirements
C. Understanding of requirements
D. All of the above
Reset Selection
Question 6 of 20
5.0 Points
Requirements review process is carried out to
A. Spend time in requirements gathering
B. Improve the quality of SRS
C. Document the requirements
D. None of the above
Reset Selection
Question 7 of 20
5.0 Points
During program development, software requirements specify
A. how the program will accomplish the task
B. how to test the program when it is done
C. how to divide the task into subtasks
D. what the task is that the program must perform
Reset Selection
Question 8 of 20
5.0 Points
Which of the following order stage is compatible with requirement process?
A. Elicit & Analyze Requirements -> Develop SRS ->
Manage Traceability ->
Manage Requirement Status -> Manage Requirement Changes ->
Validate Requirements.
B. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Requirement Status ->
Manage Traceability ->
Manage Requirement Changes.
C. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Traceability ->
Manage Requirement Status -> Manage Requirement Changes.
D. Elicit & Analyze Requirements -> Develop SRS ->
Validate Requirements ->
Manage Requirement Changes ->
Manage Traceability ->
Manage Requirement Status.
Reset Selection
Question 9 of 20
5.0 Points
What is purpose of SRS Review check list ?
A.To ensure you comply with processes.
B.To make sure you understood completely the requirements.
C.To review the requirements by yourself
D.To describe the system
Question 10 of 20
5.0 Points
Validation is to check
A. whether we are building the right product
B. whether we are building the product right
C. ensure you comply with processes.
D. the methodology of software development
Reset Selection
Question 11 of 20
5.0 Points
Let say that you are in the requirements gathering/analysis phase for developing a web-based pet shop, what is considered
a typical task in this phase ?
A.You ask the clients what functionality should the website provide to its customers
B.You ask the clients how the web interface should look like in style and colors
C.Study whether the client requirements are possible to implement
D.Technical Information like hardware used would be gathered
Question 12 of 20
5.0 Points
To check whether we are developing the right product according to the customer requirements are not. It is a static process
A. Quality Assurance
B. Validation
C. Quality Control
D. Verification
Reset Selection
Question 13 of 20
5.0 Points
SRS document is for
A. System’s requirement.
B. Costing and scheduling of a system
C. “What”of a system?
D. How to design the system?
Reset Selection
Question 14 of 20
5.0 Points
Which one is not a step of requirement engineering?
A. Requirements design
B. Requirements elicitation
C. Requirements documentation
D. Requirements analysis
Reset Selection
Question 15 of 20
5.0 Points
Which is not a characteristic of a good SRS?
A. Complete
B. Brief
C. Correct
D. Consistent
Reset Selection
Question 16 of 20
5.0 Points
To validate requirement, what type of checking answers the question of
-Are all functions required by customer INCLUDED?
A. Completeness check
B. Consistency check
C. Realism check
D. Verifiability check
Reset Selection
Question 17 of 20
5.0 Points
Three things that make requirements elicitation difficult are problems of
A.budgeting
B.understanding
C.volatility
D.scope
Question 18 of 20
5.0 Points
What type of characteristics of good SRS describes that it should reviewable & testable in finite cost-effective process ?
A. Correct
B. Traceable
C. Unambiguous
D. Verifiable
Reset Selection
Question 19 of 20
5.0 Points
Which of the following role uses requirement documents to:
- develop validation tests for the system ?
A. System test engineers
B. System engineers
C. Manager
D. System customer
Reset Selection
Question 20 of 20
5.0 Points
How to requirement clarifying?
A.Using SRS review checklist
B.Clarify unclear item(s) using Q&A
C.Discuss with other members to clarify or confirm your understanding.
D.Self study related materials.
1: What is purpose of using use case diagram in requirement modeling?------ D. All of these
5: What type of characteristics of good SRS describes that it is good reference for future dev/enhance documents ?----
C. Traceable
6: What is purpose of SRS Review check list ?---- A.To review the requirements by yourself
9: What type of documents address what users need to do their jobs? URD - User Requirement Definition
10: What type of characteristics of good SRS describes that no conflict between individual requirements ? Consistent
12: What is purpose of SRS Review check list ?-- .To make sure you understood completely the requirements.
13: What type of characteristics of good SRS describes that it should reviewable & testable in finite cost-effective
process ?--- D. Verifiable
------------------------------------- A. Controls are grouped and arranged from left to right or top to bottom.
12 Which of following item should you choose to reduce users' memory load when design user interface?
--------------------------------------- C. Provide defaults, undo, and redo
13 Which of the following are valid reasons for collecting customer feedback concerning delivered software?
--------------------------- D. All of the above
15 Which of the following order stage is compatible with requirement change process?
------------ D. Problem analysis and change specification ->
Change analysis and costing ->
Change implementation.
19 Which of the following are valid reasons for collecting customer feedback concerning delivered software?
-------- D. All of the above
21 Which of the following is not one of the context-free questions that would be used during project inception?
--------------- Who will pay for the work?
23 Which of the following should be considered as candidate objects in a problem space? D. all of the above
---- C. Functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to
be
27 Which of following shows a good UI design? A. Controls are grouped and arranged from left to right or top to bottom.
29 Which of following is non-functional Requirement? A. ATM system must following rule of National Banking.
31 Which control can be used to put some related controls in a group? Group box
32 Which of the following stage is done to:
- Make sure that the requirements define the system that the customer really wants ?
D. Validate Requirements
33 Which of the following stage is done to:
- Detect and resolve conflicts between requirements ? D. Elicit & Analyze Requirements
34 Which of the following are valid reasons for collecting customer feedback concerning delivered software? D. All of the
above