Validation phase
Value:17%
Due date:
24-May-2018
Length:Word length1800 to 2000
Submission method options
Alternative submission method
Task
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 : 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, identify3 (three) most importantuse 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 (Learning outcome 1)
• Converting design diagrams into program code (Learning outcome 8)
• Preparing project documentation (Learning outcome 4 - 6)
• Developing presentations, and through peer review to reflect on their own practice and improve their design (Learning outcome 8)
Marking criteria
Criteria
|
Requirement
|
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
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.
(8 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:
All possible use cases of the subsystem are identified; developed communication or sequence diagrams are correctly showing logical flow of the system activities, input/output messages, and accurate symbols/notations.
|
Submit a proper documentation describing the different aspect of developed component, within 2000 words.
(5 Marks)
|
Comprehensive documentation which describes each component of developed system and has insights and awareness of deeper more subtle aspects of the case study.
|
Clarity of expression, presentation and referencing.
(4 Marks)
|
Fluent writing style appropriate to assessment task type. Grammar and spelling accurate.
Referencing is mainly accurate and according to the APA standard. All references are cited in the text
|
Presentation
Reports should be submitted is MS Word format, using the CSU referencing style of APA.
Diagrams can be created using any available tools.\
Requirements
Students should visit and read the CSU Referencing Policy at http://student.csu.edu.au/study/referencing-at-csu