Kwemoi Alex Juma

ONLINE HOSTEL MANAGEMENT RESERVATION SYST
PROJECT NAME: ONLINE HOSTEL MANAGEMENT RESERVATION SYSTEM.
PRESENTER: KWEMOI ALEX JUMA
INDEX NUMBER: 6211070111
INSTITUTION: MATILI TECHNICAL TRAINING INSTITUTE.
SUPERVISOR: MR. WASWA MUKHOYANI
SUBMITTED TO: KENYA NATIONAL EXAMINATION COUNCIL IN PARTIAL

FULFILMENT AWARD OF DIPLOMA IN INFORMATION
COMMUNICATION TECHNOLOGY MODULE 3
PAPER CODE: 2920/308
SERIES: NOV 2023
1
DECLARATION
This product is an original development. Copyright law, right protected from any privacy, governs
the Contents.
No duplication or reproduction of this document should be done without permission of the author.
Any duplication is liable for persecution. It is therefore to be used for implementation only.
The author:
KWEMOI ALEX
alexkwemoi96@gmail.com
Date:……..
Supervisor:…….
Mr. Waswa Mukhoyani.

Date:
ACKNOWLEDGEMENT
I would like to extend my appreciation to God for being with me throughout the entire project.
I am deeply indebted to my supervisors Mr Mukhoyani for the all the support, guidance, significant
suggestion and help that he has given me. I would like to thank the entire Matili fraternity for their
co-operation they gave me.
Last, but certainly not least, I would like to thank my classmates, Linnet, Paul, Amilla, Mercy and
Mary who helped me very much during my printing, Kepkemoi who have help me with my coding
and friends. Completing this project could not have been successful without their support and
encouragement.
2
Table of Contents
DECLARATION...............................................................................................................................II
ACKNOWLEDGEMENT................................................................................................................III
PREFACE......................................................................................................................................... V
GLOSSARY OF TERMS..................................................................................................................6
CHAPTER ONE..................................................................................................................................7
1.0 INTRODUCTION.......................................................................................................................7
1.1 PROJECT BACKGROUND.......................................................................................................7
1.2 OBJECTIVES..............................................................................................................................7
1.3 PROBLEM STATEMENT........................................................................................................7
1.4 SCOPE OF THE SYSTEM.......................................................................................................8
1.5 RESEARCH QUESTIONS.......................................................................................................8
1.6 EXPECTED BENEFITS...........................................................................................................8
1.7 JUSTIFICATION..................................................................................................................9
1.8 MISSION STATEMENT..........................................................................................................9
CHAPTER 2.......................................................................................................................................10
2.0 INTRODUCTION...................................................................................................................10
2.1 LITERATURE REVIEW........................................................................................................10
2.2 RECOMMENDATIONS;........................................................................................................12
2.3 CONCLUSION.........................................................................................................................12
CHAPTER THREE...........................................................................................................................13
3.0 INTRODUCTION..................................................................................................................13
3.1 METHODOLOGY..................................................................................................................13
3.2 FACT FINDING METHODS.................................................................................................13
3.3 OBSERVATION.......................................................................................................................13
3.4 SYSTEM ANALYSIS AND DESIGN.....................................................................................17
3.5 FEASIBILITY STUDY............................................................................................................20
3.6 FEASIBILITY STUDY REPORT............................................................................................21
3.7 DESIGN.....................................................................................................................................21
3.7.1 MASTER FILE OF STUDENT DETAILS FORM...............................................................22
3.7.2 STUDENT CCEPTANCE FORM........................................................................................22
3
3.7.3 STUDENT NOT ACCEPTANCE FORM.............................................................................23
CHAPTER FOUR.............................................................................................................................24
4.1 USER LOGIN FORM...............................................................................................................24
4.2 USER LOGIN FORM ACCEPTED..........................................................................................24
4.3 THE MAIN SWITCHBOARD.................................................................................................25
4.4 THE STUDENTS DETAIL FORM..........................................................................................25
4.5 SYSTEM GENERATED STUDENTS REPORTS...................................................................26
4.6 ACCEPTED STUDENTS REPORTS.......................................................................................26
4.7 DECLINED STUDENT REPORTS..........................................................................................27
4.8 NEW STUDENTS REGISTRATION FORM..........................................................................27
4.9 APPEDICES..............................................................................................................................28
.9.1 REFERENCE...........................................................................................................................28
4.9.2 BOOKS...................................................................................................................................29
PREFACE
In this era where many things have come up which have really affected the Housing and Hostels
sector. Some of the things that have contributed to the problems in the sector are: rural to urban
migration which is due to people who are is search of greener pastures, lifestyle and employments.
People are building and buying houses than before and the population is increasing at a very high
rate and long queues since most of the institutes are not computerised, poor management of hostels
just to mention but a few.
With these problems there is a need of proper management system. This report describes what a
hostel reservation system is. It covers initial study, requirement analysis, system design,
implementation and testing of the system.
4
GLOSSARY OF TERMS
Menu: A list of activities in an application, which the user can select.
Msgbox: This is a messenger box that prompted the user to select Yes or No.
EOF: End of a file.
BOF: Beginning of the file.
Program: A set of instructions used for carrying out some specific tasks.
Master file: This is a file that keeps records of all data permanently.
Transaction file: This is a file that keeps records of all data temporarily.
Virus: It’s a software program that corrupts the system files.
Record set; It is a set of records in a file.
Database: It’s a collection of related data stored together with a minimum redundancy
from which data can be accessed or retrieved simultaneously.
Form: These are the foundation upon which an application in visual basic is created.
Change over process: It is a process of changing from old system to the new system.
Text box: These are the controls that can be used to obtain user input in
an application.
File conversion: It is converting the exiting data into a format the
programs of the new system can work with.
Label: This is an object that can be used to display text that the user cannot
change directly.
Command button: This is a button that is used to enable the user with a
way of executing commands.
Txt: This is an abbreviation of a text box.
Lbl: This is an abbreviation of a label.
Frm: This is an abbreviation of a form.
Cmd: This is an abbreviation of a command.
Password: This is a set of characters that enable the user to access the
system if the correct password is entered.
5
CHAPTER ONE
1.0 INTRODUCTION
Online Hostel management reservation System, provide the easiest way of registration and
accommodation service.
1.1 PROJECT BACKGROUND

