IT420 – OOP in Java Project Guidelines

Advanced Diploma in Information Technology

IT420 –OOP in Java
Project Guidelines

1 Overview

The project for IT420 should be based on the topics covered in the module.
Students may opt to design a database type program or a game-simulation
program.
In the case of the simulation type project, the simulation should be fairly
complex. Trivial simulation programs will not be accepted. In both cases, students
should aim to use external files to store permanent data. The user interface must
be Graphical in nature. Students should use the AWT and/or the Swing packages.

2 Project Proposal

The proposal document should consist of a cover page and details as

specified in appendix A. If a proposal is not accepted, the student should re-submit
an alternative one. No project development should commence without prior
approval of the respective supervisor/lecturer.

Several recommended project titles are listed in appendix C. Students may

opt to do any one of these projects. Students may also submit other titles
according to their interests. However, the project content should be equivalent to
those of the listed titles.

3 Format (Project Documentation and Project Proposal)

All documents (proposal and final project documentation) should be

word-processed. No hand written documents will be accepted. The cover page
should contain the student particulars and other details as specified in appendix B.

The final project documentation should be bounded properly with the

diskette attached to the back cover of the document. The Font style to be used is
the Times New Roman. The font size should be 12 and the line spacing 1.5. Every
chapter/part must begin on new page. A content page must be included at the
beginning of all documents. Every page(except cover) should contain a page
number and the module tittle

4 Deadlines and Submissions

ADIT/IT420/Project Guideline Page 1

IT420 – Object-Oriented Programming in Java Project Guidelines

The deadline for the project proposal is lesson 3. The deadline for the
proposal re-submission is lesson 4. The deadline for the full project submission is
on lesson 14. Late submissions will result in a 10-mark deduction per-day. The
submitted projects are non-returnable, so students should maintain a copy for their
own reference. The final deliverables (lesson 12) should include:

1. One copy of the final project documentation (original).

2. The approved project proposal should be included in the final

document.

3. One copy of the source program on a virus free 31/2-inch floppy disk.

4. An executable file must be included on the 31/2-inch floppy disk.

5 Backup

Students are reminded to make backup copies all their programs and
documents. Excuses, such as "hard-disk crashes" or "printer problems" will not be
tolerated.

6 Integrity and Plagiarism

Any duplicated or plagiarised work, if detected, will be automatically

awarded 0 marks. Lecturers reserve the right not to accept any project that is
found lacking in substance or copied from some other sources. Students are
required to develop their project according to the stated project specifications.

ADIT/IT420/T107/Project Guidelines Page 2

IT420 – Object Oriented Programming in Java Project Guidelines

PROGRESSIVE SUBMISSION
Candidates are required to submit their project documentation part by part. The
project supervisor/lecturer has the right not to accept or award a ‘fail’ grade to
candidate who fails to submit their project documentation progressively. The
following submissions should be handed according to the stated lesson number.

1st submission on lesson 4 with the following chapters, total marks is 40:

- New System Description

- Input-Process-Output Specification (and Files)
- Screen Design
- Program Design
- Validation and processing

2nd submission on lesson 8 with the following chapters, total marks is 23:

- Objects, Classes
- Data structures, Files
- Compatibility with Design
- Correct Logic/Functionality
- Program Listing

3rd submission on lesson 12 with the following chapters, total marks is 17:

- Test Plan, Test cases, & test log shown

- Actual result & Screen dumps
- Conclusion of test conducted

Final submission is on lesson 14 with all the chapters (8 chapters)

compiled properly as a whole, total mark is 100.

ADIT/IT420/T107/Project Guidelines Page 3

IT420 – Object-Oriented Programming in Java Project Guidelines

7 Project Guidelines
Students are required to document their projects based on the Suggested
Table of Content as shown below.

Suggested Table of Contents for database type program

1. Current System(if any).

2. Proposed System
3. Specifications

3.1 Input Specification

3.2 File Specification
3.3 Screen Design
3.4 Program Design
3.5 Validation and processing

4. Program Listing
5. Testing
5.1 Test Plan
5.2 Test Cases
5.3 Test Log
5.4 Screen Dumps

6. Implementation
6.1 User Manual

7. Conclusion
7.1 Strengths
7.2 Weaknesses
7.3 Enhancements

8.Critical Appraisal

Suggested Table of Contents for simulation program

1. Description and details of game to be simulated

2. Specification
2.1 Input Specification
2.2 Screen Design
2.3 Program Design
2.4 Validation and processing

