In the final phase of the project, you need to validate your system designs. You have the following two choices to develop detailed object-oriented design models. You also need to submit a proper documentation describing the different aspect of developed component using around 2000 words.
The students who have expertise in object-oriented programming are required to validate their system design through developing a prototype for at least one subsystem of JHC. You have an option to use any object-oriented programming language such as C++, Java, C#, etc. to develop this subsystem.
OR
The students who have no expertise in object-oriented programming are required to validate their system design using interaction diagrams (i.e., communication diagrams or sequence diagrams) for at least one subsystem of JHC.
The purpose of this assessment task is to develop student’s skills and knowledge in :
• validating an OO design through the construction of a prototype
• converting design diagrams into program code
• preparing project documentation
• developing presentations, and through peer review to reflect on their own practice and improve their design.
This assessment item links to the learning outcomes (LO) 1,2,3,4,5 and 6.
The tasks in this assessment involve a sequence of several steps and therefore you will be marked on the correctness of your answer as well as clear and neat presentation of your diagrams, where required.
Criteria | HD | DI | CR | PS | FL |
Task 1: The students who have expertise in object-oriented programming are required to validate their system design through developing a prototype for at least one subsystem of JHC. You have an option to use any object-oriented programming language such as C++, Java, C#, etc. to develop this subsystem.
16 Marks OR Task 2: The students who have no expertise in object-oriented programming are required to validate their system design using interaction diagrams (i.e., communication diagrams or sequence diagrams) for at least one subsystem of JHC. 16 Marks |
Task 1: Fully functional prototype using major principles of object-oriented programming such as encapsulation, data abstraction, polymorphism and inheritance. Each variable, function/method, loops, if/else statements, etc are well commented. OR Task 2: |
Task 1: Mostly fully functional prototype using major principles of object-oriented programming such as encapsulation, data abstraction, polymorphism and inheritance. Each variable, function/method, loops, if/else statements, etc are well commented. OR Task 2: |
Task 1: Mostly fully functional prototype using major principles of object-oriented programming such as encapsulation, data abstraction, polymorphism and inheritance. Each variable, function/method, loops, if/else statements, etc are well commented. Minor omission only OR Task 2: |
Task 1: Prototype not always functional using major principles of object-oriented programming such as encapsulation, data abstraction, polymorphism and inheritance. Each variable, function/method, loops, if/else statements, etc are not well commented. OR Task 2: |
Task 1: Prototype has major errors and not working. OR Task 2: |
Submit a proper documentation describing the different aspect of developed component.
6 Marks |
Comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study. | Mostly comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study. | Mostly comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study. Minor emission only |
Reasonable documentation describes few components of developed system. | Documentation is wrong and not matching with system components. |
Presentation and clarity (accuracy, spelling, grammar, punctuation)
2 Marks |
Fluent writing style appropriate to the assignment with accurate grammar and spelling. | Mostly Fluent writing style appropriate to assignment with accurate grammar and spelling. | Mostly fluent writing style appropriate to the assignment with mostly accurate grammar and spelling. Minor omissions only. | Writing style not always fluent or well organised and grammar and spelling contain errors. | Writing style not fluent or well-organised, and many grammatical and spelling mistakes. |
Referencing and Citation
1 Marks |
Referencing is mainly accurate and according to the APA standard. All references are cited in the text. | Referencing is mainly accurate and according to the APA standard. Most of the references are cited in the text. | Some attempt at referencing and according to the APA standard. Few references are cited in the text. | Attempt at referencing but not exactly according to APA standard and only few references are cited in the text. | Referencing is absent/ unsystematic. |
Reports should be submitted is MS Word format, using the CSU referencing style of APA.
Diagrams can be created using any available tools.