Online hostels management reservation system is a system in a secondary school that will be used to
capture all details of all the students, both new and old and maintain their records while at the
school. The school administration stringently maintains accounts for all the resources owned by the
students for the school using a well laid down procedure.
1.2 OBJECTIVES
11.2.1 General Objectives of Online Hostels management reservations system
 Maintain the students as hostellers and waiting list students separately.
 Process allotment list.
 Admin can send the approval notification to every approved student via email.
 Automatically insert student’s details to the hosteller’s record when the allotment is
confirmed by the admin and deleted when vocation is conformed or after course end
date.
 Students can register their complaints.
 Hostellers can check the status of every month’s hostel fee.
1.2.2 Specific Objectives of the project

The objectives of the project will be as follows:
Keeping records of students and specific hostels occupied.
To keep track of payments by the students.
To keep information about students.
To come up with window based system that will minimise fraud cases.
1.3 PROBLEM STATEMENT

To reduce congestion in schools during admission days due of the use of manual system.
6
In the current system most of the work was done manually. It was somehow slow since all the
records are done by people. The current system had complications whereby it was unreliable and
sometimes the records were not accurate. Most of the records in the store were vanished and there
were no clear records to show and confirm that those items have been used up. The current system
needed human help because it could not work on its own, and sometimes human beings could enter
records that are not accurate hence leading to the loss of students details. The current system could
not work for a long period of time because human beings also get tired and need to rest. The current
system could not perform and detect easily the total number of students that have been registered.
1.4 SCOPE OF THE SYSTEM

Schedule inventory system inventory system will be doing the following;
Capture all details of students in the school.
Capture stock of items in the school.
Maintains records of items issued and returned.
Maintains records of items in the store in their respective categories.
1.5 RESEARCH QUESTIONS

What is the importance of the system?
How does the system work?
1.6 EXPECTED BENEFITS

1.6.1 How will the company benefit?
Enhance security
The proposed system will enforce security constraints, which will user; will satisfy before accessing
any of the information.
Improve customer service
The system will provide high quality service to the customer since there will be faster and accurate
unlike the current system.
Increase storage capacity and faster retrieval of data
The information will be stored in hard disk that will provide high data capacity storage and the use
of primary keys which will enable faster retrieval of information.
Improve efficiency
Faster data retrieval by the proposed system will speed up report generation
7
Administration will be easier