3 Program Listing

ADIT/IT420/T107/Project Guidelines Page 4

IT420 – Object Oriented Programming in Java Project Guidelines

4 Testing
4.1 Test Plan
4.2 Test Cases
4.3 Test Log
4.4 Screen Dumps

5 Implementation
5.1 User Manual

6 Conclusion
6.1 Strengths
6.2 Weaknesses
6.3 Enhancements

8.Critical Appraisal

1. Current System

Provide some background information about the types of problem

currently faced in the company. A detailed description of all the problems
encountered by the users and why there is a need to implement a new system.
Students may approach this by identifying problem areas in the company and why
the need to change from the current system to the proposed system.

2. Proposed New System

Describe the features of the proposed system and justify how the features
of the proposed new system will be able to solve existing problems faced by the
users.

3. Program Specification

3.1 Input Specification

In this section, students have to show all the input variables that will
be used in the program. Information such as Item Name, Description, Data
Type and Size should be described in detail.

3.2 Screen Design

The Screen Design section is a diagrammatic representation of all screens
that will appear in the program. Links between the various screens should
be clearly highlighted. For example, the Main Menu links to individual
screens such as Data Entry, Edit etc.

3.3 Program Design

The program should be modular in nature meaning one module should
ideally perform one function only. The Program design should depict the

ADIT/IT420/T107/Project Guidelines Page 5

IT420 – Object-Oriented Programming in Java Project Guidelines

program architecture and tools such as JSP or pseudocodes. However,

since Java is Object-oriented a more appropriate would be using object
oriented design tools such as UML.
Note: the design should be independent of any programming language.

3.4 Validation and processing

Details on how the data is validated and processed should be explained
clearly. Data validation is required so that only accurate data is accepted.
Listed below are some examples of validation checks:

 Input Type check - the acceptable entry in terms of characters, digits.

 Uniqueness - where no duplication/similar entry is allowed, normally
applicable to key field such NRIC, Identification NO. etc.
 Length check - where a particular field entry should not exceed the
stated size, normally applicable to alphanumeric and alphabetic fields.
 Range check - where the entry of a particular field is within a specified
range, normally applicable to numeric fields.

4 Program Listing
A copy of an updated error-free program listing should be included in this
section. Students are reminded to include comments in the program so as to
enhance its readability. Using meaningful identifier names with codes properly
indented are good traits, which will be looked upon very favourably in the grading
process. Also, these attributes will increase the maintainability of the program.

5 Program Testing

5.1 Test Plan

A proper Test Plan should be produced to test the functionality of the
program. Students may adopt the Top-down or the Bottom-up testing strategy.
The plan should include a list of all the tests to be performed and its objectives.
An example of a test plan entry is as follows:-

Test case Objectives

1 To check for the correct activation of first
option in the main menu
5.2 Test Cases and Results
The tests outlined in the test plan should be carried out by running the
program and monitoring the results. The results should then be matched against
the projected results to determine the success/failure of the test. An example of a
test case is shown below:

Test Case : 1
Objective : Explain the purpose of this test case
Test Data : Show actual test data used in this test case
Expected Test Result : The output you expect the program to generate.
Actual Test Result : This should be produced by your program in the
actual testing environment. You should capture the

ADIT/IT420/T107/Project Guidelines Page 6

IT420 – Object Oriented Programming in Java Project Guidelines

screen output by using the ALT print screen

key.(screen dumps)

Conclusion : If the test was a success, a failure or acceptable

6 User Manual

This section should include detailed instructions on how to use the various
functions in the program. Screen displays with step by step instructions should be
included to guide the user. The user manual should be detailed enough for a non-
computer literate user to operate and also it should not contain any computer
jargon. A good approach would be to use actual screen displays to guide the user.

7 Conclusion

Comment on the weaknesses of your program by evaluating its

performance and suggest ways to enhance it. Also, you may wish to include some
comments on the strengths of your program and how it could benefit the user.
8 Critical Appraisal

A short write-up on whether or not this project has met its objectives.
Discuss the lessons you have learnt as a result of doing this project and how you
may apply the skills gained.
Assessment criteria

