CSC 186 – OBJECT ORIENTED PROGRAMMING

SEMESTER MARCH – AUGUST 2021

ASSIGNMENT DESCRIPTION

1. Instructions:
o Please follow the requirements and submission date accordingly.

Tasks Requirement Submission Date

Phase 1: o Submit a proposal to suggest a o Week 4
Proposal suitable case for object & class. o Group Work - A group
o Class selection must be related to the project must consist of
following themes: TWO to THREE
- Banking – customer information, persons.
account activities, payments, o You will be given
deposits, loan, etc. feedback on suitability
- Airlines – reservation and of the proposed class.
schedule information
- Universities – student
information, course registrations,
colleges and grades
- Telecommunication – keep call
records, monthly bills,
maintaining balances, etc.
- Finance – storing information
about stock, sales and
purchases of financial
instruments like stock and
bonds.
- Sales – storing customer,
product and sales information
- Manufacturing – tracking
production of items, inventories
status in warehouse, etc.
- HR Management – information
about employees, salaries,
payroll, deduction, generation of
paychecks, etc.

o Your proposal should have:

- Introduction: highlighting on
what is the project is about
- Objectives: project
achievement (apply the SEVEN
basic algorithms: minimum,
maximum, counter, total,
average, sorting and searching),
e.g. to find the highest price, to
search staff ID, etc.
- Class design: list all the
suitable attributes and method
for the proposed class
 Tasks Requirement Submission Date
Phase 2: o Design the solution for the above o Week 7
Model Solution proposed scenario using UML o You will be given
Using UML diagram: feedback on suitability
- Use case diagram of the proposed
- Class diagram solution.

Phase 3: o From proposal and phase 2 o Week 10

Concept of feedbacks, implements your proposed
Classes and class (both proposed & test class)
File IO o The proposed class should have:
- Default and normal constructors
- Mutator methods
- Accessor methods
- At least one processor method (for
calculation)
- toString() or display method
o Once you have completed the proposed
class definition, then write the code for
the application(test) class where an
array of objects is declared. The
application is designed to test ALL
methods in the class that you have
written previously. The program must
include the implementation of basic
algorithms; maximum, minimum,
counting, total, average and searching.
Include File IO in your test class. Use
your own creativity on implementing
the input and output file

2. Documentation

a) Phase 1: Proposal Guidelines

• The cover should contain:
 Course code and name of subject (E.g.: CSC186 Object Oriented
Programming)
 Course Group (E.g.: JCS1102A)
 Project Title (E.g.: Student Information Management System – SIMS)
 Title of Report (E.g.: Project Proposal)
 Group members name with student ID
 Lecturers name
 Submission date: Will be informed by your lecturer
• Format Content:
 Introduction
 Objectives
 Class Design
• Report must be written in Arial font, size 11, 1.5-line spacing

CSC186 Project/March – August 2021

b) Phase 2: Model Solution Using UML
• The cover should contain:
 Course code and name of subject (E.g.: CSC186 Object Oriented
Programming)
 Course Group (E.g.: JCS1102A)
 Project Title (E.g.: Student Information Management System – SIMS)
 Title of Report (E.g.: Project Proposal)
 Group members name with student ID
 Lecturers name
 Submission date: Will be informed by your lecturer
• Format Content:
 Introduction
 Objectives
 Proposed Solution using UML Diagram
a) Use Case Diagram (a representation of a user's interaction with the
system) and the explanation about the diagram.
b) Class Diagram (describe systems by illustrating attributes, operations and
relationships between classes) and the explanation about the diagram.
 Report must be written in Arial font, size 11, 1.5-line spacing
 UML diagrams should be designed using appropriate tools such as draw.io.

c) Phase 3: Final Report

• The cover should contain:
 Course code and name of subject (E.g.: CSC186 Object Oriented
Programming)
 Course Group (E.g.: JCS1102A)
 Project Title (E.g.: Student Information Management System – SIMS)
 Title of Report (E.g.: Project Proposal)
 Group members name with student ID
 Lecturers name
 Submission date: Will be informed by your lecturer
• Format Content:
 Introduction
 Objectives
 UML Diagram - Use Case and Class Diagram
 Source code for all classes - Every statement should have comments indicating
its purpose.
 Sample of input and output (Input and Output Files)
- Program testing should use fictitious data and should provide at least 10
samples of input.
 Conclusion
• Report must be written in Arial font, size 11, 1.5-line spacing.
• Source code must be written in Courier New font, size 11, and ALL with single
spacing.
• UML diagrams should be designed using appropriate tools such as draw.io.

CSC186 Project/March – August 2021

3. Rubrics

Assignment Rubric
Proposal
Tasks 1 2 3 Weight Total
Good class
Not an
selection but too Good selection
Class selection appropriate class 2 6
simple without and well thought
selection
careful thought
Good and
Attributes are not Appropriate but
Attributes appropriate 2 6
appropriate incomplete
attributes
Good method
Not an
selection but too Good selection
Methods appropriate 2 6
simple without and well thought
method selection
careful thought
Very late without
Late with
Submission reasonable Right on time 2 6
acceptable reason
excuse
UML Diagram
Tasks 0 1 2 Weight Total
Use Case Not exist Exist but
Complete 2 4
Diagram incomplete/incorrect
Not exist Exist but
Class Diagram Complete 2 4
incomplete/incorrect
Class Design
Tasks 0 1 2 Weight Total
Exist but
Constructor Not exist Complete 2 4
incomplete/incorrect
Exist but
Accessors Not exist incomplete/incorrect Complete 1 2

Exist but
Mutator(s) Not exist incomplete/incorrect Complete 1 2

Exist but
Processor(s) Not exist incomplete/incorrect Complete 2 4

Exist but
toString() Not exist incomplete/incorrect Complete 1 2

Main/Test Class
Tasks 0 1 2 Weight Total
Exist but
Array
Not exist incomplete/incorrect Complete 2 2
declaration
Exist but
Object creation Not exist incomplete/incorrect Complete 2 4

Exist but
Input & Output
Not exist incomplete/incorrect Complete 2 4
File creation
Exist but
Input File
Not exist incomplete/incorrect Complete 3 6
Process

CSC186 Project/March – August 2021

 Exception Exist but
Handling Not exist incomplete/incorrect Complete 1 2

Input/Output Exist but

File Not exist incomplete/incorrect Complete 2 4

Overall
Tasks 1 2 3 Weight Total
Executed and
Overall Program failed to Executed with output displayed
3 9
Execution execute inaccurate output correctly

Very late without

Late with
Timeliness reasonable Right on time 2 6
acceptable reason
excuse
Not compliance
Comply with project Exceed project’s
Completeness with the project 2 6
description expectation
description
Class diagram
Class diagram is uses UML
missing some correctly to
obvious classes depict the
Class diagram
that should be classes in the
UML Class very poorly
present. Class right format. All 2 6
Diagram reflects the rest of
diagram doesn't classes that are
the design.
correctly depict needed are
relationships among present, and the
classes. level of detail is
acceptable.
Format and
Format and content
Did not follow the content
Report 70% according to 3 9
guideline given. according to the
the guideline given.
guideline given.

TOTAL MARKS
104

CSC186 Project/March – August 2021