Empirically Driven Design of Software Development Processes for Wireless Internet Services

Boggio²,

IIEEE Trans. Software Eng.

et al. 2003

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

Section: ----------------mentioning

confidence: 99%

Toward a reference process for developing wireless Internet services

Boggio²,

IIEEE Trans. Software Eng.

et al. 2003

“…The basis for our approach is the creation of customizable, domain-specific process models (i.e., reference process models) through the bottom-up identification of process variations. The overall approach can be seen in Figure 1, and is described with details in (Becker-Kornstaedt et al 2002). The mentioned article describes a validated method on how to gain process knowledge for an upcoming field fast and incrementally.…”

mentioning

confidence: 99%

Software process commonality analysis

Bella

Softw Process Imprv Pract

2005

Self Cite

To remain viable and thrive, software organizations must rapidly adapt to frequent and, often, rather far-ranging changes to their operational context. These changes typically concern many factors, including the nature of the organization's marketplace in general, its customers' demands, and its business needs. In today's most highly dynamic contexts, such as web services development, other changes create additional, severe challenges. Most critical are changes to the technology in which a software product is written or which the software product has to control or use to provide its functionality. These product-support technology changes are frequently relatively small and incremental. They are, therefore, often handled by relatively small , incremental changes to the organization's software processes. However, the frequency of these changes is high, and their impact is elevated by time-to-market and requirements change demands. The net result is an extremely challenging need to create and manage a large number of customized process variants, collectively having more commonalities than differences, and incorporating experience-based, proven best practices . This paper describes a tool-based approach to coping with product-support technology changes. The approach utilizes established capabilities such as descriptive process modeling and the creation of reference models. It incorporates a new, innovative, tool-based capability to analyze commonalities and differences among processes. The paper includes an example-based evaluation of the approach in the domain of Wireless Internet Services as well as a discussion of its potentially broader application

“…Some of the possibilities include: Looking at similar domains and trying to adapt their processes, eliciting the actual practices and tailoring them to the new domain, or the combination of both. In the context of the WISE project, a method was developed and used in order to design an adaptable software process based on existing practices from related domains, industrial piloting, and expert knowledge [3]. As part of the method, descriptive process modeling was used in order to capture the real experience of the process performers and to verify the evidence (products).…”

Section: Process and Product Modelsmentioning

confidence: 99%

Capturing Evidence from Wireless Internet Services Development

Bella

Eleventh Annual International Workshop on Software Technology and Engineering Practice

Abstract-The merging of the Internet with the Wireless services domain has created a potential market whose characteristics are new technologies and time-to-market pressure. The lack of knowledge about new technologies and the need to be competitive in a short time demand that software organizations learn quickly about this domain and its characteristics. Additionally, the effects of development techniques in this context need to be understood. Learning from previous experiences in such a changing environment demands a clear understanding of the evidence to be captured, and how it could be used in the future. This article presents definitions of quantitative and qualitative evidence, and templates for capturing such evidence in a systematic way. Such templates were used in the context of two pilot projects dealing with the development of Wireless Internet Services.