Scribd
Upload
41 views

UZ Finance and Accounting Computer Project Chapter-1-Guideline

This document provides guidelines for writing Chapter 1 of a research project. Chapter 1 includes an introduction summarizing the proposed system and highlighting the research purpose and gap. It also includes background information on what motivated the research and the organization. The problem statement identifies challenges in key organizational processes. The aim summarizes the study purpose, and objectives are derived from process diagrams and should be specific and measurable. The methods section outlines how data will be collected for developing and testing the system. Justification explains why the system is important, and the conclusion summarizes chapter discussions and previews the next chapter.

Uploaded by

believe mashana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views

UZ Finance and Accounting Computer Project Chapter-1-Guideline

This document provides guidelines for writing Chapter 1 of a research project. Chapter 1 includes an introduction summarizing the proposed system and highlighting the research purpose and gap. It also includes background information on what motivated the research and the organization. The problem statement identifies challenges in key organizational processes. The aim summarizes the study purpose, and objectives are derived from process diagrams and should be specific and measurable. The methods section outlines how data will be collected for developing and testing the system. Justification explains why the system is important, and the conclusion summarizes chapter discussions and previews the next chapter.

Uploaded by

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

CHAPTER ONE

GUIDELINES
CHAPTER ONE: INTRODUCTION
1.1 Introduction
• The introduction should include a brief summary of the proposed system.
• It should explicitly show the general background, specific background, knowledge gap,
and specifically what you're doing in the research. This section always focuses on
highlighting the purpose of the research and have a discussion of what you want to look
at.

1.2 Background of the study


• Here you are supposed to indicate what motivated you to develop the system. Give
strong argument why there is need for the research and also focus on motivational
factors. Convince the reader that there is need for the research.
• Under the background of the organisation, you need to give the company history, its
vison and mission statement and the organogram for the organisation you are
developing the system for.
• On the vision, mission statement and values, there is need for a discussion. For
example, when looking at the vision, there is need to first define what a vision is then
relate it to the organization you want to study by stating its vision and even show how the
research informs or add value to the concept.
1.3 Problem statement
The Hook, Anchor, General and Specific sentences of the problem.
Identify problems faced in execution of the major company process. Use the major
problem as your problem statement.
For brain storming, you can draw a DFD (current system) for the major processes of the
organisation and identify problems from those processes. Example of a Bank
Reconciliation DFD is shown below. Choose a challenging problem for your system.
1.4 Aim
One sentence for the project aim required.
Summarise the purpose of the study.

1.5 Objectives
• You derive your objectives of the proposed system from the DFD of the system
• A DFD is for brain storming, do something challenging. The name of the processes
relates to the objectives of the system.
• Objectives should tell us what the system itself can do.
• Show some innovation in your problem formulation.
• Remember objectives must be smart 4-6 of them and system specific.
• Don't use generic objectives such as follows since every project will fulfill
this:
1. Increase security/authentication (username and password)/ audit
trails/logs.
2. Increase speed or improve efficiency
3. Provide back-up facility
4. Reduce costs through any means such as paper work reduction, or
reducing overtime allowances.
5. Allow editing/updating, adding, deleting, and searching of records.
6. Adhoc reports
• *NB: Your system must satisfy this though they can’t be called objectives of
the system.

1.6 Methods and instruments


Should indicate the data gathering methodologies to be used for
gathering data for developing the system and the software
development tools to be used for the system. E.g. define
instruments, define PHP/C# and justify it (application +
discussion) scholarly inferring to the purpose of the research. To
detect the problems of the current system, a pilot study should
have been carried out using various data gathering
methodologies. Information of when the pilot study was carried
out and which data gathering methodologies were used be
included in this section. Also highlight on time frame to carryout
the research(not a Gantt chart)
1.7 Justification – is based on the problems identified there is
thus need to explain why the system is of paramount importance
to the organization.
1.8 Conclusion
This is a summarization of major discussions done in this chapter
and highlighting the purpose of the next chapter.

You might also like