2008
DOI: 10.1007/978-3-540-85936-9_13
|View full text |Cite
|
Sign up to set email alerts
|

Lightweight Process Documentation: Just Enough Structure in Automotive Pre-development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2009
2009
2019
2019

Publication Types

Select...
5
2
1

Relationship

3
5

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 4 publications
0
6
0
Order By: Relevance
“…Some of these requirements, like the visual distinction between solid and fluid, led to the creation of a new notation instead of reusing DFDs. Very simple but flexible notations were most appropriate wherever we used information flow analysis so far (Schneider, ; Schneider & Lübke, ; Stapel et al ., , , ; Schneider et al ., ).…”
Section: Flow Fundamental Conceptsmentioning
confidence: 99%
“…Some of these requirements, like the visual distinction between solid and fluid, led to the creation of a new notation instead of reusing DFDs. Very simple but flexible notations were most appropriate wherever we used information flow analysis so far (Schneider, ; Schneider & Lübke, ; Stapel et al ., , , ; Schneider et al ., ).…”
Section: Flow Fundamental Conceptsmentioning
confidence: 99%
“…As a first approximation the number of observation packages that mention problems related to missing context, missing awareness, or missing documentation can be used. In addition, observers that are trained in FLOW analysis can be sent to each development location, or already present developers can be quickly trained before project start [10] to capture the relevant information flows remotely. A combination of a survey based approach [10] and Social Network Analysis [9] could be used to measure team awareness.…”
Section: Qip-23 Choose Processmentioning
confidence: 99%
“…Although quite a few contributions found informal communication to be a main driver of (global) software projects [1,2,5,[7][8][9], not many approaches have been proposed to explicitly take informal, verbal, or ad-hoc communication into account. But, especially at project start, when distributed teams still grow together and requirements are unclear, these types of communication are very common [1,5,7,10] and thus should be analyzed and optimized.…”
Section: Introductionmentioning
confidence: 99%
“…Some of these requirements, like the visual distinction between solid and fluid, led to the creation of a new notation instead of reusing DFDs. Very simple but flexible notations were most appropriate wherever we used information flow analysis so far (Schneider, 2004;Schneider & Lübke, 2005;Stapel et al, 2007Stapel et al, , 2008Stapel et al, , 2009Schneider et al, 2008). Table 1 summarizes the symbols that satisfy the mentioned requirements and form the graphical FLOW notation.…”
Section: The Graphical Flow Notationmentioning
confidence: 99%