A. Identifying Stakeholder
B. Listing out Requirements
C. Requirements Gathering
D. All of the mentioned
Explanation: Stakeholders are the one who will invest in and use the product, so its essential to chalk out stakeholders first.
A. Object Oriented Design (by Booch)
B. Use Cases (by Jacobson)
C. Fusion (by Coleman)
D. Object Modeling Technique (by Rumbaugh)
Explanation: Use Case captures who does what with the system, for what purpose, without dealing with system internals?
i. Consolidation
ii. Prioritization
iii. Requirements Gathering
iv. Evaluation
A. iii, i, ii, iv
B. iii, iv, ii, i
C. iii, ii, iv, i
D. ii, iii, iv, i
Explanation: Requirements gathering captures viewpoint from different users followed by evaluation of those view points.Now comes the task of checking the relative importance of the requirements and finally to consolidate or bind together the information collected.
A. Availability
B. Testability
C. Usability
D. Flexibility
Explanation: A developer needs to test his product before launching it into the market.
A. It is a degree to which software running on one platform can easily be converted to run on another platform
B. It cannot be enhanced by using languages, OS’ and tools that are universally available and standardized
C. The ability of the system to behave consistently in a user-acceptable manner when operating within the environment for which the system was intended
D. None of the mentioned
Explanation: Option c is termed as reliability and option e refers to efficiency.
A. Maintainability
B. Portability
C. Robustness
D. None of the mentioned
Explanation: All are non-functional requirements representing quality of the system. Functional requirements describe what the software has to do.
A. Functional
B. Non-Functional
C. Known Requirement
D. None of the mentioned
Explanation: Functional requirements describe what the software has to do.
A. True
B. False
Explanation: The behavior of functional requirements may be expressed as services, tasks or functions the system is required to perform.
A. Two
B. Three
C. Four
D. Five
Explanation: Software Quality Tree [Boehm 1976], Roman [IEEE Computer 1985], Process-Product-External considerations [Sommerville 1992], Mc Call’s NFR list and Dimensions of Quality–Components of FURPS+ are the five classification schemes for NFRs.
A. Usability, Reliability, Security, Flexibility
B. Availability, Reliability, Maintainability, Security
C. Availability, Reliability, Security, Safety
D. Security, Safety, Testability, Usability
Explanation: All the traits of option c sync with dependability.
advertisement