Assignment title: Information


ASSIGNMENT ____________________________________________________________________ SUMMARY  Optional but worth 20% of marks.  Must pass all 3 tests before an assignment may be submitted.  Work divided into C, B and A grade sections.  May work as a pair in some sections.  Must keep and submit a log of all activities.  Submit through Blackboard by week 12.  Demonstrate during your week 12 lab. Grade Map Check the criteria with each assignment for C, B and A grades. Grade Meaning Mark Range % Assignment Mark A+ Pass with Distinction 90 - 100 18 – 20 A 85 – 89 17 A- 80 – 84 16 B+ Pass with Merit 75 – 79 15 B 70 – 74 14 B- 65 – 69 13 C+ Pass 60 – 64 12 C 55 – 59 11 C- 50 – 54 10 D Fail 0 - 49 0 – 9 INTRODUCTION The assignment is optional, but is worth 20% of the overall marks for Foundation Programming. It is intended for those who have demonstrated their mastery of the basics by passing the 3 practical tests. You cannot get an A grade in Foundation Programming if you do not attempt the assignment. The assignment gives you the chance to do some research, and to work on something more interesting than the routine exercises and tests of units 1 to 6. This document lists the options you have for the assignment. More detailed information is available for each of these options. DOCUMENTATION For all stages of the assignment, you must keep a log of your activities. You may use the Journal on Blackboard or a physical log book. If you wish to use a word processor, you must print out your completed log and hand it in. For those stages that allow working as a pair, please note that you must each produce your own independent log. A joint log is not acceptable. Each time you work on the assignment record the date, an outline of what you did, and how long you spent working. In addition, record problems you had and how you solved them, your ideas behind anything you designed, how hard or easy you found the tasks, and any research you had to do. You should also keep a record of your testing. You should include references for any materials you used, including URLs of any internet sites you referenced. Reflection When you have completed the assignment, think about what you have learned from it in terms of programming. Each stage comes with reflection questions to guide you. Put these at the end of your log. BACKING UP Your H drive at AUT is regularly backed up by IT staff. If you are working on your home computer or a laptop, or are keeping your files on a memory stick, you are responsible for your own backing up. If you lose all your work the week before your assignment is due, and you have no back up, do not expect much sympathy. You have been warned! How often should you back up your work? A good guide is to ask how much time you are prepared to spend redoing work you have lost. Whatever the answer, that is how often you should back up. PRESENTATION During your last lab session, you will be expected to demonstrate your working assignment. This is a compulsory part of the assignment. SUBMISSION Your source code must be placed into a ZIP file then submitted through Blackboard. The assignment submission link will be made available during your last lab session. If you wish to submit earlier, talk to your stream tutor. Your log may be on Blackboard's Journal, in which case it does not need to be submitted. You may keep a handwritten log book, or may use an online document which you must print. Either of these must be submitted in your lab or through the assignment box. You will require a front cover sheet which you should download from Blackboard, complete and sign. That must be submitted in your lab or through the assignment box. STAGES The assignment is divided into stages, and must be completed in the order shown. You are not required to complete the stages for B or A grades, but if you do not do so your best grade will be a C. You may submit incomplete work which may gain you some marks. The 3 stages are outlined here, but more detail follows. All code is expected to follow the programming standards for Foundation Programming. C STAGE Satisfactory completion of this stage will result in your gaining a C grade (10 to 12 marks) for the assignment. Requirements 1. This stage must be done individually. 2. Write a program in C# or other approved language that meets the specifications listed in Appendix 1. 3. Documentation must include your log with test results and a reflection. B STAGE Satisfactory completion of this stage will result in your gaining a B grade (13 to 15 marks) for the assignment. Requirements 1. This stage must be done individually. 2. Complete the C stage outlined above. 3. Write a program in C# or other approved language that meets the specifications listed in Appendix 2. This is an extension of the C stage. 4. Documentation must include your log with test results and a reflection. A STAGE Satisfactory completion of this stage will result in your gaining an A grade (16 to 20 marks) for the assignment. Requirements 1. Satisfactorily complete the C and B stage work outlined above and have them checked by your tutor. 2. Write a program in C# or other approved language that meets the specifications listed in Appendix 3. This is a GUI version of the C and B stages. 3. Documentation must include your log with test results and a reflection. 4. This may be done individually, or as a pair. If working as a pair, pair programming must be used and included in your log. Notes This stage gives you scope to explore aspects of programming you may encounter in programming papers later in your student life, such as the graphical user interface (GUI). Other examples include: i. Appropriate use of methods.