Since we don't expect you to read our minds, this is one purpose of the checkpoints - we give you feedback on the project and tell you if you're on track to do well and if not how to get there, without penalizing you for not being able to read our minds.
However, for those who want a bit more of an idea of what's an acceptable project, we offer the following rough guidelines. We expect that each application should eventually have:
The domain that I'm going to model is going to be the banking domain; i.e., the kind of information that is stored about the accounts in one bank.The aspects of the bank that I will be modelling will be the information relevant to the customer information in the bank. This includes things like the the accounts that a given customer has, information specific to the customer (e.g., the customer's name and address), and the customer's credit cards. There will be a number of different kinds of accounts, and some of these accounts will have additional information to let customers know if that account is right for them (e.g., a mutual fund account will contain information on what stocks are included in the mutual fund and how the fund performed over the past year).
There will be two different classes of users of the system: the customers, and the bank employees. The customers will be able to access their own accounts, and transfer money from one account to another. They will also be able to update some of their personal information, like their bank account password. The bank employees will be able to access all of the customers' data - both the customer accounts and the customer personal information. Only the bank employees will be able to change things like the customers' SIN. Bank employees may reset the customers' account passwords, but may not see them.
This project will be done using the CS department's oracle database and using Java and JDBC. I do not anticipate using any special software or hardware.