Puntland State University

Faculty of Computer Science and Information Technology

Bachelor of Science in Information technology

SOFTWARE DEVELOPMENT PROJECT

BACHELOR STUDENT’S GUIDE

Final Year Project

Marking and Writing
Guidelines
FINAL YEAR PROJECT WRITING PROPOSAL EVALUATION
Students are required to submit the Project proposal (appendix B) by WEEK THREE (3). The
proposal will be evaluated by the proposal evaluation panel and this panel decides whether the
proposal is acceptable and should the student proceed to the next stage of the project paper.
1. CHANGE OF TITLE
Students are not allowed to change the title of APPROVED project. Any changes of the title
must get approval from the faculty.
Wherever students want to change the project title, they must fill up the Change of Title Form
(appendix Q). The form must then get approval from the Project Supervisor, and to be
acknowledged by the Project Coordinator.

2. PROJECT PRESENTATION
Students are required to present project progress to the supervisor by WEEK ELEVEN (4).
They must get consent and approval from the project Supervisor for the final presentation.
Students are to complete Presentation Approval Form (appendix O). The form will then be
approved and submitted to the Project Coordinator by the Project Supervisor.

3. RE-PRESENTATION FOR IT PROJECT

A failed Project Oral Presentation (appendix P) means the project is not acceptable and must
be redone and presented again to the Faculty in person. This second attempt must take place
within the next TWO (2) weeks of the semester. For student with Non-Satisfaction result.
He/she will not be able to receive higher than a grade C+. No re-presentation is allowed during
short semester

4. ABSENCE FROM PROJECT PRESENTATION

If a student is absent for a reason not accepted by the faculty, they are deemed to have failed
the presentation component and a mark of 0 should be returned for them. In cases where
students are absent for reasons such as significant illness or other exceptional personal
circumstances. The IT project coordinator will reschedule the presentation.

5. PROJECT REQUIREMENT
Development Tool:
Any appropriate development tool is acceptable EXCEPT for obsolete development tool such
as Visual Basic (VB). The students MUST clearly state the development tools to be used in
the project proposal.
Simulation Software:
For research/prototype project, students may use a simulation software to model a real
phenomenon to observe an operation without actually performing that operation in real network
environment. Therefore, students MUST clearly state the simulation software to be used in the
project proposal. For example: NS-2, Opnet IT Guru, Riverbed Modeler. Students are NOT
ALLOWED to use just only Network Monitoring tools (for example, PRTG, Wireshark) in
designing their experiment. However, A combination of Simulation software and network
monitoring tools are allowed to design their project experiments.
6. PLAGIARISM
Plagiarism is the attempt to fulfill an academic requirement by using the ideas, words or work
of another person and representing them as one’s own. Academic conventions dictate that
students must acknowledge the source phrases and ideas that are not their own. Many ideas
and phrases are so familiar that they have become the common property of all; these obviously
require no documentation. However, the use of ideas or phrases [or entire works] that are
clearly original with another author requires that the appropriate credit be given to the original
author.
A student shall not plagiarize any ideas, writing, data or invention belonging to another person.
For the purpose of this rule, plagiarism includes:

• Using another writer’s words without proper citation

• Using another writer’s ideas without proper citation
• Citing the source but reproducing the exact words of a printed source without quotation
marks
• Borrowing the structure of another author’s phrases or sentences without crediting the
author from whom it came
• Borrowing all or part of another student’s paper or using someone else’s outline to write
own paper
• Using paper writing “service”, outsource or translates the writing or creation of another
person from one language to another
Any form of plagiarism found in the PROJECT PAPER will result in disciplinary action
leading to FAIL and rejection of the Project Paper by the Faculty.

IT PROJECT I PROPOSAL FORMAT

The following particulars should be provided on the IT Project Proposal.
▪ Name of Student:
▪ Supervisor of Student:
▪ Title of Project:
▪ Problem Statement (at least three):
▪ Objectives (at least five):

PROJECT PAPER FORMAT

The structure of the project report is based on a standard format which contains the following
sections:

1.1 FRONT COVER (APPENDIX C)

The front cover includes the following information:
i. Title of project
ii. Name of candidate
iii. Name of degree
iv. Name of university
v. Year of submission
1.2 PREFATORY PAGES
The prefatory pages include the
i. Title page
ii. Abstract page
iii. Acknowledgement page
iv. Approval page
v. Agreement letter
vi. Declaration page
vii. Table of Contents
viii. List of Tables
ix. List of Figures
x. List of Abbreviations and symbols
xi. Body of PROJECT PAPER (Chapters)
xii. References
xiii. List of Appendices

