National Cheng Kung University

Institute of International Management

Strategic Information System Final Term Paper

Evaluation of IT Infrastructure (NCKU Website) by

Using MC Calls Quality Principle

Student: Bahalwan Apriyansyah

RA6047455
Instructor: Dr. Jeng-Chung (Victor) Chen
January, 2016

TABLE OF CONTENT

Table of Content..............................................................................................................i
List of Table...................................................................................................................iii
List of Figure.................................................................................................................iii
Abstract...........................................................................................................................1
CHAPTER 1 INTRODUCTION....................................................................................2
1.1

Research Background......................................................................................2

1.2

Problem Statement...........................................................................................5

1.3

Research objective...........................................................................................5

1.4

Assumption and Boundaries............................................................................5

1.4.1

Research Assumption................................................................................5

1.4.2

Research Boundaries................................................................................5

1.5

Research Procedure..........................................................................................6

1.6

Research Outline..............................................................................................6

CHAPTER 2 LITERATURE REVIEW..........................................................................8

2.1

Software...........................................................................................................8

2.2

Quality dimension............................................................................................8

2.3

Software Quality..............................................................................................8

2.4

Quality Software Testing Tools......................................................................12

2.4.1

Reliability...............................................................................................12

2.4.2

Integrity...................................................................................................13

2.4.3

Usability..................................................................................................13

2.4.4

Efficiency................................................................................................14

2.4.5

Testability................................................................................................15

2.4.6

Portability...............................................................................................15

2.4.7

Usability..................................................................................................16

2.4.8

Maintainability........................................................................................16

2.4.9

Reusability..............................................................................................17

2.4.10

Interoperability.......................................................................................17

2.4.11

Flexibility................................................................................................18

CHAPTER 3 research design and methodology...........................................................19

3.1

Research Flow Chart......................................................................................19

3.1.1

Input........................................................................................................19

3.1.2

Methodology Determination...................................................................20

3.1.3

Testing Plan.............................................................................................20

3.1.4

Testing design.........................................................................................21

3.1.5

Testing Implementation..........................................................................21

3.2

Specific Methodology Test............................................................................22

3.2.1

Usability..................................................................................................22

3.2.2

Portability...............................................................................................22

3.2.3

Efficiency................................................................................................23

3.2.4

Testability................................................................................................23

3.2.5

Integrity...................................................................................................24

3.2.6

Reliability...............................................................................................24

REFERENCES.............................................................................................................25

LIST OF TABLE
Table 2.1 Comparison between criteria/goals of the McCall, Boehm and ISO 9126 quality
models [14].................................................................................................... 16

LIST OF FIGURE
Figure 1.1 Conceptual Model of S planning system (adapted from King, 1988)..................7
Figure 1.2 Research Procedure............................................................................10
Figure 2.1 McCalls metrics contributing to software quality factors.............................15
Figure 2.2 Load Impact Display..........................................................................16
Figure 2.3 SQL Injection................................................................................... 17
Figure 2.4 Checkmycolours Display.....................................................................18
Figure 2.5 Speed Online Page Display..................................................................18
Figure 2.6 NCKU Website in Testability................................................................19
Figure 2.7 Mobile Access and Pc Access Comparison...............................................19
Figure 2.8 Testing Usability Test.........................................................................20
Figure 2.9 Maintenance Website..........................................................................20
Figure 2.10 Web Service Technology....................................................................22
Figure 3.1 Research Flow Chart..........................................................................23
Figure 3.2 Usability Step Test.............................................................................26
Figure 3.3 Portability Step Test...........................................................................26

Figure 3.4 Efficiency Step Test...........................................................................27

Figure 3.5 Testability Step Test........................................................................... 27
Figure 3.6 Integrity Step Test.............................................................................. 28
Figure 3.7 Reliability Step Test...........................................................................28

Evaluation of IT Infrastructure (NCKU Website) by Using MC Calls

