BMIS 33181 FYP Guidelines

BMIS 33181
FINAL YEAR
PROJECT
GUIDELINES

FACULTY OF BUSINESS AND

MANAGEMENT
AIMST UNIVERSITY
SEMELING, 08100 BEDONG
KEDAH, MALAYSIA.
Tel : +604-4298000
Fax: +604-4298153
Revision Date: August 2015
NHMR

BMIS 33181 FYP Guidelines

TABLE OF CONTENTS
Contents

Page

1.0

GENERAL INFORMATION
1.1 The Learning Outcomes

1
1

2.0

PROJECT INFORMATION
2.1 Final Year Project Topic Selection
2.2 Project Proposal
2.3 Follow-up sessions with Supervisor (s)

2
2
2
2

3.0

PROJECT PROCEDURES

4.0

PROJECT PRESENTATION AND PROJECT

DEMONSTRATION
4.1 Project Proposal Presentation
4.2 Final Project Presentation
4.3 Final Project Demonstration

4
4
4
5

5.0

FINAL YEAR PROJECT REPORT

5.1 Final Year Project Report Submission
5.2 Final Year Project Format
5.3 ProjectWriting Contents

6
6
6
8

6.0

WRITING CONVENTIONS
6.1 Units of Measurement
6.2 Project Ethics
6.3 Miscellaneous of Writing Conventions

15
15
15
16

7.0

PROJECT EVALUATION

17

BMIS 33181 FYP Guidelines

1.0 GENERAL INFORMATION

BMIS 33181 Final Year Project is a course whereby each undergraduate student of BSc.
(Hons) Management Information Systems (MIS) must undertake and pass in order to
graduate. It aims is to equip the students with knowledge and skills in problem solving
and software development concepts through appropriate academic and project activities. It
is undertaken in two semesters with 6 credit hours.
1. The students are advised to start their project work prior to the registration to ensure
that the project paper can be completed on time.
2. Once registered, students are advised to work closely with their supervisor (s)
regarding their project works.
3. The students must under go BMIS 33181 in two semesters. In the first semester when
they registered they are required to complete the Project Proposal. Then they have to
proceed on BMIS 33181 in the consequence semester to complete the project.

1.1 The Learning Outcomes

Identify, understand and formulate the project problems.

Define the objectives, methodologies and scope of the project

Describe the important activities associated with project initiation, planning,

system analysis and design and execution phase of information system project.

Develop information system as described and planned in Project Formulation.

Describe the important activities associated with project architecture building

and execution phases of and information system.

Demonstrate the information system developed.

BMIS 33181 FYP Guidelines

2.0 PROJECT INFORMATION

2.1 Final Year Project Topic Selection

Students have to identify a specific information system areas and topic, clearly understand
the problems, scope and objectives, and the implementation aspect of the project.
Therefore, the students are advised to :
a) Discuss with their project supervisor to get a better understanding of the various
information system areas pertaining to the project.
b) Obtain relevant systems, reading material, reference books from the library and
other resources with the guidance from their supervisor.
2.2 Project Proposal
Project topics can be a product of students own ideas or it can be a suggestion from a
respective supervisor. Upon finding a title that suits the student, the student must put
together a basic information search, discuss with the supervisor and prepare a basic
proposal. Then they have to omplete the Project Proposal Report and submit it to Faculty
FYP Coordinator.

2.3 Follow-up sessions with Supervisor (s)

While the project is being carried out, students are required to discuss with their
supervisor at least once a week, to report the progress and to get advice on problems they
might be facing. Regular review from supervisors will ensure that students execute their
project according to the facultys procedure and standards, as well as the project
objectives and aims. Students should use log book on their progress and meet up session
with their supervisors.
Student must arrange a minimum of four (4) formal meetings with their supervisors before
receiving permission to submit and present their project. However, students are strongly
advised to arrange a weekly meeting with the supervisors to address issues related to
project execution. All meetings must be recorded in a logbook and the supervisors
signature of approval of each meeting is required. The logbook form is available in the
appendices.

BMIS 33181 FYP Guidelines

3.0 PROJECT PROCEDURES

Project Flow
Project topic selections process.

Background reading on project topic.

Discussion with supervisor.
Submission of Project Proposal Report to supervisor.
Project Proposal Presentation.
Correction on report as per required by supervisor.
Identifying problem statements, objectives, and scopes of the project.
Literature review.
Project methodology.