1.2.1 TITLE PAGE

This page (APPENDIX D) is not numbered and includes the following information:
▪ Full title of project;
▪ Full name of author;
▪ Degree for which the project is submitted. It should be indicated that the
dissertation is being submitted in fulfillment of the requirement for that particular
degree.
▪ School in which project paper was conducted; and
▪ Month & Year of submission.

1.2.2 ABSTRACT PAGE

The abstract is written after the completion of writing the dissertation. It summarizes
the structure of the whole text and the major facts it contains. It should be between 300
and 500 words in length. It should be only one paragraph.

1.2.3 ACKNOWLEDGEMENT
This sub-section is not compulsory but most reports convey appreciation to those who
have been involved in the study (See Appendix E).

1.2.4 APPROVAL PAGE

This page contains the names and signature of the Supervisor. Photocopies of these
pages are not acceptable (See Appendix F).

1.2.5 AGREEMENT LETTER

Sample letter of agreement between Faculty of Creative Multimedia and Innovative
Technology (FCMIT) and student. (See Appendix G).
1.2.6 DECLARATION PAGE
This page (APPENDIX H) includes the following information:
▪ Declaration text
▪ Name
▪ Student ID
▪ Date
▪ Signature

1.2.7 TABLE OF CONTENTS

The Table of Contents lists the chapters, topics and sub-topics together with their page
numbers. Sub-topics and topics should be labeled according to the chapter, for
example, the first topic in Chapter 1 should be marked 1.1 and the first sub-topic, 1.1.1.
The use of letters in parenthesis (for example, 1.3.7 (a)) is appropriate as a means of
differentiating sub-topics of the same topic from each other. This numbering system
should provide a clear picture of the relationship between chapters and topics and show
how they are connected. Sample of table of contents is shown in APPENDIX I.

1.2.8 LIST OF TABLES

This list contains the titles of tables, together with their page numbers, which are listed
in the text or in the appendix. The numbering system is the same as that used for topics,
for example; Table 1.3, Table 1.3.7 and Table 1.3.7 (a) (See Appendix J)..

1.2.9 LIST OF FIGURES

This list contains the titles of figures, together with their page numbers, which are listed
in the text or in the appendix. The numbering system is the same as that used for topics,
for example; Figure 1.3, Figure 1.3.7 and Figure 1.3.7 (a) (See Appendix K)..

1.2.10 LIST OF ABBREVIATIONS, SYMBOLS

If an assortment of abbreviations and acronyms (e.g. FOA, MARDI, PORIM), symbols,
or nomenclature are used in the PROJECT PAPER, it is best to list them with their
meaning, even though the full names are given at the first mention in the text. This list
should appear after the list of figures and tables and should serve as ready reference to
readers not familiar with the abbreviations, symbols or nomenclature used in the text.
Universally recognized symbol (e.g. cm, kg and mm) need not be listed
1.2.11 MAIN BODY SECTION HEADINGS FOR A SOFTWARE
DEVELOPMENT PROJECT - SOFTWARE
i. Chapter I: Introduction (analysis phase)
• brief introductory to the title
• purpose and objective of study
• the problem stated in general and the specific way
• rationale for problem solving and methods available

ii. Chapter II: Literature Review (analysis phase)

• show thorough knowledge of the research, theory, concepts, ideology and
opinion related to the title
• make aware that the review is selective
• show critical analysis of the review
• does the review reveal the relation between what has previously been done
by others and what is proposed in this project

iii. Chapter III: Research Methodology (design phase)

• explain what was done to gather the information essential to problem solving
such as user requirements
• specific research methods used to design the prototype/product
• explain if any control methods and testing are used
• list all the resources needed and their usefulness
•
iv. Chapter IV: Prototype/Product Development (development phase)
• describe each stage of prototype development in detail
• report unforeseen outcome or limitation, and how these factors were
eliminated or minimized

v. Chapter V: Testing and Results (implementation/testing phase)

(a) explain the testing method/approach used to test the prototype
(b) describe the complete prototype and compare with the initial purpose
and objectives
(c) discuss the behavior of the finished prototype and show its functionality
and output
(d) highlight the results and do include any major variations from the
original design

vi. Chapter VI: Conclusion and Suggestion (evaluation phase)

