CA314
COURSE MATERIALS (2008-2009)
N.B.: There will be some modifications in the course content compared
to that given in the module specification on the Computing School web pages.
Notes:
1. While much of course material is/will be on the web, some notes will be distributed in hard copy at lectures.
2. Also, additions and adjustments of the on-line material may be made during lectures.
3. A good deal of the material is as for
2007-2008. However, there will be some re-arrangement in the order of
presentation as well as in the content of the later parts.
Course notes:
Some reference material:
OMG Unified Modeling Language Specification Version 1.5
Figures in Stevens & Pooley Book
A. OVERVIEW, including outline of UML:
B. INTRODUCTORY CASE STUDY, including class & use case models, sequence & state diagrams etc; requirements:
Main material (pdf) [Won’t go through line by line in notes!]
Some indicative requirement stuff on web
C. ELEMENTS OF UML (including notes on corresponding SW development activities & processes)
C.1.A Class Models (chapter 5 of text): Class model essentials, Supplementary notes
C.2 Use Case Models (chapters 7 & 8 of text): Use case models
Note: Covered D.1 (see below) at this point of lectures
C.3 Interaction Diagrams (chapters 9 & 10 of text): Interaction diagram essentials and more
C.4 State & Activity diagrams (Chapters 11 & 12 of text): Essentials and more; Note on Harel state-charts
C.1.B Class Models (chapter 6 of text): More on Class Models, Re interfaces etc
C.5 Implementation diagrams, Packages etc (Chapters 13 & 14 of text)
D. Aspects of software
Verification, Especially testing
D.1 Generating test cases from use cases: Heumann’s approach
D.2 Classic Testing Summary , Cobertura (example test coverage tool) & Outline of issues in OO testing
D.3 Some specific details (N.B.: Some materials will be handed out in hard copy at lectures and will not appear on this web-page)
D.4 Summary of structural test features for given example.
E. Simple Framework Example
Continuous Assessment:
NOTE FOR REPEATS
(dated June 25th, 2009): Any repeat continuous assessment work should
be submitted by August 21st, 2009, at the latest. The submission should
be in a clearly labelled (Lecturer name, Module identifier, Student name & number,
etc) large envelope and should be handed in to the School Office. After handing
in the submission, the student should send an email to W.G. Tuohey informing him
of the fact. The repeat continuous assessment work is the same as that originally
specified.
a) General
In this module there are 75 marks for the final examination and 25 marks
for the continuous assessment.
Most students will pass both parts individually and so will automatically pass the complete module (i.e. achieve 40% or more). (Of course, usually, a lot of students achieve honours!).
However, for whatever reason, a student may fail one part and so the question arises whether that student can still pass overall. The rules for this situation in CA314 are
(1) At least 30% must be obtained in the failed part (i.e. at least 7.5/25 in continuous assessment; at least 22.5/75 in exam).
And
(2) Enough marks must be obtained in the passed part to ensure that the total marks add up to at least 40%.
(For example, an exam mark of 30% could be “brought up” by a continuous
assessment mark of 70% as 30x0.75 + 70x0.25 = 22.5 + 17.5 = 40).
b) Details of
the continuous assessment assignment:
- This year there
is a single project assignment to be carried out and reported on throughout the
semester. The assignment is detailed in two documents as follows:
I. Statement of
work for the assignment
II. Software requirements
specification for the assignment
Note: The project group memberships are here.
c) Plagiarism
University and School of Computing rules on plagiarism will be strictly applied. In particular, careful reference should be made to any material used that is not a team’s own work.
d) Provisional continuous assessment marks