Mark Grade
90% and above A Outstanding performance, showing insight, creative thinking
and flair exceeding normal expectations. Extremely well-
designed program including exceptionally good user interface
design and very clear and accurate documentation. Program
should work perfectly and should be fail-proof. Good and
efficient use of external files.
85% to 89% A- Very good performance, showing insight, creative thinking
and flair exceeding normal expectations. Close to an “A”
performance but falling short in some minor aspects. Again,
the user interface should be exceptional. Good and efficient
use of external files.
80% to 84% B+ Very sound performance. Competent and appropriate
responses to the relevant tasks. Several minor but tolerable
shortcomings which is not serious enough to gravely weaken
the entire exercise. Also, a well-designed user interface should
be present. The use of external files should be evident
75% to 79% B Very good attempt where most objectives are achieved, but
(40-49) the work may lack certain important elements which would
otherwise result in excellent work. A good user interface
should be present. The use of external files should be evident
70% to 74% B- Fairly good attempt where most objectives are achieved, but
the work may lack certain important elements which would

ADIT/IT420/T107/Project Guidelines Page 7

IT420 – Object-Oriented Programming in Java Project Guidelines

otherwise result in good work. A reasonably designed user

interface should be present. The use of external files should be
evident.
65% to 69% C+ Moderate attempt where most objectives have been achieved
but the quality of work does not warrant a high grade award.
The user interface should be average. No external files used
60% to 64% C Fairly moderate attempt where most objectives have been
achieved but the quality of work does not warrant a high
grade award. A fairly average user interface should be present.
No external files used
55% to 59% C- Fairly mediocre attempt where most objectives have been met
but with very notable shortcomings. A fairly average user
interface should be present. No external files used
50% to 54% D A very mediocre effort where some of the objectives have
been met but with several prominent shortcomings. A simple
user interface is needed as well. No external files used
0% to 49% F Non-compliance of the specifications or non-submission. A
fail grade should be awarded if no GUI's are used.

Appendix A

Project Title:

Software Requirement:

Hardware Requirement:

Abstract:

ADIT/IT420/T107/Project Guidelines Page 8

IT420 – Object Oriented Programming in Java Project Guidelines

Project status: Reject/Pending/Refinement/Accept

Date of Approval:
Approved by:
Signature:

Appendix B

Cover Page

Student Name: Lecturer/Supervisor Name:

Student Number: Student Contact Number:

Class Code: Center Code:

Subject Name:OOP in Java Country:

Subject Code: IT420

ADIT/IT420/T107/Project Guidelines Page 9

IT420 – Object-Oriented Programming in Java Project Guidelines

Appendix C

Suggested Tittles

Part A Simulation programs

1. Black-Jack simulation program

2. Chequers simulation program

3. Master-Mind simulation program

4. Tic-Tac-Toe(with expandable board)

5. Minesweeper

6. Solitaire

Note: all simulation programs should include a file element.

e.g to store the winners and their timings(if applicable) or other details

Part B Database Type programs

1. Clinic Patient-queuing System

2. Hotel reservation system

ADIT/IT420/T107/Project Guidelines Page 10

IT420 – Object Oriented Programming in Java Project Guidelines

3. Airline reservation system

4. Student Information System

5. Stock Control System

Note:
1. Use of data structures such as linked-lists, binary tress and stacks and
Queues is strongly encouraged.

Other Guidelines

1. Indicate all references, e.g. Web-site URL or reference books, used in the preparation
of the assignment.

Students are to indicate the following items of information in referencing:

 Author of the reference

 Title of the reference
 Publisher
 Edition
 Year of edition
 Pages to which information was taken from.

An example of such a referencing would be as follows:

[PRE97] Pressman, Roger S., Software Engineering: A Practitioner’s Approach

(4th Edition), McGraw-Hill International Editions, 1997. Pages 400 to 405.

If you are drawing information from a web site, indicate the following:

 Web site URL

 Title of URL
 Author of URL/Publisher of URL
 Year of last modification

[TAT97] Tate, Debi (1997). NT Firewalls take charge of network. LAN Times
Online.
http://www.lantimes.com/97/97aug/708a005a.html

Marks will be deducted for improper or inadequate referencing.

ADIT/IT420/T107/Project Guidelines Page 11

IT420 – Object-Oriented Programming in Java Project Guidelines

2. Plagiarism, i.e. copying and treating it off as original will result in your entire
assignment being awarded zero marks. In the event that quotations from various
published works are used, you are to indicate the reference behind the quotation.

3. The marks indicated behind each question part of the assignment are indications of
the weight of your answer. You should correspondingly accord more attention to the
parts that have been allocated more marks.

ADIT/IT420/T107/Project Guidelines Page 12