Introduction to the team software process
Introduction to the team software process
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Proceedings of the 2004 ACM workshop on Interdisciplinary software engineering research
Technical Software Development Process in the XML Domain
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
Effects of architecture and technical development process on micro-process
ICSP'07 Proceedings of the 2007 international conference on Software process
Reconciling software development models: A quasi-systematic review
Journal of Systems and Software
Building software process line architectures from bottom up
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Requirements and constructors for tailoring software processes: a systematic literature review
Software Quality Control
| Hi-index | 0.00 |
Currently, proposed development processes are often considered too generic for operational use. This often leads to a misunderstanding of the project-specific processes and its refuse. One reason for non-appropriate project-specific processes is insufficient support for the tailoring of generic processes to project characteristics and context constraints. To tackle this problem, we propose a method for the acquisition of a project-specific process. This method uses a domain-specific process line for top-down process tailoring and supports bottom-up refinement of the defined generic process based on tracking process activities. The expected advantage of the method is tailoring efficiency gained by usage of a process line and higher process adherence gained by bottom-up adaptation of the process. The work described was conducted in the automotive domain. This article presents an overview of the so-called Emergent Process Acquisition method (EPAc) and sketches an initial validation study.