Scribd
Upload
162 views5 pages

In-Course Assessment (Ica) Specification: School of Computing, Engineering and Digital Technologies

This document provides specifications for an in-course assessment (ICA) assignment in an Object Oriented Programming module. It details that students must submit a portfolio of 10 programming problems by May 6th, 2020 either online through Blackboard or in person. The portfolio must include the code, a written report on the design choices, and a summary of testing. 8 sample programming problems are provided ranging from 1 to 3 portfolio points each involving phone books, text messaging, student marks, stock control, cellular automata, and agents. The document concludes with marking criteria for the portfolio focusing on documentation, discussion, and code quality.

Uploaded by

ZERO TO VARIABLE
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
162 views5 pages

In-Course Assessment (Ica) Specification: School of Computing, Engineering and Digital Technologies

This document provides specifications for an in-course assessment (ICA) assignment in an Object Oriented Programming module. It details that students must submit a portfolio of 10 programming problems by May 6th, 2020 either online through Blackboard or in person. The portfolio must include the code, a written report on the design choices, and a summary of testing. 8 sample programming problems are provided ranging from 1 to 3 portfolio points each involving phone books, text messaging, student marks, stock control, cellular automata, and agents. The document concludes with marking criteria for the portfolio focusing on documentation, discussion, and code quality.

Uploaded by

ZERO TO VARIABLE
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

SCHOOL OF COMPUTING, ENGINEERING AND

DIGITAL TECHNOLOGIES

IN-COURSE ASSESSMENT (ICA) SPECIFICATION

Module Title: Module Leader: Jackie Barker


Object Oriented Programming
Module Code: CIS4037-N

Assignment Title: Deadline Date: 6th May 2020


Java Portfolio
Deadline Time: 4:00pm

Submission Method:

Online (Blackboard) 
Middlesbrough Tower 

Online Submission Notes:

 Please follow carefully the instructions given on the Assignment Specification

 When Extenuating Circumstances (e.g. extension) has been granted, a fully


completed and signed Extenuating Circumstances form must be submitted to the
School Reception or emailed to [email protected].

Central Assignments Office (Middlesbrough Tower M2.08) Notes:

 All work (including DVDs etc) needs to be secured in a plastic envelope or a folder
and clearly marked with the student name, number and module title.

 An Assignment Front Sheet should be fully completed before the work is submitted.

 When Extenuating Circumstances (e.g. extension) has been granted, a fully


completed and signed Extenuating Circumstances form must be submitted to the
School Reception or emailed to [email protected].

FULL DETAILS OF THE ASSIGNMENT ARE ATTACHED


INCLUDING MARKING & GRADING CRITERIA
OBJECT ORIIENTED PROGRAMMING

Portfolio Requirements

Brief
OBJECT ORIENTED PROGRAMMING is assessed on the basis of a portfolio of work. You
are provided with a suite of programming problems (see below), each of these is worth a
stated number of Portfolio Points (PPs). For your portfolio work you should submit 10 PPs
worth of work. If you submit less than 10 PPs you will lose marks; if you submit more
than 10, only the first 10 will be marked.

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).
Page 2 of 5
SCHOOL OF COMPUTING, ENGINEERING AND
DIGITAL TECHNOLOGIES
 Testing at class and UI level (save time by learning to
use the testing facilities in Netbeans).
Portfolio problems
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.
Page 3 of 5
SCHOOL OF COMPUTING, ENGINEERING AND
DIGITAL TECHNOLOGIES

9. Agents – vants [1 PP]


Extending earlier work, this will adapt "the trail" to
implement Langton's Virtual Ants.

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
Requirement Pass (50-59) Good (60-69) Excellent (70+)

Documentation Level of English & technical authorship is English & technical authorship presents a Full (but concise) explanation of the problem
acceptable; clear explanation of the problem; domain and the objectives of each task;

discussion/critique demonstrates understanding Discussion/critique shows a good appreciation Clear insight into main challenges &
of main issues & problems; of main issues & objectives; compromises;

Some evidence of tutor feedback recorded, and Feedback from tutor is appropriately recorded Excellent recording of and reflection on the
evidence of subsequent action taken. with a short supplementary discussion on what response and actions taken to tutor
response and actions followed. feedback.
Discussion Demonstrated understanding of the problems A critical refection and/or evaluation of the A thorough reflection on the nature of the
and/or critique tackled and their solution; problem and solution(s); problem and the validity and/or efficacy of the
solution provided (see note below);
Some suggestions about alternative solutions; Suggestions for improvements and
alternative solutions; Sensible suggestions for improvements and
alternative solutions;

Program code Code implements a reasonable solution; code meets all major requirements; Code meets all necessary requirements &
performs consistently as intended;
It is of acceptable quality & is adequately It is of good quality & is well commented
explained. and/or explained; It is of good quality & elegantly specified;

The code is possible to extend & maintain. Code is well commented and explained;

Code is easy to extend & maintain.

Note: portfolios which are incomplete or present too little work will have their marks adjusted accordingly. Tutors will give advice about
appropriate levels of work.

Page 5 of 5

You might also like