CSC574 Jul-Nov 10

Mini project for CSC 574

This subject requires the students to undertake a mini project. The format of the report and the
description are provided below. The draft of the final report is to be submitted before the project
presentation. The submission date for the Final Report is on the presentation day.

Allocation of marks is as follows: 20 marks for the system development and the presentation.

The Report Format

The report of the respective systems should be between 10 – 15 pages using Arial 11pt, excluding the
appendix and single spacing. The content structure is as follows:

1. Introduction / Background
The overview of the project undertaken, with respect to the title chosen, should be in this part.
A little background of the system should also be included as to provide enough information in
understanding what is to be expected of the system and its capabilities. In short this part
answers the question on what triggers the initial decision to develop the project.

2. Objective
Once the clarification has been made on the project/system, the objectives as to what are the
benefits that could be gained from the project or the advantages of it.

3. Scope
A project without a scope could prove futile and disastrous because there are no guidelines to
follow. The scope should explain what are the areas to be expected in the system rather than
what areas are not. In simpler terms, the scope dictates what should be in the system and the
unavailability of other features should not be questioned.

4. Problem Description
This part describes and highlights the problems that are experienced in the non-existence of
such a system. It is hoped that with the development of the system, there is a decline in the
problems or total eradication of the same.

5. Methodology / Paradigm
The choices of methodology or development paradigm that are available are Structured
approach or Object-Oriented approach. Elaboration on the chosen approach, respective of
the title, is expected to provide some insights on the system development.

6. Analysis and Design technique

The analysis and design technique is based on the previous methodology adopted and the
relevant materials should be provided for a better documentation. For a selected approach,
the outlined documents for each should be made available:
Structured approach - Workflow, Data Flow Diagram of the system, Entity Relationship
Diagram, Database.
Object-Oriented approach – use CASE, Sequence diagram, State diagram, Class diagram,
Deployment diagram.

7. Implementation
Statements on any of the followings should also be supplied where ever used and applied.
Formula / Calculation / Algorithm
SQL statement (Create Retrieve Update Delete)

8. Conclusion
This part sums up all the preparation, development and findings done in the development of
the system. It also provides information on the realization and achievement of the system

9. Appendix
Related diagram
Source code

1
CSC574 Jul-Nov 10

The Project Titles:

There are a few common features shared by all of the titles, which the students need to consider. All
of the project titles have two levels; one level for the end user and the second level is for the
administrator.

Any end user is allowed to register (only for the first time) and to log in for the user to be able to view
the information. This is a standard feature for all titles.

At the second level, the standard features of logging in and CRUD (Create, Retrieve, Update and
Delete) are available for the administrator perusal. The administrator must log in to perform any of the
CRUD features and a password is required at this level.

E – Booking
E – Registration
E – Inventory

REMINDER : PLEASE FOLLOW THE REPORT FORMAT