Toward a reference process for developing wireless Internet services

Abstract

Wireless Internet services such as mobile Web applications promise an enormous market potential. The field is characterized by extreme time-to-market pressure and insufficient knowledge about development procedures and technical constraints. This results in insufficient guidance for project managers and software developers on selecting appropriate development processes, techniques, methods and tools. In addition, there is an enormous lack of knowledge about the effects (such as effort consumption, defect injection) of such technologies that hinders the transfer of innovative technologies into practice. This article decribes an initial reference process by summarizing essential technologies for the development of wireless Internet services and experience with these technologies on the levels of life cycle processes, engineering processes, and managerial processes. The reference process is based on a comprehensive literature survey and the execution of development projects for wireless Internet services. The goal of the article is to provide domain-specific guidance for project managers and software developers with accompanying lessons learned from the past

Process Model Difference Analysis for Supporting Process Evolution

“…In the bottom-up approach, standards are mainly developed based on observation and descriptive modeling. The WISEP reference process for wireless Internet services [5] and the LIPE reference model for e-business software development [6] illustrate this approach. It is important to observe that, independently of how process evolution is managed, observing processes in practice, identifying variations in them, analyzing these variations, and feeding them back into the standard process model [7] are fundamental activities for actual improvement.…”

Engineering Wireless Mobile Applications

“…However, out of the six papers accepted in the special issue only two papers deal with the development process. Ocampo, Boggio, Munch, and Palladino (2003) provided an initial reference process for developing wireless Internet applications, which does not differ significantly from traditional iterative process models but includes domain-specific guidance on the level of engineering processes. Satoh (2003) developed a framework for building and testing networked applications for mobile computing.…”

Software process commonality analysis

“…This must recognize differences in the application domain as well as goals and contexts of the pilot projects. (6) Create comprehensive process model: The models for the processes used in the pilot projects as well as practices and processes from related fields are integrated to create a comprehensive process model (Ocampo et al 2003). The resulting comprehensive process model can be seen as a reference process model because it is intended to be used as a reference for developers and managers that provides a starting point for developing a customized process, meeting the requirements for a set of product-support technologies.…”