The document outlines the methodology for a project, including using an iterative and incremental development model. It will collect data through questionnaires, interviews, and literature review, then analyze the data. The system will be designed using data flow diagrams and entity relationship diagrams, and implemented with C# and MySQL. A feasibility study found the project economically and technologically feasible within the scheduled time.

1. 1
CHAPTER THREE
METHODOLOGY
3.1 Introduction
This chapter illustrates the procedures that would be used to achieve the objectives of this
project. It contains the following sections; Data Collection Methods and Tools, Data Analysis,
System Analysis and Design, System Implementation, System Testing and Validation.
3.1.1 Project Development Approach
I will use Iterative and Incremental Development model (IID) for my project development. This
development approach is also referred to as Iterative Waterfall Development approach. Iterative
and Incremental Development is a software development process developed in response to the
more traditional waterfall model.

2. 2
Figure 3.1: Iterative and Incremental Life Cycle
The basic idea behind iterative enhancement is to develop a software system incrementally,
allowing the developer to take advantage of what was being learned during the development of
earlier, incremental, deliverable versions of the system. Learning comes from both the
development and use of the system, where possible. Key steps in the process will be to start with
a simple implementation of a subset of the software requirements and iteratively enhance the
evolving sequence of versions until the full system is implemented.
At each iteration, the procedure itself will consist of the Initialization step, the Iteration step, and
the Project Control List. The initialization step creates a base version of the system. The goal for
this initial implementation is to create a product to which the user can react. It should offer a
sampling of the key aspects of the problem and provide a solution that is simple enough to
understand and implement easily. To guide the iteration process, a project control list is created
that contains a record of all tasks that need to be performed. It includes such items as new
features to be implemented and areas of redesign of the existing solution. The control list is
constantly being revised as a result of the analysis phase.
The iteration involves the redesign and implementation of a task from project control list, and the
analysis of the current version of the system. The goal for the design and implementation of any
iteration is to be simple, straightforward, and modular, supporting redesign at that stage or as a
task added to the project control list. The code can, in some cases, represent the major source of
documentation of the system. The analysis of iteration is based upon user feedback, and the
program analysis facilities available. It involves analysis of the structure, modularity, usability,
reliability, efficiency, and achievement of goals. The project control list is modified in light of
the analysis results.
During the implementation of the project by this approach, a step called V&V i.e. Verification
and Validation will be carried out at certain intervals.

3. 3
 Verification: “Am I building the product right?”
 Validation: “Am I building the right product?”
3.2 Data Collection Techniques
Data would be collected through the use of questionnaires, interviews and in-depth literature
review with the aim of collecting reliable and complete data that can provide concrete
conclusions and recommendations for the project.
3.2.1 Questionnaires
Neuman, (2003) asserts, “Questionnaires are set of open or closed ended questions administered
to respondents to gather information on a research phenomenon.” Questionnaires are categorised
into three; Qualitative, Quantitative and Mixed Questionnaires (Johnson and Turner, 2003). In
qualitative questionnaires the type of questions are unstructured, exploratory, and in-depth open-
ended, while those in quantitative questionnaires are closed ended, respondents answer by
selecting from a set of possible responses. On the other hand, mixed questionnaires are a self-
report instrument filled out by respondents and contain a mixture of completely open and closed-
ended questions (Johnson and Turner, 2003).

4. 4
I will use mixed questionnaires because of its appropriateness in measuring attitudes of
participants and in gathering extra information that could miss out in a closed ended question
(Johnson and Turner, 2003). Besides, I will prefer to use questionnaire method because the
sample size will be large. The questionnaire development will consist of introduction, reason for
the study project.
3.2.2 Interviews
An interview is a data collection method where a researcher asks a respondent a set of questions
and records his/her answers (Neuman, 2003). I will use interviews to establish grounds for
accessing the acceptability and feasibility of my proposed solution and to understand the
business environment with its associated needs. Face-to-face interviews will be carried out with
the interest of getting data about the current mode of System and exploring the entire school
environment at the nearby school. This is vital in probing for the theory to get respondent’s
opinions about the appropriateness of the intended solution and the challenges in the current
system.
3.2.3 In-depth literature review
Neuman, (2003) explains, “In-depth literature review is the analyzing of existing documentation
on a given subject.” I will express interest in using this technique to identify different methods
used by different institutions and business enterprises in accepting payments from their clients,
exploring the challenges faced and the associated benefits with using such platforms, usage of
manual system in many businesses and the level of their penetration into the economy to back
our project idea.
3.3 Data Analysis