Data collection.

User/system requirements analysis.

Project design.
Project implementation,coding and testing.
Project discussion and conclusion.
Final project draft writing submitted to supervisor for correction.
Final project draft writing return by supervisor.
Submission of ONE (1) spiral bound project project to supervisor (Evaluation

will be done on this copy).

Submission of pre-final report by the supervisors to the selected examiners.
Final year project presentation (Viva-voce).
Demonstration of the project to the examiners.
Evaluated students project by supervisor.
Approval (signatures) for the Certification of Project Paper from supervisor

should be obtained.
Submit THREE (3) hardcopies in hard cover to supervisor.

BMIS 33181 FYP Guidelines

4.0 PROJECT PRESENTATION AND PROJECT DEMONSTRATION

In BMIS 33181, there are two types of project presentations required. The first one is the
presentation for the proposal of the proposed project that the student would like to do,
called as Project Proposal Presentation while the other presentation is the final year
project presentation, called Viva Voce for the executed project that the student has
completed.
4.1 Project Proposal Presentation
Project Proposal Presentation is the presentation for the student to express their idea and
proposed project title to the Faculty FYP Committee. Student is required to present their
project proposal in fifteen (15) minutes, with 10 minutes for slides presentation and 5
minutes for the question and answer session. It is advisable for the students to include
only important points in the slide to ensure that the presentation time is not exceeded. The
whole presentation should contain the following items:
i.

An introduction to introduce presenter, the proposed project title, as well as the

supervisor.

ii.

An overview of the overall presentation (i.e. structure of the presentation, outline)

iii.

The poposed project background, aim, objectives, and scopes of the project (this
should be enough to cover what has been written in Chapter 1 of the projects
proposal report)

iv.

Summary of literature review for the proposed project (as explained in Chapter 2
of the projects proposal report)

v.

Summary of proposed research/system development methodology. This may

include the proposed data collection techniques such as survey, organization visits,
etc.

vi.

List of software and hardware that are required to develop the proposed project.

vii.

Discussion on implementation of the proposed project.

viii.

Conclusion of the presentation.

4.2 Final Project Presentation

Final Project Presentation or Viva Voce is required for the student after they have
completed their final year project up to the development and implementation stage. They
are given twenty (20) minutes to present with 15 minutes for the presentation and 5
minutes for the question and answer session. It is advisable for the students to include
4

BMIS 33181 FYP Guidelines

only important points in the slide to ensure that the presentation time is not exceeded. The
whole presentation should contain the following items:
i.

An introduction to introduce presenter, the final project title, as well as the

supervisor.

ii.

An overview of the overall presentation (i.e. structure of the presentation, outline)

iii.

The final project background, aim, objectives, and scopes of the project (this
should be enough to cover what has been written in Chapter 1 of the final project
report)

iv.

Literature review for the proposed project (as explained in Chapter 2 of the final
project report)

v.

Summary of research/system development methodology. This may include the

project data collection techniques such as survey, organization visits, etc.

vi.

List of software and hardware that are required to develop the project.

vii.

Discussion on implementation and the development stages of the final project.

viii.

Future recommendations and improvement for the final project.

ix.

Conclusion of the presentation.

Students are advised to follow the subsequent good practices for their projects
presentations:
i.

Arrive early for the presentation.

ii.

Limit the use of text in slides and make sure there is no spelling error.

iii.

Include more figures, pictures, charts, etc.

iv.

Have eye contact with the audience.

v.

Dress according to the AIMST Universitys student dress code.

vi.

Speak clearly. Do not mumble.

vii.

Manage the presentation time so that there is ample time for Q&A session.
Practice beforehand.

viii.

Do not forget to thank the audience for listening.

4.3 Final Project Demonstration

Students are required to demonstrate their developed final project to their supervisors and
examiners. The demo is compulsory and are evaluated as part of BMIS 33181 grade. This
demo also as a prove that the system/website that the student developed is working.
5

BMIS 33181 FYP Guidelines

5.0 FINAL YEAR PROJECT REPORT

