CA314 COURSE MATERIALS (2009-2010)

 

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 2008-2009. However, there will be some additional examples & some re-arrangement in the order of presentation etc.

 

Course notes:

Some reference material:

                        OMG Unified Modeling Language Specification Version 1.5

            Figures in Stevens & Pooley Book

1. INTRODUCTION (Here)

2. INTRODUCTORY CASE STUDY (Here)

3. UML Class Models Essentials (Here)

4. UML USE CASE Models (Here)

5. TEST CASES based on USE CASEs (Here)

6. UML INTERACTIONS (Here)

7. UML STATE & ACTIVITY DIAGRAMS (Here)

8. MORE ON CLASS MODELS (Here)

9. IMPLEMENTATION MODELS & DIAGRAMS etc (Here)

                        (Example protocol state machine, to define usage of a component)

10. MORE ON TESTING etc (Here)

Code inspection procedure - Example

11. CONCLUDING CASE STUDY

            Requirements

            Design

            Note that, for assessment purposes, familiarity with the detail of section 11 is not expected. The purpose is to provide an example of a fairly complete set of requirements and corresponding design, plus an approach to documenting these. The example illustrates the notion and use of framework classes. Use is also made of some design patterns; however, we have not had time to present these so knowledge of them is not expected (anyone interested can find definitions on the internet).

Continuous Assessment:

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 the pass mark of 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 those of the current DCU’s “Marks & Standards” namely that the module mark is a simple weighted average of the continuous assessment mark and the final examination mark. There are NO thresholds in either continuous assessment or examination that a student has to achieve other than an overall module mark of 40.

 

b) Details of the continuous assessment assignment:

- This year there is a single project assignment to be carried out separately by different groups and reported on throughout the semester. The assignment is detailed here (MS word format).

Note: The project group memberships and provisional marks appear here.

Note (added Oct. 27): The project presentations, scheduled for Tuesday December 15th as mentioned in section 2 (page 7) of the assignment specification, will take place in L114 from 13.00 to 17.00.

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 (TBD)