Canadian Institute of Technology

Faculty of Engineering
Software Engineering Department

Project Title

A project submitted
in partial fulfillment of the requirements for the degree of
Bachelor Studies in Software Engineering (change if different)

by
Student’s First Name Last Name

Supervised by
Fabjan Lashi
Ibrahim Cekirri , Bledar Kazia
 UNDERTAKING

This is to declare that the project entitled “Project Title” is an original work done
by undersigned, in partial fulfillment of the requirements for the degree “Bachelor of ….

All the analysis, design and system development have been accomplished by the
undersigned. Moreover, this project has not been submitted to any other college or
university.

Student 1

Note: sign across your name

ii
 ABSTRACT

An abstract can be either descriptive or informative. A descriptive abstract

summarizes the motivation, scope and methods used to attain the solution or findings. An
informative on the other hand, is almost like the table of contents written in paragraph. It
also includes the results, conclusions and recommendations. The abstract should not
exceed 300 words and its contents are italicized.

State your problem identification, method used to resolve it the outcomes in a

short description not more than 300 words.

iii
Table of Contents

LIST OF TABLES ........................................................................................................................... v

LIST OF FIGURES ......................................................................................................................... vi
1. Software Requirements (Heading 1) ....................................................................................... 1
2. Background ............................................................................................................................. 1
2.1 Abbreviations and Acronyms (Heading 2) ...................................................................... 1
2.2 UML Diagrams (mandatory for the second year student/optional for first year students)
2
2.3 Tables (use them to formalize your document like actor system table or responsibility
tables) 3
3. Using the Template.................................................................................................................. 3
3.1 Contents ........................................................................................................................... 3
3.2 Figures and Table............................................................................................................ 3
4. Submission .............................................................................................................................. 4
5. Conclusion ............................................................................................................................... 4
Major Contributions (if in a group) ................................................................................................. 5
References ....................................................................................................................................... 6

iv
 LIST OF TABLES

Table 1: data coming from the application ..................................................................................... 2

v
 LIST OF FIGURES

Figure 1: UML Class Diagram showing f..... ..................................................................................... 2

vi
 1. Software Requirements (Heading 1)

This chapter comprises background of the project, the reasons for taking it,
problems addressed by the project and expected outcomes. A good report starts with an
introduction to the title of project. The necessary background information is provided to
establish context of the project. The motivation and significance of the project should be
highlighted. A crisp problem statement is followed by scope of the project along with any
limitation or exclusions. The specific objectives to be achieved should be stated. A
roadmap or organization of report concludes the chapter.

2. Background

When drafting your document, you may keep the data in separate files. You can
later copy and paste them in this template using “Keep Text Only” so that source
formatting isn’t included.

Always proofread your document. MS Word provides grammar and spell

checking. Although the grammar checking isn’t perfect at all times, the service serves as
a great guide in constructing your statements. The rule of thumb states that if it doesn’t
sound good, then something must be wrong. When using MS Word you can change it to,
“when there’s a red, green or blue wavy line, then something must be wrong.” Other
proofreading pointers follow in the next subsections.

2.1 Abbreviations and Acronyms (Heading 2)

Before using abbreviations or acronyms, make sure that the long name has been
used first followed by the short name enclosed in parentheses. Afterwards, the
abbreviations and acronyms can then be used alone. However, try not to use them when
writing titles or subtitles.

1
 Notice Heading 2’s format with a style of Bold, Italics and Left Indent. This
format should be followed for all subtitles and even inner subtitles.

2.2 UML Diagrams (mandatory for the second year student/optional for first year
students)

Figure 1: UML Class Diagram showing f.....

Jjsdsdsjdjs sdls

Sdjksj

ds

Table 1: data coming from the application

2
 2.3 Tables (use them to formalize your document like actor system table or
responsibility tables)

3. Using the Template

When your data are ready for the template, open the template file and click File-
Save As from MS Word menu. Your filename should follow this format:
Student name surname.docx

3.1 Contents

Start by changing the items in the preliminary pages of this template: cover page,
abstract, and table of contents. Use your outline as the basis for your table of contents.

3.2 Figures and Table

Place figures and tables in the same page where they were cited. You may use the
abbreviation “Fig. 1” to cite the figure.

Titles for both table and figure should be bold and centered using 10 point Times
New Roman. However, a table’s title should be written on top while a figure’s should be
at the bottom.

3
 In numbering both tables and figures, prefix the chapter number. For example the
2nd table in chapter 3 should be numbered as 3.2.

4. Submission

Put all project report and source code in a zip/rar archive and submit it by email
based on the dead line.

5. Conclusion

The conclusion is a required part that closes the document with a brief summary
of the study including the problems found and the proposed solution. Most importantly, it
should recommend to the readers the benefits of pursuing the project based on the
researcher’s analysis

4
 Major Contributions (if in a group)

In this section, students should list the major tasks each student, as member of the
team, has performed as well as highlight the major individual contributions for the
success of the project. It is expected that all students should fairly share the responsibility
of the tasks of the project under the direction of the supervisor.

5
 References

Citations are numbered consecutively inside brackets. In writing the references,

we follow American Psychological Association (APA) style. The references below show
examples of how to include a book with 3 authors [1], a project report [2], a book with
one author and cited 3 times [3-5], a book with 2 authors [6], an online book [7], an
article in a journal [8], an article from an online newspaper [9], work with no author [10],
an article in Wikipedia [11], a personal interview [12], a website [13], and a video found
online [14].

[1] Alred, G.J., Brusaw, C.T. & Oliu, W.E. Handbook of Technical Writing.
Bedford/St. Martin's, 2006.
[2] Al-Naim M. & Al-Mudara N. Electronic Court. King Faisal University
College of Computer Sciences and Information Technology, 2012.
[3-5] Bond, J. K. (2012). Advanced Programming in Java. (2nd ed.). New York:
ABC Publishing Company.
[6] Bond, J. K. & Lang, A. (2012). Action Script 3. (2nd ed.). New York: ABC
Publishing Company.
[7] Al-Arfaj, H. (2009). The Neural Networks in Motion. Retrieved from
http://books.google.com
[8] Al-Eid, A. (2012). The Changes in GUI. Journal of Computer Explosion,
27(10), 1327-33.
[9] Regal, R. (2012, April 7). Globalizing Variables. KFU News. Retrieved from
http://www.kfu.news.sa
[10] Snippets in C#. (2010). San Diego: ABC Press.
[11] Plagiarism. (n.d.). In Wikipedia. Retrieved January 10, 2013, from
http://en.wikipedia.org/wiki/Plagiarism
[12] Rosario, R. (2008, April 7). Personal interview.
[13] Sebastian, B. (2010, July 25). Programming Style. PCPrograms.com.
Retrieved July 25, 2010, from http://www.pcprograms.com.
[14] Al-Mulhem, K. (2009). Delphi Guide [Online Video]. Delphi Videos.

6
Retrieved from http://www.youtube.com/watch?v=asd5thw.