Since the will be a centralised server the administration of the data and information will be faster and
easier.
Cutting down of expense
The system will only require few employees that will be responsible of maintaining the system since
it (system) will be doing most of the work.
1.6.1 How will I benefit as a developer?

I will be able to utilise what I have learnt into practise.
I will learn more from the challenges that I have encountered during development.
I will be able to learn more from other developers (student and lecturers).
1.7 JUSTIFICATION
The new proposed system will be better than the current system in many ways such as:
 Easy to update students’ details.
 It will ease on data entry and retrieval.
 Ensure maximum security on their data entered.
 The system will take minimal time when recording details and all the records will be
accurately captured.
 The system will have a large storage memory capacity for data recording compared to
the current system.
 The system will have no duplication of details since the new system will dictate
duplication of data.
 The system will reduce the paper work for the staff while registering the new
students.
1.8 MISSION STATEMENT

1.8.1 mission statement
To provide a simple, quick, accurate and justified information during students’ registration and
accommodation processes.
Encourage young scientists to appreciate their environment as they offer solutions contemporary
problems in society.
8
1.8.2 Vision statement

To develop a passion of research in young scientists and have clear and neat students’ details
recorded in the system.
CHAPTER 2
2.0 INTRODUCTION
2.1 LITERATURE REVIEW

This chapter contains the work frame, empirical review and the conceptual review of the proposed
system.
Existing content
There existed no system for student registration and accommodation to enter and maintain data for
the students.
2.1.1 Empirical review

According to (D. Koch 2020) Rapid population growth in schools has made education centres a very
complex and busy places. The 21 century has withes tremendous advancement in technology which
has led to far reaching development administrative system cost effective technology combined with
flexibility in learning. The administrative activity is essential and enhance efficiency of computer
can be used extensively for institutional administrative management.
2.1.2 General administration

According to (Hosson, 2008) hostel reservation system transformations industrial economic and
school managements. He quoted that different institutes are using hostel reservation system to
increase efficiency, effectiveness, productivity and reduce work load to the staff at large. Hostel
reservation system changes the way institutions are operated and managed, the way is linear more
efficiency and more flat line management structure.
According to (H. John) hostel reservation technology provide several facilities and possibilities for
school administrator to do their task. There is mentioned that hostel reservation system has changed
the very nature of management allowing information to be transferred, stored, retrieve and processed
by almost all who work or interact within any institution. The author has also quoted from other
research work that there is an increase in managerial effectiveness and efficiency through use of
hostel reservation technology. The overall administration of institutions mainly covers general and
day to day operational activities.
9
2.1.3 Conceptual review

Kenya are adopting hostel reservation technology as a tool to improve transparency, efficiency and
effectiveness in service delivery, through implementation of information system. (ISs). Whereas
many institutions have adopted several practices in the implementation of ISs, a number of
challenges may arise during implementation thus, making them not to realize the envisioned
benefits. The main objective of the study was to establish the practice of hostel ISs implementation
and determine the challenges faced by state parastatal in ISs implementation. This study therefore
adopted a survey design methodology because I intended to collect cross sectional data on hostel
reservation practice and implementation challenges in Arabuko Sokoke High School.
The main instrument for data collection was a structured questionnaire which was administered to
the principal, targeting 50% of the total population through judgmental sampling. The Drop-and-
pick later approach was used to collect the questionnaire.
Out of the 600 questionnaires distributed, 530 were filled and turned giving a response rate of 82%.
The research questions were systematically generated from the objectives. The data collected was,
cleaned, coded and analysed with the aid of SPSS package. Descriptive statistics and factor analysis
were used to help in drawing comparisons and conclusions.
After the interview the following short coming were noted;

I noted in data analysis that the results obtained were quite a representative for the general school
population. The findings of the practice of hostel reservation implementation in Arabuko Sokoke
High School indicated that most schools have not adopted several practices in their hostel
reservation implementation.
The findings show that there is lack of detailed risk log and risk management procedures which are
fundamental for successful hostel reservation implementation.
The study further, found that that the following challenges are faced by most schools in admission
and hostels reservation implementation. These include the challenge in process and structure,
procurement and communication, corruption, technical, system tuning, information systems
designing and people management. The study findings drew the following conclusion, institutions
10
have not yet adopted to several practices of hostel reservation development systems and
implementation whereas some of the practices are good, and others are challenges faced by many
schools in hostel reservation implementation. As observed the challenges tend to compare heavily
with literature, but fall on the process, people and hostel reservation management aspects.
2.2 RECOMMENDATIONS;
As the system developer behind the project, I recommended to the principal and the staff to adopt the
second alternative which entails designing a system for the same. The alternative was most suitable
because it would be based on their suggestions.
The following table shows the estimated requirements and costs that I required to develop the
system.
DESCRIPTION AMOUNT {KSHS}
A printer 13,500
A computer 22,500
Ups 4,000
Cost of development 12,000
Implementation 8,000
Operating system 6,000
Personnel training 3,000
Stationery 1,000
TOTAL 70,000
2.3 CONCLUSION
The proposed system will cater for the following processes;
 Data entry, editing, retrieval and printing of students and specific hostels occupied.
 To keep track of payments by the students.
 To keep information about students.
 To come up with window based system that will minimise fraud cases.
11
CHAPTER THREE
3.0 INTRODUCTION
3.1 METHODOLOGY
In this chapter, the problems identified are brought into a sharper scrutiny by the developer. He also
tries to study very closely on the current system so as to understand the problems in a more detailed
manner.
In order for a comprehensive investigation to be done on the current system, the following methods
of gathering data were used;
Interviews
Interviews were the main method that was used during data collection. The interviewer interviewed
the video library manager and the staff so as to on the current state of the problems and receive
suggestions that were used in the analysis of the current system. Both structured and unstructured
methods were used during the interview.
3.2 FACT FINDING METHODS

Among the questions raised included the following:
How does the current system work?
How is data stored in the current system?
How are students registered to the system?
How long does it take to register one student?
What security measures are envisaged in the current system?
In case of data loss, does the current system have a recovery measure?
What sequence of operation takes place while serving a student?
How does the system generate a receipt after fee payment?
Observations
This involved seeing how the current system worked. Observation was done on the staff at work,
record keeping, how transactions are captured and how charges are collected.
3.2.1 how the investigation was actually done.
12
3.3 OBSERVATION
in using this method, first I wrote a letter to the principal of Arabuko Sokoke High School requesting
for permission to carry out an observation of how registration and accommodation is carried out in
their institute. The content specified the 4w’s: who, what, why, when of the observation.
Below is a sample letter that I sent to the principal of Arabuko Sokoke High School;
KWEMOI ALEX JUMA,

P.O box 76-50204,
KIMILILI.
08/02/2021.
To the principal-
Arabuko Sokoke High School,
P.O Box 308-19090,
KILIFI.
Dear Sir,
RE: REQUEST TO CONDUCT INVESTIGATION.
I wish to request for a permission to conduct a registration and accommodation investigation in your
field of work. The purpose of the investigation is to ascertain how registration and accommodation
done and the various difficulties encountered in the current in anticipation of the automation of the
institute.
Besides, this letter wishes to notify you and your school staffs that cooperation and participation
during the exercise on the material day will be highly appreciated as you will be expected to provide
crucial information on the working of the manual system in your school.
Yours Faithfully,
ALEX JUMA
An authorization was effected by the Principal. To conduct an effective observation, I carried out the
observation during new intake of the new students. The reason for this pattern of observation was
because I wanted to ascertain on how work was done by the current manual system when there was a
sudden multiple of students.
13
Observation was made by maintaining very minimal interruption to the staff. The crucial data I
collected during observation was immediately recorded into my note book- my source
documents.
Interviews
In using this method, I chose who to be interviewed, the location of interviewing which was my area
of interest, date and time to conduct the exercise. I sent a prior notification through an official letter
to the principal informing him appropriately on the interview. I used a structured interview technique
where I was able to direct specific questions to my respondent.
The technique was more appropriate because supplementary information was given out on further
doing probing. In addition, the interviewees were able to give articulate on their current problems
that they underwent while conducting their registration and accommodation work.
On the material day of the exercise, I arrived very early at the school and was warmly welcomed by
the principal and his entire staff. I explained and emphasized on the importance of why the interview
was taking place and urged for maximum cooperation from them because some of the questions
were to be directed to specific individual staffs. I raised supplementary questions on the points I
didn’t understand well. During the entire period, I wrote down the important data from the
interviewee.
3.2.2 Fact Finding Report

