Java Reference
In-Depth Information
2.
An Ȓextremeȓ spiral model, with lots of iterations.
3.
To give frequent feedback as to whether the current iteration of the product
fits customer needs.
4.
FileWriter
5.
To produce the shipping address of the customer.
6.
Reword the responsibilities so that they are at a higher level, or come up
with more classes to handle the responsibilities.
7.
Through aggregation. The bank manages bank account objects.
8.
Through inheritance.
9.
The
BankAccount
,
System
, and
PrintStream
classes.
10. The
Invoice
class is responsible for computing the amount due. It
collaborates with the
LineItem
class.
11. This design decision reduces coupling. It enables us to reuse the classes
when we want to show the invoice in a dialog box or on a web page.
12. The bank needs to store the list of customers so that customers can log in.
We need to locate all bank accounts of a customer, and we chose to simply
store them in the customer class. In this program, there is no further need to
access bank accounts.
13. The
Bank
class needs to have an additional responsibility: to load and save
the accounts. The bank can carry out this responsibility because it has
access to the customer objects and, through them, to the bank accounts.
