A. Context Diagrams
B. DFDs
C. ER model
D. UML diagrams
Explanation: Unified Modeling Language (UML) diagrams are constructed during the design phase of the SDLC.
A. True
B. False
Explanation: Requirements traceability refers to the ability to describe and follow the life of a requirement in both forwards and backwards direction. Requirements can be traced from its origins, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases.
A. Cost
B. Design Constraints
C. Staffing
D. Delivery Schedule
Explanation: Design constraints include standards to be incorporated in the software, implementation language, resource limits, operating environment etc.
A. Enduring
B. Volatile
C. Both Enduring & Volatile
D. All of the mentioned
Explanation: For library management system issue/return of a book, cataloging etc. are core activities and are stable for any system.
A. Known, Unknown, Undreamed
B. User, Developer
C. Functional, Non-Functional
D. Normal, Expected, Exciting
Explanation: According to QFD, Normal, Expected and Exciting requirements maximizes customer satisfaction from the Software Engineering Process.
A. Testability
B. Speed Efficiency
C. Serviceability
D. Installability
Explanation: Speed Efficiency belong to Performance (P) in FURPS+
A. Problem of scope
B. Problem of understanding
C. Problem of volatility
D. All of the mentioned
Explanation: Users specify unnecessary technical detail that may confuse, rather than clarify overall system objectives.Also, the customers/users are not completely sure of what is needed, have a poor understanding of the capabilities and limitations of their computing environment and they do not understand that the requirements change over time