This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Real-World Software Development: A Project-Driven Guide to Fundamentals in Java and have Dr. Raoul-Gabriel Urma & Richard Warburton on-line! See this thread for details.
Assume that there is a requirement to add state transitions to a "Cancelled" state from any states except "Closed". Which of the following are valid ways to add the "Cancelled" state? a) Funnel all cancellations from only one of the other states.
b) Add a "Cancelled" superstate to the diagram.
c) Add transitions from "Submitted" and "Qualified" to a new "Cancelled" state.
d) Add an "Active" superstate that handles the transition to "Cancelled".
The answer C is fine, how come the D is correct? I thaught it could be B & C ==============================================
2. Here is a question, which Answer given is C, just have a look at it:
Which of the following is the BEST strategy for resolving class name collisions that occur during OO analysis? a) Allow each team member to choose names for only those classes which they will build.
b) Create a class for each domain name, passing on requests to the one class that implements the behavior for all of them to share.
c) Discover unique names for different concepts that are referred to by the same term.
d) Put the classes into different packages so that the fully qualified class names are different.
Single Select - Please select the best answer (one and only one choice must be selected).
according to me the answer must be d)
can any one explain it if i m wrong?? =================================================== 3.
this question i did not understad, is there any design diagram missing??
- In Design #1, the Catalog object has a getProducts() method, which returns a xx collection object, such as a Dictionary or array, containing all the Products the company sells. - In Design #2, the Catalog object has a getProductNumbered(anIdentifier) method, which returns the Product with the specified unique identifier.
Considering a requirement to get a specific product, which of the following BEST characterizes the two designs?
a) Both designs maintain the objects' encapsulation and reduce coupling by accessing state data via methods only and not directly.
b) Both designs break the objects' encapsulation, adding brittle coupling.
c) Design #1 adds brittle coupling. Design #2 maintains the encapsulation of the Catalog, making future design changes easier.
d) Design #1 maintains the encapsulation of the Catalog by hiding the implementation details in the getProducts() method. Design #2 breaks the encapsulation of the Catalog since it uses anIdentifier as the Product key.
waiting for your replies..
"Walking on water and building IT Architecture from <br />specification are easy if and only if both are frozen"
If tomatoes are a fruit, then ketchup must be a jam. Taste this tiny ad: