Template FYP Final Report Web

[Your project title] DCS 5098

ACKNOWLEDGEMENT

The Acknowledgements page is where you thank all the people who have helped you with the project, including your supervisor, if appropriate. You will also need to acknowledge the contribution of others at different places in the body of the report.

Centre for Diploma Programme 1


ABSTRACT

It is a very brief but clear description of what the report is all about, summarizing

your plan and your progress so far. Keep your abstract to 100 to 150 words or in one

page.



LIST OF TABLES

Table 1.1: Division of tasks ………………………………………………… 11

If the table exists in Part 1, it should be referred as Table 1.x where x is an integer

based on the order of appearance.



LIST OF FIGURES

Figure 1.1: Sample website screenshot ……………………………………………… 22

If the figure exists in Part 2, it should be referred as Figure 2.x where x is an integer

based on the order of appearance.



Table of Contents (kindly please change the page number accordingly)

ACKNOWLEDGEMENT 1

ABSTRACT 2

LIST OF TABLES 3

LIST OF FIGURES 4

TABLE OF CONTENTS 5

PART 1: INTRODUCTION 7

1.1 Overview 8

1.2 Project Objectives 9

1.3 Target User 10

1.4 Project Scope 11

1.5 Gantt Chart 1 12

1.6 Gantt Chart 2 13

1.7 Division of Work 14

PART 2: CASE STUDY AND LITERATURE REVIEW 15

2.1 Primary Study 16

2.2 Problem Statement 17

PART 3: PROPOSED SOLUTION 18

3.1 System Features 19

3.2 Hardware/Software Requirements 20

3.2.1 For Developer 20

3.2.2 For User 20

3.3 Context Diagram & Data Flow Diagram 21

3.4 Entity Relationship Diagram 22

3.5 Data Dictionary 23


PART 4: SYSTEM PREVIEWS 25

4.1 Customer/Member Module 26

4.2 Staff/Admin/Front Desk Module 26

PART 5: SYSTEM TESTING 27

5.1 System Testing 28

PART 6: CONCLUSION 30

6.1 Conclusion 31

6.2 Further Enhancements 32

PART 7: REFERENCES 33

PART 8: APPENDIX 36

Appendix A: Minutes of Meeting 37

Appendix B: Website Samples/Questionnaire/Forms 37

Appendix C: Request Interview Letter 38

Appendix D: Interview Questions 38

Appendix E: Client/Server Setup Guide 38

Appendix F: CD (Softcopy of Report and System) 38

Part I:

Introduction

1.1 Overview

The overview describes the current technologies or trends (e.g: online

business, online ordering) related to your project. This section describes a

general understanding about the system.

1.2 Project Objectives

This section focuses on outcomes of your project. State what you would like to

achieve from the system. The objectives must be measurable and achievable.

(Objectives MUST be between THREE to FIVE points)

1. To reduce …2. To improve …3. To increase …

Example:

1. To provide better convenience for users towards this systemFast loading, good and clean layout by making sure that it is not crowded with too many unwanted text of images. Easy to find links. Most of the important links can be seen in one view without scrolling down the webpage. Making sure visitors can get the information that they wanted within 3 clicks of the mouse.

1.3 Target Users

Target users are people who can interact with your system (e.g: E-Learning:

target user: students, lecturers). However, you may want to narrow down your

target users based on the accessability of your project.

Example:

1. TeenagersState the reasons why you target teenagers to use your system.

2. Music loversState the reasons why you target music lovers to use your system.

1.4 Project Scope

This section refers to the coverage of your system (area, time, payment,

delivery, cancellation). The project scope and concept is also related your

target users.

Example: For a shopping cart system, visitors must register and become a

member before being allowed to purchase products online.

It also states the limitation, or what are the areas that the system is limited to.

Example: For a shopping cart system, the limitation may be no delivery is

provided. Only credit card payments is accepted.

Note:Example: - Admin can add new products [WRONG - this is not your scope]

1.5 Gantt Chart 1

A Gantt chart outlines the aspects of the project that has been compeleted

during the Part 1. The Gantt chart must show the duration taken for selecting

group members until delivering the Interim Report/Presentation of Part 1. You