This is the report I drew illustrating all the findings and the problems that were currently experienced
with the manual system of that school. The following are some of the findings I made;
 Some data got biased due to wear and tear.
 The manual system was very slow and prone to errors.
 It had poor filing of the receipt after a transaction had occurred.
 It lost data/ information which was not being recorded properly.
 There was inadequate control for security and validation of students.
 The system had difficulties in report generation.
 They experienced inconveniences when one need to retrieve a specific report
concerning a certain student.
 It took too long in the process to register a single student.
 During the pick hours, the staff were overwhelmed and at times the student details
were not well recorded.
14
3.2.3 alternative solutions

Having done a comprehensive investigation on the existing system, it was evident that there were a
lot of problems experienced with the current system and therefore urgency was needed to rectify on
the anomalies experienced.
Now as a system developer, the following are the alternative solutions I raised to the principal
concerning the students’ hostel reservation system;
1. Alternative one
I suggested the school management to consider purchasing off shelf hostel reservation system that
would easy the process of students’ registrations, accommodation and outsource the subsequent
installation and maintenance of the system and other tasks needed.
The only major disadvantages option which was depicted was that;
 The software may not sufficiently suit the needs of the organization.
 It might be an expensive for them to acquire the system.
 There could be other costs depicted on outsourcing any operations and running the
system.
 The staff, who are the end users of the system may resist it.
 Their proposal and requirements on the system may be ignored.
2. Alternative two
This involved adopting my recommendations by the school management team of designing a new
system from scratch that would improve and provide flexibilities in its enhancement in future. These
alternatives would be able to capture all the end user requirements as I collected during the system
investigation and therefore, the staff, may be receptive to the idea.
Designing a system from scratch has the following advantages;

 The system will constitute all the requirement specifications by the staff.
 The program can provide flexibility in case of need of expandability of the program
in future.
15
 The user will have understood fully how the program works even before it is
implemented because it’s an in-house product whereby they have been involved during the
entire period of development and implementation.
 As the system developer, I will offer post implementation services to the system and
the staff in general.
 The cost of developing the system may not be such expensive compared to the off
shelf systems.
 Additional features not included initially may be added as part of customizing the
system.
However, by adopting this alternative, the following limitations were experienced;

 Inadequate understanding of the problem thus developing the wrong system.
 Lacked good system due to inexperienced programmer.
 I experienced resistance from the staff who felt that once the system was
implemented lead to their job displacement.
 End users’ ignorance and negate attitude towards the system.
3.4 SYSTEM ANALYSIS AND DESIGN

Introduction
here I brought down the collected data and interpreted to the Alex hostels reservation system,
identifying the problems I noticed to deploy it to the development process. Planning on how to come
up with workable models of the system will be dealt with in line with the user requirements
objectively. This section focuses on how to accomplish the objective of the
System.
Software development methodologies
Methodology and tools;
Ms- office access, visual language method is the method I chose to use in the development of the
Alex hostels reservation system. A usual language believes that every project needs to be handled
differently and the methods that exist need to be tailored to best suit the requirements of the project
to deliver specific features for the release.
The final build will have all the features required by the client.
16
Figure
1.1 Methodology
Tools used;
In this methodology, the tools to be involved tables and flow charts. The flow charts will involve the
use of shapes that have distinct logical meanings. The user requirements will be mapped into a
conceptual and logical flow. On the contrary, the tables will be employed to illustrate the logical
working of the application.
Data Flow diagrams (DFD’s)
A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and
outputs. As its name indicates its focus is on the flow information, where data comes from, where it
goes and how it gets stored.9
Flow charts
According to Farrell (2014), I found this the most appropriate tool to demonstrate a sequence of
events. Despite how complicated the processes in my Alex hostel reservation System may look, the
flow charts will easily break down them into logical parts that users can easily understand. Each
module of the project will be logically shown for easy breakdown of processes.
Lastly, relationships and dependencies will be easy to understand, and critical path processes
demonstrated.
17
Logical Data Modelling

A logical data model describes the data in as much detail as possible, without regard to how they
will be physically implemented in the database. The features of logical data modelling include
entities, attributes, foreign keys and normalization.
Data Dictionary
A data dictionary also known as meta-data repository is a centralized repository of data elements and
other meta-data about them.
Software methodology strengths
The Ms- office access, visual language method is a very new approach to software engineering.
Compared to the old way of developing systems i.e. Waterfall, access has so many pros and will be
employed in my system due to its versatile nature.
The strengths that come with the Ms- office access, visual language model include:
 Its user friendly

 It is a very realistic way of developing software.
 promote training and team work.
 Due to its versatile nature, functionality can be rapidly developed and easily
demonstrated. This is, in fact, the primary reason I chose to employ it in my project.
 Furthermore, it requires very little resources in its development.
 Lastly, the access approach will assist me in delivering quick working solutions that
can be presented to the supervisors and the panel in case prototypes and working models are
needed.

3.2.2 Software methodology weakness
The methodology has the following weaknesses;
 Lack of long term planning. Lack of final vision of the project may be disorganizing
in some cases.
 Professional teams are vital. It requires teams to make serious decisions constantly.
 Difficult planning of early stages. Planning in access development is essential before
the process is started.
 Problems with workflow condition. Access project involves several small teams
working on their own software pieces. They should always coordinate their work with each
other testers and management.
18
3.5 FEASIBILITY STUDY

The need for a feasibility study to be conducted was important as it facilitated the problems to be
studied in depth and estimated the cost and benefits weighed to ascertain whether the system was
viable to the institute. A new system would only be viable if only the benefits out weighted the cost.
The content of the feasibility report for the system included the following;
The problems experienced with the manual system.
The availability of the school to the required technical and operational resources.
The impact that occurred once the system was implemented.
The benefits that was to be achieved when the new system was in place.
The cost to be encountered when the new system was implemented.
3.5.1 terms of reference

This is a formal document used during feasibility study which indicated the area where I carried the
study.
The areas of interest in the system included;
 Data entry
 Data processing
 Data output
 System controls
 System environment
 Overall implementation of the system
The above areas were studied for a period of one week.
3.5.2 operational Feasibility study.

Operational feasibility study establishes the extent to which the users of the current system are able
to work on the system with ease and comfort. Though the current system was manual, it was evident
that the inefficiency observed during data collection made it to be a very slow system to work on.
The principal and his staff encountered various file checks in order to execute a transaction. This
counter checking created so many inconveniences.
3.5.3 Technical Feasibility Study

Though the current system was manual, there was no level of technology integration was noted.
However, the level of education for the staff was of employee who had a proficiency in computer
19
applications, data entry and therefore with this basic skills system to be developed had the right
personnel to work with. The system was mad to operate on Windows Operating System platform.
3.5.4 Economic Feasibility Study

Economic feasibility study was done to establish whether the designing a new system was viable.
After making a careful scrutiny of the current system and its environment, the following
justifications were concluded;
 The system would reduce on paper work.
 The system would reduce on the number of staff working in the institute thus saving
on salary expenses.
 The system would improve the speed in terms of how the students would be served.
 The system would reduce on overhead costs e.g. cost on stationery.
 The system would provide security of all its data.
3.6 FEASIBILITY STUDY REPORT

After analysing the requirements of the system as wished by the school management team, the
following details provided a list of what could be accomplished;
 Data entry into the system database.
 Generation of students reports.
 Security of the system.
 Updating the database.
 Verifying the system data.
3.7 DESIGN
Entities and Attributes
A STUDENT DETAIL FORM has attributes STUDENT NAME, ROLL NUMBER, GENDER,
FEE, COURSE in conjunction with HOSTEL NAME, ACCEPTANCE.
HOSTEL NAME has attributes HOSTEL NAME.
Below is a STUDENT DETAIL FORM showing all the required details that a student will input.
3.7.1 MASTER FILE OF STUDENT DETAILS FORM
ADD FIRST LAST NEXT PREVOIUS DELETE SAVE PRINT

RECORD RECORD RECORD RECORD RECORD RECORD RECORD RECORD
20
CLOSE FORM
UNDO
BLOOD GRP
3.7.2 STUDENT CCEPTANCE FORM

