February 2019

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.

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.