This is an archived handbook for a previous year. The current undergraduate and postgraduate handbooks can be viewed using the links above.
Postgraduate Handbook 2007-2008 (archived)
Module COMP51815: OBJECT ORIENTED PROGRAMMING IN JAVA AND UML
Department: Computer Science
COMP51815: OBJECT ORIENTED PROGRAMMING IN JAVA AND UML
| Type | Level | Credits | Availability | Module Cap | Location |
|---|---|---|---|---|---|
| Open | 4 | 15 | Available in 2007/2008 | Durham |
Pre-requisites
- None.
Corequisites
- None.
Excluded Combinations
- None.
Aims
Content
- Computing programme - purpose and principles
- OO Programming in the context of other programming paradigms
- Introduction to Java
- Introduction to modelling languages - purpose and principles
- Introduction to UML
- Objects in Java
- Imperative programming constructs in Java - simple and compound statements
- Methods, classes, projects
- Interfaces, inheritance
- Constructing more complex programs - problems involved with scaling up
- Problem solving
- Problem solving via computer programming
- Algorithms design and efficient design of programs
- Stand-alone Java applications
- Java and the WWW; RMI and related distributed APIs
- UML constructs
- Simple UML designs and the use of UML in large systems
- Relation between UML and Programs - using UML in software development
Learning Outcomes
Subject-specific Knowledge
- Specialist knowledge: Java and UML constructs; APIs for distributed systems
- Practical design skills: designs expressed in UML
- Design integration: using UML in software development for Java
- the engineering of software systems: writing Java programs, problem solving, algorithm and program design, and Java applications and Java and the WWW
- Professional skills: modelling, problem solving, scaling up - large systems and efficiency, and evaluation of Java programs
Subject-specific Skills
Key Skills
Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module
Teaching Methods and Learning Hours
| Activity | Number | Frequency | Duration | Total Hours | Attendance Monitored |
|---|---|---|---|---|---|
| Lectures | 20 | 5 in week 1, 15 in week 2 | 1 hour | 20 | |
| Tutorials | 4 | weekly | 1 hour | 4 | |
| Seminars | 3 | 1 per week in weeks 1,3,4 | 1 hour | 3 | |
| Practical | 5 | daily in week 1 | 6 hours | 30 | |
| Laboratory | 10 | daily in weeks 3,4 | 6 hours | 60 | |
| Directed reading | 33 | ||||
| Total | 150 | ||||
Summative Assessment
| Component | Component Weighting | Element | Length/Duration | Element Weighting | Resit Opportunity |
|---|---|---|---|---|---|
| Laboratory report | 100% | Laboratory report | equivalent to 2500 words | 100% |
Formative Assessment
Staged written feedback of practical work by staff/demonstratots. Level of success in practical programming exercises, using written feedback from demonstrators.
Students who do not attend monitored activities shown under Teaching Methods
and Learning Hours, or who fail to complete the summative or formative
assessment(s) specified above, may be subject to the Academic Progress
procedures defined in the University's General Regulation V, and may be
required to leave the University.