When do we use an extended use case?
What will be an ideal response?
When developing use cases, we may discover that some functionality has been left out: we expected the customer to pay by cash, but we find out that the business accepts credit cards as well. Instead of rewriting the use case, we can create an "extending" use case and add a conditional step to the "base" use case that branches to the new one if the customer decides to pay by credit card. This type of dependency is called an "extend" relationship and adds flexibility to maintaining use cases. The catch is that the normal outcome of the base use case must not depend on the success or failure of the "extending" use case.
You might also like to view...
Alex is considering replacing old machinery with a new one. The old machinery can still be used for another 2 years. The depreciation on the old machinery represents which type of cost?
a. Variable costs b. Relevant costs c. Sunk costs d. Opportunity costs
The journal entry to record the issuance of a note for the purpose of borrowing funds is:
A) debit Accounts Payable; credit Notes Payable. B) debit Cash; credit Notes Payable. C) debit Notes Payable; credit Cash. D) debit Cash and Interest Expense; credit Notes Payable.
What is a waiting line model, and what information can it provide?
What will be an ideal response?
Universally around the globe, women employees earn less than their male counterparts. Although the difference in pay rates varies dramatically from one country to the next, women typically earn _____ less than men according to the International Trade Union Confederation
A) close to 5% B) close to 10% C) close to 20% D) close to 30%