Quality Principle
ABSTRACT
The purpose of this study is to evaluate the IT infrastructure of NCKU trough
the website by looking at functional and non-functional (usability, reliability,
portability, integrity and efficiency). Mostly the network creator neglect the
importance of the non-functional aspect at the beginning of designing process.
Definitely, the non-functional aspects could impact to the software failure even some
cases it would bring negative impact to the organization. The software testing use MC
Calls Quality Principle which have been mentioned with several factor that have to be
concern. The study of software testing is still on progress to evaluate the
communication system through the website from NCKU in order to effective
informing to the Universitys entities as the learning process.
Key words: IT Infrastructure, non-functional (usability, reliability, portability,
integrity and efficiency) , MC Calls Quality Principle

CHAPTER 1
INTRODUCTION

1.1

Research Background
Currently the development of knowledge especially in technology growing

rapidly. Based on facts, the software developer prioritize functional needs rather than a
necessity non-functional (usability, reliability, portability, integrity, efficiency, etc.) for
consideration in software development. In fact the need for user in the information
technology like that increases both based software desktop and website. By looking at
this phenomenon, the software developer should be more recognize the importance of
the quality of software. Quality was not only can be seen from the functional needs
but also seen in non-functional needs who often ignored. Neglecting non-functional
needs in a software can cause failure software itself can even have a negative impact
in the Organization.
Companies operating in a digital world are relying on a comprehensive
information systems infrastructure to support their business processes and competitive
strategy. With ever-increasing speed, transactions are conducted; likewise, with everincreasing amounts of data to be captured, analyzed, and stored, companies have to
thoroughly plan and manage their infrastructure needs in order to gain the greatest
returns on their information systems investments. When planning and managing their
information systems architectures, organizations must answer many important and
difficult questions. NCKU as the non-profit organization also has competitive
advantages through the vision and mission as the leading education institution in
Taiwan. As people and companies rely on basic infrastructures to function, businesses

also rely on an information systems infrastructure (consisting of hardware, software,

networks, data, facilities, human resources, and services) to support their decision
making, business processes, and competitive strategy. Business processes are the
activities that organizations perform in order to reach their business goals and consist
of core processes and supporting processes. The core processes make up the primary
activities in the value chain; these are all the processes that are needed to manufacture
goods, sell the products, and provide service.
The primary objective of IS management is to support the organizations
pursuit of its business goals and objectives. The information input component
represents the inputs on business goals and plans, and the IS mission. Resources
represents the various non-information resources such as time and effort of top
management, users, and IS and business planning staff, financial resources, and
planning methodology.
The Planning Process converts the information inputs into a system of plans
that provides strategic directions for the IS function [8]. It analyzes the
external/internal environment, the business plans, the technology trends, the users
information requirements, and develops an information architecture and a set of plans
for managing the IS function.

Figure 1.1 Conceptual Model of S planning system (adapted from King, 1988).

Outcome is the impact of planning on the performance of the organization. It

