Requirement Engineering

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

A. Use Cases
B. Entity Relationship Diagram
C. State Transition Diagram
D. Activity Diagram

Explanation: Activity Diagram comes under the design phase of SDLC.

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

Explanation: Problem Recognition, Evaluation and Synthesis (focus is on what not how), Modeling, Specification and Review are the five phases.

A. True
B. False
C. Depends upon the size of project
D. None of the mentioned

Explanation: Requirements must be actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

A. Developer
B. User
C. Non-Functional
D. Physical

Explanation: The perspectives or views have been described as the Operational, Functional, and Physical views.All three are necessary and must be coordinated to fully understand the customers’ needs and objectives.