AUTHOR ’ S NAME

Enrollment

Title of the Dissertation

Bachelor of Science in Computer Science

Supervisor: Supervisor Name

Co-Supervisor: Co-Supervisor name

Department of Computer Science

Bahria University, Islamabad

September 2015

c Author Name, 2015
 Certificate

We accept the work contained in the report titled “TITLE OF THE REPORT”, written by
Mr. AUTHOR1 NAME AND Mr. AUTHOR2 NAME as a confirmation to the required
standard for the partial fulfillment of the degree of Bachelor of Science in Computer
Science.

Approved by . . . :

Supervisor: Name of the Supervisor (Title)

Internal Examiner: Name of the Internal Examiner (Title)

External Examiner: Name of the External Examiner (Title)

Project Coordinator: Name of the Project Coordinator (Title)

Head of the Department: Name of the HOD (Title)

September 31st , 2015

Abstract

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut purus elit, vestibulum ut,
placerat ac, adipiscing vitae, felis. Curabitur dictum gravida mauris. Nam arcu libero,
nonummy eget, consectetuer id, vulputate a, magna. Donec vehicula augue eu neque.
Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas.
Mauris ut leo. Cras viverra metus rhoncus sem. Nulla et lectus vestibulum urna fringilla
ultrices. Phasellus eu tellus sit amet tortor gravida placerat. Integer sapien est, iaculis
in, pretium quis, viverra ac, nunc. Praesent eget sem vel leo ultrices bibendum. Aenean
faucibus. Morbi dolor nulla, malesuada eu, pulvinar at, mollis ac, nulla. Curabitur auctor
semper nulla. Donec varius orci eget risus. Duis nibh mi, congue eu, accumsan eleifend,
sagittis quis, diam. Duis eget orci sit amet orci dignissim rutrum.
Nam dui ligula, fringilla a, euismod sodales, sollicitudin vel, wisi. Morbi auctor lorem
non justo. Nam lacus libero, pretium at, lobortis vitae, ultricies et, tellus. Donec aliquet,
tortor sed accumsan bibendum, erat ligula aliquet magna, vitae ornare odio metus a mi.
Morbi ac orci et nisl hendrerit mollis. Suspendisse ut massa. Cras nec ante. Pellentesque a
nulla. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus
mus. Aliquam tincidunt urna. Nulla ullamcorper vestibulum turpis. Pellentesque cursus
luctus mauris.
Nulla malesuada porttitor diam. Donec felis erat, congue non, volutpat at, tincidunt
tristique, libero. Vivamus viverra fermentum felis. Donec nonummy pellentesque ante.
Phasellus adipiscing semper elit. Proin fermentum massa ac quam. Sed diam turpis,
molestie vitae, placerat a, molestie nec, leo. Maecenas lacinia. Nam ipsum ligula, eleifend
at, accumsan nec, suscipit a, ipsum. Morbi blandit ligula feugiat magna. Nunc eleifend
consequat lorem. Sed lacinia nulla vitae enim. Pellentesque tincidunt purus vel magna.
Integer non enim. Praesent euismod nunc eu purus. Donec bibendum quam in tellus.
Nullam cursus pulvinar lectus. Donec et mi. Nam vulputate metus eu enim. Vestibulum
pellentesque felis eu massa.
Quisque ullamcorper placerat ipsum. Cras nibh. Morbi vel justo vitae lacus tincidunt
ultrices. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. In hac habitasse platea
dictumst. Integer tempus convallis augue. Etiam facilisis. Nunc elementum fermentum
wisi. Aenean placerat. Ut imperdiet, enim sed gravida sollicitudin, felis odio placerat
quam, ac pulvinar elit purus eget enim. Nunc vitae tortor. Proin tempus nibh sit amet nisl.
Vivamus quis tortor vitae risus porta vehicula.
Fusce mauris. Vestibulum luctus nibh at lectus. Sed bibendum, nulla a faucibus
semper, leo velit ultricies tellus, ac venenatis arcu wisi vel nisl. Vestibulum diam. Aliquam
pellentesque, augue quis sagittis posuere, turpis lacus congue quam, in hendrerit risus eros
eget felis. Maecenas eget erat in sapien mattis porttitor. Vestibulum porttitor. Nulla facilisi.
Sed a turpis eu lacus commodo facilisis. Morbi fringilla, wisi in dignissim interdum, justo

i
ii

lectus sagittis dui, et vehicula libero dui cursus dui. Mauris tempor ligula sed lacus. Duis
cursus enim ut augue. Cras ac magna. Cras nulla. Nulla egestas. Curabitur a leo. Quisque
egestas wisi eget nunc. Nam feugiat lacus vel est. Curabitur consectetuer.
Suspendisse vel felis. Ut lorem lorem, interdum eu, tincidunt sit amet, laoreet vitae,
arcu. Aenean faucibus pede eu ante. Praesent enim elit, rutrum at, molestie non, nonummy
vel, nisl. Ut lectus eros, malesuada sit amet, fermentum eu, sodales cursus, magna. Donec
eu purus. Quisque vehicula, urna sed ultricies auctor, pede lorem egestas dui, et convallis
elit erat sed nulla. Donec luctus. Curabitur et nunc. Aliquam dolor odio, commodo pretium,
ultricies non, pharetra in, velit. Integer arcu est, nonummy in, fermentum faucibus, egestas
vel, odio.
Sed commodo posuere pede. Mauris ut est. Ut quis purus. Sed ac odio. Sed vehicula
hendrerit sem. Duis non odio. Morbi ut dui. Sed accumsan risus eget odio. In hac habitasse
platea dictumst. Pellentesque non elit. Fusce sed justo eu urna porta tincidunt. Mauris felis
odio, sollicitudin sed, volutpat a, ornare ac, erat. Morbi quis dolor. Donec pellentesque,
erat ac sagittis semper, nunc dui lobortis purus, quis congue purus metus ultricies tellus.
Proin et quam. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per
inceptos hymenaeos. Praesent sapien turpis, fermentum vel, eleifend faucibus, vehicula eu,
lacus.
Acknowledgments

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut purus elit, vestibulum ut,
placerat ac, adipiscing vitae, felis. Curabitur dictum gravida mauris. Nam arcu libero,
nonummy eget, consectetuer id, vulputate a, magna. Donec vehicula augue eu neque.
Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas.
Mauris ut leo. Cras viverra metus rhoncus sem. Nulla et lectus vestibulum urna fringilla
ultrices. Phasellus eu tellus sit amet tortor gravida placerat. Integer sapien est, iaculis
in, pretium quis, viverra ac, nunc. Praesent eget sem vel leo ultrices bibendum. Aenean
faucibus. Morbi dolor nulla, malesuada eu, pulvinar at, mollis ac, nulla. Curabitur auctor
semper nulla. Donec varius orci eget risus. Duis nibh mi, congue eu, accumsan eleifend,
sagittis quis, diam. Duis eget orci sit amet orci dignissim rutrum.
Nam dui ligula, fringilla a, euismod sodales, sollicitudin vel, wisi. Morbi auctor lorem
non justo. Nam lacus libero, pretium at, lobortis vitae, ultricies et, tellus. Donec aliquet,
tortor sed accumsan bibendum, erat ligula aliquet magna, vitae ornare odio metus a mi.
Morbi ac orci et nisl hendrerit mollis. Suspendisse ut massa. Cras nec ante. Pellentesque a
nulla. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus
mus. Aliquam tincidunt urna. Nulla ullamcorper vestibulum turpis. Pellentesque cursus
luctus mauris.
Nulla malesuada porttitor diam. Donec felis erat, congue non, volutpat at, tincidunt
tristique, libero. Vivamus viverra fermentum felis. Donec nonummy pellentesque ante.
Phasellus adipiscing semper elit. Proin fermentum massa ac quam. Sed diam turpis,
molestie vitae, placerat a, molestie nec, leo. Maecenas lacinia. Nam ipsum ligula, eleifend
at, accumsan nec, suscipit a, ipsum. Morbi blandit ligula feugiat magna. Nunc eleifend
consequat lorem. Sed lacinia nulla vitae enim. Pellentesque tincidunt purus vel magna.
Integer non enim. Praesent euismod nunc eu purus. Donec bibendum quam in tellus.
Nullam cursus pulvinar lectus. Donec et mi. Nam vulputate metus eu enim. Vestibulum
pellentesque felis eu massa.
Quisque ullamcorper placerat ipsum. Cras nibh. Morbi vel justo vitae lacus tincidunt
ultrices. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. In hac habitasse platea
dictumst. Integer tempus convallis augue. Etiam facilisis. Nunc elementum fermentum
wisi. Aenean placerat. Ut imperdiet, enim sed gravida sollicitudin, felis odio placerat
quam, ac pulvinar elit purus eget enim. Nunc vitae tortor. Proin tempus nibh sit amet nisl.
Vivamus quis tortor vitae risus porta vehicula.
Fusce mauris. Vestibulum luctus nibh at lectus. Sed bibendum, nulla a faucibus
semper, leo velit ultricies tellus, ac venenatis arcu wisi vel nisl. Vestibulum diam. Aliquam
pellentesque, augue quis sagittis posuere, turpis lacus congue quam, in hendrerit risus eros
eget felis. Maecenas eget erat in sapien mattis porttitor. Vestibulum porttitor. Nulla facilisi.
Sed a turpis eu lacus commodo facilisis. Morbi fringilla, wisi in dignissim interdum, justo

iii
iv

lectus sagittis dui, et vehicula libero dui cursus dui. Mauris tempor ligula sed lacus. Duis
cursus enim ut augue. Cras ac magna. Cras nulla. Nulla egestas. Curabitur a leo. Quisque
egestas wisi eget nunc. Nam feugiat lacus vel est. Curabitur consectetuer.
Suspendisse vel felis. Ut lorem lorem, interdum eu, tincidunt sit amet, laoreet vitae,
arcu. Aenean faucibus pede eu ante. Praesent enim elit, rutrum at, molestie non, nonummy
vel, nisl. Ut lectus eros, malesuada sit amet, fermentum eu, sodales cursus, magna. Donec
eu purus. Quisque vehicula, urna sed ultricies auctor, pede lorem egestas dui, et convallis
elit erat sed nulla. Donec luctus. Curabitur et nunc. Aliquam dolor odio, commodo pretium,
ultricies non, pharetra in, velit. Integer arcu est, nonummy in, fermentum faucibus, egestas
vel, odio.
Sed commodo posuere pede. Mauris ut est. Ut quis purus. Sed ac odio. Sed vehicula
hendrerit sem. Duis non odio. Morbi ut dui. Sed accumsan risus eget odio. In hac habitasse
platea dictumst. Pellentesque non elit. Fusce sed justo eu urna porta tincidunt. Mauris felis
odio, sollicitudin sed, volutpat a, ornare ac, erat. Morbi quis dolor. Donec pellentesque,
erat ac sagittis semper, nunc dui lobortis purus, quis congue purus metus ultricies tellus.
Proin et quam. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per
inceptos hymenaeos. Praesent sapien turpis, fermentum vel, eleifend faucibus, vehicula eu,
lacus.

AUTHOR NAME
Islamabad, Pakistan

September 2015
 “We think someone else, someone smarter than us,
someone more capable, someone with more resources will solve that problem.
But there isn’t anyone else.”

Regina Dugan

v
vi
Contents

Abstract i

1 Introduction 1
1.1 Is computer science science? . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 The Degree Project Report . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Literature Review 3

3 Requirement Specifications 5

4 Design 7
4.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Design Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Design Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 High Level Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.5 Low Level Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.6 Database Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.7 GUI Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.8 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5 System Implementation 11
5.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 System Testing and Evaluation 13

7 Conclusions 15

A User Manual 17

References 19

vii
viii CONTENTS
List of Figures

1.1 Final Year Project Lifecycle . . . . . . . . . . . . . . . . . . . . . . . . 2

ix
x LIST OF FIGURES
List of Tables

xi
xii LIST OF TABLES
Acronyms and Abbreviations

DSA Data Structure and Algorithms

OOP Object Oriented Programming
PF Programming Fundamentals
SE Software Engineering
SQL Structured Query Language
UNESCO United Nations Educational, Scientific and Cultural Organization
UNICODE Unique, Universal, and Uniform Character enCoding
XML Extensible Markup Language

xiii
xiv Acronyms and Abbreviations
Chapter 1

Introduction

1.1 Is computer science science?

Is computer science, science? Yes, it is [1].

This is one of the most important chapters of the report. It should begin with a clear
statement of what the project is about so that the nature and scope of the project can be
understood by any reader. It should summarise everything you set out to achieve, provide
a clear summary of the project’s background, relevance and main contributions. The
introduction should set the context for the project and should provide the reader with a
summary of the key things to look out for in the remainder of the report. When detailing
the contributions it is helpful to provide pointers to the section(s) of the report that provide
the relevant technical details. The introduction itself should be largely non-technical. It is
useful to state the main objectives of the project as part of the introduction. Should have
the following headings:

• Project Background/Overview

• Problem Description

• Project Objectives

• Project Scope

1.2 The Degree Project Report

The project report is an extremely important aspect of the degree project. It should be
properly structured and contain all the necessary and appropriate information regarding
the project.

1
2 Introduction

Project-I PROJECT-II

Phase 5 Phase 6
Maintain Phase 1 Phase 9 Midterm
Folder(for project FYP Life Assign group id`s to Give awards to FYP Life Evaluation of
coordinator) and Project by
File(for Cycle students who register
project-1
prize winning
projects Cycle supervisor and
supervisor) of submit form D to
each group project coordinator

Phase 4 Phase 3 Phase 2 Phase 7

Submission of Schedule Defense Phase 9 Collection of
Proposal and form A,B Phase 8
Form G and new presentation, External plagiarism report
submission by student
copy of proposal create panel and Evaluation Open House abstract, cv , Pena
to project coordinator
after defense assign panel to And compile flex and broachers
After selecting
presentation each group result from groups
supervisor and project

Figure 1.1: Final Year Project Lifecycle

Project report has to be progressively developed as and when various stages of project
are completed and last few weeks should be used to bring it together as a coherent
document.
A well structured and consistently formatted project report makes reading easier
and is suggestive of a careful and professional attitude towards its preparation.
Remember that quantity does not automatically guarantee quality. A 150 page report is
not twice as good as a 75-page one, nor a 10,000 line implementation twice as good as a
5,000 line one. Conciseness, clarity and elegance are invaluable qualities in report writing,
just as they are in programming, and will be rewarded appropriately.
This document provides various guidelines for preparing a well structured project
report.
Chapter 2

Literature Review

Literature review is a systematic method of identifying, evaluating and interpreting the

work (similar to yours) produced by others. This chapter should set the project into context
and give the proposed layout for achieving the project goals. It is an important chapter
especially if the project involves significant amount of ground work. Review prior work
critically, identify gaps in knowledge/areas of application and build an argument for your
own work. When referring to other pieces of work, cite the sources where they are referred
to or used, rather than just listing them at the end.

3
4 Literature Review
Chapter 3

Requirement Specifications

In this chapter, first describe the existing system, its limitations or drawbacks and then
explain how the new or proposed system will overcome these problems. This should then
be followed by complete requirements specification for the proposed system. Describe
the behavior of the system to be developed and include a set of use cases that describe
interactions the users will have with the system. In addition also describe non-functional
requirements. Non-functional requirements impose constraints on the design or imple-
mentation (such as performance engineering requirements, quality standards, or design
constraints). Should have the following headings:

• Existing System

• Proposed System

• Requirement Specifications

• Use Cases

5
6 Requirement Specifications
Chapter 4

Design

Systems design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. This chapter should have the
following sections:

4.1 System Architecture

This section describes the system in narrative form using non-technical terms. It should
provide a high-level system architecture diagram showing a subsystem breakout of the
system, if applicable. The high-level system architecture or subsystem diagrams should, if
applicable, show interfaces to external systems. Supply a high-level context diagram for
the system and subsystems, if applicable.

4.2 Design Constraints

This section describes any constraints in the system design (reference any trade-off analyses
conducted such, as resource use versus productivity, or conflicts with other systems) and
includes any assumptions made during the developing the system design.

4.3 Design Methodology

Summarize the approach that will be used to create and evolve the designs for this system.
Cover any processes, conventions, policies, techniques or other issues which will guide
design work. This is for deciding whether you will use structured, object-oriented or other
specific methodologies. Most people will use some object-oriented technique with UML.

7
8 Design

4.4 High Level Design

This section describes in further detail elements discussed in the Architecture. High-level
designs are most effective if they attempt to model groups of system elements from a
number of different views. Typical viewpoints are:

1. Conceptual or Logical: This view shows the logical functional elements of the system.
Each component represents a similar grouping of functionality. For UML, this would
be a component diagram or a package diagram.

2. Process: this view is the runtime view of the system. The components are threads or
processes or distributed applications. In UML, this would be a process interaction
diagram.

3. Physical: this view is for distributed systems. The components are physical pro-
cessors that have parts of the system running on them. For UML, this would be a
deployment diagram.

4. Module: this view is for project management and code organization. The components
are typically files or directories. This picture shows how the directory structure of
the build and development environment will be designed.

5. Security: this view typically focuses on the components that cooperate to provide
security features of the system. It is often a subset of the Conceptual view.

4.5 Low Level Design

This section provides low-level design descriptions that directly support construction of
modules. Normally this section would be split into separate documents for different areas
of the design. For each component we now need to break it down into its fundamental units
or modules. For an OO implementation in Java, our components would become packages.
Then the low level design will take each package and break it down into its classes. For
smaller systems, you may have a single UML class diagram that each module description
refers to.

4.6 Database Design

The section should reveal the final design of all database management system (DBMS)
files and the non-DBMS files associated with the system under development. Provide a
comprehensive data dictionary showing data element name, type, length, source, validation
rules, maintenance (create, read, update, delete capability), data stores, outputs, aliases,
and description.
4.7 GUI Design 9

4.7 GUI Design

This section provides the detailed design of the system and subsystem inputs and outputs
relative to the user. Depending on the particular nature of the project, it may be appropriate
to repeat these sections at both the subsystem and design module levels.

4.8 External Interfaces

External systems are any systems that are not within the scope of the system under
development. In this section, describe the electronic interface(s) between this system and
each of the other systems and/or subsystem(s), emphasizing the point of view of the system
being developed.
10 Design
Chapter 5

System Implementation

Implementation is the process of moving an idea from concept to reality. The System
implementation is a realization of a technical specification or algorithm as a program,
software component, or other computer system through programming and deployment.

5.1 System Architecture

Describe the architecture e.g. in terms of: System internal components, Functionality of
the components, Communication between the components Tools and Technology Used
Development Environment/Languages Used Processing Logic/Algorithms Application
Access Security Describe new application access related security measures, e.g. in terms of:
Security Zones/Firewalls, Encryption, Authentication, e.g. Account & Password structures
and rules, Authorization, e.g. operator rights and roles, authority handling, Auditing /
Access Logging, Safe Data Storage Database Security
Describe new DB related security measures, e.g. in terms of: Remote Access, Authen-
tication (Account & Password: structure, rules), Authorization (rights/roles, handling),
Anonymous and Group Users, Auditing/Logging (events, data, log handling).

11
12 System Implementation
Chapter 6

System Testing and Evaluation

System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system’s compliance with its specified requirements. Be warned
that many projects fall down through poor evaluation. Simply building a system and
documenting its design and functionality is not enough to gain top marks. It is extremely
important that you evaluate what you have done both in absolute terms and in comparison
with existing techniques, software, hardware etc. This might involve quantitative evaluation
and qualitative evaluation such as expressibility, functionality, ease-of-use etc. At some
point you should also evaluate the strengths and weaknesses of what you have done. Avoid
statements like "The project has been a complete success and we have solved all the
problems associated with ...! It is important to understand that there is no such thing as
a perfect project. Even the very best pieces of work have their limitations and you are
expected to provide a proper critical appraisal of what you have done. The following are
different types of testing that should be considered during System testing:

• Graphical user interface testing

• Usability testing

• Software performance testing

• Compatibility testing

• Exception handling

• Load testing

• Security testing

• Installation testing

13
14 System Testing and Evaluation

For research based projects this chapter should include complete description of evalua-
tion metrics and analysis/discussion of evaluation results.
Chapter 7

Conclusions

The project’s conclusions should list the things which have been learnt as a result of the
work you have done. For example, "The use of overloading in C++ provides a very elegant
mechanism for transparent parallelisation of sequential programs". Avoid tedious personal
reflections like "I learned a lot about C++ programming..." It is common to finish the report
by listing ways in which the project can be taken further. This might, for example, be a
plan for doing the project better if you had a chance to do it again, turning the project
deliverables into a more polished end product.

15
16 Conclusions
Appendix A

User Manual

Appendices are provided to give supplementary information, which is included in the main
text may serve as a distraction and cloud the central theme.

• Appendices should be numbered using alphabets, e.g. Appendix A, Appendix B, etc.

• Tables and References appearing in appendices should be numbered and referred to

at appropriate places just as in the case of chapters.

• Appendices shall carry the title of the work reported and the same title shall be
written in the contents page.

17
18 User Manual
References

[1] Peter J. Denning. Is computer science science? Commun. ACM, 48(4):27–31, April
2005. Cited on p. 1.

19
20 REFERENCES