5. 5
After the data collection exercise, I will carry out data analysis of the administered
questionnaires using SPSS and a post interview follow-up on the interviews will be conducted to
eliminate inconsistencies.
3.4 System Analysis
System analysis and design will be achieved using Data flow diagrams (DFD), Entity
relationship diagrams (ERD).The system would be implemented using C#, MySQL database
server.
System testing and validation would be done through testing of components/modules, integration
testing, and finally, system testing.
1.5 Feasibility Study
A feasibility study was carried out to find out the viability of the system. The feasibility
attempted to check whether the idea will work and whether it will be cost effective. The
following are the areas where feasibility study covered.
3.3.1 Economic Feasibility
This test involves checking whether the system is affordable to build and maintain. The
analysis indicated that the system is affordable by organization using itdue to the fact that the
system was build and uses open source software.
It was also discovered that the systems benefit outweigh the cost of building and running the
system.
3.3.2 Technological feasibility
Technological feasibility investigates whether the project being undertaken meets the current
technological advances. In this new era, use of the internet is common hence the decision to
design a web based system is feasible since most people nowadays have the knowledge of the
internet. This project is technically feasible since it uses mobile technology which is modern
technology in the information and technology age.

6. 6
This study also involves checking the systems interaction with other systems and availability of
the hardware, software and personnel for building and running the system. Expertise and
resources required for the development of the system were readily available.
3.3.3 Operational Feasibility
It was necessary to change the current method of accessing apartments from tenants from
manual to web based .Most people prefer not to travel come and view or book houses but
would rather access it from anywhere they are. Thus introduction of web based system through
which they can make access to information remotely is exclusively acceptable.
3.3.4 Schedule Feasibility
The time allocated for the development of the system was 32 weeks. This was enough time
given my expertise and enough knowledge gained through the course work.
CHAPTER THREE
METHODOLOGY
3.1 Introduction
This chapter illustrates the procedures that would be used to achieve the objectives of this
project. It contains the following sections; Data Collection Methods and Tools, Data Analysis,
System Analysis and Design, System Implementation, System Testing and Validation.
3.1.1 Project Development Approach
I will use Iterative and Incremental Development model (IID) for my project development. This
development approach is also referred to as Iterative Waterfall Development approach. Iterative

7. 7
and Incremental Development is a software development process developed in response to the
more traditional waterfall model.
Figure 3.1: Iterative and Incremental Life Cycle
The basic idea behind iterative enhancement is to develop a software system incrementally,
allowing the developer to take advantage of what was being learned during the development of
earlier, incremental, deliverable versions of the system. Learning comes from both the
development and use of the system, where possible. Key steps in the process will be to start with
a simple implementation of a subset of the software requirements and iteratively enhance the
evolving sequence of versions until the full system is implemented.
At each iteration, the procedure itself will consist of the Initialization step, the Iteration step, and
the Project Control List. The initialization step creates a base version of the system. The goal for
this initial implementation is to create a product to which the user can react. It should offer a
sampling of the key aspects of the problem and provide a solution that is simple enough to

8. 8
understand and implement easily. To guide the iteration process, a project control list is created
that contains a record of all tasks that need to be performed. It includes such items as new
features to be implemented and areas of redesign of the existing solution. The control list is
constantly being revised as a result of the analysis phase.
The iteration involves the redesign and implementation of a task from project control list, and the
analysis of the current version of the system. The goal for the design and implementation of any
iteration is to be simple, straightforward, and modular, supporting redesign at that stage or as a
task added to the project control list. The code can, in some cases, represent the major source of
documentation of the system. The analysis of iteration is based upon user feedback, and the
program analysis facilities available. It involves analysis of the structure, modularity, usability,
reliability, efficiency, and achievement of goals. The project control list is modified in light of
the analysis results.
During the implementation of the project by this approach, a step called V&V i.e. Verification
and Validation will be carried out at certain intervals.
 Verification: “Am I building the product right?”
 Validation: “Am I building the right product?”