can create Gantt chart in MS Project, SmartDraw or other project management

software.

1.6 Gantt Chart 2

A Gantt chart outlines what aspects of the Part 2 has been compeleted. The

Gantt chart must show the duration taken from Design phase until delivering

the Final Report/Presentation for Part 2. You can create Gantt chart in

Microsoft Excel, MS Project, SmartDraw or other project management

software.

1.7 Division of Work

Division of work is very important make sure every member participates in the

project development. Some of the tasks such as preparing documentation and

background study must be done by all group members. However certain tasks

must be delegated to each group member by the group leader.

TASKS STUDENTS

Ali Chong Kumar

Preparing project proposal X

Overview X X

Objectives X

Target Users X

Project Scope

Gantt chart

Primary Study

Problem Statements

System Features

Hardware/Software Requirements

Data flow diagram & Context Diagram

Entity relationship diagram

Data dictionary

System Interface Design

System Coding

System Testing

Compilation of Final Report

Presentation and Demo

Meeting Minutes

Table 1.1: Division of tasks

Part II:

Primary Study/

Literature Research

2.1 Primary Study

Students need to conduct a research for two or three existing/similar systems

on the market. Explain the aspects of design, features and functions of the

systems (including advantages and disadvantages of the systems).

Primary study refers to background information or technical knowledge

that is critical to develop your project. Primary study also includes feasibility

study on your system given the time constraint and resources available.

Snapshot or screenshots of the webpages or sections are required.

Example

Figure 2.1 ABC Registration Page

The example above shows how the registration section lists out all the errors

above the form, which then forces the user to scroll and scan down to the rest

of the form to fix the errors. This will be troublesome for longer forms and

frustrating as the user has to scroll up and down to fix each error. It would be

much easier if the errors could be seen next to the form field.

2.2 Problem Statement

The problem statement refers to the problem area that your proposed system

aims to solve. It should reflect the objectives and primary study.

Example: (Explain your point in proper sentences)

Example:

Objective: To provide better convenience for users towards this system

Problem Statement:Current websites do not implement a user-friendly concept. Tend to drag the visitors all over the place before displaying the information that the visitors are searching for, this might be one of their advertising strategies. Some of the websites also has a cluttered design with large amount of unnecessary images that makes the loading time longer.

It is not regarding the problems that encountered during your project/system

development (e.g: Communication problem with group members, time

management).

Part III:

System Design

3.1 System Features

List down all features of the proposed system for each type of user.

Example:

Admin

o Can add new staff.

o Can add and edit bulletin.

Member

o Can register and log into the system.

o Can edit profile.

3.2 Hardware/Software Requirements

3.2.1 For Developer

This section list the hardware components (if any), software or any

tools you (as the programmer/designer) plan to use to develop your

project. You may also include the price, how and where do you plan to

get them. This information may be presented in point form or table.

Example:

XAMPP : This is an all in one application to setup a server to run PHP

and MySQL web based systems. It is free to download and easy to use.

3.2.2 For User

This section describes the hardware (if any) and/or software

requirement for the user to run your new project. This information

may be presented in point form or table.

Example:

Browser : The user will need any browser such as Internet Explorer,

Mozilla Firefox or Chrome in order to interact with the application.

3.3 Context Diagram & Data Flow Diagram

For Web Based/Standalone project, students need to draw Context Diagram

and Data Flow Diagram (DFD) Level 0 to model the process and data flow

your system. You may use any diagramming tool which is related. It is

advisable to follow Gane & Sarson model.

Example: Gane & Sarson Model

3.4 Entity Relationship Diagram This section is for Web-based or Standalone project. The diagram describes

data entities in the system requirements, and relationships or associations

among those entities. You may present it using Chen model or Crow’s-foot

model. You may use also any diagramming tool which is related.

Example: Chen Model

Example: Crow’s Foot Model

3.5 Data Dictionary

This section describes in details the attributes and tables used in developing

the project. This section is for Web-based or Standalone project.

Sample:

[Your project title] [Your subject code]

Part IV:

System Previews



4.1 Customer/Member Module

In this section, show and explain screen shots related to user type: Customer/

