3.
0 METHODOLOGY
3.1 Introduction
The interview and questionnaire techniques are going to be used to collect information from the
staff at NMS. However, a certain group will be asked the specific questions and in order to get
the necessary information from the big population. I will use the multistage sampling method
where I will divide the departments into clusters and I will collect the clusters randomly.
3.2 Type of probability sampling method.
3.2.1 Multistage Sampling
This is a sampling technique where two or more probability techniques are combined. It is used
when the elements of population are spread over a wide geographical region and it is not possible
to obtain a representative sample with only one aforementioned technique. It can be described as
sampling within the sample. The final unit or element of population which is used in
investigation is obtained after sampling at several stages.
The multistage method increases cost and time efficiency, for instance, instead of investigating
all the elements within a cluster, if a sample is randomly drawn from each cluster, the results will
be similar but with lesser efforts and the technique is also useful in overcoming the heterogeneity
problem within the clusters.
However, If the selected clusters do not capture the characteristic diversity of population, the
sample would not be representative of the population and if the characteristic variable used for
making strata (in case of heterogeneity) at any stage is not appropriately selected depending on
the nature of investigation, the whole research may go in vain.
For the departments in my area of interest which are stores and operations, procurement and the
administration, cluster sampling is the best method because in those departments there are many
individuals so I will choose a few and form clusters within. These clusters will be visited and
asked questions concerning how the medicines and medical equipment are distributed and
monitored in the country.
3.3 Data collection methods
3.3.1 Questionnaires
Questionnaires, as we consider them here, are stand-alone instruments of data collection that will
be administered to the sample subjects either through mail, phone or online. They have long been
one of the most popular data collection techniques. Questionnaires give the researchers an
opportunity to carefully structure and formulate the data collection plan with precision.
Respondents can take these questionnaires at a convenient time and think about the answers at
their own pace.
The reach is theoretically limitless. The questionnaire can reach every corner of the globe if the
medium allows for it. However, Questionnaires without human intervention (as we have taken
them here) can be quite passive and miss out on some of the finer nuances, leaving the responses
open to interpretation. Interviews and Focus Group Sessions, as we shall see later, are
instrumental in overcoming this shortfall of questionnaires. Response rates can be quite low.
Questionnaires can be designed well by choosing the right question types to optimize response
rates, but very little can be done to encourage the respondents without directly conversing with
them. I read about the types of questionnaire data technique model and this is the information I
gathered.
3.3.2 Interviews
Conducting interviews can help you overcome most of the shortfalls of the previous two data
collection techniques that we have discussed here by allowing you to build a deeper
understanding of the thinking behind the respondents’ answers. Interviews help the researchers
uncover rich, deep insight and learn information that they may have missed otherwise. The
presence of an interviewer can give the respondents additional comfort while answering the
questionnaire and ensure correct interpretation of the questions.
The physical presence of a persistent, well-trained interviewer can significantly improve the
response rate. However, reaching out to all respondents to conduct interviews is a massive, time-
consuming exercise that leads to a major increase in the cost of conducting a survey. To ensure
the effectiveness of the whole exercise, the interviewers must be well-trained in the necessary
soft skills and the relevant subject matter.
3.4 Designing the new system.
The Agile model will be used to design the new system. Agile SDLC model is a combination of
iterative and incremental process models with focus on process adaptability and customer
satisfaction by rapid delivery of working software product. The Agile thought process had started
early in the software development and started becoming popular with time due to its flexibility
and adaptability.
In this phase using the agile methods I will break the product into small incremental builds.
These builds will be provided in iterations. Each iteration typically will last from about one to
three weeks. Every iteration will involve cross functional teams working simultaneously on
various areas like Planning, Requirement, Analysis Design, Coding Unit Testing and Acceptance
Testing.
At the end of the iteration, a working product will be displayed to the different staff members
and important stakeholders of NMS. Agile model believes that every project needs to be handled
differently and the existing methods need to be tailored to best suit the project requirements. The
tasks will be divided to time boxes (small time frames) to deliver specific features for a release.
Iterative approach will be taken and working software build will be delivered after each iteration.
Each build is incremental in terms of features; the final build will hold all the features required
by the customer.
Figure 3.1: An illustration of the Agile model.
3.5 Implementation of the new system.
The actual code of the new system will be done in this phase. With the help of the documents
collected from the system design and it shall be divided into units as the coding is being done. It
is in this phase where designing of the interfaces and the developing of the database is done. PHP
(hypertext preprocessor), HTML (hypertext markup language), Java Script and CSS (Cascading
Style Sheets) languages will be used in coding. The development of the databases will be done
with use of MySQL that will be used to retrieve data from the database.
At the front end, I will use HTML, CSS and JavaScript languages to design the code.
At the middle end, PHP will be used to connect with the database in the back end.
At the Back end, MySQL will be used to create tables, insert, delete and modify the data in the
database and give grants and revokes to the users of the database.
3.5 Testing of the new system.
System testing is mainly carried out to identify any errors within the new system and how they
are to be corrected. This is done after the system has been put on trial for some time and the
users have been able to identify its strengths and weaknesses.
Therefore, in this phase using the grey box testing technique, the system will be tested using the
different types of testing. This is because the gray box testing technique combines the input of
developers as well as testers and improves overall product quality. It reduces the overhead of
long process of testing functional and non-functional types. It gives enough free time for
developer to fix defects. Testing is done from the user point of view rather than designer point of
view.
Figure 3.2: An illustration of the grey box testing technique.
Usability Testing - mainly focuses on the user's ease to use the application, flexibility in
handling controls and ability of the system to meet its objectives
Load Testing - is necessary to know that a software solution will perform under real-life loads.
Regression Testing- it involves testing done to make sure none of the changes made over the
course of the development process have caused new bugs. It also makes sure no old bugs appear
from the addition of new software modules over time.
Recovery Testing - Recovery testing is done to demonstrate a software solution is reliable,
trustworthy and can successfully recoup from possible crashes.
Migration Testing - Migration testing is done to ensure that the software can be moved from
older system infrastructures to current system infrastructures without any issues.
Functional Testing - Also known as functional completeness testing, it involves trying to think
of any possible missing functions. Testers might make a list of additional functionalities that a
product could have to improve it during functional testing.
Hardware/Software Testing - IBM refers to Hardware/Software testing as "HW/SW Testing".
This is when the tester focuses his/her attention on the interactions between the hardware and
software during system testing.
In conclusion, I will make use of all these types of testing using the gray box testing technique to
ensure that the new system is suitable to adopt and later on replaced with the current system.
3.6 CONCLUSION
The purpose for the creation of this system is to ensure that drugs will be monitored as they are
being distributed among the different health facilities.