Assessment rubric for course code : CSC186

CSC186 : UML DIAGRAM, CONCEPT OF CLASSES 1, CONCEPT OF CLASSES 2 AND FILE INPUT OUTPUT (10%)
Group Project Presentation
Week 10

CLO 2 : Demonstrate effective interpersonal skills through OOP projects. (PLO4, A3)
PLO 4 : Demonstrate interpersonal skills for the well-being of society.

Requirements:

1. Using a tool to create presentation slides such as Microsoft Power Point, Canva, Prezi etc.

2. Presentation Criteria.
a) Knowledge
b) Contributions
c) Problem-solving
d) Attitude
e) Confidence
f) Working with others
g) Teamwork

Rubric : Presentation

Category Poor (1) Good (2) Very Good (3) Excellent (4)

Shows inconsistent and Demonstrates a basic Demonstrates an excellent

Shows little evidence of
Knowledge unreliable evidence of understanding of and is understanding and
an understanding.
understanding. able to explain well. explanation.
 Each of group member Each of group member Each of group member is
Each of group member
rarely provides useful sometimes provides excellent and provide a lot
usually provides useful
Contributions ideas when participating useful ideas when of effort to give useful
ideas when participating
in the presentation. May participating in the ideas when participating in
in the presentation.
refuse to participate. presentation. the presentation.

Does not try to solve Does not suggest or

Actively looks for and
problems or help others refine solutions but is Refines solutions
Problem-solving suggests solutions to
solve problems. Let’s willing to try out solutions suggested by others.
problems.
others do the work. suggested by others.

Sometimes try to explain

Usually try to explain and Most of the time help
Does not try to explain and help others to
help others. Often shows others. Always has a
Attitude or help others to answer answer the question.
a positive attitude about positive attitude about the
any question. Shows positive attitude
the task. task.
about the task.

Shows less negative

Positive body language.
Does not believe in body language and most
Positive approach to Believes strongly in self
Confidence oneself. Negative body of the time doesn't
answer the question. and can explain correctly
language. answer the question
with high confidence.
confidently.

Usually listens to, shares, Almost always listens to,

Rarely focuses on the Often listens to, shares with and supports the shares with, and supports
Working with others task and what needs to with, and supports the efforts of others. Does the efforts of others. Tries
be done. efforts of others. not cause any problem in to keep people working
the group. well together.
 1. The project was 1. The project was 1. The project was carried 1. The project was carried
carried out by more than carried out by more than out by more than TWO out by more than TWO
TWO members. 2.
TWOThemembers.
workload and members. members.
variety on each member
2. The workload and does not seem to be fair 2. The workload and 2. The workload and
variety on each member or at least one member variety on each member variety on each member
is poor. has been assigned non- seems good. seems excellent.
technical tasks (e.g.
3. Leadership
writing role by
the report).
3. Leadership role by 3. Leadership role by 3. Leadership role by each
each member for
each member for each member for different member for different task
different tasks is NOT
different tasks is poor. task is NOT clear. is evident.
apparent.
4. Application program
4. Apply all requirements 4. Apply all requirements 4. Apply all requirements
is not complete and
Teamwork in application program in application program in application program with
apply only a few
with satisfactory level. with good level. excellent level.
requirements.

5. No presentation flow, 5. Satisfactory

5. Good presentation with 5. Excellent presentation
over time limit and does presentation with
explanation and use time with explanation and use
not fully cover all insufficient elaboration
wisely. time wisely.
requirements. and use of time.

Total mark : 28 marks

 Assessment rubric for course code : CSC186

CSC186 : UML DIAGRAM, CONCEPT OF CLASSES 1, CONCEPT OF CLASSES 2, FILE INPUT OUTPUT, INHERITANCE AND/OR POLYMORPHISM (25%)
Group Project (Final Report)
Submission : Week 14

CLO 3 : Display digital skills in the applications of OOP features and UML. (PLO6, P2)
PLO 6 : Demonstrate digital skills in a broad range of digital technologies.

Requirements:

Each group is required to develop a Java application by applying UML diagram, File Input Output, Concept of classes, Inheritance and Polymorphism. Please ensure you fulfill all
requirements below in order to be graded.

1. Using tool to draw UML Diagrams such as ArgoUML, Lucidchart, UMLet, draw.io, etc.
2. Using tool to develop Java program such as Textpad, BlueJ, NetBeans and Eclipse.
3. Using word processor to produce a report such as Microsoft Word, Word Perfect, Google Docs etc.

