2. Create a UML class diagram for system described below. Make sure you include correct multiplicity. Show all attributes (with types) and associations. If generalizations are necessary, show them too. Marks will be given for effort, even if you do not have a perfect solution. However, marks will be lost for the common types of mistakes we talked about in class (e.g. poor generalizations, wrong multiplicity, etc.). (30 points).

3. Write five functional requirements, three quality requirements, one process requirement and one platform requirement for the system described below. Make your own assumptions. (20 points)

Imagine you were re-creating an Investment System for OOBank. OOBank has a separate investment division. This division manages various mutual funds in which investors may invest and also looks after the investment portfolios of investors. An investor may at any point in time have several investment advisors. These help the investor decide in what to invest. Different investment advisors specialize in different types of investments. Investors make a series of transactions and may have to pay a commission on each transaction. The commission is paid to the investment advisor that arranged the transaction. For each investment the system must keep track of the number of shares (also called units) in addition to the amount the investment is worth today and the amount originally invested. Each mutual fund invests its money in various securities. The securities can be stocks, bonds or other mutual funds. We must be able to calculate the original amount invested in each security as well as how much that investment is worth today. Each mutual fund may have several investment advisors that help the fund decide what securities in which to invest.

The system must also keep track of:

The investors personal information including the name, last name, SSN, date of birth, address and phone number.

The advisors personal information including the name, last name, and employee id.

Each transaction will be uniquely identified by an id. A timestamp will be recorded for each transaction.