Information systems development research: an exploration of ideas in practice
The Computer Journal - Special issue on methodologies (systems and software)
Software development method tailoring at Motorola
Communications of the ACM - Digital rights management
A Practical Guide to Product Line Scoping
SPLC '06 Proceedings of the 10th International on Software Product Line Conference
The REMIS approach for rationale-driven process model evolution
ICSP'07 Proceedings of the 2007 international conference on Software process
Focused identification of process model changes
ICSP'07 Proceedings of the 2007 international conference on Software process
Improving the development of e-business systems by introducing process-based software product lines
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Connecting the rationale for changes to the evolution of a process
PROFES'07 Proceedings of the 8th international conference on Product-Focused Software Process Improvement
Meta Model Based Architecture for Software Process Instantiation
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
A framework for the flexible instantiation of large scale software process tailoring
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process
An MDE approach to software process tailoring
Proceedings of the 2011 International Conference on Software and Systems Process
A declarative framework for work process configuration
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
Hi-index | 0.00 |
Defining process standards by integrating, harmonizing, and standardizingheterogeneous and often implicit processes is an important task, especiallyfor large development organizations. However, many challenges exist,such as limiting the scope of process standards, coping with different levels ofprocess model abstraction, and identifying relevant process variabilities to beincluded in the standard. On the one hand, eliminating process variability bybuilding more abstract models with higher degrees of interpretation has manydisadvantages, such as less control over the process. Integrating all kinds ofvariability, on the other hand, leads to high process deployment costs. This articledescribes requirements and concepts for determining the scope of processstandards based on a characterization of the potential productzs to be producedin the future, the projects expected for the future, and the respective process capabilitiesneeded. In addition, the article sketches experience from determiningthe scope of space process standards for satellite software development. Finally,related work with respect to process model scoping, conclusions, and an outlookon future work are presented.