Member/Student and etc.

Example:

Figure 4.11 Quizzes List

This is the Students Quiz List for students to select to answer quizzes. Students are only allowed to this page if the students are one of the students for this subject. Once directed, students have to just choose the subjects based on the lecturer and click on Answer button.



4.2 Admin/Staff/Front Desk Module

In this section, show and explain screen shots related to user type: Admin/ Staff/ Front

Desk/ Lecturer and etc.

Example:

Figure 4.6 Quiz List

This is all the Quiz that already been created in the system. The quizzes will only display if the lecturer is one of the lecturers in MMU. There are two sections in this Centre for Diploma Programme 26


Quiz List. One is the Private Quiz and Public Quiz. Private Quiz is for lecturers who decided for their own use and not for sharing. The public quiz is for lecturers who decided to share the quiz with other lecturers.

Part V:

System Testing



5.1 System Testing

This testing should cover functionality testing only. However you may include

security testing or GUI testing. The system testing may be presented in a test

plan (in a table form/checklist) that consists of functions to be tested, expected

result and actual result. Then, you need to summarize the system testing.

Example:

Test ID Test Case Expected Result Actual Result Status

1 Login:

Enter valid username

and valid password.

Click “Login”

button.

User should be

able to login to

the system.

The system

should display

home page with

the name of the

user.

User is able

to login.

Home page

with name of

user is

displayed.

Pass

2 Login:

Enter invalid

username and invalid

password.

Click “Login”

button.

User should not

be able to login

to the system.

User is able

to login.

Fail



Part VI:

Conclusion



6.1 Conclusion

In this section, it is to wrap up what you have mentioned in previous chapters, and to sum up what you have achieved in this project.



6.2 Future Enhancements

This chapter should address any future system development.



Part VII:

References



List of URL addresses, reference books or bibliography entries

Books:

Anti, J.M. and Ryan, P.V.S., “Civil Engineering Construction”, 3rd Ed.,

Sydney, Angus and Robertson, London, 1967, 631 pages

Journal:

Downs, R.B., “The Military Approach to Soil Stabilization”, Journal of the

Institute of Highway Engineers, London, Volume XIX, No. 3, March, 1972,

pg 19-23

Monograph:



Body, D.M., “Flood Estimation”. Water Res. Board of Australia. No.4, 1959,

41 pages

Thesis:

Marques, J.L.G.,”A Study of Anchorage Capacities of Confined Bentbar

Reinforcement”. Ph.D. Thesis, Rice University, Houston Texas May, 1988

Conf.

Lea, F.M., “Cement Research: Retrospect and Prospect” in Proc. 4th

Proceedings: International Symposium on the Chemistry of Cement ,

Washington DC, 1960, pg 5-6

Web Page:

Smith, A. B., “Description of the Intel P6 Processor”, Intel Corp.,

http://www.intel.com/pentium/p6/description.htm

Working Paper:

Kuo, C and Sayer, P, “Education of Engineers in Marine Technology”,

presented at the World Conference on Education in Applied Engineering &

Engineering Technology Cologne German, 16-19 April, 1984

Standards:

British Standard Institute, “BS 6000:1972, Guide to the use of BS 6001,

sampling procedures and tables for inspection by attributes”, London, 50

pages


http://www.intel.com/pentium/p6/description.htm




Part VIII:

Appendix

Appendix A: Meeting minutes

All meeting minutes must be included in the report in the appendix section.



Appendix B: Website Samples/Questionnaire/Forms

Any website screen shots, questionnaires and forms used as reference to your

project will be included in this section.

Figure 4.1: Sample website screenshot

Appendix C: Request Interview Letter

Students need to include the request interview letter if they have conducted an

interview session. Centre for Diploma Programme 37


Appendix D: Interview Questions

Students need to include the interview questions if they have conducted an

interview session.

Appendix E: Client/Server Setup Guide

This section should provide the user manual for user and administrator in

terms of:

Hardware configuration or setup

System Integration Manual

Installation Procedure

Appendix F: CD (Softcopy of Report and System) Attach the CD that contains the softcopy of the report and also the system.


Documents

Template FYP Final Report Web