The final report is essential to BMIS 33181. The early chapters, Chapters 1,2 and 3, are
similar to Project Proposal Report. It must be reminded that the tenses in Chapter 3 must
be changed. In Project Proposal Report, Chapter 3 presents the plan, while in Final Year
Project Report it presents actions already taken. Consequently, the past tense must be used
in this report.
As part of their progress, students are required to submit drafts of Chapters 4 and 5 to their
supervisors for evaluation. Corrections must be done as required. It is hoped that the
quality of the students project report is improved by having the ongoing report draft
submission. A copy of Final Year Project Report has to be submitted to the FYP
coordinator.
5.1 Final Year Project Report Submission
The final hard-bound report should be prepared after all the corrections based on
comments by evaluators and the supervisors are done. Please ensure that the endorsement
forms are completed and submitted.
Students must prepare at least three (3) copies of hard-bound reports (1 each for
supervisor, faculty and library).
5.2 Report Year Project Format
The sample of the format for the items discussed in this section can be viewed in
Appendices I
5.2.1 Language

Must be in English.

5.2.2 Paper type and Quality

Printing should be done in letter quality or on a laser printer. White simili paper
(80gm) or equivalent quality should be used.

Only one side of the paper is to be used.

Students are advised to refer closely to this guide to avoid errors and delays.

With the exception of photographs, one type and brand name of paper must be used
throughout the project report.

BMIS 33181 FYP Guidelines

The standard paper size is A4 (210mm x 297mm) of A4 size and must be of good
quality (80gm) with a hard, bright and even surface.

5.2.3 Page Limits

The report should not exceed 200 pages long.

5.2.4 Typeset and Font Size

The entire text of writing, including headings and page numbers, must be produced
using Times New Roman.

The font size should be 12 point and should not be scripted or italicized except for
scientific names and terms in a different language.

Chapter title
font size 14 bold /all capital/Times New Roman

Section
font size 12 bold /word first letter capital/Times New Roman

Sub-section
font size 12 bold / word first letter capital/indent by 0.5

Footnotes and text in tables should not be less than 10 point.

5.2.5 Margins

For binding purposes, the left margin should be at least 4cm (1.5 inch) and the right,
top and bottom margins should be at least 2.5cm (1 inch).

Margin specifications are meant to facilitate binding and trimming.

All information (text headings, footnotes and figures), including page number, must be
within the text area.

5.2.6 Spacing

The writing should be typed 1.5 lines and for spaces between paragraphs and sections.

Body text should be justified.

The following, however, should be single-spaced:

a. Explanatory footnotes (if necessary);
b. Quotations longer than three lines set in a block;
c. References;
d. Multi-line captions (tables, figures);
e. Appendices such as questionnaires, letters; and
7

BMIS 33181 FYP Guidelines

f. Headings or subheadings
5.2.7 Pagination

Placed 1 cm from bottom, in the centre.

Page number for preface are lower case Roman numerals (ii, iii, iv).

The Title page is considered page i but the number is not shown. Therefore, the page
number for Acknowledgement should be ii.

Page number for Text and References are Arabic numerals (1, 2, 3, 4)

5.2.8 Hard-cover bound (3 copies)

The hard-cover bound project report must be in the following colour: sky blue colour,
rexin-bound cover with gold letters.

The cover of the final project report must include the following information printed in
gold block capital letters, 14 point font, Times New Roman:
- Full project title
- Full name
- AIMST UNIVERSITY
- Year of submission
- (Refer to Appendix A)

The book spine must contain the following printed in gold block capital letters, use
appropriate font size to fit, Times New Roman:
- Full name
- Full project title (if the title is too long to fit, use an appropriate shorter title)
- Year of submission
- (Refer to Appendix B)

5.3 Project Writting Contents

A project report generally consists of THREE (3) main parts:
a. Preface including title page, certification of final year project , permission to use,
disclaimer, declaration, acknowledgements, abstract, table of contents, list of
tables, list of figures, and abbreviation.
b. The text of main body divided into chapters and sections.
c. Supplement consist of tables, references and appendices.

BMIS 33181 FYP Guidelines

The sequence is as listed below:

No.
1.
2.

Items

Remarks

Blank Page
Title page

Not to be paginated but

counted as 1 or i. Subsequent
pages are paginated and are
numbered consecutively or
according to the chapter and
listed in the Table of Contents

3.
4.
5.
7.
8.
9.
10.
11.
12.
13.

Certification of Final Year Project

Permission to Use
Disclaimer
Declaration
Acknowledgement
Abstract
Table of Contents
List of Tables
List of Figures
List of Abbreviation/Notations/Glossary of

14.
15.
16.
17.
18.

Terms
List of Appendices
Text of Dissertation (Chapters)
References
Appendices
Blank Page