3.2 Data Collection Techniques
Data would be collected through the use of questionnaires, interviews and in-depth literature
review with the aim of collecting reliable and complete data that can provide concrete
conclusions and recommendations for the project.
3.2.1 Questionnaires
Neuman, (2003) asserts, “Questionnaires are set of open or closed ended questions administered
to respondents to gather information on a research phenomenon.” Questionnaires are categorised
into three; Qualitative, Quantitative and Mixed Questionnaires (Johnson and Turner, 2003). In

9. 9
qualitative questionnaires the type of questions are unstructured, exploratory, and in-depth open-
ended, while those in quantitative questionnaires are closed ended, respondents answer by
selecting from a set of possible responses. On the other hand, mixed questionnaires are a self-
report instrument filled out by respondents and contain a mixture of completely open and closed-
ended questions (Johnson and Turner, 2003).

10. 10
I will use mixed questionnaires because of its appropriateness in measuring attitudes of
participants and in gathering extra information that could miss out in a closed ended question
(Johnson and Turner, 2003). Besides, I will prefer to use questionnaire method because the
sample size will be large. The questionnaire development will consist of introduction, reason for
the study project.
3.2.2 Interviews
An interview is a data collection method where a researcher asks a respondent a set of questions
and records his/her answers (Neuman, 2003). I will use interviews to establish grounds for
accessing the acceptability and feasibility of my proposed solution and to understand the
business environment with its associated needs. Face-to-face interviews will be carried out with
the interest of getting data about the current mode of System and exploring the entire school
environment at the nearby school. This is vital in probing for the theory to get respondent’s
opinions about the appropriateness of the intended solution and the challenges in the current
system.
3.2.3 In-depth literature review
Neuman, (2003) explains, “In-depth literature review is the analyzing of existing documentation
on a given subject.” I will express interest in using this technique to identify different methods
used by different institutions and business enterprises in accepting payments from their clients,
exploring the challenges faced and the associated benefits with using such platforms, usage of
manual system in many businesses and the level of their penetration into the economy to back
our project idea.
3.3 Data Analysis

11. 11
After the data collection exercise, I will carry out data analysis of the administered
questionnaires using SPSS and a post interview follow-up on the interviews will be conducted to
eliminate inconsistencies.
3.4 System Analysis
System analysis and design will be achieved using Data flow diagrams (DFD), Entity
relationship diagrams (ERD).The system would be implemented using C#, MySQL database
server.
System testing and validation would be done through testing of components/modules, integration
testing, and finally, system testing.
1.6 Feasibility Study
A feasibility study was carried out to find out the viability of the system. The feasibility
attempted to check whether the idea will work and whether it will be cost effective. The
following are the areas where feasibility study covered.
3.3.1 Economic Feasibility
This test involves checking whether the system is affordable to build and maintain. The
analysis indicated that the system is affordable by organization using itdue to the fact that the
system was build and uses open source software.
It was also discovered that the systems benefit outweigh the cost of building and running the
system.
3.3.2 Technological feasibility
Technological feasibility investigates whether the project being undertaken meets the current
technological advances. In this new era, use of the internet is common hence the decision to
design a web based system is feasible since most people nowadays have the knowledge of the
internet. This project is technically feasible since it uses mobile technology which is modern
technology in the information and technology age.

12. 12
This study also involves checking the systems interaction with other systems and availability of
the hardware, software and personnel for building and running the system. Expertise and
resources required for the development of the system were readily available.
3.3.3 Operational Feasibility
It was necessary to change the current method of accessing apartments from tenants from
manual to web based .Most people prefer not to travel come and view or book houses but
would rather access it from anywhere they are. Thus introduction of web based system through
which they can make access to information remotely is exclusively acceptable.
3.3.4 Schedule Feasibility
The time allocated for the development of the system was 32 weeks. This was enough time
given my expertise and enough knowledge gained through the course work.