4. UML Diagram.
a) Class diagram
Maximum 4 classes.
Minimum 2 attributes.
Minimum 2 methods.
Minimum two relationships (inheritance and composition/aggregation)

b) Use Case diagram

1 actor only.
Minimum 3 use cases.
Include relationship (inclusion or/and extension).

5. Process/System requirements.
a) Create class definition for superclass, subclasses and related classes.
b) Read data from input file.
c) Store data into array of object.
d) Edit existing data (update).
e) Perform a minimum of 3 tasks to objects applying inheritance and/or polymorphism.
f) Perform calculation.

6. Report.
a) Front cover and Table of Content.
b) Organizational structure.
c) Introduction.
d) Objectives.
e) Scope
f) UML Class Diagram and Use Case Diagram
g) Input file.
h) Class definition for all classes.
i) Class application.
j) Output file or/and sample interface.
k) Reference.

Rubric : UML Diagram

Category Poor (1) Fair (2) Good (3) Very Good (4) Excellent (5)
Class Diagram

Correct class
Correct class diagram, Very good, correct class
Incorrect shape of class diagram and Excellent and perfect
somewhat relevant class diagram, relevant class
Class diagram diagram and incorrect somewhat class diagram with 4
name and follow name and follow
class name. relevant class classes.
convention name. convention name.
name.

Excellent and
Incorrect syntax, appropriate attributes
Incorrect syntax, not Good, correct syntax,
somewhat Very good, correct syntax, provided. Exist suitable
Attribute relevant and not somewhat relevant and
relevant and relevant and organized. composite object as an
organized. organized.
organized. attribute. More than 2
attributes.

Excellent and
Incorrect syntax,
Incorrect syntax, not Good, Correct syntax, appropriate methods
somewhat Very good, correct syntax,
Method relevant and not somewhat relevant and provided. Exist
relevant and relevant and organized.
organized. organized. overloading method.
organized.
More than 2 methods.

Correct
Very good, correct
Incorrect relationship relationship type, Good, correct relationship Excellent and perfect
relationship type, correct
type, wrong connection wrong connection type, correct connection relationship. Multiplicity
connection line and
Relationship line and no relation of line and no line and no relation of and roles are also
provide relation of
attributes between relation of attributes between provided. More than two
attributes between
classes. attributes classes. relationships.
classes.
between classes.

Use Case Diagram

Excellent and perfect

Correct shape
Correct shape, somewhat Very good, relevant actor actor. Include actor to
Incorrect shape and and somewhat
Actor relevant actor name and name and follow actor relationship
incorrect actor name. relevant actor
follow convention name. convention name. (generalized and
name.
specialized actor)

Correct shape, Good, correct shape, Excellent and

Incorrect shape, not Very good, correct shape,
somewhat somewhat relevant and appropriate use cases
Use Case relevant and not relevant and organized.
relevant and organized. Number of use provided. Number of use
organized. Number of use cases is 4.
organized. cases is 3. case is more than 4.
 Incorrect
Very good, correct
Incorrect relationship relationship type Good, correct relationship Excellent and perfect
relationship type, correct
Relationship type and wrong and somewhat type, correct connection relationship. Exist
connection line. Exist
connection line. correct line. inclusion and extension.
inclusion or extension.
connection line.

Total mark : 35 marks

Rubric : Process/System.

Category Poor (1) Fair (2) Good (3) Very Good (4) Excellent (5)

Correct defined
with related
Good and correct Very good and correct
Incorrect defined. superclass and
Class definition for defined. Some attributes defined. Most attributes Excellent and perfect
Subclasses are not subclass name.
superclass and subclass. and methods are not and methods use concept superclass and subclass.
related to superclass. Attributes and
applying reusability. of reusability.
methods are not
well defined.

Correct formatted Good and correct Very good, correct Excellent and
and match with formatted. The formatted. Successfully successfully store data
Read data from input file and Incorrect format of input
class definition of application can store data into array of into array of object using
store into array of object. file.
superclass and successfully read data object using inheritance or inheritance and/or
subclass. from input file. polymorphism. polymorphism.

Good, data are not Excellent, provide user

No required process Contain major Very good and display
Edit existing data (update). updated and saved input for update and
applied. code error. confirmation message.
properly. confirmation message.

Perform all tasks Excellent and provide

Perform 2 task
Perform a minimum of 3 No required process Perform 1 task successfully, relevant and more tasks than
successfully and relevant
tasks. applied. successfully. display confirmation required. Task similar
process.
message. with use cases.

