- The assignment requires that you write working code for a small but plausible business system. To keep the amount of work involved to a reasonable level, the programs you create will be much more restricted in capability, and much cruder in overall presentation, than anything you would actually create for a paying customer. However, the essence of the problem will be the same. You will be graded on correctly solving the technical requirements, not on the "polish" of the finished product. Note however, that some aspects of ease of use, for example how easily the program may be started or configured, will be part of the scoring criteria. Pay careful attention to any such requirements and be sure to adhere to them.
- The problem is likely to be something along the lines of a simple booking system, allowing users to view available resources, then book them. The system will not require complex business rules, but will require access to persistent storage, typically in a flat-file format, for reading and modification. You will be expected to make effective use of many of the core Java APIs, but you will not be expected to use more advanced APIs. Below you will find a list of APIs that you will be expected to use, as well as a list of APIs that you may not use. Any APIs that do not appear in either list may be used at your discretion. In fact, using more advanced APIs is likely to be specifically prohibited, as these APIs are often the subject of other certifications. You should use a consistent set of programming style conventions for your entire project. Preferably, these should be the style conventions described at http://java.sun.com/docs/codeconv.
|