Scribd
Upload
17 views

Project Preparation Guide Line

Uploaded by

Ayana Negera
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
17 views

Project Preparation Guide Line

Uploaded by

Ayana Negera
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/ 2

===========================================================================

Department: Computer Science


Program: Regular Year: III A/Year: 2024
Project Document Preparation General Guideline
You should have to should organize your document, basically including the following issues:
1) Writing format
 Typefaces, Font Size, Paper and Pagination
o Mandatory write in English.
o All pages should be set with the same margin.
 The left margin should be 4 cm (for binding purposes)
 Top margin 2.5 cm
 right 2.5cm
 bottom margin 2.5
o Line spacing at 1.5
o Font size 12 point
o Font type is Times New Roman.
o Page numbers at the bottom right-hand corner.
o The preliminary pages must be numbered in Roman numerals (i, ii, ii).
o All pages of the main text should be numbered 1, 2, and 3.
2) Basic structure of the document
I) Title Page /Cover pages/
------- Contains ------
 University College Name
 Full title of the project as approved by the department.
 The full name of the author/your name/.
 The month and year of submission (2024).
II) Acknowledgements
This part is all about thanking those who have helped you directly or indirectly on the
completion of the project.
III) Abstract
------- Contains ------
It should be:
• Short and concise (n o t longer than 250 words and rarely longer
than one paragraph)
• State the objective
• State the method used
• State the result (optional)
• State the conclusions
IV) Table of contents
V) Acronym of the abbreviated words
Chapter 1: Introduction
Introduction chapter should include the following sub chapter:
 Background of the organization (on which you are working)
 Background of Study (about your title)
 Mission and vision statement
 Problems Statement
 Objective
 Scope and limitation of the study
 Methodology
 Significance and contribution of the study
===========================================================================
 Hardware & Software Requirements
 Project cost and budget estimation (schedule for the
project)
 Constraint & Critical Assumption
Chapter 2: Description of Existing System and Requirement
In this section you need to discuss thoroughly on --------
2.1 Over view of existing system
2.2 Problem with existing system
2.3 Business rules of existing system
2.4 Over view proposed system
2.5 Functional Requirement
2.6 Non-Functional requirement
Chapter 3: System Modeling and Design of the system
The Design section documents the design decisions that have been taken. The
structure of the system and its components has to be established.
The various system design issues that have to be addressed are:
 Software Design Approach  Flexibility
 Performance  Re-usability and portability
 Robustness  Security
 Interactively
The design should also consist of the following:
 Architecture Design – Interaction between components and/or modules
 Interface Design
 System Modeling – UML diagrams
All UML diagrams
 Database Design – ERD diagram (Optional if any )
____
__
_
Chapter 4: Conclusion and Recommendation
This is usually the last chapter in the report which contains three main parts:
Conclusion:
1) Achievements: It should critically assess the work done including
the strengths and weaknesses and try to explain the results obtained.
2) Difficulties: The difficulties can also be summarized. Keep in mind
that the conclusion should not be overcritical or sound depressing.
Recommendation:
3) Future Works: No report is totally complete or has completely explored a
domain. You can give some indications where future work might be
carried out or what other domain you would have explored without the
current time/resource constraints.
Reference

You might also like