1005ICT Object Oriented Programming
Project (35%)
Due: 12AM (mid-night) on 26/09/2014 (Friday Week 13)
Email submission (See course profile regarding late submission policy).
[email protected]
Academic Misconduct policy: All programs will be compared with one another,
and any students involved in sharing programs will be penalized. Furthermore they
may receive a permanent record on their official university transcript and can also
be excluded from QIBT.
This document contains a single project worth 35 marks. The project
consists of a coding component and a written component (report). You
must submit both components in order to be eligible to pass.
Learning outcomes
This assessment item relates to the following learning outcomes:
1. Understand the concepts behind object-oriented programming;
2. Understand and create Unified Modeling Language class diagrams;
3. Understand the syntax and semantics of the Java programming language;
4. Understand and use the Java class library;
5. Design and apply reusable Java software components;
6. Effectively use Java to solve simple programming problems;
7. Use basic software engineering skills for designing, implementing, testing and
documenting small-sized programs using object-oriented programming.
Submission
Your digital submission should include the following
• All your JAVA source code (raw text JAVA files, zipped),
• A compiled version of your working program (all classes), and
• A written report (in PDF format, word doc will not be accepted)
JAVA Source Code
Your Java source code should be fully commented, including for each method, a
description and explanation of all, if any input arguments. The zip file must contain
everything required to rebuild your program elsewhere using the JAVA 1.7 JDK. If your
program includes any code segments written by someone else, then you must make clear
reference to it. Failing to clearly define these code snippets and their sources will be seen
as academic misconduct. Including third party code will impact on your mark, so it is
strongly encouraged that you reverse engineer and write your own version of any
unoriginal code.
1005ICT Object Oriented Programming ! ! ! 2014-02
Project! ! ! ! ! ! ! ! Page 1 of 6
Working Version of your Programs
A zip file containing all the classes and additional files (text files, image files, etc) required
to run your program. It should be assumed that your program will be run on a computer
that does not have the JDK installed. This should be attached to your submission. Make
sure that the program you submit, does in fact compile and run. So using version control is
important.
Written Report
Your submission must also include a written report in PDF format. Your report should
include the following:
• A description of the project (the requirements),
• A clear descriptive explanation of any algorithms used,
• A defense of your approach to addressing the requirements,
• mock-ups (not screen shots) of any windows you create;
• a paragraph that describes how each window is used by its intended user;
• A clear system analysis and design of your solution (UML diagrams, flowcharts,
etc)
• UML class design that shows how the classes in your program will relate to
each other.
• a UML class box that details the important attributes and methods in each new
class.
• Clear Flow charts showing the operation of main methods used in your
program.
• A clear description of the testing and validation procedures that were performed.
This will prove qualitative evidence that all the requirements were met.
• A closing statement about how you felt you addressed all the requirements, and
how the project turned out.
• You should mention any requirement you didn’t complete.
• You should also include a list of references (sites, books or journals you used
for help) and clearly show in your report how these references were used. It is
strongly encourage that you use APA referencing.
• Include clear instructions, for building and running your source code.
Marking Criteria
Written Documentation – 15 Marks
Java Source Code! – 9 Marks
– Properly comment and indented, and
– Matching the design outlined in the written report.
Function (how it runs)! – 6 Marks
Innovations (add-ons)! – 5 Marks
More detail regarding the level of competency required, is shown in the rubric on the
following page.
1005ICT Object Oriented Programming ! ! ! 2014-02
Project! ! ! ! ! ! ! ! Page 2 of 6
Detailed Marking Criteria
| Format / Presentation |
100% | 70% | 30% | 0% | |
| 4.0 Marks ____ / 4.0 |
All sections filled, correct APA referencing is used. Introduction is written in own words. |
All sections filled with appropriate material. |
Follows template but sections incomplete and used incorrectly. |
Doesn’t follow a logic layout. |
|
| System Analysis and Design |
100% | 60% | 40% | 10% | 0% |
| 6.0 Marks ____ / 6.0 |
Flowcharts and UML are correctly drawn. Easy to follow and show an easy translation to JAVA. Shows Top-Down design methodology. |
Proper use of symbols. Designs are neat and performs the basic function. However, missing detail. |
Design use the correct symbols, however does not perform the task required. |
Flowchart and UML symbols used incorrectly. |
Design is missing |
| Written Defense |
100% | 50% | 10% | 0% | |
| 5.0 Marks ____ / 5.0 |
Student’s report shows a clear understanding of the problem and an in-depth knowledge of the solution. |
Student has grasped the basic idea of the design. |
Students report contains very little explanation in the form of comments or solution. |
Student adds no independent interpretation of problem. |
|
| In Code Documentation |
100% | 80% | 60% | 30% | 0% |
| 4.0 Marks ____ / 4.0 |
Each methods contains a header, with post and pre conditions, numerous comments. |
Code is heavily commented, but no headers. |
Code has few comments, but no headers. |
Intermittent comments. |
No comments. |
| Coding Style | 100% | 60% | 10% | 0% | |
| 5.0 Marks ____ / 5.0 |
Clearly follows design. Has a focus on reusable , modular and readable code. Sensible variable names. |
Code resembles flowcharts and performs desired actions. |
Code performs task but shows no similarity to design. |
Extremely difficult to read. |
|
| Functionality | 100% | 60% | 10% | 0% | |
| 6.0 Marks ____ / 6.0 |
Program meets all requirements |
Program meets most requirements |
Program doesn’t compile. |
No attempt made. | |
| Innovation | 100% | 60% | 10% | 0% | |
| 5.0 Marks ____ / 5.0 |
Student included additional supportive functionality. Splash screens, dialogs and graphic buttons. |
Students has included some beneficial additional features. |
Has attempted little innovation. |
Basic System |
AssignmentTutorOnline
1005ICT Object Oriented Programming ! ! ! 2014-02
Project! ! ! ! ! ! ! ! Page 3 of 6
Project Outline
1.0 Background
Our client is Origin Energy, They require us to develop a new customer service system
(OECSC). This system will help their personal better deal with customers questions and
issues. The roles within the company that will be using the system are:
Level 1 Customer Support (L1CS) – The Level 1 customer support personal will take
down the customers details, the enquiry or request, and pass the job onto a relevant
expert. The Level 1 may in fact be able to solve the problem themselves and therefore not
need to pass the request on. Depending on the nature of the request the issue could be
passed on to a Technical Support Person or an Account/Billing Agent.
Technical Support Personnel (TSP) – The TSP is responsible for fixing technical issues,
generally at the client’s address. The TSP will arrange an appointment time with the client
so that the issue can checked, and fixed at a time that is convent. The TSP is also
responsible for carrying out the work and arranging any additional work or subcontractors.
Account/Billing Agent (ABA) – The ABA deals with all the customer enquires relating to
accounts. If the client was overcharged or under paid, then it is the ABA responsibility to
sort out the issue.
Regional Manager (RM) – the RM has oversight of all other roles, but is not involved
directly in customer service.
2.0 Program
The proposed solution consists of a single interactive program with a graphical user
interface, consisting of four windows open at all times:
(a) The interface required by an L1CS for logging a new enquiry/issue:
i. It should allow the L1CS to enter the clients account number, the particulars
of their problem and then allow them to assign it to a queue (either technical
or financial) and assign a priority to it.
ii. The screen should also show the clients details once their account number
has been entered, namely their:
(a) Name
(b) Address
(c) Contact phone number
(d) Email Address
(e) Preferred method of communication
(f) Whether or not they have solar panels installed
(g) Are they a user of electricity, gas, or both.
(b) The interface required by TSP, should enable the following functions:
i. They should be able to see the queue of jobs sent from the L1CS,
ii. They should be able to select a job from this queue and assign an
appointment time to it,
1005ICT Object Oriented Programming ! ! ! 2014-02
Project! ! ! ! ! ! ! ! Page 4 of 6
i. Once a time has been assigned it goes into their pending job queue.
ii. They also need to be able to see the jobs for a particular day, in
chronological order,
iii. Add comments to the job,
iv. They also need to be able assign a job to a completed state.
(c) The interface required by ABA, should enable the following functionality:
i. Be able to see the clients details,
ii. See the current account details,
(a) Amount owing,
(b) Current power usage
(c) Feed-in Amount
iii. See the history of their account (over at least a year),
iv. See a histogram of the clients usage and or charged amount over the last
year.
v. The histogram should also show the mean usage across all the clients (can
be read from a file).
vi. Add comments to the job.
vii.Be able to close a job.
(d) The interface required by the RM should enable the following functionality:
i. Be able to see all queues, move an item from one queue to another, be able
close a job in any queue.
ii. See the TSP’s daily work load.
(e) Your program should store all the queues into separate files and maintain a file of
all the completed jobs.
(f) These requirements are the minimum, adding your own additional functionality is
encourage.
3.0 Data files
The ASM’s data will be stored in a series of text files:
ClientData.txt – A file that contains all of the details relating to a client.
The contents of this file are:
where each client consists of the following items:
Account# – The number randomly assigned by Origin Energy.
Account Holders Name – The name of the account holder.
Address – The location of the residence that utilizes this resource.
Mailing Address – The address were all mail should be sent
Contact Number – The best phone number for contacting the client.
Email – Their Email address.
Solar – Yes or No
UserOf – Gas | Electricity | Both
1005ICT Object Oriented Programming ! ! ! 2014-02
Project! ! ! ! ! ! ! ! Page 5 of 6
Significant notes – Important information about the client.
For example: Enter property by side gate, ferocious dog on premises.
For example a client entry in the file would be:
57680011
Brett Wildermoth
28 Street Avenue, Burbsville, 4189
Same as address
0324812390
[email protected]
Yes
Electricity
Enter via side gate
NOTE: Your program will require additional files to store the various queues
and any additional information that is required by your program. I leave the
design of these files up to you. However you should read the account usage
information from a file similar to the one used in Lab 5 (or can be generated
by Lab 7).
1005ICT Object Oriented Programming ! ! ! 2014-02
Project! ! ! ! ! ! ! ! Page 6 of 6
- Assignment status: Already Solved By Our Experts
- (USA, AUS, UK & CA PhD. Writers)
- CLICK HERE TO GET A PROFESSIONAL WRITER TO WORK ON THIS PAPER AND OTHER SIMILAR PAPERS, GET A NON PLAGIARIZED PAPER FROM OUR EXPERTS