STUDENT ACCEPTANCE FORM
STUDENT NAME
ROLL NO
GENDER
ACCEPTED
21
3.7.3 STUDENT NOT ACCEPTANCE FORM
STUDENT NOT ACCEPTANCE FORM
STUDENT NAME
ROLL NO
GENDER
ACCEPTED
22
CHAPTER FOUR
4.1 USER LOGIN FORM
4.2 USER LOGIN FORM ACCEPTED
23
4.3 THE MAIN SWITCHBOARD
4.4 THE STUDENTS DETAIL FORM
24
4.5 SYSTEM GENERATED STUDENTS REPORTS
4.6 ACCEPTED STUDENTS REPORTS
25
4.7 DECLINED STUDENT REPORTS
4.8 USER LOGIN DESCRIPTION
26
4.9 APPEDICES
.9.1 REFERENCE
Web – Sites
http://www-db.stanford.edu/~burback/watersluice/node53.html
http://www.simonmetz.com/project_management/waterfall_methodology.php
http://www.hyperthot.com/pm_sdm.htm
http://www.answers.com/topic/requirements-analysis
http://en.wikipedia.org/wiki/Non-Functional_Requirements
4.9.2 BOOKS
IAN SOMMERVILLE (1996) Software Engineering. Fifth Edition. Adison – Wesley
APTECH (1999) Developing Solutions with Visual Basic (No further information provided)
E, C, OLIVER, R, J, CHAPMAN (1996) Data Processing and Information Technology.
"Modern Structured Analysis" Edward Yourdon, Prentice-Hall 1989
"Structured Systems Analysis: tools and techniques" Chris Gane and Trish Sarson, Prentice-Hall
1979
“Database Management Systems” Raghu Ramakrishnan / Johannes Gehrke, McGraw-Hill 2001
" Systems Analysis and Design" Kendall & Kendall, Sixth Edition, Prentice Hall 2005
“Software Engineering” Ian Somerville, Fourth Edition, Addison Wesley, 2001
“Software engineering A Practitioner’s Approach”, Pressman, R.S. McGraw-Hill 1994.
“Software engineering Theory and Practice”, Shari, Lawrence, Pfleeger Second Edition Prentice
Hall 2001.
27

Kwemoi Alex Juma

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Kwemoi Alex Juma

Uploaded by

Copyright:

Available Formats

ONLINE HOSTEL MANAGEMENT RESERVATION SYST

PROJECT NAME: ONLINE HOSTEL MANAGEMENT RESERVATION SYSTEM.

PRESENTER: KWEMOI ALEX JUMA

INDEX NUMBER: 6211070111

INSTITUTION: MATILI TECHNICAL TRAINING INSTITUTE.

SUPERVISOR: MR. WASWA MUKHOYANI

SUBMITTED TO: KENYA NATIONAL EXAMINATION COUNCIL IN PARTIAL

Mr. Waswa Mukhoyani.

3.7.3 STUDENT NOT ACCEPTANCE FORM.............................................................................23

1.1 PROJECT BACKGROUND

1.2.2 Specific Objectives of the project

1.3 PROBLEM STATEMENT

1.4 SCOPE OF THE SYSTEM

1.5 RESEARCH QUESTIONS

1.6 EXPECTED BENEFITS

Administration will be easier

1.6.1 How will I benefit as a developer?

1.8 MISSION STATEMENT

1.8.2 Vision statement

2.1 LITERATURE REVIEW

2.1.1 Empirical review

2.1.2 General administration

2.1.3 Conceptual review

After the interview the following short coming were noted;

3.2 FACT FINDING METHODS

KWEMOI ALEX JUMA,

3.2.2 Fact Finding Report

3.2.3 alternative solutions

Designing a system from scratch has the following advantages;

However, by adopting this alternative, the following limitations were experienced;

3.4 SYSTEM ANALYSIS AND DESIGN

Logical Data Modelling

 Its user friendly

3.5 FEASIBILITY STUDY

3.5.1 terms of reference

3.5.2 operational Feasibility study.

3.5.3 Technical Feasibility Study

3.5.4 Economic Feasibility Study

3.6 FEASIBILITY STUDY REPORT

3.7.1 MASTER FILE OF STUDENT DETAILS FORM

ADD FIRST LAST NEXT PREVOIUS DELETE SAVE PRINT

3.7.2 STUDENT CCEPTANCE FORM

3.7.3 STUDENT NOT ACCEPTANCE FORM

STUDENT NOT ACCEPTANCE FORM

4.1 USER LOGIN FORM

4.2 USER LOGIN FORM ACCEPTED

4.3 THE MAIN SWITCHBOARD

4.4 THE STUDENTS DETAIL FORM

4.5 SYSTEM GENERATED STUDENTS REPORTS

4.6 ACCEPTED STUDENTS REPORTS

4.7 DECLINED STUDENT REPORTS

4.8 USER LOGIN DESCRIPTION

You might also like