Perform calculation to
Perform calculation to
Perform Perform calculation to many objects using
No required process many objects using
Perform calculation calculation to one one object using inheritance and/or
applied. inheritance and/or
object. inheritance. polymorphism. Display
polymorphism.
appropriate message.

Total mark : 25 marks.

Rubric : Report

Category Poor (1) Fair (2) Good (3) Very Good (4) Excellent (5)
 Incomplete front Complete front cover. All
Front cover & Table of No front cover and no cover and no page numbers being
NA NA
Content page numbers listed. page number entered accordingly in
listed. table of content.

Describe the
Fair
organizational structure
organizational Good organizational Very good organizational
Poor organizational of the project team and
structure of the structure of the project structure of the project
Organizational structure structure of the project group members’ formal
project team. One team with their job team with their detail job
team. pictures and their
of the member description. description.
responsibilities with
does not exist.
perfect job description

Excellent description and

Good description and
Satisfactory description many clear & creative
Fair description many clear ideas. Include
Poor description and no and a few of clear ideas. ideas. Include current
Introduction and lack of clear current process, proposed
clear ideas. Include current process process, proposed
ideas. process and calculation
and proposed process. process, calculation
formula.
formula with examples.

One/ two Three objectives with

Objectives are not Two objectives with Two objectives with good
Objectives objective(s) with excellent and concise
relevant at all. satisfactory explanation. explanation.
no explanation. explanation.

Excellent description and

Satisfactory description Good description and
many clear & creative
Fair description and a few of clear ideas. many clear ideas. Include
Poor description and no ideas. Include 4 class
Scope and lack of clear Include 4 class diagram, 4 class diagram, 1 actor,
clear ideas. diagram, 1 actor, more
ideas. 1 actor and minimum 3 minimum 3 use cases and
than 3 use cases and
use cases. relationship.
relationship

UML Class Diagram and Use

Refer to the above UML diagram rubric
Case Diagram

Contain enough data as Contain enough data,

Contain enough data and
required in class complete, excellent and
Contain lack of complete. Include correct
Input File Not exist. definition. Does not well used. Include
data. data as required for
include correct data as correct data as required
Inheritance.
required for Inheritance. for Inheritance
 Excellent and well used
Does not apply
Class definition of Apply few features of Apply few features of the features of
features of
Inheritance, Polymorphism Not exist inheritance (reusability) inheritance (reusability) inheritance (reusability)
inheritance
and related classes with ONE (1) subclass with TWO (2) subclasses with TWO (2)
(reusability)
subclasses.

Excellent, well and

Good used of array of Very good used of array of
creative used of array of
Apply array of object to apply object to apply inheritance
Does not apply array of object to apply
Class application object without inheritance with ONE (1) with TWO (2) arrays of
object. inheritance with TWO (2)
inheritance. arrays of object for the object for each
arrays of object for each
subclass. subclasses.
subclasses.

Output file with no Excellent and creative

Good output and Very good output and
Output File or/and sample No output file or/and relevant data output and interface.
interface. Display interface. Display
interfaces interface. or/and interface is Exist both console
appropriate message. appropriate message.
not related. window and dialog box.

More than one

References One reference. NA NA NA
reference.

Total mark : 45 marks.

Grand total : 105 marks.

 Assessment rubric for course code : CSC186

CSC186 : UML DIAGRAM, CONCEPT OF CLASSES 1, CONCEPT OF CLASSES 2, FILE INPUT OUTPUT, INHERITANCE AND/OR POLYMORPHISM (5%)
Group Project (Progress Report)
Submission : Week 6

CLO 3 : Display digital skills in the applications of OOP features and UML. (PLO6, P2)
PLO 6 : Demonstrate digital skills in a broad range of digital technologies.

Requirements:

Each group is required to develop a Java application by applying UML diagram, File Input Output, Concept of classes, Inheritance and Polymorphism. Please ensure you fulfill all requirements
below in order to be graded.

1. Using tool to draw UML Diagrams such as ArgoUML, Lucidchart, UMLet, draw.io, etc.
2. Using tool to develop Java program such as Textpad, BlueJ, NetBeans and Eclipse.
3. Using word processor to produce a report such as Microsoft Word, Word Perfect, Google Docs etc.

4. UML Diagram.
a) Class diagram
Maximum 4 classes.
Minimum 2 attributes.
Minimum 2 methods.
Minimum two relationships (inheritance and composition/aggregation)

