0% found this document useful (0 votes)
30 views5 pages

In-Course Assessment (Ica) Specification: Module Title

This document provides specifications for an in-course assessment assignment requiring students to submit a Java programming portfolio. The portfolio must include 1-3 programming problems addressing topics like a phone book, text messaging, student marks, stock control, cellular automata, and agents. For each problem, students must submit the NetBeans project, a written report outlining the design and evaluation, and a summary of testing. The portfolio will be graded based on the quality of documentation, discussion/explanation, and program code. Feedback will be provided to help students improve their work.

Uploaded by

Richa ARORA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
30 views5 pages

In-Course Assessment (Ica) Specification: Module Title

This document provides specifications for an in-course assessment assignment requiring students to submit a Java programming portfolio. The portfolio must include 1-3 programming problems addressing topics like a phone book, text messaging, student marks, stock control, cellular automata, and agents. For each problem, students must submit the NetBeans project, a written report outlining the design and evaluation, and a summary of testing. The portfolio will be graded based on the quality of documentation, discussion/explanation, and program code. Feedback will be provided to help students improve their work.

Uploaded by

Richa ARORA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

IN-COURSE ASSESSMENT (ICA) SPECIFICATION

Module Title:
Object Oriented Programming

Assignment Title:
Java Portfolio

Online Submission Notes:

 Please follow carefully the instructions given on the Assignment Specification

FULL DETAILS OF THE ASSIGNMENT ARE ATTACHED


INCLUDING MARKING & GRADING CRITERIA
OBJECT ORIIENTED PROGRAMMING

Portfolio Requirements

Brief

All portfolio entries are due in by the final ICA deadline for the module but you are
strongly advised to present work as the module progresses. This will prevent you having
a lot of work to complete at the end of the module, but more importantly you will receive
feedback that can be reflected and acted upon, and will also strengthen your future work.

For each portfolio entry you are expected to submit:

1. A NetBeans project containing all relevant code (including tests, etc).

This should be provided as a .zip compressed file.


Do not include irrelevant code or other portfolio work.
If your code does not compile or is not laid out correctly or your Netbeans project has
an invalid structure, then your work will not be marked.

2. A brief written report which outlines:

a. The design of your code;


b. Identifies the classes used and provides a critical evaluation of the choices you
made (generally this should include a brief comment about any collection
classes used);
c. Record of any feedback received and any subsequent actions taken.

3. A summary of the testing used.

Portfolio work
The following problems are intentionally understated. They do not provide Object
Oriented designs or specify which classes from the Java API should be used or which
should be coded. Tutors will provide advice when asked but expect discussions about
design, etc. to be led by you. Considering appropriate designs and investigating the API &
facilities offered by Netbeans contribute to the learning outcomes of this module and
form part of the problem-based learning approach we use.

Note that all programs should include the following:

 A UI adequate for testing and demonstration purposes. These can be minimalistic


but should be clean and obvious to use.
 Appropriate use of pop-up messages to inform users of key events (Option panes
or other).
 Testing at class and UI level (save time by learning to use the testing facilities in
Netbeans).
Portfolio problems

Page 2 of 5
1. phone book #1 [1 PP]
A simple phone-book which associates names with phone numbers. Allows
name/number entries to be added and provides a number lookup function (find a
number for a given name). Complete solutions will also allow lookup of names given
numbers.
2. phone book #2 [1 PP]

Extends phone book #1 by associating names with more personal data


eg: mobile number, email address, work number, etc.
2. additional (optional) [1 PP]
Lookup mechanism for partial names.
3. text messaging [1 PP]

Provide a facility to display SMS format messages ordered appropriately by contact


name & date. You are required to provide UI facilities to add new entries for testing
purposes but you are not expected to provide load/save routines so take an easy
approach to loading sample data for testing purposes.
4. student marks [2 PP]
A simple UI linking to a dataset of student marks where each student
has a name, an id and a range of marks for their modules. The UI
allows new students to be added; new marks to be added and
provides various lookup functions and facilities to check the average
mark & number of passes/fails for a given student.
• Additional guidance for this problem will be given by tutors.
4. additional (optional) [1 PP]

Module statistics; the UI provides various lookup functions and facilities to check the
average mark & number of passes/fails for a given module.

5. stock control with change monitor [3 PP]


Implement a stock control system which reads/writes stock data to/from text files. A
UI provides lookup facilities and functions to buy (remove) stock and to resupply. A
facility to add change monitor(s) is part of this work.
• Information about change monitors and other additional guidance for this problem
will be given by tutors.
6. Cellular Automata (Conway's Game of Life) [3 PP]
The first tile-based and animated graphics work. Uses 2 image buffers (and 2 backing
data structures) to update and display tile-based cellular automata following Conway's
rules for the game of life. Programs will be single-threaded but will allow basic world-
size, speed and pause adjustments.
• Additional guidance for this problem will be given by tutors.
7. Cellular Automata (Genetic Drift) [1 PP]
Extending the work developed for the Game of Life this will change the CA rules to
implement a genetic drift model.
8. Agents – the trail [2 PP]

Further extending the cellular automata infrastructure, this adds mobile


agents/entities, implementing (for this example) an entity that makes random
movements, leaving a trail of coloured tiles.
9. Agents – vants [1 PP]
Extending earlier work, this will adapt "the trail" to implement Langton's Virtual Ants.

Page 3 of 5
Assessment criteria
Portfolios are individual pieces of work and may be prepared in different ways and
documented in different styles. All portfolios require some program code, some
explanation of key design & implementation issues and some discussion and/or critique.

Marks will be awarded for the following:

 The quality of documentation


 The quality of discussion/explanation
 Program code

Page 4 of 5
Page 5 of 5

You might also like