5.3.1 Preface
5.3.1.1 Title page
Title Page should include the following:
a. Full title of project report (in uppercase using times new Roman 12-point fonts)
b. Full name of author (in uppercase using Times New Roman 12-point fonts)
c. Degree for which the project is submitted (in titlecase using Times New Roman
12-point fonts)
d. Name of the institution to which the project is submitted, e.g.: Faculty of Business
and Management (in titlecase using Times New Roman 12-point fonts)
e. Month and year of submission
(Refer to Appendix C)
5.3.1.2 Certification of Final Year Project
The sheet signed by Faculty Dean, Examiner and Supervisor can be obtained from
supervisor (Refer to Appendix D).
9

BMIS 33181 FYP Guidelines

5.3.1.3 Permission to Use

Students are expected to include in the front of their project work; a statement in
paragraph from granting permission to use the project under specifically stated conditions,
and indicating the address of the person of whom request for such permission should be
sent (Refer to Appendix E).
5.3.1.4 Disclaimer and Declaration
A signed declaration on the originality of the work presented in the project and providing
authority to AIMST University has the right to amend and comprehend this project for the
future enhancement (Refer to Appendix F & G).
5.3.1.5 Acknowledgements
Acknowledgements usually contain written expression of appreciation for guidance and
assistance from individuals and institutions. The acknowledgements should not exceed
250 words.
5.3.1.6 Abstract
The abstract should identify clearly and succinctly the purpose of the project, the methods
used, the results obtained and the significance fo the results or findings. The abstract
should be written in one page, one paragraph and should not exceed 250 words.
5.3.1.7 Table of Contents
The table of contents must list and provide page references for all elements of the project,
it will indicate chapters, sections and important sub-divisions of each section. The title of
each chapter should be written in full capital. The title of a subdivision of a chapter or
section should be in small letters, with the exception of the first letter of significant words.
E.g:
TABLE OF CONTENTS
Page
PERMISSION TO USE

iii

DISLAIMER

iv
10

BMIS 33181 FYP Guidelines

DECLARATION

ACKNOWLEDGEMENT

vi

ABSTRACT

vii

TABLE OF CONTENTS

viii

LIST OF TABLES

ix

LIST OF FIGURES

LIST OF APPENDICES

xi

CHAPTER 1 :

INTRODUCTION
1.1 Introduction

1.2 Project Problem

5.3.1.8 List of Tables

The list of tables follows the table of contents. This list includes the number of each table,
the title and the page number.
5.3.1.9 List of Figures
The list of figures follows the list of tables. This list includes the number of each figure,
the title and the page number.
5.3.1.10 List of Abbreviations/Notations/Glossary of Terms/List of Appendices
The list includes all non-standard abbreviations used in the text of the project. It follows
the list of figures.
5.3.1.11 List of Appendices
The list includes all supported documents for the text of the project attached as
appendices. It follows the list of figures.
5.3.2 Text of Project
Generally, the body of a project consists of the following sections:
5.3.2.1 Chapter in the Report
1. Introduction
1.1. Introduction
11

BMIS 33181 FYP Guidelines

1.2. Problem Statement

Example: Explain why current technology T is underperforming environment Z.
1.3. Project Goal
A single sentence statement.
Explaining the key target of the project.
Example:

To develop a system X using technology Y to be employed in

environment Z.
1.4 Objectives
A minimum of three objectives and a maximum of four.
Must be measurable
1.5 Scope
Describes in detail tasks to be executed.
Constraints regarding any part of the project development (e.g. size of system and
technology).
What will and will not be done as part of the project.
1.6 Significance of the project
2. Literature Review
2.1 Introduction
2.2 Current system analysis (e.g.: product/prototype/software/tools)
Characteristics of the system
2.3 Compare between existing systems
Ensure strength and weakness between systems
2.4 Literature review on technology used
2.5 Chapter summary
3

System Development Methodology

3.1 Introduction
3.2 Methodology choice and justification.
3.3 Phases within the chosen methodology (traditional or modern)
Describes activities and process in each phase
Design modelling (e.g. using UML)
Design tools
12

BMIS 33181 FYP Guidelines

Gantt Chart
3.4 Describe briefly the technology or tools used to develop the system.
3.5 System requirement analysis: hardware and software
List and justify
3.6 Chapter summary
4

Requirement Analysis and Design