b) Use Case diagram

1 actor only.
Minimum 3 use cases.
Include relationship (inclusion or/and extension).

5. Report.
a) Front cover and Table of Content.
b) Organizational structure.
c) Introduction.
d) Objectives.
e) Scope
f) UML Class Diagram and Use Case Diagram

Rubric : UML Diagram

Category Poor (1) Fair (2) Good (3) Very Good (4) Excellent (5)
Class Diagram

Correct class
Correct class diagram, Very good, correct class
Incorrect shape of class diagram and Excellent and perfect
somewhat relevant class diagram, relevant class
Class diagram diagram and incorrect somewhat class diagram with 4
name and follow name and follow
class name. relevant class classes.
convention name. convention name.
name.

Excellent and
Incorrect syntax, appropriate attributes
Incorrect syntax, not Good, correct syntax,
somewhat Very good, correct syntax, provided. Exist suitable
Attribute relevant and not somewhat relevant and
relevant and relevant and organized. composite object as an
organized. organized.
organized. attribute. More than 2
attributes.

Excellent and
Incorrect syntax,
Incorrect syntax, not Good, Correct syntax, appropriate methods
somewhat Very good, correct syntax,
Method relevant and not somewhat relevant and provided. Exist
relevant and relevant and organized.
organized. organized. overloading method.
organized.
More than 2 methods.

Correct
Very good, correct
Incorrect relationship relationship type, Good, correct relationship Excellent and perfect
relationship type, correct
type, wrong connection wrong connection type, correct connection relationship. Multiplicity
connection line and
Relationship line and no relation of line and no line and no relation of and roles are also
provide relation of
attributes between relation of attributes between provided. More than two
attributes between
classes. attributes classes. relationships.
classes.
between classes.

Use Case Diagram

Excellent and perfect

Correct shape
Correct shape, somewhat Very good, relevant actor actor. Include actor to
Incorrect shape and and somewhat
Actor relevant actor name and name and follow actor relationship
incorrect actor name. relevant actor
follow convention name. convention name. (generalized and
name.
specialized actor)

Correct shape, Good, correct shape, Excellent and

Incorrect shape, not Very good, correct shape,
somewhat somewhat relevant and appropriate use cases
Use Case relevant and not relevant and organized.
relevant and organized. Number of use provided. Number of use
organized. Number of use cases is 4.
organized. cases is 3. cases is more than 4.

Incorrect
Very good, correct
Incorrect relationship relationship type Good, correct relationship Excellent and perfect
relationship type, correct
Relationship type and wrong and somewhat type, correct connection relationship. Exist
connection line. Exist
connection line. correct line. inclusion and extension.
inclusion or extension.
connection line.
Total mark : 35 marks

Rubric : Report

Category Poor (1) Fair (2) Good (3) Very Good (4) Excellent (5)

Incomplete front Complete front cover. All

Front cover & Table of No front cover and no cover and no page numbers being
NA NA
Content page numbers listed. page number entered accordingly in
listed. table of content.

Describe the
Fair
organizational structure
organizational Good organizational Very good organizational
Poor organizational of the project team and
structure of the structure of the project structure of the project
Organizational structure structure of the project group members’ formal
project team. One team with their job team with their detail job
team. pictures and their
of the member description. description.
responsibilities with
does not exist.
perfect job description

Excellent description and

Good description and
Satisfactory description many clear & creative
Fair description many clear ideas. Include
Poor description and no and a few of clear ideas. ideas. Include current
Introduction and lack of clear current process, proposed
clear ideas. Include current process process, proposed
ideas. process and calculation
and proposed process. process, calculation
formula.
formula with examples.

One/ two Three objectives with

Objectives are not Two objectives with Two objectives with good
Objectives objective(s) with excellent and concise
relevant at all. satisfactory explanation. explanation.
no explanation. explanation.

Excellent description and

Satisfactory description Good description and
many clear & creative
Fair description and a few of clear ideas. many clear ideas. Include
Poor description and no ideas. Include 4 class
Scope and lack of clear Include 4 class diagram, 4 class diagram, 1 actor,
clear ideas. diagram, 1 actor, more
ideas. 1 actor and minimum 3 minimum 3 use cases and
than 3 use cases and
use cases. relationship.
relationship

UML Class Diagram and Use

Refer to the above UML diagram rubric
Case Diagram

Total mark : 23 marks.

Grand total : 58 marks.