Documenting variability in requirements artefacts

Software Product Line Engineering: Foundations, Principles, and Techniques

Volumn , Issue , 2005, Pages 89-113

  Pohl, Klaus ^a   Weyer, Thorsten ^a  

^a UNIVERSITY OF DUISBURG ESSEN   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892339318     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28901-1_5     Document Type: Chapter

References (2)

1. Large systems are typically subdivided into several abstraction levels, such as system level, subsystem level, and component level. The use case diagram can be used to provide an overview of the use cases at any abstraction level, i.e. of the system use cases as well as the subsystem and component use cases.
2. The class diagram is also used at other stages of software development. We use it in domain realisation to describe the internal structure of components. Similar statements hold for the state machine diagram also described in this section.