0% found this document useful (0 votes)
22 views

Guide Line

The document provides a template for the contents and formatting of a final year computing project documentation. It outlines the required preliminary pages, chapters to be included, and formatting guidelines for fonts, spacing, margins and pagination. The chapters cover introduction, existing system, system analysis, system design, implementation, and conclusions.

Uploaded by

Alebel Ayalneh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views

Guide Line

The document provides a template for the contents and formatting of a final year computing project documentation. It outlines the required preliminary pages, chapters to be included, and formatting guidelines for fonts, spacing, margins and pagination. The chapters cover introduction, existing system, system analysis, system design, implementation, and conclusions.

Uploaded by

Alebel Ayalneh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

December 2012 E.

Computing College
For all Computing 4th Year Students
Final Year Project I and II documentation Contents Template

Layout and Appearance

 The project should be printed on white A4 paper in Times New Roman, 12pt and the project
may be printed on both side of the paper.
 Line spacing in the abstract and text of the project should be 1.5.
 Single spacing should be used in long tables, block quotations separated from the text,
footnotes and bibliographical entries.
 Paragraphs should not be indented. One line space should be left between paragraphs.
 Margins should be one inch or 2.5cm on all sides.
 Pages should be numbered at the bottom in the center, using Arabic numerals (1, 2, 3)
starting with the first page of the project (i.e. the first page of the Introduction). Pages prior
to this should be numbered with lowercase Roman numerals (i, ii, iii).
 Chapters should start on a new page, but sections and subsections should not.
 Referencing style as recommended.
December 2012 E.C

A Project ON

(Title of the project)

<Font Size 16>times new roman<bold>

PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR THE


AWARD OF THE DEGREE OF

<Font Size 14>times new roman<normal>

BACHELOR OF SCIENCE
IN
(Computer Science)
<Font Size 14> times new roman <bold>

SUBMITTED BY

<Font Size 14> times new roman <bold>

(Name of the group members in capital letters)

<Font Size 12> times new roman <bold>

Under the Guidance of

<Font Size 12> times new roman <bold>

(Name of the Advisor)

<Font Size 12> times new roman <bold>

Department of Computer Science


College of Computing
Deber Berhan University
Deber Berhan Ethiopia

<Font Size 12> times new roman <bold>


YEAR
December 2012 E.C
DECLARATION

The project entitled ---------------------------------------------------------------------------------------- -------


------------------------------------------------------------------------------------------------------------ -----------
------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------- submitted to the DEPARTMENT for
the award of BSC in Computer Science is based on our original work carried out under the guidance
of -------------------------------------------- The project has not been submitted elsewhere for award of
any degree.

The material borrowed from other source and incorporated in the project has been duly
acknowledged and/or referenced.

We understand that we ourselves could be held responsible and accountable for plagiarism, if any,
detected later on.

Name of the students Signature Date


1. _________________________________ _______________ _________
2. _________________________________ _______________ _________
3. _________________________________ _______________ _________
4. _________________________________ _______________ _________
5. _________________________________ _______________ _________
6. _________________________________ _______________ _________

Name of the Advisor Signiture Date


_________________________________ _______________ _________
December 2012 E.C

Format for Project Submission


Programme name Example BSC CS
Batch
Name of the student
Title
Name of the advisor
Designation of guide

We hereby submit the hard bound copies (3) of project report.


Date:
Signature of the student
Name of the student

Recommended / not recommended by the supervisor

Signature of the advisor


Name & Designation of guide

----------------------------------------------------------------------------------------------------------------
For office use only
 The project is in prescribed format Yes / No
 Has the committee recommended the submission of project Yes / No

Signature of the HOD

Conformation of project submission


December 2012 E.C

Contents of Industrial Project Documantation

Preliminary pages
I. Title page (See its format)
II. Approval letter (the letter has to be prepared by the department on letter head and signed by
the supervisor)
III. Dedication (One page -optional)
IV. Acknowledgement
V. Table of contents
VI. List of figures
VII. List of Tables
VIII. Abbreviations
IX. Patents Information (optional)
X. Abstract
December 2012 E.C

CHAPTER ONE: INTRODUCTION


1.1 Introduction
1.2 Background of the project
1.3 Statement of the problem
1.4 Objectives of the project
1.4.1 General objective
1.4.2 Specific objective
1.5 Feasibility Analysis
1.6 Significance of the project
1.7 Beneficiaries of the system
1.8 Methodology for the project
1.8.1 Data collection method
1.8.2 System Analysis and Design Methodology
1.8.3 CASE Tools
1.8.4 Requirement specification testing
1.9 Scope and Limitation of the project
1.10 Assumption and Constraints

CHAPTER TWO: DESCRIPTION OF THE EXISTING SYSTEM


2.1 Introduction
2.2 Players in existing system
2.3 Business rules
2.4 Report, forms generated in the existing system
2.5 Problems of existing system
2.6 Practices to be preserved from existing system
2.7 Proposed system
2.8 System requirements of the new system
2.8.1 Functional requirements
2.8.2 Non-functional requirements

CHAPTER THREE: SYTEM ANALYSIS


3.1 Introduction
3.2 Scenario of the Use Case
3.3 Use Case Modeling
3.4 Use Case description
3.5 Analysis level class diagram (conceptual modeling)
3.6 Sequence Diagram
3.7 State Chart Modeling
3.8 Activity diagram
3.9 User Interface Prototyping
3.10 Supplementary specifications
3.10.1 Business Rules
3.10.2 Constraints
December 2012 E.C

CHAPTER FOUR: SYSTEM DESIGN


4.1 Introduction
4.2 System Architecture
4.3 Class Modeling
4.4 Component Diagram
4.5 Subsystem decomposition
4.6 Deployment Modeling
4.7 Database Design
CHAPTER FIVE: IMPLEMENTATION
5.1 Introduction
5.2 Hardware and Software acquisitions
5.3 Language specification and selection strategy
5.4 Sample code
5.5 Test procedures
5.6 User manual preparation
5.6.1 Training
5.6.2 Installation
5.6.3 Start-up Strategy

CHAPTER SIX: CONCLUSIONS AND RECOMMENDATIONS


6.1 Conclusions
6.2 Recommendations
 References

References or Bibliography , Webliography


Use the following format (APA citation style)
Author(s) (date & year), Title of Book, Title of Article, Title of Periodical, Volume, Pages, Place
of Publication, Publisher and Other Information.
Example:
James, N. E. (1988). Two sides of paradise: The Eden myth according to Kirk and Spock. In D.
Palumbo (Ed.), Spectrum of the fantastic (pp. 219-223). Westport, CT: Greenwood.
Lynch, T. (1996). DS9 trials and tribble actions review. Retrieved March 08, 2010, from Psi Phi:
Bradley’s Science Fiction Club
 Appendix

NB:
 Final Project I documentation includes the first 4 chapters (chapter 1 to 4) only.
 Final Project II documentation should contain all chapters; which is Final Project I
documentation plus chapter 5 and 6.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy