KENYATTA UNIVERSITY

SCHOOL OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF COMPUTING AND INFORMATION

TECHNOLOGY

SCO400 PROJECT

XYZ SYSTEM

SUBMITTED

BY

Name: YOUR NAME

Reg No. JXXX/XXXXX/201X

PROJECT SUPERVISOR: WINNIE S W WACHIRA

(This project proposal is submitted in partial fulfillment of the requirements for a

Bachelor of Science (Computer Science)/Bachelor of Information Technology etc Degree
at Kenyatta University)

1
Contents
IMPORTANT TO NOTE .............................................................................................. 4
CHAPTER ONE: INTRODUCTION .......................................................................... 5
1.1 INTRODUCTION / BACKGROUND INFORMATION ............................ 5
1.2 PROBLEM STATEMENT ........................................................................... 5
1.3 OBJECTIVES ............................................................................................... 5
1.4 SCOPE AND LIMITATION ........................................................................ 6
1.5 JUSTIFICATION .......................................................................................... 7
CHAPTER TWO: LITERATURE REVIEW .............................................................. 8
2.1 INTRODUCTION ......................................................................................... 8
2.2 CASE STUDY 1 ........................................................................................... 8
2.3 CASE STUDY 2 ........................................................................................... 8
2.4 CONCLUSION ............................................................................................. 8
CHAPTER 3: METHODOLOGY ............................................................................... 9
3.1. APPROACH TO BE USED ............................................................................. 9
3.2 TECHNIQUES TO BE USED TO COLLECT FACTS AND DATA ......... 9
3.2.1 ... ............................................................................................................. 9
3.2.2 … ............................................................................................................ 9
3.2.3 ... ............................................................................................................. 9
3.2.4 ... ............................................................................................................. 9
3.3 TOOLS TO BE USED TO ANALYSE THE DATA AND THE PROCESS
9
3.4 TOOLS TO IMPLEMENT AND TEST THE SYSTEM .............................. 9
3.5 TIME SCHEDULE AND PROJECT COST................................................. 9
3.5.1 TIME SCHEDULE ................................................................................ 9
3.5.2 PROJECT BUDGET.............................................................................. 9
3.6 CONCLUSION ........................................................................................... 10
3.7 REFERENCES ............................................................................................ 10
PROJECT PAPER ..................................................................................................... 11
CHAPTER FOUR: SYSTEM ANALYSIS AND REQUIREMENT MODELING 13
CHAPTER FIVE: SYSTEM DESIGN ...................................................................... 14
CHAPTER FIVE: SYSTEM DESIGN ...................................................................... 16

2
CHAPTER SIX: SYSTEM IMPLEMENTATION ................................................... 17
CHAPTER SEVEN: LIMITATIONS, CONCLUSIONS AND
RECOMMENDATIONS ........................................................................................... 18
REFERENCES: ......................................................................................................... 19
APPENDIX ................................................................................................................ 20
Blank leaflet ............................................................................................................... 21

3
 IMPORTANT TO NOTE
Document Language:

The document should be written in 3rd person plural.

Plagiarism

Please check the following two websites that give a basic overview of what
plagiarism is.

http://en.writecheck.com/ways-to-avoid-plagiarism/

https://wts.indiana.edu/writing-guides/pdf/plagiarism.pdf

In all cases, having huge tracts of copied text that are not enclosed with quotation
marks = plagiarism. Further, in universities and other academic institutions, even
having huge tracts of text that are enclosed is plagiarism. You should be able to use
your own words/paraphrase.

4
 CHAPTER ONE: INTRODUCTION
1.1 INTRODUCTION / BACKGROUND INFORMATION

This should be between a minimum of 2 and Maximum of 3 pages

i). Background of the Study – is a minimum of ½ page and maximum of 1 page

If applicable: Brief outline of the company in which the study will be done
and the work done in that company.
You should use the specific name of the organisation (one that actually exists)
that you are writing about, for example, Jamii Wholesalers, in Kiambu county.
Your systems are ideally created for existing organisations. If that is not the
case and you have a generic system that can be used by more than one
business, brand or individual, please show evidence of visiting several
organisations/potential clients for requirements gathering/fact finding. In
addition, include a sound business model to demonstrate the workability of the
project. How will value be created? What will make it profitable/viable?
Amongst other things, of special interest would be the proposed customer base,
how it will be financed, and the revenue model (ads? subscriptions? pay per
use?).

1.2 PROBLEM STATEMENT

ii). Problem Statement(s): - It should be stated in paragraph form.

State clearly the challenges they have with their current system of operations,
and keep in mind this is how you will justify providing the proposed system in
the company.

1.3 OBJECTIVES

iii) Objectives: - only project objectives should be included and which should be
SMART (S – Specific, M- Measurable, A- Achievable, R- Realistic/Relevant, T-
Time bound/boxed. The supervisor should guide the student on the minimum and
maximum number of objectives as per his/her project. Key words like Investigate,
develop and analyse should be used to list objectives

* The main objectives of the undergraduate project are summarised as

follows:

a). To provide students with the opportunity to integrate the knowledge and
skills developed from the BSc. Program;
5
 b). To provide students with the independent study and to develop the ability
to organize work with a view to achieve specific goal and

c). To undertake an academic project based on sound Technology, Business

and Innovation Management principles and intellectual reasoning.

Each objective should be measurable and achievable. The number of

objectives should be between three and four. Use words like investigate,
develop and analyse to list objectives
e.g.
1. To investigate the need for a xxxxx system to xxxxxx
2. To investigate problems ...
3. To analyse the current system...
4. To analyse the operations of company xxxxxx
5. To design a friendly UI...
6. To design web pages containing..
7. To develop a system that/module/database that will capture data for
xxxxxxx
8. To develop an online system/module/database xxxxx
9. To develop circles of networks to enable ...
Note that during the project presentation, the student will demonstrate that the
system is able to demonstrate each of the objectives. If the objective was to
analyse/investigate, the project document (report) should show what
investigation was carried out, and what the findings were. It the objective was to
develop, the system should have that model or that report.
10. At least one objective should be for input/processing/output of the
system. The system should in the final stage be able to accept data input, verify
the data, process the data, and produce processed data in form of a report or
something that shows results of an operation.

1.4 SCOPE AND LIMITATION

iv). Scope and Limitation of the Study – student should clearly show how
much s/he intends to cover in his/her project and why the much
Explain clearly how much will be covered in the project, what will be left out,
and why.

6
 E.g. to automate the purchasing operations only, leaving out the accounts
(give good reasons why you are leaving out accounts).

1.5 JUSTIFICATION

v). Justification; - student should justify their project by indicating the

interestingness and challenge that the project presents, the timeliness of the idea,
the possible advantages that realisation of such a project would bring.
Give reasons for developing this system, explaining how it will help the
organisation. 1 or two paragraphs only.

7
 CHAPTER TWO: LITERATURE REVIEW AND CONCEPTUAL/
THEORETICAL FRAMEWORK
It should have a minimum 3 pages and maximum 5 pages

CHAPTER TWO: LITERATURE REVIEW

2.1 INTRODUCTION

Begin with a detailed explanation of the general type of system being

proposed. Explain the type of environments it is used in.

2.2 CASE STUDY 1

Research and select from the internet/text book/academic journals an existing

system that is quite similar to the proposed system. Explain the way the system
works, where it is used, its advantages and its disadvantages.
Indicate clearly the sources of this information, and include these references
in the reference section at the end of this chapter. Note that the References
section will be moved to the end of Chapter 3 in your final proposal.

2.3 CASE STUDY 2

Research and select from the internet/text book/academic journals an existing

system that is quite similar to the proposed system. Explain the way the system
works, where it is used, its advantages and its disadvantages.
Screenshots of the two systems may be included to illustrate the sections.

2.4 CONCLUSION

Outline briefly how the systems researched are of benefit to their host
organisations. Explain how they differ (if at all) from the proposed system.

Cite your sources. Use the APA format. Refer to the APA's official site,
https://www.apastyle.org/ )

Note:
In computing, you want the majority (if not all) of your sources to be
contemporary. Ideally not more than 4 or 5 years old.

8
 CHAPTER THREE: METHODOLOGY
This is a minimum of 4 and Maximum of 5pages

CHAPTER 3: METHODOLOGY
3.1. APPROACH TO BE USED

Outline the selected methodology, give reasons you have chosen it, and
outline the phases in that methodology.

The methodology chapter should describe a model/framework under which the

system will be developed. It should address at least the following areas:-

The exact techniques to be used to collect facts and data

Tools to be used to analyse the data and the process
Tools to implement and test the system
Time schedule and project cost

3.2 TECHNIQUES TO BE USED TO COLLECT FACTS AND DATA

3.2.1 ...

3.2.2 …

3.2.3 ...

3.2.4 ...

3.3 TOOLS TO BE USED TO ANALYSE THE DATA AND THE

PROCESS

3.4 TOOLS TO IMPLEMENT AND TEST THE SYSTEM

3.5 TIME SCHEDULE AND PROJECT COST

3.5.1 TIME SCHEDULE

Gantt chart of activities

This gives the breakdown of the events scheduled throughout the project
lifespan and their timings. It should be a maximum of one page

3.5.2 PROJECT BUDGET

Table of budget items.

Budget
This gives a breakdown of the cost involved to complete the project and is a
maximum of one page.

9
3.6 CONCLUSION

3.7 REFERENCES

This is a minimum of 1 page and Maximum of 2 pages and

• should have a minimum of 3 books, 3 journals and 5 URL (Online
references)
• APA format to be used

NB:

Refer to the APA's official site, https://www.apastyle.org/ )

The references must match the in text citations.

10
 PROJECT PAPER
Upon the supervisors’ approval of the detailed project proposal, the students should
proceed and prepare their project paper under the supervisor’s guidance; the
document should

• be written in past tense

• have a minimum of 35 and maximum of 50 pages of the main document
• have an appendix; a minimum of 10 pages and Maximum of 20 pages and
which consists of at least 4 pages of important and necessary code.
THE ORGANIZATION OF THE PROJECT PAPER

The Project paper should consist of three main parts;

• The preliminary pages or front end

o The preliminary pages include elements such as
▪ the title page,
▪ dedication,
▪ abstracts,
▪ acknowledgements,
▪ declaration form,
▪ table of contents,
▪ list of tables, figures and abbreviations.
• The text or main body, usually divided into parts – chapters and sections
• The supplementary pages or back end.
o The supplementary pages consist of
▪ references and
▪ appendices or annexes. (Refer to Table 1 as an example).
Table 1: lists the major components of the project paper
Remember, for tables and figures, use 10-point.

11
No. ITEMS REMARKS
1. Blank paper Blank leaflet
2. Title Page Counted as page i, but not numbered (Please refer to
Appendix B)
3. Dedication (optional) Listed in the Table of Contents
4. Abstract
5. Acknowledgements (optional) Listed in the Table of Contents
6. Declaration
7. Table of Contents
8. List of Tables Listed in the Table of Contents
9. List of Figures/Illustrations Listed in the Table of Contents
10. List of Abbreviations, Symbols/ Specialised Listed in the Table of Contents
Nomenclature (optional)
11. Main Body (Page 1 begins with Chapter 1) To be paginated with numerals
12. Bibliography/References To be paginated, continuing with the numerals
13. Appendices/Annexes First sheet to be counted but not paginated (Insert a leaf
with only the word APPENDICES at the centre of the
page, followed by the actual appendices which are
paginated)
14. Blank Blank leaflet

12
 CHAPTER FOUR: SYSTEM ANALYSIS AND REQUIREMENT
MODELING
This is a minimum of 8 pages and Maximum of 10 pages.

Start by restating the methodology you are using (which you described in chapter 3)
and use it when analyzing, designing, testing, implementing etc. For instance, when
modelling, do not mix UML based models with other models.

The chapter should address at least the following areas: -

1. Description on how the current system works using tools like flow charts,
DFDs, etc.
2. How the facts and the data were gathered including the methods used e.g.:
• Interviews
• Questionnaires
• Observation
3. Requirement definitions and modeling of the current system in terms of
physical DFDs and Logical DFDs
4. Requirement definitions and specifications of the proposed system.
5. Requirement definitions and modeling of the proposed system in terms of
physical DFDs and Logical DFDs.
These should include processes and data modeling.

You must include the diagrams that show an understanding (analysis) of the existing
system (even if it is manual), and diagrams modelling the proposed system.

13
 CHAPTER FIVE: SYSTEM DESIGN
This is a minimum of 7 and Maximum of 10 pages

The section should include

1. Introduction
2. Architecture of the proposed system
3. System processes
4. Database design
5. User interface design

Once Chapter 5 has been approved, you begin developing the system.

14
 SUMMARY OF CHAPTER 4 AND CHAPTER 5

Chapter 4: Analyse the current and proposed system.

In the context of requirements engineering, requirements analysis would be the
process in which we establish what is required of a future system. In analysis you
want to understand the problem to be solved (the current system, its environment,
your clients, etc.) and the solution you propose to meet the user and system
requirements (e.g. the behavior it should exhibit). You structure the requirements
that you got during requirements elicitation and produce the first models.
Use models of the current system to help clarify what the existing system does and
to serve as a basis for discussing its strengths and weaknesses. The latter help you in
eliciting requirements for the proposed (new) system.
Use models of the proposed system to help explain the proposed requirements to
other system stakeholders, evaluate design proposals and to document the system for
implementation.
Chapter 5: Design the proposed system i.e. build a solution for the problem.
Now that you understand the problem, derive a solution that satisfies the software
requirements. Use the customer’s requirements to identify software
components/modules and their relationships. This requires creativity. Create the
architecture of the software. It is in this phase that you also do detailed/object design
where you transform the subsystem decomposition into reusable components that
you can implement in the next phase (implementation).
To break all this down to actual diagrams:
Chapter 4: requires process models (like DFD), data models (e.g. ERDs) and
behavioural models (e.g. state diagrams).
Use graphical models (supplemented by text annotations) to define the functional
requirements for the system. (If you are using UML, commonly used diagrams
include use case and activity diagrams. Sequence diagrams may cut across both
analysis and design. In requirements engineering, they may be used to add detail to
use-cases by showing the sequence of event processing in the system.)
Chapter 5: as per guidelines:
• (Introduction; System architecture; System processes; DB design; UI design)
System Architecture: For the software architecture: give the proposed organisation
of the system into components/sub-systems and describe the software you will use.

15
For hardware architecture give the proposed organisation of the system, (e.g. client-
server) and describe the hardware you will need.
For the system processes design, you may show the relationships between program
components (e.g. using a structure chart) and program specs (e.g. using pseudocode)
If using UML, you would have class diagrams, sequence diagrams, state
diagrams, etc. You may have component and deployment diagrams, although
these can be taken care of by software and hardware architecture respectively.
Following is a suggested structure for your chapters 4 & 5.
CHAPTER 4: SYSTEM ANALYSIS AND REQUIREMENT MODELING
• Methodology Application
• Description of Current Situation
Organizational structure; Context Diagram
 Process Models
Data Models
Behavioural Models
• Requirements Definition
CHAPTER FIVE: SYSTEM DESIGN
• Introduction
• System Architecture
 S/W architecture
H/W architecture
• Process Design
 Including Logical DFDs to Physical DFDs (or equivalents depending on your
methodology) and program specifications
• Database Design
• User Interface Design

16
 CHAPTER SIX: SYSTEM IMPLEMENTATION
This is a minimum of 3 and Maximum of 4 pages.

The chapter should address the following areas: -

1. Tools used for coding and testing

2. Testing: this should be explained in terms of the data used to test and the
approach
3. Proposed Change-over techniques

17
 CHAPTER SEVEN: LIMITATIONS, CONCLUSIONS AND
RECOMMENDATIONS
This is a minimum of 1 page and Maximum of 2 pages.

The chapter has the following sections:

1. Limitations: In this section you need to state some of the problems you
encountered in the process of doing your research e.g:
a. time factor,
b. finances,
c. anti-cooperative responses
2. Conclusion: ties the results of the study to theory, practice and policy by
pulling together the theoretical background, literature review, potential
significance for application and results of the study.
3. Recommendations: the section highlights suggestions and recommendations
for further improvements in the system.

18
 REFERENCES:
(Bibliography/References to be paginated, continuing with the numerals of the
main doc)

This is a minimum of 1 page and Maximum of 2 pages and should have

• Minimum of 3 books, 3 journals and 5 URLs

• APA format to be used

Example

• BOOK CHAPTER, ESSAY, or ARTICLE when author is credited

de Paula, T. C. M., Lagana, K., & Gonzalez-Ramirez, L. (1996). Mexican

Americans. In J. G. Lipson, S. L Dibble, & P. A. Minarik (Eds.), Culture and nursing
care: A pocket guide (pp. 203-221). San Francisco: USCF Nursing Press.

• JOURNAL ARTICLE (from an online database)

Kavanagh, K., Absalom, K., Beil, W., & Schliessmann, L. (1999). Connecting and
becoming culturally competent: A Lakota example. Advances in Nursing Science, 21,
9-31. Retrieved March 26, 2001 from ProQuest/Nursing Journals database.

19
 APPENDIX
This is a minimum of 10 pages and Maximum of 20 pages.

(Appendices/Annexes: First sheet to be counted but not paginated - insert a leaf

with only the word APPENDICES at the centre of the page, followed by the actual
appendices which are paginated)

Should include items such as;

• Organisational structure

• Instruments like document reviewed

• Interesting codes to a maximum of 4 pages

• Technical guide and users’ manual

20
Blank leaflet

21