%PDF-1.4
%
1 0 obj
<<
/Type /Catalog
/Pages 2 0 R
/Metadata 3 0 R
>>
endobj
4 0 obj
<<
/Producer (MiKTeX pdfTeX-1.40.9)
/Creator (TeX)
/CreationDate (D:20090304125440+01'00')
/ModDate (D:20090304125440+01'00')
/Trapped /False
/PTEX.Fullbanner (This is MiKTeX-pdfTeX 2.7.3147 \(1.40.9\))
/Subject (It is widely assumed that following a process is a good thing if you want to achieve and exploit the benefits of traceability on a software development project. A core component of any such process is the definition and use of a traceability information model. Such models provide guidance as to those software development artifacts to collect and those relations to establish, and are designed to ultimately support required project analyses. However, traceability still tends to be undertaken in rather ad hoc ways in industry, with unpredictable results. We contend that one reason for this situation is that current software development tools provide little support to practitioners for building and using customized project-specific traceability information models, without which even the simplest of processes are problematic to implement and gain the anticipated benefits from. In this paper, we highlight the typical decisions involved in creating a basic traceability information model, suggest a simple UML-based representation for its definition, and illustrate its central role in the context of a modeling tool. The intent of this paper is to re-focus attention on very practical ways to apply traceability information models in practice so as to encourage wider adoption.)
/Author <5061747269636B204DE464657220616E64204F726C656E6120476F74656C20616E6420496C6B61205068696C6970706F77>
/bibtex#2Fbibtexkey (conf/tefse/MaederGP09)
/bibtex#2Fbooktitle (Proceedings of 5th International Workshop on Traceability in Emerging Forms of Software Engineering \(TEFSE 2009\). In conjunction with the 31st International Conference on Software Engineering, ICSE 2009, May 16-24, 2009, Vancouver, Canada)
/bibtex#2Fdoi (http://dx.doi.org/10.1109/TEFSE.2009.5069578)
/bibtex#2Ffile (:/Users/Patrick/Desktop/pdfs/TEFSE09_maeder_gotel_PromotingTraceabilityInformationModel.pdf:PDF)
/bibtex#2Fisbn (978-1-4244-3741-2)
/Keywords (Unified Modeling Language, project management, software tools, UML-based representation, customized project-specific traceability information model, software development artifacts, software development project, software development tools, class diagram, traceability model, traceability meta-model, Patrick Maeder, Patrick Mader)
/bibtex#2Fpages (21--25)
/bibtex#2Fpublisher (IEEE Computer Society)
/Title (Getting Back to Basics: Promoting the Use of a Traceability Information Model in Practice)
/bibtex#2Fyear (2009)
/bibtex#2Fentrytype (Inproceedings)
>>
endobj
2 0 obj
<<
/Type /Pages
/Count 5
/Kids [5 0 R 6 0 R 7 0 R 8 0 R 9 0 R]
>>
endobj
3 0 obj
<<
/Type /Metadata
/Subtype /XML
/Length 10 0 R
>>
stream
It is widely assumed that following a process is a good thing if you want to achieve and exploit the benefits of traceability on a software development project. A core component of any such process is the definition and use of a traceability information model. Such models provide guidance as to those software development artifacts to collect and those relations to establish, and are designed to ultimately support required project analyses. However, traceability still tends to be undertaken in rather ad hoc ways in industry, with unpredictable results. We contend that one reason for this situation is that current software development tools provide little support to practitioners for building and using customized project-specific traceability information models, without which even the simplest of processes are problematic to implement and gain the anticipated benefits from. In this paper, we highlight the typical decisions involved in creating a basic traceability information model, suggest a simple UML-based representation for its definition, and illustrate its central role in the context of a modeling tool. The intent of this paper is to re-focus attention on very practical ways to apply traceability information models in practice so as to encourage wider adoption.
Patrick Mäder
Orlena Gotel
Ilka Philippow
bibtex/bibtexkey/conf/tefse/MaederGP09
bibtex/booktitle/Proceedings of 5th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2009). In conjunction with the 31st International Conference on Software Engineering, ICSE 2009, May 16-24, 2009, Vancouver, Canada
bibtex/file/:/Users/Patrick/Desktop/pdfs/TEFSE09_maeder_gotel_PromotingTraceabilityInformationModel.pdf:PDF
bibtex/isbn/978-1-4244-3741-2
bibtex/pages/21--25
http://dx.doi.org/10.1109/TEFSE.2009.5069578
Unified Modeling Language
project management
software tools
UML-based representation
customized project-specific traceability information model
software development artifacts
software development project
software development tools
class diagram
traceability model
traceability meta-model
Patrick Maeder
Patrick Mader
IEEE Computer Society
Getting Back to Basics: Promoting the Use of a Traceability Information Model in Practice
2009
application/pdf
Inproceedings
Patrick Mäder
Orlena Gotel
Ilka Philippow
conf/tefse/MaederGP09
Proceedings of 5th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2009). In conjunction with the 31st International Conference on Software Engineering, ICSE 2009, May 16-24, 2009, Vancouver, Canada
http://dx.doi.org/10.1109/TEFSE.2009.5069578
:/Users/Patrick/Desktop/pdfs/TEFSE09_maeder_gotel_PromotingTraceabilityInformationModel.pdf:PDF
978-1-4244-3741-2
Unified Modeling Language, project management, software tools, UML-based representation, customized project-specific traceability information model, software development artifacts, software development project, software development tools, class diagram, traceability model, traceability meta-model, Patrick Maeder, Patrick Mader
21--25
IEEE Computer Society
Getting Back to Basics: Promoting the Use of a Traceability Information Model in Practice
2009
Inproceedings
endstream
endobj
5 0 obj
<<
/Type /Page
/Contents 11 0 R
/Resources 12 0 R
/MediaBox [0 0 612 792]
/Parent 2 0 R
>>
endobj
6 0 obj
<<
/Type /Page
/Contents 13 0 R
/Resources 14 0 R
/MediaBox [0 0 612 792]
/Parent 2 0 R
>>
endobj
7 0 obj
<<
/Type /Page
/Contents 15 0 R
/Resources 16 0 R
/MediaBox [0 0 612 792]
/Parent 2 0 R
>>
endobj
8 0 obj
<<
/Type /Page
/Contents 17 0 R
/Resources 18 0 R
/MediaBox [0 0 612 792]
/Parent 2 0 R
>>
endobj
9 0 obj
<<
/Type /Page
/Contents 19 0 R
/Resources 20 0 R
/MediaBox [0 0 612 792]
/Parent 2 0 R
>>
endobj
10 0 obj
6277
endobj
11 0 obj
<<
/Length 21 0 R
/Filter /FlateDecode
>>
stream
xڕZKWHU|'T6˕Z"<_~4T9h 6?}e08U&,I6iAm'{=}TxߔQ쟷(6̽]FG͕T%O,4f<3]{تS9e?6*(/7jl4Ǝp|~$t]^A6($a`1̝mwaicZR
$K6ߨڦliV}7oHsbZ["3^-Qpy%>A }!_W*E8*?#G;_u_Iv|tDo>O02X4]ӔӬVck
l
[u-Mנj-6eNFLYgSgGbQ曀2Եߋ^^F~H
V/?oS?pwetf熵kvT0_u>
A"?}|\LTa^3{F#E}]O2*2pY)Xx
ǽ+GRq;>џe\p