0% found this document useful (0 votes)
25 views6 pages

Guidline

The document outlines the content and submission guidelines for final-year projects, detailing required sections such as the cover page, certificate of approval, declaration, and various chapters including introduction, user requirements, and system design. It emphasizes the importance of a structured approach, including feasibility studies, methodology, and proper referencing. Additionally, it provides formatting and originality guidelines to ensure academic integrity and clarity in presentation.

Uploaded by

Eyob
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)
25 views6 pages

Guidline

The document outlines the content and submission guidelines for final-year projects, detailing required sections such as the cover page, certificate of approval, declaration, and various chapters including introduction, user requirements, and system design. It emphasizes the importance of a structured approach, including feasibility studies, methodology, and proper referencing. Additionally, it provides formatting and originality guidelines to ensure academic integrity and clarity in presentation.

Uploaded by

Eyob
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/ 6

CONTENT AND SUBMISSION GUIDELINES FOR FINAL-YEAR PROJECTS

Cover Page

Include the project title, group number, and the names of all group members, along with the
advisor's name and the department.

Certificate of Approval

A signed certificate from the department confirming the project title's approval.

Declaration

A declaration page signed by the advisor approving the submission.

Acknowledgment

Table of Contents

A detailed table of contents listing all chapters, sections, and sub-sections.

List of Tables

Include a numbered list of tables (if any) with captions.

List of Figures

Include a numbered list of figures with captions.

List of Abbreviations/Acronyms

Define all acronyms and abbreviations used in the document.

Executive Summary (Abstract)

Provide an abstract (200 to 300 words) summarizing the project's objective, methodology, scope,
and key results. Avoid undefined abbreviations or unspecified references.
CHAPTER ONE

INTRODUCTION

1. Introduction/Background of the Project

Explain the project’s context and relevance.

2. Motivation of the Project

Highlight the reasons and importance of selecting the project.

3. Statement of the Problem

Clearly define the problem the project aims to address.

4. Objectives of the Project

General Objective:- Broad goal of your project.

Specific Objectives: - Detailed and measurable goals that support the general
objective.

5. Feasibility Study

5.1 Technical feasibility

5.2 Financial Feasibility and

5.3 Operational Feasibility of Your Project.

6. Methodology
Describe the methods used to gather information, develop the system, or implement the
solution.

7. Scope and Delimitation

Define the boundaries and focus areas of the project.

8. Limitations
Discuss any constraints or challenges that might impact your project.

9. Significance of the Project

Explain the project's potential impact and value.

10. Organization of the Document

Outline the structure of the document.

CHAPTER TWO

USER REQUIREMENTS AND ANALYSIS

1. Overview of Existing Systems

Describe any current systems or processes and their limitations. This portion will
help to easily show problems in the existing system and reflect the importance of
the proposed system.

2. Overview of Proposed Systems

Describe the solution proposed.

3. Functional Requirements

✓ Briefly write the functions that must be done to achieve the overall goal or objective
of the project.

✓ Collect and analyze data needed for the project.

✓ Prepare and preprocess data (for ML-related projects).

4. Supplementary Specification

✓ Business Rules:- Outline policies or constraints.

✓ Nonfunctional Requirements:- this portion is about how your project achieve the
functional requirements of your project
5. Use Case Modeling

✓ Essential Use Case Modeling

✓ System Use Case Modeling and Descriptions.

6. User Interface Prototyping

✓ Develop prototypes of the user interface.

7. Activity and Sequence Diagrams

✓ Include visual representations of workflows and interactions.

CHAPTER THREE

SYSTEM DESIGN

1. Layered Architecture

✓ User-Interface Layer.

✓ Controller/Process Layer.

✓ Business/Domain Layer.

✓ Persistence Layer.

2. Class Modeling

✓ Use techniques such as inheritance, association, and aggregation.

✓ Introduce interfaces and attributes.

3. User Interface Design

✓ Develop a comprehensive design for the user interface.

4. Database Design

✓ ERD (Entity-Relationship Diagram).

✓ Table normalization.

✓ Persistence diagram
5. Performance Evaluation

✓ Assess system performance (for ML-related projects).

6. Diagrams
Include state chart, component, and deployment diagrams.

Reference
Cite all sources using IEEE style.

Appendices
Include supplementary materials such as raw data, survey questions, or additional diagrams.

SUBMISSION GUIDELINES

1. Formatting

✓ Line spacing: 1.5.

✓ Font: Times New Roman, size 12 (body text) and 14 (headings).

✓ Margins: 1-inch on all sides.

✓ Page numbers: Centered at the bottom of each page.

2. Content writing

✓ Begin all chapters on new pages.

✓ Make sure headings are not placed at the bottom of a page without any content
following them.

3. Figures and Tables

✓ Number all figures and tables with Arabic numerals.

✓ Provide concise captions for each.


4. Referencing

✓ Use APA style.

✓ List only works cited in the document.

5. Originality

✓ Cite all borrowed ideas or words.

✓ Avoid plagiarism.

You might also like