Software Process Dynamics and Agility
DOI: 10.1007/978-3-540-72426-1_10
|View full text |Cite
|
Sign up to set email alerts
|

Representing Process Variation with a Process Family

Abstract: Abstract. The formalization of process definitions has been an invaluable aid in many domains. However, noticeable variations in processes start to emerge as precise details are added to process definitions. While each such variation gives rise to a different process, these processes might more usefully be considered as variants of each other, rather than completely different processes. This paper proposes that it is beneficial to regard such an appropriately close set of process variants as a process family. … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0
1

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 22 publications
(14 citation statements)
references
References 35 publications
0
13
0
1
Order By: Relevance
“…Processes are also composed of structuring elements, which act as the glue between single elements, such as control or data/product flows, or predefined element groups such as iterations or components. The process can be also tailored by means of varying these structuring elements, as proposed in: Simidchieva et al (2007), Hesse and Noack (1999), Giese et al (2007), Schnieders (2006), Jaufman and Münch (2005), or Lobsitz (1996), which include variability in control or data flows; Chou and Chen (2000), Biffl et al (2006), Park et al (2006), Madhavji and Schafer (1991), or Dai and Li (2007) propose grouping element variations. Figure 4 shows these proposals that are classified according to the type of element that is varied, namely control and data flow variations, elements, and others.…”
Section: Software Process Elements Used In Tailoring Processesmentioning
confidence: 99%
“…Processes are also composed of structuring elements, which act as the glue between single elements, such as control or data/product flows, or predefined element groups such as iterations or components. The process can be also tailored by means of varying these structuring elements, as proposed in: Simidchieva et al (2007), Hesse and Noack (1999), Giese et al (2007), Schnieders (2006), Jaufman and Münch (2005), or Lobsitz (1996), which include variability in control or data flows; Chou and Chen (2000), Biffl et al (2006), Park et al (2006), Madhavji and Schafer (1991), or Dai and Li (2007) propose grouping element variations. Figure 4 shows these proposals that are classified according to the type of element that is varied, namely control and data flow variations, elements, and others.…”
Section: Software Process Elements Used In Tailoring Processesmentioning
confidence: 99%
“…Scopus answered once two studies for RQ1. Mello et al (2012) Checklist-based inspection technique for feature models review 2012 IEEE Xplore Cunha et al (2012) A set of inspection technique on software 2012 Google Scholar product line models Mello et al (2010) Activity diagram inspection on requirements specification 2010 IEEE Xplore Chen et al (2009) Variability management in software product 2009 ACM Digital lines: A systematic review Library Petersen et al (2008b) The impact of time controlled reading on 2008 ACM Digital Library software inspection effectiveness and efficiency: A controlled experiment Simidchieva et al (2007) Representing process variation with a process family 2007 Google Scholar Winkler et al (2007) Early software product improvement with sequential 2007 IEEE Xplore inspection sessions: An empirical investigation of inspector capability and learning effects Tørner et al (2006) Defects in automotive use cases 2006 ACM Digital Library He and Carver (2006) PBR vs. checklist: A replication in the N-fold inspection context 2006 ACM Digital Library Lange and Chaudron (2006) Effects of defects in UML models -an experimental investigation 2006 ACM Digital Library Wagner (2006) A model and sensitivity analysis of the quality 2006 ACM Digital economics of defect-detection techniques Library Cooper et al (2005) Experiences using defect checklists in software 2005 Google Scholar engineering education Belgamo et al (2005) TUCCA improving the effectiveness of use case 2005 IEEE Xplore construction and requirement analysis Staron et al (2005) An empirical assessment of using stereotypes to 2005 ACM Digital Library improve reading techniques in software inspections Investigating the active guidance factor in reading 2004 IEEE Xplore techniques for defect detection Lanubile et al (2004) Assessing the impact of active guidance for defect 2004 IEEE Xplore detection: A replicated experiment Denger and Paech (2004) an integrated quality assurance approach for use 2004 Google Scholar case based requirements Grunbacher et al (2003) An empirical study on groupware support for 2003 IEEE Xplore software inspection meetings Kelly and Shepard (2003) An experiment to investigate interacting versus 2003 ACM Digital Library nominal groups in software inspection Miller and Yin (2003) Adding (2001) A case study in the use of defect classification in inspections 2001 ACM Digital Library Freimut et al (2001) Investigating the impact of reading techniques on the accuracy 2001 IEEE Xplore of different defect content estimation techniques …”
Section: Data Sources X Rqs X Research Typesmentioning
confidence: 99%
“…Other approaches are similar to ours. One approach [27] proposes to model one process and to augment it with process elements selected according to a process goals specification, in order to obtain a particular process. The notion of process goals specification is close to our notion of requirements of a project.…”
Section: Use Of Cvl Independently Of the Process Metamodelmentioning
confidence: 99%