The document provides guidelines for formatting a project proposal, including margins, font style, spacing, cover page details, title page, declaration page, pagination, and sections to include such as dedication, acknowledgement, table of contents, list of tables, abbreviations, definitions, chapters on introduction, literature review, and methodology. Chapter 1 is to include sections on background, challenges, problem statement, proposed solutions, proposed system, and scope. Chapter 2 is to include an introduction and review of related studies. Chapter 3 is to cover methodology, including requirements analysis and specification, and system design with input, output, flow charts, use case diagrams and entity relationship diagrams.

1. PROJECT PROPOSAL GUIDELINES
FORMATTING GUIDELINES
 Margins – Top – 40mm (1.5”)
- Left – 40mm (1.5”)
- Right – 25mm (1.0”)
- Bottom – 25mm (1.0”)
 Font style – Times New Romans size 12
 Spacing – 1.5
 Alignment – Justified
 Cover Page – Font Size = 16 (in Capitals). With the following title: Bachelor of Business
Information Technology/ Bachelor of Information Communication Technology.
 Title page: will have the following wordings = A project submitted in partial fulfilment for
the degree in Business Information Technology in Scott Christian University.
 Declaration page (all headings centered). Names should be in bold and intended for both
student and supervisor.
 Pagination starts here and at page ii. The preliminary pages ought to be numbered in romans
(i,ii,…..) with number 1 starting from Chapter one. Use bottom – centered.
 Dedication page
 Acknowledgement page
 Table of Contents page - Chapter titles should not be numbered.
 List of tables page – numbering for the table number is bold and centered.
 List of appendices page
 Abbreviations and Acronyms page
 Definition of terms page
 Abstract page
 Referencing - APA
 Formulas are centered
 Caption for figures is at the bottom below the figure
 Printing cannot be done back – to – back
THE DOCUMENT
Title page
Declaration
Dedication
Acknowledgement
Table of content
List of tables
List of figures
List of appendices

2. Abbreviations and Acronyms
Definition of terms
Abstract
1.0 Chapter One: Introduction
1.1 Background – gives the background of the organization under
review, its vison, mission, goals and business processes
undertaken as well as how they are undertaken. Its aim is to bring
out the challenges/ weaknesses of the current way of doing things
and brings out the problems which the system being proposed
should address.
1.2 Challenges – this is a descriptive outline of the challenges that
have been discussed as part of the business activities taking place
there in the organization or in the context described in the
background study.
1.3 Problem statement – Describes the problem with the current
system from a technical perspective to give the developer the
required understanding of the challenges identified.
1.4 Proposed solutions – gives a descriptive outline of the solutions
proposed by the study.
1.5 Proposed system – gives a proposed solution that is going to be
addressed by the proposed project.
1.6 Scope – shows the boundaries or limits of what the system
proposed is going to cover.
1.7 Justification – it is an argument as to why the proposed project is
of importance and why it should be done. Here the factors for
justification would be like revenue generation, reduction of
expenses, saving on cost, contribution to the body of knowledge,
application of technical skills acquired, etc.
2.0 Chapter Two: Literature review
2.1 Introduction – It introduces the descriptive analysis of related studies done on the subject your
study is addressing. It aims at giving the reader the understanding of other developers who have
worked on a similar system or solution.
2.2 There needs to be a so as to comprehensively show how the solution has been implemented
elsewhere, how it works, its benefits (advantages), challenges (Disadvantages) and its selling
points.
2.3 It is from there now the study draws the gap between what has been accomplished by the
existing systems (projects) and what the new project is going to be offering.

3. 3.0 Chapter Three: Methodology/ System Design
3.1: Introduction - This introduces the methods which have been used in the project to collect data,
do systems analysis, and design of the system. It also gives a description of each in the context of
the project in question and shows how it adds value to its understanding and implementation.
3.2: Requirements Analysis and Specification - it is quite essential for you to understand and
document the exact requirement of the customer.
3.2.1 Requirements gathering and analysis – it describes the process and methods of collecting all
information from the customer which could be used to develop the requirements of the system.
Discuss the different requirements capture methods (interviews, observations or questionnaires)
that you will use to identify the system requirements. Include their advantages and disadvantages.
3.2.2 System requirements – Summarize the various requirements identified from the requirements
gathering process. Categorize the requirements as:
3.2.2.1 Functional requirements of the system
3.2.2.2 Non-functional requirements of the system, and
3.2.2.3 Goals of implementation
3.3 System Design - it does a pictorial description of the system concept breakdown using tools
like flow charts, Data – flow – diagrams, Data Dictionaries, Entity Relationship Diagrams, Use
case diagrams, Input, output and report designs etc.
3.3.1 Input design – Using MS Word, design the input forms (3 – 5) that you shall use for entry of
data into your system
3.3.2 Output design - Using MS Word, design the output reports (3 – 5) that you shall use for
reporting of information from your system
3.3.3 Flow charts/Data Flow Diagrams – Design at least 3 flow charts/data flow diagrams to
illustrate the flow of data in achieving different requirements as identified in 3.2.2
3.3.4 Use case diagram – design a single use case diagram for the entire system
3.3.5 Entity Relationship Diagram – This is specifically used for the design of the database.
Illustrate the diagrammatic representation of your database.