1. Consider an automatic teller machine (ATM) system. Attempt to apply the 11 categories of business goals to that system and infer what goals might have been held by various stakeholders involved in its development.

2. Create a utility tree for the ATM system. Consider a minimum four different quality attributes. Ensure that the scenarios that you create at the leaf nodes have explicit responses and responses measures.

3. Using a MVC based system as example to show how a single class system can be decomposed step-by-step into a multi-class system by using ADD.

4. Draw an UML sequence diagram to show the behavioral view of the fully decomposed MVC based system in question 6 for a typical functionality.

5. Suppose your company has just purchased another company and that you have been given the task of merging a system in your company with a similar system in the other company. What views of the other system’s architecture would you like to see and why? Would you ask for the same views of both systems? Explain your answers.

6. List some of reasons why an architecture and a code base inevitably drift apart. What processes and tools might address this gap? What are their costs and benefits?