Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Spring 2003 M4: User Interface Design and Implementation
Now provide an interface for your personal finance software.
You should be able to:
- define users, portfolios and accounts and make connections between them
- fill in information for them
- check for accuracy and missing information, querying, and so on.
We will start your system with:
Squeaken new openThis should open up your application. It should start up assuming a maximum 800x600 display space, but should be resizable by the user for a larger space.
(Note however that, whatever you do, all the financial data is not going to fit into even the largest display. Think about ways of collapsing information.)
Besides the necessary data entry screens, you will need to generate textual and graphical reports that provide financial status to the user.
You should provide a pie chart like representation of allocation of finances by category (i.e. % in cash, in equities, in bonds). You should also be able to drill down into each category to see details in each category. For instance, if I drill down into equities, I should be able to see what percent of my equity portfolio is invested in each stock or mutual fund. Besides percent, it would also be nice to see the allocation in total dollars.
History Graphs which show:
- Variation of net worth over time.
- Performance over time of different portfolios. ex. How does my Merril Lynch Portfolio look compared to my Fidelity Mutual Fund.
- Textual reports as in M2. Show transaction histories for different portfolios/accounts. List all the portfolios and what accounts/assets they contain.
The look and feel of the user interface is entirely up to you!
However, if the TA can't use a particular function, she or he can't grade it, and you can't get credit for it.
IT IS WORTH YOUR WHILE TO MAKE SURE THAT YOUR TA CAN USE YOUR SOFTWARE!
HINT!: Students in Summer 2002 wrote drawing editors where boxes, circles, etc. could be dragged around and resized in Morphic. Any of their designs and code can be reused from the Cases page. Also look in SqueakMap for some graphing classes that might help.
Turn-in your code using the Spring 2003 Turnin Information with the code 'M4'. Turn in your design in class.
- 10% Good updated Scenarios: Accounts for all major functions in assignment, touches on every class.
- 10% Good updated CRC card analysis: Reasonable names, understandable and clearly defined responsibilities, good exploration of other class names
- 3% Good updated UML class diagram with correct usage of notation
- 7% Detailed and understandable Class descriptions and names
- 10% Quality of the UI design
- 10% Well-documented and good style source code
- 50% Working system:
- 20% Can create necessary financial information (users, portfolios and accounts), fill in their information, and can create all relationships between them.
- 10% Can display transaction histories for all accounts or porfolios
- 15% Can generate graphical charts
- 5% SUnit Tests and good error/exception handling
Note: If the TAs can't figure out how to do these things, they don't have to give you the points. The UI must be usable.
Links to this Page