# validate your system designs, computer science homework help

In this assignment, you are required to complete the followings 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, within 2000 words.

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 chosen case study. You have an option to use any object-oriented programming language such as C++, Java, C#, etc. to develop this subsystem.

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 chosen case study. To do this, identify 3 (three) most important use cases for the subsystem and develop communication diagrams or sequence diagrams for these use cases.

Rationale

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.

Marking criteria

Criteria |
HD |
DI |
CR |
PS |
FL |

Task 1 (70%): 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 chosen case study. You have an option to use any object-oriented programming language such as C++, Java, C#, etc. to develop this subsystem. OR Task 2 (70%): 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 chosen case study. To do this, identify all possible use cases for the subsystem and develop communication diagrams or sequence diagrams for these use cases. |
Task 1: OR Task 2: |
Task 1: OR Task 2: |
Task 1: OR Task 2: |
Task 1: OR Task 2: |
Task 1: OR Task 2: |

Task 1 & Task 2 (30%) |
Task 1 & Task 2: Comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study. |
Task 1 & Task 2: Mostly comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study. |
Task 1 & Task 2: Mostly comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study. |
Task 1 & Task 2: Reasonable documentation describes few components of developed system. |
Task 1 & Task 2: Documentation is wrong and not matching with system components. |

Presentation

Reports should be submitted is MS Word format, using the CSU referencing style of APA.

Diagrams can be created using any available tools.