Coursework Report Template COMP1752 - 1819 2

COMP1752 – Object-Oriented
Programming
[Your name or enrolment number]

[Date]
Page 0 of 11
Table of Contents
1 Introduction ............................................................................................................................. 3
2 Class Diagram ......................................................................................................................... 4
2.1 The Class Diagram ........................................................................................................... 4
2.2 A Brief Explanation of the Diagram ................................................................................ 4
3 The Code for the Extra Classes Created ................................................................................. 5
3.1 Class … ............................................................................................................................ 5
3.2 Class … ............................................................................................................................ 5
3.3 Class … ............................................................................................................................ 5
3.4 Class … ............................................................................................................................ 5
4 White Box Testing .................................................................................................................. 6
4.1 Testing for class … .......................................................................................................... 6
5 Screen Shots of the Program Working.................................................................................... 7
5.1 Screen 1 - … ..................................................................................................................... 7
5.2 Screen 1 – A brief description .......................................................................................... 7
5.3 Screen 2 - … ..................................................................................................................... 7
5.5 Screen 3 - … ..................................................................................................................... 7
6 The Evaluation ........................................................................................................................ 8
6.1 What went well? ............................................................................................................... 8
6.2 What went less well? ........................................................................................................ 8
6.3 What was learned? ........................................................................................................... 8
6.4 How would a similar task be completed differently? ....................................................... 8
6.5 How could the course be improved? ...............................Error! Bookmark not defined.
7 Self-Grading ............................................................................................................................ 9
Page 1 of 11
Page 2 of 11
1 INTRODUCTION
Please note that this report should only include the extra work completed for the coursework and
not the work carried out for the lab sessions as required in the weekly tasks. Here, you’re
expected to introduce the application you’ve produced the features you’ve implemented as well
as the one you developed during the hackathon. (200-300 words)
Page 3 of 11
2 CLASS DIAGRAM
Include a UML class diagram showing all the classes that you have implemented and the
relationship between them. Your narrative for section 2.2 should also describe the design
decisions you made and the OOP techniques used (200-400 words).
2.1 THE CLASS DIAGRAM
2.2 A BRIEF EXPLANATION OF THE DIAGRAM
Page 4 of 11
3 THE CODE FOR THE EXTRA CLASSES CREATED
Add the code you have written for each of the classes implemented here. Copy and paste relevant
code - actual code please, not screen shots! Make it easy for the tutor to read. Add explanation if
necessary – though your in-code comments should be clear enough. Please DO NOT just DUMP
all the code you’ve written! Include and describe the bits that specifically implement the features
actually implemented.
3.1 CLASS …
3.2 CLASS …
3.3 CLASS …
3.4 CLASS …
Page 5 of 11
4 WHITE BOX TESTING
Design white box testing of your system (using a test table (test plan)) and provide evidence of
both the functionality of your program and the testing results.
4.1 TESTING FOR CLASS …
Page 6 of 11
5 SCREEN SHOTS OF THE PROGRAM WORKING
Provide screen shots that demonstrate the features that you have implemented. Give a brief
description for each (up to 100 words) to explain which features are being demonstrated. Make
sure that the screen shots make clear what you have implemented and achieved.
5.1 SCREEN 1 - …
5.2 SCREEN 1 – A BRIEF DESCRIPTION
5.3 SCREEN 2 - …
5.5 SCREEN 3 - …
Page 7 of 11
6 THE EVALUATION
Give a summary of the application and discuss what you would do if you had more time to work on
it. Answer the following questions for the reflection and write at least 400-500 words overall.
6.1 WHAT WENT WELL?
6.2 WHAT WENT LESS WELL?
6.3 HOW WOULD YOU RATE YOUR APPLICATION?
6.4 WHAT WAS LEARNED (TECHNICAL AND OTHERWISE)? COULD YOU APPLY WHAT YOU’VE LEARNED
TO OTHER PROJECT?
6.5 HOW WOULD A SIMILAR TASK BE COMPLETED DIFFERENTLY?
Page 8 of 11
7 SELF-GRADING
Please assess yourself objectively for each section shown below and then enter the total
mark you expect to get.
Viva 1 (5)
Not attended or no work demonstrated – 0
Work demonstrated was not up to the standard expected – 1 to 2
Work demonstrated was up to the standard expected – 3 to 4
Work demonstrated exceeded the standard expected – 5
Viva 2 (5)
Not attended or no work demonstrated – 0
Work demonstrated was not up to the standard expected – 1 to 2
Work demonstrated was up to the standard expected – 3 to 4
Work demonstrated exceeded the standard expected – 5
For this section I think I got: out of 10
Features implemented (15)

