Business Programming

Summary module description:

Aims:
This module introduces Business Programming in a modern environment. It also covers design techniques suited to imperative and object-oriented program development.

Assessable learning outcomes:
By the end of the module, it is expected that the student will be able to:

- describe design techniques suited to imperative and object-oriented program development
- explain how problems can be solved using programs
- explain how programming languages are used to produce computer and web-based applications
- identify the programming constructs available in modern programming environments
- be able to program within the Windows environment
- identify testing approaches that can be applied to different programs

Additional outcomes:
The module also aims to encourage the development of the following skills:
identifying which design techniques are suitable in a variety of circumstances; the ability to identify common programming constructs and features; an understanding of how software tools such as compilers, debuggers, and language specific editors can aid programming.

Outline content:
This module is designed to acquaint students with programming and design, the use of design will be integrated with the development of programming skills. Content will include:

Imperative and object oriented programming in modern programming languages, including sequencing constructs (loops and conditionals), types (simple and structured), functions and parameters, pointers, modular programming, encapsulation, inheritance, methods and properties. Aspects of visual programming will also be considered.
Brief description of teaching and learning methods:
Normally: one 3-hour practical each week. Practical assignments will be given out regularly, and these will give practice in design and programming; and assist appreciation of the theoretical aspects of the module. Practical work will be assessed in practical sessions, and appropriate advice will be given. Some of the learning will require self study.

Summative Assessment Methods:
Set exercise 100%

Other information on summative assessment:
Seven assignments:

1 Produce UML models for Coursework 6 (a major software project) (5%)
2 Build weekly portfolio of tutorials aimed at novice programmers (25%)
3 Reflections on Autumn term learning and progress (5%)
4 Submit academic report on programming related topic (20%)
5 Make weekly code submissions and prioritise future work (10%)
6 Implement and demonstrate major software project (30%)
7 Reflections on Spring term learning and progress (5%)
Formative assessment methods:
Penalties for late submission:

Work will be assessed in accordance with the University-wide Framework for Classification and Progression for First Degrees (see, particularly, Annex 3).

Penalties for late submission:

Penalties for late submission on this module are in accordance with the University policy.
For major pieces of work (courseworks 2, 4 and 6):
? where the piece of work is submitted up to one calendar week after the original deadline (or any formally agreed extension to the deadline): 10% of the total marks available for the piece of work will be deducted from the mark;
? where the piece of work is submitted more than one calendar week after the original deadline (or any formally agreed extension to the deadline): a mark of zero will be recorded.
For Minor pieces of work (courseworks 1,3, 5 and 7):
Late work, without an accepted extenuating circumstances form, will have a mark of zero recorded.
You are strongly advised to ensure that coursework is submitted by the relevant deadline. You should note that it is advisable to submit work in an unfinished state rather than to fail to submit any work.

The Module Convener will apply the following penalties for work submitted late, in accordance with the University policy.
where the piece of work is submitted up to one calendar week after the original deadline (or any formally agreed extension to the deadline): 10% of the total marks available for the piece of work will be deducted from the mark for each working day (or part thereof) following the deadline up to a total of five working days;
where the piece of work is submitted more than five working days after the original deadline (or any formally agreed extension to the deadline): a mark of zero will be recorded.

The University policy statement on penalties for late submission can be found at: http://www.reading.ac.uk/web/FILES/qualitysupport/penaltiesforlatesubmission.pdf
You are strongly advised to ensure that coursework is submitted by the relevant deadline. You should note that it is advisable to submit work in an unfinished state rather than to fail to submit any work.

Requirements for a pass:
40%