Which of the following is not a part of a test design document ?
A. Test Plan
B. Test Design Specification
C. Test Case Specification
D. Test Log
Explanation: Test log is a part of testing result document.
advertisement
A. Test Plan
B. Test Design Specification
C. Test Case Specification
D. Test Log
Explanation: Test log is a part of testing result document.
advertisement
A. encapsulating the knowledge of which document subclass to is to be created and
B. moving this knowledge out of the framework
C. instantiating the application specific documents without knowing their class
D. all of the mentioned
Explanation: Following all the options in order will solve the factory method problem.
A. specify required services for types of objects
B. program in Java, but not in C++ or Smalltalk
C. define executable logic to reuse across classes
D. define an API for all classes
Explanation: An interface is like a template design for a class that contains no data or implementation; only definitions for methods, properties etc
A. patterns
B. documents
C. structures
D. methods
Explanation: A pattern is the outline of a reusable solution to a general problem encountered in a particular context.
A. Verified Version
B. Version Validation
C. Verification and Validation
D. Version Verification
Explanation: V&V generally refers to any activity that attempts to ensure that the software will function as required.
A. modality
B. cardinality
C. entity
D. structured analysis
Explanation: The modality is 1 if an occurrence of the relationship is mandatory, else 0 for optional relationship
A. operations only
B. attributes only
C. both operations and attributes
D. none of the mentioned
Explanation: In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, operations, and the relationships among objects.