See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/326914915

The Use of System Development Methodologies in the Development of Mobile

Applications: Are they Worthy of Use?

Article · August 2018

CITATIONS READS

0 209

2 authors:

Okonkwo Chinedu Magda Huisman

University of Johannesburg North-West University
17 PUBLICATIONS   131 CITATIONS    10 PUBLICATIONS   471 CITATIONS   

SEE PROFILE SEE PROFILE

Some of the authors of this publication are also working on these related projects:

PhD Studies View project

To investigate the adoption and diffusion of mobile applications in African countries. View project

All content following this page was uploaded by Okonkwo Chinedu on 29 January 2020.

The user has requested enhancement of the downloaded file.

 2018 42nd IEEE International Conference on Computer Software & Applications
The use of system development methodologies in the
development of mobile applications: Are they worthy of use?
Wilfred C. Okonkwo and Magda Huisman
School for Computer, Statistics and Mathematics, North-West University, Potchefstroom Campus, Private Bag X6001, Potchefstroom 2520, South Africa
Abstract
The implementation of system development methodologies
(SDMs) in mobile applications (mobile apps) development has a
positive effect on companies and their respective software
projects. SDMs provide a framework for planning, executing, and
managing the process of developing software systems. In this
paper, we investigate the worthiness of using of SDMs in the
development of mobile applications. A survey was conducted
among software developers both individuals and organizations.
The organizations include software development companies,
financial institutions, telecommunication companies, engineering
companies and educational institutions. A total of 152 out of 392
questionnaires distributed, were returned, giving a response rate
of 38.8%. Furthermore, the responses were categorized into two
groups (users/non-users of SDMs) and T-test analysis was
performed to determine the differences between the means of the
two groups. The findings indicate that SDMs are effectively used
in developing mobile apps and there are significant practical
differences between the users and non-users of SDMs in mobile
apps development in areas of organizational size, the number of
developers in the organization, years of experience, the number
of applications developed and application success. The users
(companies and individuals) are larger, more experienced and
more productive. Furthermore, the use of SDMs in mobile apps
development leads to more successful mobile apps. We conclude
that SDMs are indeed worthy of use in mobile apps development.
Keywords: Mobile applications development; system
development methodologies; software developers; software
systems; users and nonusers.
1. Introduction
In the domain of mobile apps development, it is still unclear if the
use of SDMs is important, and how effective the applications are
to the organizations. Mobile apps can be created either with the
use of SDMs or without the use of SDMs. Most of the researches
on SDMs focused on the development of new methodologies and
the emphasis on the need to use SDMs in mobile apps
development rather than on the evaluation of the use or effect of
SDMs on the development of mobile apps. Studies have proposed
that the use of SDMs in mobile apps development helps a
developer to achieve improved efficiency [1], and to address
more aspects of the development process [2]. Dittrich [3]
0730-3157/18/$31.00 ©2018 IEEE
DOI 10.1109/COMPSAC.2018.10243
emphasized the need for a formalized methods, tools and
techniques in the development of mobile apps. Tyler [4] urged
the development team to select a suitable SDM in order to
manage the software project well. These research reports promote
and encourage the use of SDMs in the design and development of
mobile apps. They suggested that it is good to apply SDMs in
mobile apps development with less or no emphasis on the effect
of SDMs towards the development of mobile apps. How the use
of SDMs affects the success rate of mobile apps is not elucidated.
Various SDMs for mobile apps have emerged overtime [5, 6] but
there is not enough substantiation on the practical effect of the
use of these SDMs to determine their impacts (negative or
positive). In the academic research domain, much has been said
about the use of SDMs but in practice, there has been little
evaluation of the worth of these SDMs in software development.
The research question is: “Is it worth using SDMs in mobile apps
development?” This paper seeks to investigate the use of SDMs
in mobile apps development to know if it is a worthy practice and
highlights the practical significant differences among the users
and non-users of SDMs.
2. BACKGROUND
2.1. Mobile applications (mobile apps)
Mobile apps are the software created to make use of mobile
technology, supporting data gathering and transmission for
economic and social events either for commercial, governmental
and entertainment purposes [7]. In other words, mobile apps are
software that runs on various devices [8], based on mobility of
technology, users and devices [9], and are the actionable program
based on user's and context awareness to produce context-based
output [10].
2.1.1. Mobile apps development
The development of mobile apps involves a set of processes and
procedures. Mobile apps development is the process of putting a
set of coded instructions used by a mobile device for solving
problems, wireless computing and communication [11]. Mobile
apps development is referred to as a procedure used in writing
mobile social software whose scope is to support social
interactions and businesses among interconnected individuals
[12, 13]. For the purpose of this study, mobile application
development can be defined as a set of processes and procedures
involved in writing a computer program for mobile devices used
278
for social interactions, business and other services. The processes
and procedures of developing mobile apps are presented in a
framework, or organized principles or formalized methods as
discussed in Section 2.2.
2.2. System development methodology (SDM)
Software development started without the use of SDMs and the
success and failure of the software development projects relied
fully on the individual skill and experience. The emergence of
SDM was believed to address the shortcomings in the existing
techniques and to enhance the effectiveness and value of software
projects [14, 15].
2.2.1. What is SDM?
SDM has been defined by many authors in many ways with
regards to their perspectives and understandings including
definition as a framework, organized principles and as formalized
methods. SDM is a framework that is used to structure, plan, and
control the process of developing an information system [16].
SDM has been described as a collection of principles and/or
practices used in developing mobile computing software by [17].
SDM is a combination of approaches, methods, processes and
techniques [3]. In this paper, we choose the last definition which
is the formalized methods definition of SDM and the components
involved are described as follows:
Systems development approach: This involved the philosophical
view in which the SDM is constructed [18].
Systems development process models: These are abstract design
models of the SDM [19, 20].
Systems development method: This is a logical or systematic
manner of developing a software system [17, 19].
Systems development techniques: A well-defined
actions/instruments used to accomplish a particular system
development successfully [21].
The combination of all these components formed what is referred
to as SDM.
2.2.2. Some SDMs used in developing mobile apps
Similar to generic software development, a number of
methodologies are employed in developing mobile apps. These
SDMs have their unique features that distinguished each one
from the other. They are different, based on various technical,
organizational, project and team considerations [16]. Some of the
most popularly used SDMs for mobile apps development include
mobile D [22], M-compass [23], Agile [24], Mobile Application
Software Based on Agile Methodology [25], hybrid [26],
Dynamic Channel Mode [27], Chen [28] etc.
2.3. Use of SDMs
The use of SDMs implies using a structured framework, method
or guidelines to create a software system. In the 1990s, research
reports indicated that less percentage of developers make use of
SDMs during software development process [29, 30]. In the
2000s, there is a noticeable increase in the use of SDMs in
practice but not followed to the full extent and those that use
SDMs are mostly organizations and few individual developers
279
[31]. Recently, researches conducted show that > 74% of
software developers use SDM in practice [32, 33]. The use of
SDMs has been promoted and encouraged. Scholars suggested
that the use of SDMs in mobile apps development can help to
enhance the software development process by improving the
effectiveness and management of the whole process with an
increase in the productivity and quality [34, 35]. Conversely,
some investigators have presented some reasons for not using of
SDMs rigorously in practice. The use of SDMs may be too rigid,
not easily adapted to, not suitable to the social norms of the
development team, and SDMs techniques may not be appropriate
in some cases [36, 37]. However, there is minimal empirical
evidence to support these expectations and assumptions. This
study intends to investigate the use of SDMs in mobile apps
development to determine if they are advantageous or not.
3. Research methodology
In order to meet the objectives of the study, a survey was
conducted. A questionnaire was designed and used as an
instrument for data collection using the convenience sampling
technique. The questionnaire comprised of three sections:
background information, mobile apps development and the use of
SDMs. The questionnaire contained mostly closed-ended
questions with 5-point Likert scale rating of 1 (totally disagree) to
5 (totally agree). The targeted audiences were mobile apps
developers and other ICT professionals across various
organizations. The organizations used for the research study were
selected because: 1) Software companies are fully into the
business of software development and 2) Other companies
develop their respective mobile apps for their operational
services, hence they have in-house developers and ICT
professionals that develop, maintain and sustain their mobile
apps. The questionnaires were sent to the IT department and were
completed by the software developers and the ICT professional in
each respective organization. Drop off and electronic methods
were used to distribute the questionnaire. A total of 392
questionnaires were distributed to different respondents and 152
(38.8%) responses were returned. The responses comprise of 131
drop off and 21 electronically completed questionnaires.
4. Data analysis
All the responses were thoroughly examined to extract the data
and different statistical techniques were utilized in the data
analysis. A descriptive analysis was performed to describe the
frequency and percentage of responses from the study population.
A Pearson correlation analysis was performed to determine if a
linear relationship existed [38]. Cronbach alpha reliability
analysis was used to compute the reliability coefficients of each
of the examined variables [39]. The data were grouped into 2
independent categories (users and non-users of SDMs) and the
means of the variables were tested using T-test analysis to
determine if there are practical significant differences among the
groups. The mean comparison was done according to Cohen’s
effect sizes [40], and the guidelines for effect size (d values) were
as follows: 0.2 ≤ d ≤ 0.5 indicates small effect; 0.5 ≤ d ≤ 0.8
indicates medium effect; and d > 0.8 indicates large effect or
practically significant.
5. Survey results
The core business area: software companies (85
participants/55.92%), financial institutions (18
participants/11.84%), educational institutions (21
participants/13.82%), telecommunication organizations (19
participants/12.50%), and engineering companies (9
participants/5.92%).
The total number of employees in the organization: Organizations
with 1-10 employees (24.34%), 11-50 employees (22.37%), 51-
100 employees (8.55%), 101-200 employees (7.89%), and above
200 employees (36.84%).
The length of time (years) that the organization has been into
mobile apps development: 1-5 years (15.13%), 5-10 (33.55%),
above 10 years (43.42%), and never at all (7.89%).
The primary motivation for developing mobile apps:
profit/revenue (58.55%), extension of company portfolio
(53.29%), brand recognition (2.63%) and others (8.55%).
The total number of mobile apps developed by the organization:
1-10 apps (43.71%), 10-50 (22.52%), 50-100 (11.92%), above
100 (19.87%) and none (1.99%).
The application success: Rating the successfulness of developed
mobile apps: very successful (53.02%), successful (46.31%),
average (0.67%), and unsuccessful and very unsuccessful (0%).
The use of SDM in mobile apps development: 5.92% of
participants indicated NO, 88.16% of participants indicated YES,
and 5.92% were neutral (neither YES nor NO).
Generally, it is good to use SDM in mobile apps development:
2.63% (disagree), 32.24% (neutral), 58.55% (agree) and 6.58%
(strongly agree).
The uses SDM enhance mobile apps development: 3.29%
(disagree), 31.58% (neutral), 59.21% (agree) and 5.92% (strongly
agree).
SDM was adopted in the development of the mobile apps: 1.97%
(disagree), 32.89% (neutral), 57.25% (agree) and 7.89% (strongly
agree).
5.1. Interpretation of results
The core business area: Responses were obtained from all the
targeted organizations. It was observed that most of the
respondents were from software development companies
(55.92%), which meet the study target.
Number of employees in the organization: This determines the
size (total number of employees) of the organization of the
participants from all locations of the organizations. The most
responses were obtained from the organizations with more than
200 employees which align well with the study with respect to
the sampling population.
Length of time: The study seeks to understand how long the
participants have been into mobile apps development. The results
obtained indicate that about 74.87% of participating organizations
have been developing mobile applications for 5 years and longer.
The primary motivation for developing mobile apps: This defines
the reason/purpose of mobile application development in
participating organizations and individuals. It was observed that
some participants selected more than one answer, but
significantly, the primary motivation for mobile apps
development is for profit.
The total number of mobile apps developed by the organization:
98.01% of the participating population has developed working
mobile apps. The maximum responses of 43.71% came from
those that have developed from 1-10 apps. 1.99% of the
participants agreed that they have not developed working mobile
apps. It shows that the participants are developers who have the
knowledge of developing and implementing mobile apps.
The application success: 99.33% of the total responses indicate
that their developed mobile apps are successful and very
successful whereas, 0.67% indicates that their mobile apps are
average. Also, since their primary motivation for mobile apps
development is for profit and extension of their portfolio,
successfulness of the apps comprises of generated incomes and
growth of the developers/organizations.
The use of SDM: A larger percentage of the sample population
(88.16%) agreed to have used SDMs in developing mobile apps
which implies that SDMs were adopted and widely used during
the development of mobile apps. 11.84% of the participants have
not use a formalized method in mobile apps development.
Probably, most of them are among the participants that have not
developed successful mobile apps, even though, they may have
been developing other computer software. These results are
shown in Table 1.
Table 1: The use of SDM
Usage Number of participants Percentage Cumulative
SDM N = 152 percentage
YES 134 88.16 88.16
NO 9 5.92 94.08
Neutral 9 5.92 100
In order to test the perception of the participant that agreed on the
use of SDMs in developing mobile apps with regard to their most
successful mobile apps developed, some explanatory questions
were asked and the obtained results are presented in Table 2.

Table 2: Explanatory statements of the use of system development methodology

Item Description Mean Standard Scale rating
(N = 152) deviation 1 2 3 4 5
It is good to use SDM. 3.68 0.63 0 (0%) 4 (2.63%) 49 (32.24%) 89 (58.55%) 10 (6.58%)
Use of SDMs enhanced mobile apps dev. 3.67 0.63 0 (0%) 5 (3.29%) 48 (31.58%) 90 (59.21%) 9 (5.92%)
SDM was adopted in the dev. of the mobile apps. 3.70 0.63 0 (0%) 3 (1.97%) 50 (32.89%) 87 (57.25%) 12 (7.89%)

280
It is good to use SDM in mobile apps development: From Table 2
(1), 4 participants (2.63%) disagree, 49 (32.24%) neutral, 89
(58.55%) agree and 10 (6.58%) strongly agree. It is therefore
obvious that two-thirds of the participants (65.13%) accepted that
it is good to use SDMs in software development, 2.63%
completely disagree while 32.45% could not say whether it is
good or not. This indicates that the use of SDM has a good
relative advantage and the use of SDMs is promoted by the
participants.
Use of SDMs enhanced mobile apps development: From Table 2
(2), the results showed that 5 (3.29%) disagree, 48 (31.58%) were
neutral, 90 (59.21%) agree and 9 (5.92%) strongly agree.
Therefore, 99 (65.13%) of the participants perceived that the use
of SDMs enhanced mobile apps development which suggests that
SDMs contribute positively to the development of mobile apps.
SDM was adopted in the development of the mobile apps: From
Table 2 (3), the results showed that 3 (1.97%) disagree, 50
(32.89%) were neutral, 87 (57.25%) agree and 12 (7.89%)
strongly agree. This indicates that 98 (65.14%) of the participants
adopted the use of SDMs in the development of mobile apps.
Hence SDMs are significantly used during the development of
mobile apps.
The above results will help in substantiating the suggestions that
promoted and encouraged the use of SDMs in mobile apps
development [1-3, 41, 42]
5.2. Is SDMs worthy of using?
The aim of this study is to determine the practical effect of the
use of SDMs in mobile apps development. Literature offered
several convincing reasons for using SDMs in software
development [1-3, 14, 42] but lack enough empirical research
substantiation. To investigate the effect of SDMs on mobile apps
development, we performed T-test analysis on the two groups;
Group 1 – nonusers of SDM and Group 2 – users of SDMs. The
T-test is a statistical analysis used to test the difference in the
mean of two independent populations or samples and can only
compare means of the two different groups [43]. This was done to
determine the effect sizes of the use of SDMs by different
companies in mobile apps development. Effect sizes indicate
practical significance, that is, the extent to which a difference is
large enough to have an effect in practice [44].
The comparing of the means of the two groups according to
Cohen guidelines for effect sizes, d [40] were conducted using
Equation 3, and the resulting data is presented in Table 3.
 (M 2  M )  (1)
d   1

 SD pooled 

where,
( n1  1) SD 12  ( n 2  1) SD 22 ; n1  n2 (2)
SD pooled 
( n1  n 2 )  2
M2 and M1 are the means of the two groups; Spooled is the pooled
standard deviation. n1 and n2 are the sample sizes; SD1 and SD2
are the standard deviations of the groups.
From Table 3, we derived the practical effect of SDMs in mobile
apps development as follows:
Organizational size (d = 1.05): This indicates a large practical
significant difference which implies that the organizations that
make use of SDMs in developing mobile apps are likely to have
more employees than non-users of SDMs. Hence organizations
that make use of SDMs are larger and well established.
Number of developers in the organization (d = 0.80): There is
also a practically significant difference between the numbers of
developers in an organization that uses SDMs in mobile apps
development with those that do not use SDM. This implies that
organizations that embrace the use of SDMs do have more in-
house software developers than nonusers of SDMs
Organizational years of existence (d = 1.31): There is a very
large practical significant difference regarding organizational
years of existence between the two groups. Thus, SDMs are
mostly used in mobile apps development by organizations that
have been long in existence.
Number of applications developed (d = 0.7): There is a medium
significant difference between the numbers of mobile apps
developed by organizations that use SDMs in mobile apps
development opposed to those that do not use SDMs. This
implies that those organizations that use SDMs have developed
more mobile apps than non-users of SDMs.
Application success (d = 0.8): Interestingly, a practically
significant difference also exists in the success of applications
developed, which suggests that mobile apps developed with
SDMs tend to be more successful than those developed without
SDMs. The success was considered in terms of generated revenue
and adoption of the developed mobile apps. It shows that mobile
apps developed with SDMs gained wider adoption by the end-
users which in turn generated more income to the
developers/organization.

Table 3: T-test analysis between two groups (users of SDM and non-users of SDM)
Scale rating
Groups Number of Standard
Construct Mean p-value d-value
(1 & 2) respondents deviation
Min. Max
Organizational size Gr1 9 1.56 0.73 1 3
0.0001 1.05^^
Gr2 134 3.29 1.65 1 5
Number of developers in the Gr1 7 1.43 0.53 1 2
0.0008 0.80^^
organization Gr2 129 2.5 1.39 1 5

281
 Organizational years of existence Gr1 7 1.43 0.53 1 2
0.0027 1.31^^
Gr2 126 2.37 0.72 1 3
Number of applications developed Gr1 9 1.33 0.50 1 2
0.0006 0.70^
Gr2 132 2.17 1.20 1 4
Application success Gr1 9 4.11 0.60 3 4
0.0521 0.80^^
Gr2 133 4.57 0.50 4 5
Gr 1 is the total number of non-users of SDM ; Gr 2 is the total number of users of SDM.; ^^ Practically significant difference;
^ Medium significant difference
6. Conclusions 3. Dittrich, Y., Software engineering beyond the project–
The aim of this study is to investigate the use of SDMs in the Sustaining software ecosystems. Information and
development of mobile apps and to determine if they are worthy Software Technology, 2014. 56(11): p. 1436-1456.
of using. A survey was conducted among various companies 4. Tyler, H. Top 4 Software Development Methodologies.
targeting software developers and ICT professionals. The selected 2017 [cited 2017 30 May]; Available from:
sampling populations are organizations that have in one way or http://blog.blackducksoftware.com/top-4-software-
the other must have developed mobile apps. The descriptive development-methodologies.
statistics revealed that 88.16% of the participants agreed to have 5. Georgiadou, E., Software process and product
used SDMs in software development. In testing their perception improvement: a historical perspective. Cybernetics and
on the use of SDMs, 65.13% representing almost two-thirds of Systems Analysis, 2003. 39(1): p. 125-142.
the participants accepted the following facts about the use of 6. Geambasu, C.V., Jianu, I., Jianu, I., and Gavrila, A.,
SDM: i) It is good to use SDMs in the development of mobile Influence factors for the choice of a software
apps, ii) The use of SDMs enhanced the design and creation, development methodology. Accounting and
maintainability and sustainability of mobile apps, and iii) In the Management Information Systems, 2011. 10(4): p. 479.
development of their successful mobile apps, they employed the 7. Mc Namara, K.S. Mobile Applications in_Agriculture
use of SDMs. Therefore, it was discovered that SDMs are used and Rural Development_–Framing the Topic, and
actively in the development of mobile apps and contributes Learning from Experience'. in World Bank Workshop on
positively toward the improvement of mobile apps development. Mobile Innovations for Social and Economic
On the worthiness of the use of SDMs, it was observed that there Transformation. 2009.
is a practical significant difference between the users and non- 8. Qiang, C.Z., Kuek, S.C., Dymond, A., Esselaar, S., and
users of SDMs in the development of mobile apps. This indicates Unit, I., Mobile applications for agriculture and rural
that, in practice, the use of SDMs has a significant effect on the development. World Bank, Washington, DC, 2011.
development process of mobile apps and the products. The effects 9. El-Hussein, M.O.M. and Cronje, J.C., Defining Mobile
were more significant in the areas of organizational size, number Learning in the Higher Education Landscape.
of developers in the organization, organizational years of Educational Technology & Society, 2010. 13(3): p. 12-
existence, number of mobile apps developed and application 21.
success (usage and income). It seems that users (companies) of 10. Muccini, H., Di Francesco, A., and Esposito, P.
SDMs are mostly lager with over 200 employees, longer in Software testing of mobile applications: Challenges and
existence and more productive. Interestingly, it was found that future research directions. in Automation of Software
the use of SDMs help in the development of standardized mobile Test (AST), 2012 7th International Workshop on. 2012.
apps that can be widely adopted and in turn generates more IEEE. p. 29-35.
revenue to the developers/organizations. The findings of this 11. Charland, A. and Le Roux, B., Mobile application
study indicate that it is necessary to employ the use SDMs in the development: web vs. native. Communications of the
development of mobile apps because they have positive ACM, 2011. 54(5): p. 49-53.
influences on the general improvement of the organizations and 12. Zhang, D. and Adipat, B., Challenges, methodologies,
success of their products (mobile apps). We, therefore, conclude and issues in the usability testing of mobile
that SDMs are indeed worthy of use in the development of applications. International journal of human-computer
mobile apps. interaction, 2005. 18(3): p. 293-308.
13. Lugano, G. Mobile social software: Definition, scope
References and applications. in eChallenges 2007 Conference.
1. Partsch, H.A., Specification and transformation of 2007. p. 1434-1441.
programs: a formal approach to software development. 14. Iivari, J., Rudy, H., and Heinz, K.K., A dynamic
2012: Springer Science & Business Media. framework for classifying information systems
2. Wasserman, A.I. Software engineering issues for mobile development methodologies and approaches. Journal of
application development. in Proceedings of the Management Information Systems, 2000. 17(3): p. 179-
FSE/SDP workshop on Future of software engineering 218.
research. 2010. ACM. p. 397-400.

282
15. Avison, D. and Fitzgerald, G., Information systems
development: methodologies, techniques and tools.
2003: McGraw Hill.
16. CMS. Selecting a development approach. 2008 [cited
2017 30 December]; Available from:
https://www.cms.gov/research-statistics-data-and-
systems/cms-information-technology/xlc/downloads/
selectingdevelopmentapproach.pdf.
17. Pãvãloaia, V.-D., Methodology approaches regarding
classic versus mobile enterprise application
development. Informatica Economica, 2013.17(2): p. 59.
18. Iivari, J., Hirschheim, R., and Klein, H.K. Beyond
methodologies: keeping up with information systems
development approaches through dynamic
classification. in Systems Sciences, 1999. HICSS-32.
Proceedings of the 32nd Annual Hawaii International
Conference on. 1999. IEEE. p. 10 pp.
19. Wynekoop, J.L. and Russo, N.L. System Development
methodologies: unanswered questions and the research-
practice gap. in ICIS. 1993. p. 181-190.
20. Munassar, N.M.A. and Govardhan, A., A comparison
between five models of software engineering. IJCSI
International Journal of Computer Science Issues, 2010.
7(5): p. 94-101.
21. Pohl, K., Requirements engineering: fundamentals,
principles, and techniques. 2010: Springer Publishing
Company, Incorporated.
22. Spataru, A.C., Agile development methods for mobile
applications. School of Informatics. University of
Edinburgh, UK, 2010.
23. Osellus. OUR APP DEVELOPMENT
METHODOLOGY (M-COMPASS). 2015 [cited 2015
12 February]; Available from: http://www.osellus-
mobile.com/methodology.html.
24. Stoica, M., Mircea, M., and Ghilic-Micu, B., Software
development: Agile vs. traditional. Informatica
Economica, 2013. 17(4): p. 64.
25. Jeong, Y.-J., Lee, J.-H., and Shin, G.-S. Development
process of mobile application SW based on agile
methodology. in Advanced Communication Technology,
2008. ICACT 2008. 10th International Conference on.
2008. IEEE. p. 362-366.
26. Rahimian, V. and Ramsin, R., Designing an agile
methodology for mobile software development: A hybrid
method engineering approach. . Second International
Conference on Research Challenges in Information
Science, 2008: p. pp. 337-342. IEEE.
27. Afonso, A., Regateiro, F., and Silva, M.J., Dynamic
Channels: A New Development Methodology for Mobile
Computing Applications. Accessed on 21/06/2016 from
http://www.di.fc.ul.pt/biblioteca/tech-reports. 1998.
28. Chen, M., A methodology for building mobile
computing applications. International Journal of
Electronic Business, 2004. 2(3): p. 229-243.
29. Russo, N., Wynekoop, J., and Walz, D., The use and
adaptation of system development methodologies.
283
View publication stats
Managing Information & Communications in a
Changing Global Environment, Idea Group Publishing,
PA, 1995.
30. Glass, R.L., A snapshot of systems development
practice. IEEE Software, 1999. 16(3): p. 112-111.
31. Fitzgerald, B., Russo, N.L., and Stolterman, E.,
Information systems development: methods in action.
2002: McGraw-Hill Education. P:194.
32. Janse van Rensburg, C., “The relationship between
process maturity models and the use
and effectiveness of systems development methodologies”, M.Sc.
dissertation. 2012.
33. Conradie, P., “The use and effectiveness of information
system development
methodologies in health information systems”, PhD thesis. 2010.
34. Van Aswegen, K., Huisman, M., and Taylor, E., To use
or not to use? SDM utilisation in the development of
LMS in South Africa. Interactive Technology and Smart
Education, 2014. 11(4): p. 238-253.
35. Fitzgerald, B., Russo, N.L., and O'Kane, T., Software
development method tailoring at Motorola.
Communications of the ACM, 2003. 46(4): p. 64-70.
36. Pfleeger, S.L., Understanding and improving
technology transfer in software engineering. Journal of
Systems and Software, 1999. 47(2): p. 111-124.
37. Gallivan, M.J., The influence of software developers’
creative style on their attitudes to and assimilation of a
software process innovation. Information &
Management, 2003. 40(5): p. 443-465.
38. O'Rourke, N. and Hatcher, L., A step-by-step approach
to using SAS for factor analysis and structural equation
modeling. 2013: Sas Institute.
39. Numally, J.C., Psychometric theory. NY: McGraw-Hill,
1978.
40. Cohen, J., Statistical power analysis for the behavioural
sciences (2nd ed). Hillsdale, NJ: Erlbaum. 1988.
41. Huisman, M. and Iivari, J., Deployment of systems
development methodologies: Perceptual congruence
between IS managers and systems developers.
Information & Management, 2006. 43(1): p. 29-49.
42. Corral, L., Sillitti, A., and Succi, G. Software
development processes for mobile systems: Is agile
really taking over the business? in Engineering of
Mobile-Enabled Systems (MOBS), 2013 1st
International Workshop on the. 2013. IEEE. p. 19-24.
43. Creech, S. Statistically significant. 2003 [cited 2017 29
september];Available from: http://
www.statisticallysignificantconsulting.com/Anova.htm.
44. Steyn, H.S.J. Manual for the determination of Effect
size indices and Practical Significance. 2012 [cited
2017 8 June]; Available from: http://natural-
sciences.nwu.ac.za/scs/manuals/determination-of-effect-
size-indices-and-practical-significance.