(a) explain what has been accomplished and what are the major things
learned from this project
(b) describe work still needs to be done on the prototype and how it can be
improved and/or enhanced to become a complete product
(c) give details on how this product can be beneficial for future
development and research
1.2.12 MAIN BODY SECTION HEADINGS FOR AN EXPERIMENTAL / A
SIMULATION PROJECT - NETWORKING
i. Chapter I: Introduction
• brief introductory to the title
• purpose and objective of study
• the problem stated in general and the specific way
• rationale for problem solving and methods available
ii. Chapter II: Literature Review
• show thorough knowledge of the research, theory, concepts, ideology and
opinion related to the title
• make aware that the review is selective
• show critical analysis of the review (e.g. Hierarchical Literature Map)
• does the review reveal the relation between what has previously been done
by others and what is proposed in this project
iii. Chapter III: Research Methodology
• Main work, e.g. solution approach, theory, simulation software, etc.
• Use flowchart diagram to explain the workflow or process of the
system/research design.
• Use Data Flow Diagram (DFD) to create an overview of the system to show
what kind of information will be input and output from the system
• Explain how data is gathered or generated and analysed
• Provide detail information of the procedure used in gathering the
experimental data
• Discuss any precaution taken and difficulties encountered
• Provide proper description of any equipment constructed for the purpose of
the project work
iv. Chapter IV: Prototype/Product Development
• Describe each stage of prototype development in detail
• Prototype/Product Verification
• Report unforeseen outcome or limitation, and how these factors were
eliminated or minimized
v. Chapter V: Testing and Result
• explain the testing method/approach used to test the prototype
• Results and findings based on the method described in previous chapter
• Use diagram, graphs, tables, charts etc., to present your result by giving clear
explanation on the result obtained.
• It may also contain a discussion of how you are designing your experiments
to verify the objectives of your project.
• Comment on unexpected results and offer reasons for such behavior
vi. Chapter VI: Conclusion and Suggestion
• explain what has been accomplished and what are the major things learned
form this project
• summarise the most important findings.
• suggest further work for your research area.
• give details on how this product can be beneficial for future development
and research
1.2.13 REFERENCES
All works or studies referred to in the report in the form of quotations or citations must
be included in the bibliography. The References should be written using the APA style.
Each reference should be written in single spacing format and a double space should be
left between references. The detailed information about the APA style can be found in
http://apastyle.apa.org/

Example:

Referencing a book with only one author:

Schwalbe. (2010). Managing Information Technology Projects. Canada: Cengage

Learning.

Referencing a book by two authors:

O’Brien & Marakas. (2011). Management Information Systems. New York:

McGraw-Hill.

Internet site with author:

Reid S. Monaghan. (2010). Booze and the Bible – Walking in the Wisdom of God.
Retrieved March 18, 2012, from
http://www.powerofchange.org/blog/month/january-2010.

Internet document without author:

E-Commerce User Survey. (n.d.). Retrieved March 8, 2012, from

http://www.mldh.com/mmh/survey.htm

Computer Program:

Toon Boom Animate Pro [Computer Software] (2012 – 2014). Montreal, Canada:
Toon Boom Animation Inc.

Conference Proceedings

Asmidar Abu Bakar, Roslan Ismail, J.Jais, J.A. Manan, (2010). Forming Trust in
Mobile Ad Hoc Network. Proceedings from CMC '2009: INTERNATIONAL
CONFERENCE ON COMMUNICATIONS AND MOBILE COMPUTING.
Kunming: China.
 Article in Journal Paginated by Volume

Journals that are paginated by volume begin with page one in issue one, and
continue numbering issue two where issue one ended, etc.

A. Abualkishik & K. Omar (2010). Quran Vibrations in Braille Code. JOURNAL

OF COMPUTER SCIENCE AND TELECOMMUNICATIONS, 26, 1232-
1512.

Article in Journal Paginated by Issue

Journals paginated by issue begin with page one every issue; therefore, the issue
number gets indicated in parentheses after the volume. The parentheses and issue
number are not italicized or underlined.

Scruton, R. (2010). The eclipse of listening. THE NEW CRITERION, 15(30), 5-

13.

1.2.14 LIST OF APPENDICES

The list of the appendices should include the alphabet of each appendix and the title of
the appendix.

1.3 FONT TYPE

The text should be typed using Font Type Times New Roman, Font size 12.
The body of the text should be typed with single spacing. Single-spacing is permitted
in tables, long quotations, short footnotes, notes and citation and the
bibliography/references.
Any amendments or corrections should be carefully inserted in the text. The use of
cellophane tape is not allowed.

