![](bg6.png)
5 CONCLUSIONS
This paper introduces three mobile application main-
tenance models based on the analysis of mobile ap-
plication update history. We collected data to iden-
tify the new feature update frequency and standard
deviation of update time span. By studying the dis-
tributions of these two variables for sample mobile
applications, we observed the patterns of how exist-
ing mobile application maintenance works. The sum-
marized three mobile application maintenance mod-
els form the basis of future research to study explicit
and thorough definitions, instructions and guidelines,
which could be further used in maintenance practice.
The three proposed models provide promising ways
to organize better maintenance schedules and mainte-
nance requirements.
Our future research concerning mobile applica-
tion maintenance will focus on constructing mainte-
nance process model for mobile applications based
on the three maintenance methods obtained from pre-
vious findings. Traditional software maintenance
process models have been widely studied and uti-
lized (Ren et al., 2011). Considering the defects of
heavyweight maintenance practices and specific re-
quirements of current mobile applications, an agile
lightweight maintenance process model could be a
more efficient and economical solution. Related re-
search has been done concerning the result of in-
troducing XP practices to software maintenance pro-
cess. The positive results indicate it could be success-
ful introducing agile practices into software mainte-
nance process (Svensson and Host, 2005). Further-
more, concerning the construction of mobile appli-
cation maintenance models, there are also more de-
tailed research areas to be taken into account, includ-
ing methodologies of eliciting maintenance require-
ments from user feedbacks, managing maintenance
requirements, applying agile principles in mobile ap-
plication maintenance practices, and so on. Further
research should also include bigger samples with ap-
plications from other platforms.
REFERENCES
Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A.,
Cunnimgham, W., Fowler, M., Grenning, J., High-
smith, J., Hunt, A., Jeffries, R., et al. (2001). Prin-
ciples behind the agile manifesto. Retrieved, 11:2008.
Bennett, K. H. and Rajlich, V. T. (2000). Software main-
tenance and evolution: a roadmap. In Proceedings of
the Conference on the Future of Software Engineer-
ing, pages 73–87. ACM.
Berger, C., Blauth, R., Boger, D., Bolster, C., Burchill, G.,
DuMouchel, W., Pouliot, F., Richter, R., Rubinoff, A.,
Shen, D., et al. (1993). Kano’s methods for under-
standing customer-defined quality. Center for Quality
Management Journal, 2(4):3–36.
Boehm, B. (1984). Software engineering economics.
Software Engineering, IEEE Transactions on, SE-
10(1):4–21.
Choudhari, J. and Suman, U. (2010). Iterative maintenance
life cycle using extreme programming. In Advances
in Recent Technologies in Communication and Com-
puting (ARTCom), 2010 International Conference on,
pages 401–403.
Fowler, M. (1999). Refactoring: improving the design of
existing code. Addison-Wesley Professional.
Ger
¨
et
`
ısbakh, I. (1977). Models of preventive maintenance,
volume 23. North-Holland Pub. Co.(Amsterdam and
New York).
Hatton, L. (2007). How accurately do engineers predict
software maintenance tasks? Computer, 40(2):64–69.
Hunt, B., Turner, B., and McRitchie, K. (2008). Software
maintenance implications on cost and schedule. In
Aerospace Conference, 2008 IEEE, pages 1–6.
IEEE (1998). Ieee standard for software maintenance. IEEE
Std. 1219-1998, pages i –3.
Martin, J. and McClure, C. L. (1983). Software Mainte-
nance: The Problems and Its Solutions. Prentice Hall
Professional Technical Reference.
Ren, Y., Liu, Z., Xing, T., and Chen, X. (2011). Soft-
ware maintenance process model and contrastive anal-
ysis. In Information Management, Innovation Man-
agement and Industrial Engineering (ICIII), 2011 In-
ternational Conference on, volume 3, pages 169–172.
Sauerwein, E., Bailom, F., Matzler, K., and Hinterhuber,
H. H. (1996). The kano model: How to delight your
customers. In International Working Seminar on Pro-
duction Economics, volume 1, pages 313–327.
Singh, Y. and Goel, B. A step towards software preventive
maintenance. SIGSOFT Softw. Eng. Notes, 32.
Sommerville, I. (2007). Software Engineering. Interna-
tional computer science series. Addison-Wesley.
Svensson, H. and Host, M. (2005). Introducing an agile
process in a software maintenance and evolution orga-
nization. In Software Maintenance and Reengineer-
ing, 2005. CSMR 2005. Ninth European Conference
on, pages 256–264.
Swanson, E. B. (1976). The dimensions of maintenance. In
Proceedings of the 2Nd International Conference on
Software Engineering, ICSE ’76, pages 492–497, Los
Alamitos, CA, USA. IEEE Computer Society Press.
Timeanddate (2014). Calculate the number of days between
two dates @ONLINE.
Vannieuwenborg, F., Mainil, L., Verbrugge, S., Pickavet,
M., and Colle, D. (2012). Business models for the mo-
bile application market from a developer’s viewpoint.
In Intelligence in Next Generation Networks (ICIN),
2012 16th International Conference on.
Appendix of the mobile applications update his-
tory data available upon request.
ModelsforMobileApplicationMaintenanceBasedonUpdateHistory
217