What is the least cohesive approach in creating use case controllers in a system?
A) Define a single controller for all use cases.
B) Define several controllers, each with a specific set of responsibilities
C) Create a single controller for a single subsystem
D) Create one controller per use case
Correct Answer:
Verified
Q17: Design class diagrams and interaction diagrams should
Q18: The perfect solution assumption means that we
Q19: The best technique for accessing the database
Q20: The initial version of a communication diagram
Q21: It is better to have the data
Q23: A return value in an interaction diagram
Q24: On a sequence diagram constructor messages are
Q25: Which is the correct notation for a
Q26: The adapter pattern facilitates changing the API
Q27: Detailed design of use cases using communication
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents