WERABE UNIVERSITY

Institute of Technology

Final Year Project Guideline

o Information Systems
o Computer Science
o Information Technology

November, 2022

Werabe, Ethiopia

Final Year Project Guideline | 2023

 1. Format or writing style in your Documentation Project
o Paper size and margins
- Use A-4 paper (8 1/2 x 11”) and 2.5 cm for all margins of the project document
o Line and paragraph spacing
-Use 1.5 spacing for the body of the text, except for tables and references, where you
need to use single line spacing. Do not indent paragraphs but use block typing and no
need of background effects. Alignment of the text is essential.
o Font type and font size
-Capitalize only the first letter of each word, excluding common words in the title and
make its font 16 and Bold. The common words are prepositions, conjunctions or
connectives (such as: of, in, a, and, or, etc.)
Example 1: Title & Font size
-Capitalize only the first letter of the main heading and make its font size 16 and bold
as above.
Example 2: Subheading and Font size
o Chapter One

Introduction
-Capitalize only the first letter of the subheading and make its font size 14 and bold as
above.
Example 3: Sub-subheading
Project Management
-If there is a sub-subheading, capitalize only the first letter and make it italic with a
font size of 12 without bolding as above.

Final Year Project Guideline | 2023

 2. Cover Page of Your Documents

UNIVERSITY LOGO

UNIVERSITY NAME

INSTITUTE NAME

DEPARTMENT NAME

TITLE OF YOUR PROJECT

BY

STUDENT FULL NAME (WITH ID)

UNDER GUIDANCE OF

ADVISOR FULL NAME

SEPTEMBER 2022

Final Year Project Guideline | 2023

 UNIVERSITY NAME

INSTITUTE NAME

DEPARTMENT NAME

TITLE OF YOUR PROJECT

SUBMITED TO DEPARTMENT OF (YOUR DEPARTMENT NAME)

IN PARTIAL FULFILMENT OF THE REQUIREMENT FOR

THE DEGREE OF BACHLER OF SCIENCE IN (YOUR DEPARTMENT NAME)

By

Student Name (with ID)

WERABE UNIVERSITY, WERABE, ETHIOPIA

September 28, 2022

3. Approval Form

Final Year Project Guideline | 2023

This is to confirm that the project report entitled ____________________________ submitted
to Werabe University, Institute of Technology department of (your department name) in
partial fulfilment of the requirement for the award of the degree of Bachler of Science in
(department name) is an original work carried out by Student Name 1, Student Name2, ,
Student Name3, under my guidance. The matter embodied in this project is reliable and is
genuine work done by the student and has not been submitted whether to this University or to
any other University /Institute for the fulfilment of the requirement of any study.

Student Team Approval Form

Student Name Student Signature

---------------------------------------------- ---------------------

---------------------------------------------- ---------------------

---------------------------------------------- ---------------------

Advisor and department head Approval Form

Advisor Name Advisor Signature

---------------------------------------------- -------------------

Department Head Name Department Head Signature

---------------------------------------------- ---------------------

Examiner Approval Form

Examiner Name Examiner Signature

---------------------------------------------- ---------------------

---------------------------------------------- ---------------------

---------------------------------------------- ---------------------

Final Year Project Guideline | 2023

 4. Proposal of Final Year Project Documentation
o Title and Cover Page
o Approval Form Page
o Abstract
o Acknowledgments
o Table of Contents
o List of Acronyms (if any)
o List of Tables (if any)
o List of Figures (if any)
1. Introduction
2. Background of the Study
3. Motivation of the Study
4. Statement of the Problem
5. Objective of the Study
5.1. General Objective
5.2. Specific Objectives
6. Scope and Limitation of the Project
6.1. Scope of the Project
6.2. Limitation of the Project
7. Methodology
8. Significance of the Project
9. Target Beneficiaries of the System
10. Feasibility Study
10.1. Operational feasibility
10.2. Technical feasibility
10.3. Economic feasibility
10.4. Political feasibility(optional)
11. Task and Time Schedule
12. Budget Plan
13. Team Organization
14. References

Final Year Project Guideline | 2023

 5. Final Report Layout of Final Year Project Documentation
I. Preliminary Pages
II. Title Page (See its format)
III. Acknowledgement
IV. Table of contents
V. List of figures
VI. List of Tables
VII. Abbreviations
VIII. Abstract

Final Year Project Guideline | 2023

Chapter One: Introduction
1.1. Introduction
1.2. Background Information of the Organization
1.3. Background of the Project
1.4. Statement of the Problem
1.5. Objective of the project
1.5.1 General Objective
1.5.2 Specific objective
1.6. Feasibility Analysis
1.6.1 Operational feasibility
1.6.2 Technical feasibility
1.6.3 Economic feasibility
1.6.4 Behavioral/Political feasibility
1.6.5 Schedule feasibility
1.7. Scope and Limitation of the project
1.7.1. Scope of the project
1.7.2. Limitation of the project
1.8. Significance of the Project
1.9. Target Beneficiaries of the System
1.10. Methodology for the Project
1.10.1. Requirement Gathering Methods
1.10.2. Requirement Modeling (Structured or Object Oriented)
1.10.3. Tools Used
1.11. Risks & Contingencies
1.12. Assumptions and Constraints
1.13. Team Composition
1.14. Time Table

Final Year Project Guideline | 2023

Chapter Two: Description of the Existing System
2.1. Introduction of Existing System

2.2. Organization Structure (if any)

2.3. Users of Existing System

2.4. Major functions of the Existing System

2.5. Existing System Workflow Structure

2.6. Business Rules of the Existing System

2.7. Forms and other documents of the existing systems (if any)

2.8. Bottlenecks of the existing system (using for example PIECES frame Work).
2.5.1 Performance (Response time)
2.5.2 Input (Inaccurate/redundant/flexible) and Output (Inaccurate)
2.5.3 Security and Controls
2.5.4 Efficiency

Final Year Project Guideline | 2023

Chapter Three: Proposed System
3.1. Introduction
3.2. Proposed System Overview
3.3. Functional requirements
3.4. Nonfunctional Requirements

Final Year Project Guideline | 2023

Chapter Four: System Analysis
4.1. System Models
4.1.1 Scenarios
4.1.2 Use Case Model
4.1.3 Use Case Documentation/Description
4.1.4 Object Model
[Link] Data Dictionary
[Link] Class Diagram (Conceptual Modeling)
4.2. Dynamic Model
4.2.1 Sequence Diagram
4.2.2 Activity Diagram
4.2.3 State Diagrams
4.3. ER Diagram (optional depending on your design methodology)
4.3.1 Mapping
4.3.2 Normalization (1st - BNCF normal forms)

Final Year Project Guideline | 2023

Chapter Five: System Design
5.1. System Design Overview
5.2. Design Considerations
5.3. Design Goals
5.4. Design Trade-offs
5.5. Architecture of the System
5.6. System Decomposition
5.7. Hardware/Software mapping
5.8. Persistent Data Management
5.9. User Interface Design
5.10. Object Design
5.10.1. Interface documentation guidelines

Final Year Project Guideline | 2023

Chapter Six: Implementation
6.1. Introduction
6.2. Hardware and Software Acquisition
6.3. User Manual Preparation
6.4. Tanning
6.5. Installation process
6.6. Startup strategy
6.7. Algorithm
6.8. Maintenance

Final Year Project Guideline | 2023

Chapter Seven: Testing Plan
7.1. Introduction
7.2. Features to be tested
7.3. Features not to be tested
7.4. Testing Tools and Environment
7.5. Test Cases
7.6. Purpose.
7.7. Test Procedure
7.7.1 Unit Testing

7.7.2 Integration Testing

7.7.3 System Testing

7.7.4 Acceptance Testing

Final Year Project Guideline | 2023

Chapter Eight: Conclusion
8.1. Summary of Final Product
8.2. Recommendation
Reference

Final Year Project Guideline | 2023

 6. Brief Description of the Final Project Contents

Abstract
Write the executive summary of the work done in the project.

Background
Describe the project area you are working on. For example, if you are working on a title called
“Online Banking for ABC Company”, then you write about Online banking in general. Also
write about the organization for which you develop the system. Based on the previous title,
this is about ABC Company.

Statement of the Problem

In the statement of the problem, you identify the problems that exist in the current system the
organization uses and list them down. Also, discuss about the effects of the problems on the
company’s operations.

Objective
 General objective
Write a statement, which describes a result that will be achieved within your project. It should
be specific, measurable, achievable, and realistic and time bounded.

 Specific objective
Write the objective of your project i.e. what you want to achieve at the end of the project. This
is written as general objective and specific objective that help to achieve the general objective.
For the previous title, the general objective would be developing an online banking system
for ABC Company.

Methodology
 Requirement Gathering Methods
 Requirement Modeling (Structured vs object oriented)
 Tools Used

Final Year Project Guideline | 2023

Under methodology, you discuss how you gather user requirements (interview, observation,
document analysis, etc.). After requirement gathering, you have to structure the requirements
and develop software models. Therefore, you should also specify how you model the system
(OO, or structured approach) and why you chose that approach. Finally, you can list out the
tools you use for the project especially software tools (the database type you use, the
programming language you use, the UML modeling tools, etc.).
Feasibility
 Economic feasibility
 Technical feasibility
 Time feasibility
Write about the feasibility of your project in terms of economic benefit, technical knowledge
required to implement the system, and the time available for the project.
Scope of the project
Write the scope of your project. To what extent your system solves the problem of the
organization. Generally, the services, the deliverability you have to accomplish in the given
time.
Limitations of the project
 List and describe the issues you might have encountered as challenges/constraints
which hinder you from fully achieving your plan in your project
 Clearly indicate the activates left undone due to these constraints or any other factors
as the standard expected in the project
Significance of the project
Specify the significance of your project. What are effects of the project on the company or
other company’s in general. What is its contribution to the project area?

Final Year Project Guideline | 2023

The Existing System
Existing System Description
Describe how the existing system functions (manual, semi –automated, automated) how the
people working there processes their daily operations. Describe the existing system how it
works in detail systematically.
Business Rules
Write the rules used by the organization currently. In the online banking case, this could be
the interest rate allowed for saving account, the maximum amount of money that someone
can withdraw at a time, interest rate for loan, etc. Generally, they are the rules by which the
business is governed
Proposed System
Brief description of the proposed solutions for the problems mentioned in the statement of
the problem.
Requirement Analysis
Functional requirement
List all user requirements of the system. Each requirement should be uniquely identified with
a sequence number or a meaningful tag of some kind. You may provide a short description of
the feature/requirement and indicate whether it is of High, Medium, or Low priority.
 Label the requirements like FREQ-1, FREQ-2, and FREQ-3 ….etc.
System Use case
Use case Diagram
The requirements specified should be modeled using use case diagram. Show the functionality
of your system using use case diagram and how the actors interact with the system. Also show
use case reusability by including <<include>>, <<extend>>, and <<inherit>> relationships
between use cases
Use Case documentation
This section should include a use case documentation by showing use case number, name,
actor, description, pre-condition, post condition, priority, basic course of action and alternate

Final Year Project Guideline | 2023

course of actions. In the basic course of action and alternate course of action, you have to
indicate the user interface and the business rule if needed.
Business Rule Documentation
Write relevant business rules for the system, which will include (Identifier, name, description
and reference, revision history)
User Interface prototype
User interface requirements should be gathered with a prototype approach here and aligned
with system use case documentation that shows the user interaction with the system. It should
be labeled and referenced in the use case documentation.
Activity Diagram.
Draw activity diagrams to show the operations/activities performed by use cases to achieve
their functionality. Activity diagrams are drawn for each use case.
Sequence diagram
Show how objects operate with one another and in what order (chronological) to respond to
the actors.
Analysis Class Model
Model Classes with their attributes, methods, relationship, multiplicity and Role
Logic model
Algorithm/Pseudo code for each process
Nonfunctional requirement
Specify the technical requirements (performance, reliability, security, etc.) for your system.
System Requirement
Hardware requirements
Write the specification of the hardware devices such as CPU, RAM, hard disk and other
relevant hardware devices needed for successful deployment.
Software requirements
Write the specification of the set of software such as operating system, browser, plugins or
whatever software product and versions required to run the developed system.

Final Year Project Guideline | 2023

Detail Design
Design class model
Show the Design Class Model. That is, classes with their attribute data types, methods with
their return types and arguments and their data types, relationships, Access visibility,
multiplicity and role)
Persistent model for object oriented database
Show the persistent model for your system. That is classes with their attributes and data types,
length of attributes, and keys, foreign keys relationships, multicity and role.
Database design (E-R diagram) for relational database
Design the database of your system for persistent data storage using E-R diagram. Show the
cardinality of entities clearly and how the E-R diagram is mapped to database tables
User Interface Design
Show the design of the user interface of the system using implementation tool you have
already chosen.

Final Year Project Guideline | 2023

Implementation
Writing the code based on the design you have created in design phase. You can use any
programming language but if the system is designed in Object Oriented methodology, the
implementation should be based on classes and hence you should use object oriented
programming language.
 Include comments inside the code to add readability.

References
 Include the list of relevant literatures referenced in this document so readers can easily
find what you have cited.
 Use Institute for Electrical and Electronics Engineers citation (IEEE) style.

Final Year Project Guideline | 2023