evaluates the organizational context of planning, as well as assesses the efficacy of IS
planning [27]. There are links between the system components: (a) Integration, (b)
Efficiency, and (cl Implementation. They are considered as facilitators that strengthen
the relationship between the respective system components; e.g., participation of the
chief IS executive in strategic business planning (integration) facilitates the transfer of
information inputs to the planning process.
The

link

between

planning

process

and

outcome,

termed

implementation, refers to various organizational mechanisms, such as monitoring

and feedback systems, that are used to facilitate the implementation of the
recommendations of the planning process and obtain the desired outcomes.
Becoming one of leading University in Taiwan NCKU concern in service
quality through synergies in information system (Konsynski, 1985). These
opportunities lead to a complex and dynamic environment for the IS function that is
significantly affected by both the internal and external business environment and
external business environments. Information.

Strategic IS

planning, which includes all

planning activities that are directed toward identifying opportunities for using
information technology (IT) to support the organizations strategic business plans and
to maintain an effective and efficient IS function, is being extensively used to deal
with this complex environment. It has become a subject of considerable importance in
IS research (Boynton, 1987), as well as a key management issue for practitioners
(Niederman, 1991)
Hence its required testing software phase before products ready to be launched
to a user. Software testing is a technique that is used to determine whether the
software be able to solve the problems and can be implemented properly by the user.

Software testing is also necessary to ascertain quality and reliability of system, and
detect errors that might happen in software. The software testing is expected to detect
all a fault that occurs.
The NCKU has website to show the latest information regarding the
admissions, news or others importance notice from the University administration to all
Universitys entities. The website is expected to be a communication media in
cyberspace can present information with complete and fast. By considering that the
important role of website NCKU its in communicating information internally and
externally (in the campus or public), so the quality of the website must be considered
in functional and non-functional. On this term paper, will be conducted testing nonfunctional upon the a factor of the MC Calls the usability factors, reliability,
portability, integrity, efficiency, and testability and hopefully from the testing is under
the quality of website non-functional, and is expected to be a basis for developing.
1.2

Problem Statement
The problem that found in the background regarding the operational aspect of

organization (website) through IT infrastructure as the communication media is how

effective and efficient focus on McCalls Quality Principle.
1.3

Research objective
The objectives of our study is to examine the quality of NCKU Website based on

McCalls Quality Principle usability factors, reliability, portability, integrity, efficiency,

and testability.
1.4

Assumption and Boundaries

1.4.1

Research Assumption

The research assumption are:

1. During the observation there is no maintenance schedule in research

2. During the observation there is the internet connection is fair
1.4.2

Research Boundaries.

The research assumption are:

1. The observation is conducted by website of NCKU www.web.ncku.edu.tw
2. The observation looking at 6 factor of McCalls usability, reliability, portability,
integrity, efficiency, and testability.
1.5

Research Procedure

The research procedures of this study are shown as the figure below

Figure 1.2 Research Procedure

1.6

Research Outline
There are five chapters in this study and the content of each chapter is

summarized as following:

Chapter 1 Introduction
In this part, research background and motivation, research objects, research
procedure, and research structure are mentioned.
Chapter 2 Literature Review
In this part, this study also defined the research variables based on previous
researches. Other than that, the relevant literatures were collected and reviewed.
Chapter 3 Research Hypotheses and Methodology
In this part, the research hypotheses and research framework were established and
research methodology of this study is also described.

CHAPTER 2
LITERATURE REVIEW
In this chapter will discuss the literature review as the fundamental theory of the
research. This theory helps to enhance the research process as follows:
2.1

Software

According to Roger S. Pressman (2006) the definition of software is:

1. Instructions (computer programs) that when executed provide desired features,
function, and performance;
2. Data structures that enable the programs to adequately manipulate information
and
3. Documentation that describes the operation and use of the programs.
2.2

Quality dimension
According to Juran (1962) quality is conformity with purpose or benefits. The

quality of constitute a whole characteristic of products and services which includes

marketing, engineering, manufacture, and maintenance in which the products and
services for the user would be in line with necessity and customer desire
(Feigenbaum,1991)
2.3

Software Quality
Software quality is define as all characteristics of product that bear on its ability to

satisfy explicit and implicit needs of the user (ISO/IES9126,1991) according to

Pressman (2002) software quality is define as a conformance ton explicitly
documented development standards and implicit characteristics that are expected of
all professionally developed software. Therefore, the definition suggest three
requirement for quality assurance that are to be met by the developer (Galin, 2004)

Specific formal requirement, which refer mainly to the outputs of the software

system.
The software quality standards mentioned in the contract
Good software engineering practices (GSEP), reflecting state-of-the-art
professional practices to be met by the developer even though not explicitly
mentioned in the contract

The way with which we develop software impacts the quality of the software and
hence software process is one of the most crucial factors in determining the quality of
the software.
Quality system, application or product is a requirement that explain the matter ,
design model solution , code of programming can be executed and testing software to
find fault. Software engineering that better to use the measurement to assess the
quality of model analysis and design , source code , and test case that is made when
software engineered .To achieve quality assessments of real-time , engineer should
use technical measurement to evaluate quality in objectives way ( pressman , 2002 )
According to MCcall by roger pressman in his book engineering software
(2002) proposed category useful about the factors affect software. Focusing on three
key points a software product characteristic operational, its ability to adapt to the new
environment. The quality of software MCcall consisting of:
1. Correctness: The extent to which a program satisfies its specs and fulfills the
customers mission objectives.
2. Reliability: The extent to which a program can be expected to perform its
intended function with required precision.
3. Efficiency: The amount of computing resources and code required to perform
is function.

4. Integrity: The extent to which access to S/W or data by unauthorized persons

can be controlled.
5. Usability: The effort required to learn, operate, prepare input for, and interpret
output of a program.
6. Maintainability: The effort required to locate and fix errors in a program.
7. Flexibility: The effort required to modify an operational program.
8. Testability: The effort required to test a program to ensure that it performs its
intended function.
9. Portability: The effort required to transfer the program from one hardware
and/or software system environment to another.
10. Reusability: The extent to which a program can be reused in other
applications-related to the packaging and scope f the functions that the
program performs.
11. Interoperability: The effort required to couple one system to another.

McCalls quality factors were proposed in the early 1970s. They are as valid today
as they were in that time. Its likely that software built to conform to these factors
will exhibit high quality well into the 21st century, even if there are dramatic changes
in technology.
The factors that affect S/W quality can be categorized in two broad groups:
1. factors that can be directly measured (defects uncovered during testing)
2. factors that can be measured only indirectly (Usability and maintainability)

Figure 2.3 McCalls metrics contributing to software quality factors

It is difficult, and in some cases impossible, to develop direct measures of the above
quality factors. McCalls approach is to define a set of metrics and develop expressions for
each quality factor according to:

Fq =c 1 m1 +c 2 m2 ++ c n mn
Fq is a quality factor,

cn

are regression coefficients and

mn

are the metrics

that affect that quality factor. Unfortunately, many of the metrics McCall defined for these
purposes can only be defined subjectively. The metrics may be used in the form of a checklist
used to grade subjectively specific aspects of the software.

Quality covers a broad range of characteristics, which is one of the first

challenges to overcome. Usability, performance and security are common examples of
capabilities that are difficult to express as functionality, and there are many more
areas to consider. We need a taxonomy that we can expect to cover the breadth of
quality issues we may run into.
Here provide several taxonomies from each perspective of quality in software
beside McCall those are Boehm, 1978 and ISO 9126, 1993

Table 2.1 Comparison between criteria/goals of the McCall, Boehm and ISO 9126 quality models [14].

2.4

Quality Software Testing Tools

The following is tools used to test the quality of website we use in accordance

with 11 factors the quality of according to McCall:

2.4.1

Reliability

Reliability tools to use load impact. Load impact is one web security
application testing a website and had several features like multiple user scenarios,
extremely accessible service, geographic distribution of load, real-time testing, and
powerful reporting. (www.loadimpact.com)

Figure 2.4 Load Impact Display

2.4.2

Integrity

To use integrity tools of SQL injection. SQL injection is technique to exploit

an application web that use data given or inserted in query SQL. How it works by
including query SQL or order (command) as input that is made possible through the
web. Where the web pages take the parameters of 20 user, then made query SQL into
a database. One of which is on a page login user, whereby on the web pages will make
query SQL to a database to check username and the right password.

Figure 2.5 SQL Injection

2.4.3

Usability

By using tools named checkmycolours. Checkmycolours is tool that is used to

examine combination of colors foreground and color background as well as to
determine of contrasting color website. Where the algorithms that used based on the
World Wide Web consortium said (W3C). (http://www.checkmycolours.com/)

Figure 2.6 Checkmycolours Display

2.4.4

Efficiency

For measuring efficiency we use tools named page speed online. Page speed online is
a feature Google who gives facilities for us to analyze performance speed page
website that we have with score. In addition to providing score Google will also give
advice to performance web we have. Formerly Google just give this feature in the
form of tool is in browser Google chrome.
(http://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F

%2Fhima.ce.its.ac.id%2F&tab=mobile)

Figure 2.7 Speed Online Page Display

2.4.5
For

Testability
the

testability

we

directly

test

the

NCKU

Website

through

http://web.ncku.edu.tw/ to know whether function there are going well though not in

accordance. We didnt find the some features which does not function and cannot be
executed as with function desired.

Figure 2.8 NCKU Website in Testability

2.4.6

Portability

In testing portability, we do our tests with use the comparison when

http://web.ncku.edu.tw/ accessed through desktop and through mobile. This purposes to

know website its having portability who whether accessed in two different systems.

Figure 2.9 Mobile Access and Pc Access Comparison

2.4.7

Usability

In testing usability, we use methods testing directly testing in do testing

directly to tab vision and mission to know whether function has been running well or
not. When we click on tab vision and mission, would emerge page vision and mission
at the website http://web.ncku.edu.tw/ its in good conditions.

Figure 2.10 Testing Usability Test

2.4.8

Maintainability

In testing for maintainability, required usually a software maintenance, a

guidebook, and documents is or by using metrics method.

Figure 2.11 Maintenance Website

2.4.9

Reusability

For testing reusability, can be used a way that is method metrics or method
software. Metrics software is tools that can be used for measuring code that we make
with various type of measurement dealing with system, process or documents related
in software. Metrics help in doing evaluation of the development and testing needs to
be done in a system covering the aspects of testability, understandability,
maintainability and reusability. Metrics can be used for measuring software object
oriented traditional can also metric (on structural programming) and metric used
especially to the development of based software object.
p

1 R p(k)
R=

M N i + M Ci +

N F i + N FC i

R= Reusability value of a method;

method coverage value of a method R p (k)

M C i=

parameter;

M N i = meaning full name of method;

p= quantity of parameter;

of a method i;

= reusability value of a k

N F i = number function of performance

N FC i = number of call to foreigner classes of method i.

2.4.10 Interoperability
On the testing interoperability, used a tools named web technology service.
Web technology service technology called that can integrate the application,
programming language, and platform different over http, so the vary applications the
communicate and exchange data.

Figure 2.12 Web Service Technology

2.4.11 Flexibility
Substantially term for flexibility on the quality of software factor McCall is
related to a system / software that can be changed (change). More brevity is ease
make changes required by the changes in in an environment operation. Obviously that
flexibility situated upon the transition products, by which the is part of the transition
process a product / software. We had known that SAP is one of a software product that
is very large and remarkable. The strength of SAP is flexibility on how an enterprise
want module certain so software SAP can do the little transform to adjust to the needs
of a business firm .For example: an enterprise want only module primary and MM of
SAP then flexibility enough software SAP can make the change and adjust the need.

CHAPTER 3
RESEARCH DESIGN AND METHODOLOGY
In this chapter will discuss the research design and the methodology to conduct
the research. This methodology helps the research to assess the website of NCKU.
3.1

Research Flow Chart

Figure 3.13 Research Flow Chart

First step of research begin with the input of the research that is NCKU
Website. Then, enter to the process design. In research process, identifying the tools
and concept is very crucial at the beginning, hence method determination is conducted
well to do the complete research. Next, would be 3 phase of the testing process
design, first testing plan, followed by testing design and testing implementation. In
addition each of the testing phase has the output of the research. Testing plan process
has software testing plan document. Testing design has software testing design
document, then testing implementation process has software testing report documents.
3.1.1

Input

The input of this research is the website of NCKU with link

(www.web.ncku.edu.tw). This website will be assess based on McCall quality factor

those are usability, reliability, portability, integrity, efficiency, and testability where
each of the factors has tools for assessment.
3.1.2

Methodology Determination

At this early stage, we will determine how a testing be carried out. It will
determine whether the NCKU website have high quality test (high quality), a middle
quality (medium quality) or low quality (low quality). It is based on the success of
passing testing based on McCalls quality factors that is a cornerstone of testing the
quality of a software.
Testing conducted using 6 of 11 McCalls quality factors such as usability ,
reliability , portability , integrity , efficiency , and testability .This factors is
considered as crucial especially for the informative website which need speed, ease
and security access.
3.1.3

Testing Plan

In testing plan consisting of several sub processes to be run. Following the

processes that included in the planning: testing.

Testing boundaries
The boundaries of the research is the URL of the NCKU Website
Testing scope
The research scope is purposes to academic area only, not for the
commercial one. The testing will be conducted by using PC (Personal

Computer), web browser and the internet connection.

Detail testing
The detail testing consist of the purposes of these research, the level of

testing, then the data record regarding the testing

Testing schedule
The schedule of the research will be visualized by Gantt chart. The
output in this sub-process is software testing plan document.

3.1.4

Testing design

Design process testing is based on a document software test plan which has
previously made, where in the design of the testing is usually begins with a few
questions as follows:

What is to be assessed?
What are 6 function from McCalls that to be tested?
What and how the failure system can not fulfill the requirement fot
McCalls

Where the result of the process design testing this was called software test
design document. The documents detail description could include and configuration
hardware and software and procedures testing and also the registered data. Here is the
one conducted in the testing: design.
3.1.5

Testing Implementation

Generally, the implementation of testing, there are some activity that includes
the testing itself. In this phase the testing where phase, the following are activities
performed in phase of the testing process:

Activity containing about testing, correction and detection error.If necessary

will be improved and re run the test.

The method that use based on the tools of each 6 factors of McCalls
In the testing implementation, the output will be testing result and testing
implementation.

3.2

Specific Methodology Test

The specific methodology test is detail explanation about the methodology for

testing 6 factors quality from McCalls. Here detailed explanation of each factors as
follows:

3.2.1

Usability

Figure 3.14 Usability Step Test

3.2.2

Portability

Figure 3.15 Portability Step Test

3.2.3

Efficiency

Figure 3.16 Efficiency Step Test

3.2.4

Testability

Figure 3.17 Testability Step Test

3.2.5

Integrity

Figure 3.18 Integrity Step Test

3.2.6

Reliability

Figure 3.19 Reliability Step Test

REFERENCES
Education, P. (2004). Software Quality Assurance. In D. Gallin, From theory to
implementation (pp. 64-74). England: Pearson Addison Weasleu.
Khayami, S., Towhidi, A., & Ziarati, K. (2008). Measurable Quality Characteristics of
a Software System on Software Architecture Level. Proceedings of the World
Congress on Engineering, 1-5.
Rosa Ariani Sukamto, S. (2011, January). Testing dan Implementasi Sistem. Dipetik
April Monday, 2013, dari www.gangsir.com: www.gangsir.com
Cohen, S., Dor, D., & Haan, U. d. (201). A Software System Development Life Cycle
Model for Improved. Int. J. of Computers, Communications & Control, 20-41.
John E. Bentley, W. B. (2000). Software Testing FundamentalsConcepts, Roles, and
Terminology. Planning, Development and Support, 141-300.
Punter, T., & Lami, G. (1999). Factors of Software Quality Evaluation-Result of Two
European Surveys. 1-11.
Srinivasan Desikan, G. R. (2008). Software Testing : Principle and Practices. New
Delhi: Sigma Publising Services.
Pressman, R.S., System Engineering. (2001), New York: McGraw-Hill.
Education, P. (2004). Software Quality Assurance. In D. Gallin, From theory to
implementation (pp. 64-74). England: Pearson Addison Weasleu
Roger S. Pressman, Software Engineering: A Practitioners Approach (European
Adaptation), Ch. 19, Fifth Edition, 2000.
http://www.mhhe.com/engcs/compsci/pressman/resources/future.mhtml

Filip, F.-G. (2007). With Emphasis on the Integration of Three Technologies.

International Journal of Computer , Communication & Control.
G. Premkumar a, *. W. (1994 ). The evaluation of strategic information system
planning. Elsevier Science, 327-340.
Inc., C. C. (2010). Software Quality Attributes: Following All the Steps. In J.
Brosseau, Business Result Through Optimized Practice (pp. 1-9). Burnaby, BC
Canada: Clarrus Consulting Group Inc.
Pressman, R. S. (2001). Software Engineering, A P R A C T I T I O N E R S A P P R
O A C H. In R. S. Pressman, FIFTH EDITION. New York: McGraw-Hill.
Cash, J.I., McFarlan, W.E., McKenney, J.L., Vitale, M.R., Corporate Information
Systems Management: Texts and Cases, Irwin, Homewood, Illinois, 1988.
Henderson, J.C., and Cooprider, J.G., Dimensions of I/S Planning and Design Aids:
A Functional Model of CASE Technology, Information Systems Research,
Vol. 1, No. 3, 227-253.
King W.R., Evaluating Strategic Planning Systems,Strategic Management Journal,
Vol. 4, 1983, pp. 263-277.
King W.R., Evaluating an Information Systems Planning Process, Long Range
planning, Vol. 21, No. 5, October 1988, pp. 103-112.