Requirement Engineering

A. Three
B. Four
C. Five
D. Six

Explanation: Retained information, Needed services, Multiple attributes, Common attributes, Common operations and Essential requirements are the six criterion mentioned by Coad and Yourdon.

i. Managers
ii. Entry level Personnel
iii. Users
iv. Middle level stakeholder
A. i, ii, iv, iii
B. i, ii, iii, iv
C. ii, iv, i, iii
D. All of the mentioned

Explanation: Users are your customers, they will be using your product, thus making them most important of all.

A. True
B. False

Explanation: ‘What’ refers to a system’s purpose, while ‘How’ refers to a system’s structure and behavior.

A. True
B. False

Explanation: Requirements analysis is conducted iteratively with functional analysis to optimize performance requirements for identified functions, and to verify that synthesized solutions can satisfy customer requirements.

A. Performance, Design
B. Stakeholder, Developer
C. Functional, Non-Functional
D. None of the mentioned

Explanation: Option a and c are the types of requirements and not the issues of requirement analysis .

A. True
B. False

Explanation: Requirements traceability is concerned with documenting the life of a requirement and providing bi-directional traceability between various associated requirements, hence requirements must be traceable.

A. Two
B. Three
C. Four
D. None of the mentioned

Explanation: Economic feasibility (cost/benefit analysis), Technical feasibility (hardware/software/people, etc.) and Legal feasibility studies are done in Requirement Analysis.

A. System responds within 4 seconds on average to local user requests and changes in the environment
B. System responds within 4 seconds on average to remote user requests and changes in the environment
C. All of the mentioned
D. None of the mentioned

Explanation: System response to a local user is 2 seconds on average.

A. Testability
B. Speed Efficiency
C. Serviceability
D. Installability

Explanation: Speed Efficiency belong to Performance (P) in FURPS+

A. Product-oriented Approach – Focus on system (or softwarE. quality
B. Process-oriented Approach – Focus on how NFRs can be used in the design process
C. Quantitative Approach – Find measurable scales for the functionality attributes
D. Qualitative Approach – Study various relationships between quality goals

Explanation: Quantitative Approaches in NFRs are used to find measurable scales for the quality attributes like efficiency, flexibility, integrity, usability etc.