A. Collaboration
B. Use case
C. State chart
D. Activity
Explanation: A use case diagrams captures only the functionality of the system whereas a dynamic model/view captures the functions as well as the action.
A. Machine readability
B. Maintainability
C. Structure enforcement
D. Overall simplicity
Explanation: Readability is processing input.
A. short-term memory
B. shortcuts
C. objects that appear on the screen
D. all of the mentioned
Explanation: The interface should be designed to reduce the requirement to remember past actions and results.
A. Implements some functionality
B. Has explicit dependencies through provides and required interfaces
C. Communicates through its interfaces only
D. All of the mentioned
Explanation: All the options identify with features of a software component.
A. When resources (time and budget) are over
B. When some coverage is reached
C. When quality criterion is reached
D. Testing never ends
Explanation: As software testing is an exhaustive process, when the quality assurance is established and the product is ready to be delivered, testing is stopped.
A. Sequence Diagram + Collaboration Diagram
B. Activity Diagram + State Chart Diagram
C. Deployment Diagram + Collaboration Diagram
D. None of the mentioned
Explanation: Interaction diagram are used to formalize the dynamic behavior of the system.
A. tangible entities
B. scenario-based analysis
C. design-based analysis
D. none of the mentioned
Explanation: Use a scenario-based analysis where various scenarios of system use are identified and analyzed in turn.