Required features (up to 10)
None of the required features implemented – 0
Partial implementation but with some bugs – 1 to 3
Partial implementation that is fully functioning – 4 to 6
All features implemented but with some bugs – 7 to 9
All features implemented and fully functioning – 10
Additional feature (implemented at hackathon) (up to 5)
None of the required features implemented – 0
Partial implementation but with some bugs – 1 to 2
Partial implementation that is fully functioning – 2 to 3
All features implemented but with some bugs – 3 to 4
All features implemented and fully functioning – 5
Professional programming style (5)

Coding (up to 2.5)
Indenting has not been used – 0
Indenting has been used occasionally – 0.5
Indenting has been used, but not regularly – 1
Indenting has been used regularly – 1.5 to 2
All code has been indented correctly – 2.5
Naming of variables, procedure and classes (up to 2.5)
Professional naming has not been used – 0
Professional naming has been used occasionally – 0.5
Professional naming has been used, but not regularly – 1
Professional naming has been used regularly – 1.5 to 2
All items have been named professionally correctly – 2.5
Page 9 of 11
Use of OOP techniques (40)
Abstraction (15)
No extra classes or objects have been created – 0
Classes and objects have been created superficially – 1 to 3
Classes and objects have been created and used correctly – 4 to 7
New and useful classes and objects have been created – 8 to 11
The use of classes and objects exceeds the specification – 12 to 15
Encapsulation (10)
No encapsulation has been used – 0
Class variables have been encapsulated superficially – 1 to 3
Class variables have been encapsulated correctly – 4 to 6
The use of encapsulation exceeds the specification – 7 to 10
Inheritance (10)
No inheritance has been used – 0
Classes have been inherited superficially – 1 to 3
Classes have been inherited correctly – 4 to 6
The use of inheritance exceeds the specification – 7 to 10
Polymorphism (5)
No polymorphism has been used – 0
A procedure has been polymorphised – 1
A procedure has been polymorphised and used appropriately – 2 to 3
The use of polymorphism exceeds the specification – 4 to 5
Testing (10)
Testing has not been demonstrated in the documentation – 0
Little white box testing has been documented – 1 to 3
White box testing has been documented for all the coursework – 4 to 6
White box testing has been documented for the whole program – 7 to 10
Evaluation (10)
No evaluation was shown in the documentation – 0
The evaluation shows a lack of thought – 1 to 3
The evaluation shows thought – 4 or 5
The evaluation shows clearly demonstrates increased awareness – 6 to 10
Documentation (10)
The documentation cannot be understood on first reading – 0
The documentation is readable, but a section(s) are missing – 1 to 3
The documentation is complete – 4 to 6
The documentation is complete and of a high standard – 7 to 10
I think my overall mark would be: out of 100
Page 10 of 11

Coursework Report Template COMP1752 - 1819 2

Uploaded by

Copyright:

Available Formats

Coursework Report Template COMP1752 - 1819 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Coursework Report Template COMP1752 - 1819 2

Uploaded by

Copyright:

Available Formats

COMP1752 – Object-Oriented

[Your name or enrolment number]

2.1 THE CLASS DIAGRAM

2.2 A BRIEF EXPLANATION OF THE DIAGRAM

4.1 TESTING FOR CLASS …

4.2 TESTING FOR CLASS …

4.3 TESTING FOR CLASS …

4.4 TESTING FOR CLASS …

5.2 SCREEN 1 – A BRIEF DESCRIPTION

5.4 SCREEN 2 – A BRIEF DESCRIPTION

5.6 SCREEN 3 – A BRIEF DESCRIPTION

6.1 WHAT WENT WELL?

6.2 WHAT WENT LESS WELL?

6.3 HOW WOULD YOU RATE YOUR APPLICATION?

6.5 HOW WOULD A SIMILAR TASK BE COMPLETED DIFFERENTLY?

Features implemented (15)

Professional programming style (5)

I think my overall mark would be: out of 100

You might also like