Reference no: EM131497413

Assignment: Introduction to Programming

A component based marking scheme. The biggest confusion is delivering an end application whereas the program component workings are the most valuable part of this stage. The project can be in pieces and individual parts tested, and get top marks. Prototype code should be an involved consideration of the problem in more depth than your class exercises.

You can do anything in Java that you like, or use your current skill set and implement features. There is no limit on marks, as additional features can be added. You are free to `incorporate' code from the internet - but as your own. e.g. adding file read and write to save your application state can be a major additional feature (the interviews at each of the two stages help validate this) However, in practise a considerable amount of work is needed to implement additional features.

Your code is general the primary source of the projects marks at any stage.

Stage 1

Requires:

• Problem formation and description
• communication of solo or group work and members.
• competed in-class interview.
• 1 page report (demonstrated in interview)
• Original data (the problem should have its own associated data)
• working Java prototype code (demonstrate in interview)
• + optionally other documents
• Code draft required before interview

All documents submitted through gradecentre before the interview. If non-attendance of interview, no marks for the report stage as no verification of work.

Default project/theme : not sure if we will have one. An inventory type application is always possible, and can employ the array data structure and other programming. Text console menus allow for submenus and a more detailed application. Games of any sort - can use random number generation to include chance. If you run out of ideas, think bigger, then you will always have more features to implement.