1.4 MARGINS
The text should have the following margins:
Top: 2.0 cm
Right: 2.0 cm
Left: 4.0 cm
Bottom: 2.0 cm
Additional guidelines need to be followed:
 - All tables and figures must be placed within the specified margins.
- The last paragraph of the page should contain at least two sentences. If it does
not, the paragraph should begin on the next page.

1.5 PAGE NUMBERING

All page numbers should be printed 1.0 cm from the bottom margin and placed at the
right hand side without punctuation.
Font size 8 is recommended for numbers.
Roman numerals (i, ii, iii, etc) should be used in the Prefatory Section. Although the
Title Page is the first page of the Prefatory Section, no number is printed on it.
Numbering begins on the second page with (ii).

1.6 SUB-TOPICS
No specific arrangement is required for the numbering of sub-topics but, whatever
arrangement is adopted, it must be consistent.

1.7 ENDNOTES AND FOOTNOTES

There are differences in the use of endnotes and footnotes in various disciplines.
Endnotes and Footnotes should use a smaller font than the text (Font size 8).

When using endnotes and footnotes, insert a number formatted in superscript following
almost any punctuation mark. Endnote and footnote numbers should not follow dashes
( — ), and if they appear in a sentence in parentheses, the endnote and footnote numbers
should be inserted within the parentheses.

For example:
Scientists examined—over several years1—the fossilized remains of the wooly-wooly
yak.2 (These have now been transferred to the Chauan Museum.3)

When using the endnote or footnote function in a word-processing programme like

Microsoft Word, place all endnotes or footnotes at the bottom of the page on which
they appear. Footnotes may also appear on the final page of your document (usually
this is after the References page). Center the word “Footnotes” at the top of the page.
Indent five spaces on the first line of each endnote or footnote. Then, follow normal
paragraph spacing rules. Double-space throughout.

For example:
1
While the method of examination for the wooly-wooly yak provides important
insights to this research, this document does not focus on this particular species.

1.8 TABLES
Tables are printed within the body of the text at the centre of the frame and labeled
accordingly to the chapter in which they appear. Thus, for example, tables in Chapter
 3 are numbered sequentially: Table 3.1, Table 3.2, etc. The table title is placed single
space above the table itself and follows the format below:
Table 3.1: Title

Sample table

Table 2.1: BB84 Sifted Key

Alice’s Bit 0 1 1 0 1 0 0 1

Alice’s Basis + + x + x x x +

Alice Polarization

Bob’s Basis + x x x + x + +

Bob’s Measurement

Public Discussion

key 0 1 0 1

If the table contains a citation, the source of the reference should be placed below the
table.

1.9 FIGURES
Figures, like tables are printed within the body of the text at the centre of the frame and
labeled according to the chapter in which they appear. Thus, for example, figures in
Chapter 3 are numbered sequentially: Figure 3.1, Figure 3.2, etc.
Figures, unlike text or tables, contain graphs, illustrations or photographs and the labels
are placed single space at the bottom of the figure rather than at the top.
 Sample figure

Figure 3.1: Title

64-bit 64-bit

Initial Permuted
64 K1 56
Round 1 Permuted Left circular
64 56
K2
56
Round 2 Permuted Left circular

K16 48

Round 16 Permuted Left circular

56

32-bit Swap
64
Inverse Initial

64-bit
Figure 2.1: General Depiction of DES Encryption Algorithm [3]
 1400
Final Bit Length (bits) 1200 1146
1000
1003
800 702
600 590
521 Atiqah's
400 420 Simulato
200 r
127
98
0
1000 3000 5000 7000
Initital Bit Length (bits)
Figure 4.1:
Final Key Length Benchmarking on BB84 Protocol’s Simulator for No Attack
If the figure contains a citation, the source of the reference should be placed at the
bottom, after the label.

1.10 CITATION FORMAT

Research ethics involves all the moral and professional issues relating to research. The most
serious breach of ethical standards in writing PROJECT PAPER is the offence of plagiarism;
the expropriation of the intellectual property of another. Plagiarism is defined as the use of
original work, ideas or actual texts created by others, without acknowledging the original
source. Appropriate acknowledgement should be made by:
▪ Including the source in the bibliography
▪ Including the citation by acknowledging the source in the text; for example:
‘It takes leadership to improve communication.’ (Schwalbe, 2010).

Place direct quotations longer than 40 words in a free-standing block of typewritten

lines, and omit quotation marks. Start the quotation on a new line, indented one tab
from the left margin, i.e. in the same place you would begin a new paragraph. Maintain
double-spacing throughout. The parenthetical citation should come after the closing
punctuation mark.