4.1 Introduction
4.2 Requirement analysis
OOP (use case, sequence, and activity diagrams) or
Traditional (Software Development Life Cycle)
4.3 Design
OOP class diagram, overall system architecture or
Traditional (DFD)
4.4 Database design (if any)
ERD (for traditional methodology)
Normalized tables (to include primary key, foreign key, etc.)
4.5 Interface design
Menu and screen design
System navigation and content design
For web page project to include page navigation
4.6 Chapter summary

Results, Testing and Discussion

5.1 Introduction
5.2 Coding of systems main functions
5.3 Essential interfaces that show systems results and achievements
5.4 Testing
5.4.1 Black box testing
System flow, input/output, error messages
5.4.2 White box testing
5.4.3 User testing
5.5 Chapter summary

Conclusion
6.1 Introduction
13

BMIS 33181 FYP Guidelines

6.2 Achievement of project objectives

Project contribution

6.3 Suggestions for future improvement

5.3.3 Supplements
5.3.3.1 Tables
Tables are labeled according to the chapter in which they appear. For example, tables in
Chapter 3 are numbered sequentially: Table 3.1, Table 3.2 etc. The title is placed above the
table, left justified and in the following format:
Table 3.1
Short Title (italic)
E.g. :
Table 3.1
Profile of Respondents
If the table is more than one page, the continued table on the following page should
indicate that it is a continuation. If the table contains a citation, the source of the reference
should be placed below the table.
5.3.3.2 Figures
Figures such as map, charts, graphs, diagrams, photographs should be labeled according to
the chapter in which they appear. For example, figures in Chapter 3 are numbered
sequentially: Figures 3.1, Figures 3.2 etc. the title is placed below the figure, left justified
and in the following format:
Figures 3.1
Short Title (italic)
E.g. :
Figure 3.1
14

BMIS 33181 FYP Guidelines

kk
5.3.3.3 Chapter Layout
A chapter may be divided into major sections and subsections. A major section is
numbered with the First level 1, 2, 3 and subsection is numbered (1.1, 1.1.1, 1.1.2). This
should be consistent throughout the project and to be limited to 3 levels if possible.
5.32.3.6 References
References is a term commonly taken to mean a list of work cited. All references should
be in single spacing. Students are encouraged to refer to the recent edition of APA
(American Psychological Association) publication manual.
[Available at http: www.apastyle.org]

6.0 WRITING CONVENTIONS

6.1 Units of Measurement
The International System of Units (SI) must be used for all scientific data.
6.2 Project Ethics
Project ethics involves all the moral and professional issues relating to project. The most
serious breach of ethical standards in writing a project report/dissertation/thesis if the
offence of plagiarism. Plagiarism is defined as the use of original work, of ideas or actual
texts created by others, without acknowledging the original source. University has the
meachanism to verify the authenticity of the dissertation; hence the projecter is expected
to comply with the maximum requirement of 25% of the direct quotes with appropriate
citations.

15

BMIS 33181 FYP Guidelines

6.3 Miscellaneous of Writing Conventions

6.3.1 Numbers
All integers less than ten should be spelt out unless they are attached to units of measure
(e.g. 5 kg, 10 ml etc.). If a sentence begins with a number, write the numbers in word. Use
numerals for series of figures, (e.g. 8 balls, 18 softballs, etc.)
6.3.2 Brackets [ ]
Within direct quotations, brackets are used to enclose any explanatory note inserted by the
writer e.g. The said year [1998], it was a glorious year to be remembered (Maznah, 1998).
6.3.3 Symbol for Percentage
The symbol % may be used in place of the word percent, e.g. 43%. If the student uses 43
percent, consistency should be maintained.

16

BMIS 33181 FYP Guidelines

7.0 PROJECT EVALUATION

This chapter outlines evaluation criteria for both Project Proposal and Final Year Project.
Students must read the following evaluation criteria so that they are aware about the
marking schemes and able to fulfill all the required criteria to get better marks.
There are six evaluation forms related to BMIS 33181 evalutions. Two forms; Proposal
Report Evaluation Form and Proposal Presentation Evaluation Form are completed by
supervisor while there are three forms; Final Year Project Report Evaluation Form,
Final Year Project Presentation Evaluation Form and Final Year Project
Demonstration Evaluation Form are completed by the examiner. Overall Evaluation
Form is the total marks from all evaluation forms that is to be completed by supervisor.
All forms can be viewed in Appendices II.

17