……The measurement error is
the case where the results provide by the study variables are not the exact as
well as the accurate ones. It is impossible to have the study outcomes without
any measurement errors. The measurement errors may include as given: faulty
data input, the manipulated outputs, and the wrong interpretations of the data.
It can be said that measurement error cannot be
eliminated completely but they can be avoided to the possible extent.
……As far as the current study is concerned it is tried to
avoid the measurement errors to the possible extent. The strategies in
this regard may include the careful coding of the data for performing the tests
& proper recording of the data to the excel file, carefully copying the
data from the excel file and then pasting to the SPSS platform. Also, interpretation of said data to
get desired outcomes is a part of precautionary measures.
Data analysis software and techniques
The
data analysis as well as the interpretation of the data is done by using
Version 22 of SPSS (Statistical
Package for the Social Sciences).
System
Development Methodology of Government Online Service Quality and Customer
Satisfaction Portal
As a
part this chapter contains the life cycle of the software which is related to
the phases of the software development. For the purpose of achieving the
objectives of the study, the flow of the software, the modules & the
sub-modules suggest the use of the SDLC (Software Development Lifecycle) model.
This framework better assisted the directions for the development of current
software.
The
phases of SDLC needs to b followed brutally for the current study. The
development of the software is assisted fully through this step-by-step
procedure. As all the project related processes are directed by this so it is
also termed as the software development process. There are certain
sub-categories for every phase of SDLC. The effective completion of the
software is based on the accurate following of this software development life
cycle. The entire SDLC process is classified into the phases as given:
·
Planning:
the management of the entire project is based on the planning phase of SDLC.
·
Requirement
analysis: the requirement analysis is better performed in this phase.
·
Design
& prototyping: The design and the architecture of the software are better
dealt in this phase of SDLC.
·
Software
Development: This phase provides with the developed software.
·
Testing:
It is considered to the most significant phase of SDLC. Without testing, it is
not possible to deliver quality software. The parameters for measuring the quality
of the software include code quality, unit testing, integration test,
performance testing & the security testing.
·
Deployment:
It is perceived to be a highly automated phase. The moment when the software is
ready it is then deployed.
·
Maintenance:
the operations of the software are monitored accurately in this phase. The
identification of the bugs as well as the defects is the major part of this
phase.
There are different types of SDLC.
Following are given the most relevant SDLC models for the current project:
SDLC Comparison of Government Online Service Quality and Customer
Satisfaction Portal
SDLC
Model
|
Description
|
Advantages
|
Disadvantages
|
Waterfall
Model (Fig. 2.1)
|
For this model
the 7 sequential steps are used.
In case the requirements
are clear & well-known the current model can be used effectively.
There are
fewer chances for the requirements to change over the time.
|
●
Uncomplicated.
●
easily understandable
and simple
●
Convenient.
●
Provision of the
clear definitions.
●
The software
processes and the outcomes are well-documented
●
Better supports small-scale
software development.
|
●
The completion
of the software follows the sequential flow.
●
The complex and
the lengthy software development is not supported.
|
Incremental Model
(Fig. 2.2)
|
The
basis for this type of model is provided by the waterfall model. The single
parts of the software are developed by this software development model.
|
●
The important
functionality is produced earlier.
●
The long-term
projects are better supported.
●
For every
increment to the model, it is better able to be used productively.
●
It is easy to
make changes to the requirements.
●
Supports the
faster delivery of the product.
|
●
Each increment
needs to be pre-planned.
●
The requirements
for the complete system need to be known in advance.
|
Agile Model
(Fig. 2.3)
|
The agile
model is supported by the fast & the small incremental models.
|
●
Uncomplicated.
●
easily understandable
and simple
●
Convenient.
●
Flexibility is better supported.
●
Supports the
fixed as well as the changing requirements.
|
●
The complex
software development is less supported.
|
Figure. 2.1: SDLC
Waterfall Model (Source: https://www.youtube.com/watch?v=LHcpEwvpb-s)
Figure. 2.2: SDLC Iterative
Incremental Model (Source: https://www.javatpoint.com/software-engineering-iterative-model)
Figure. 2.3:
SDLC Agile Model
(Source:
https://ll-labs.readthedocs.io/en/latest/calm/sdlc.html)