DocumentCode
3153369
Title
Traceability for integration
Author
Gieszl, Louis R.
Author_Institution
Johns Hopkins Univ., Baltimore, MD, USA
fYear
1992
fDate
15-18 Jun 1992
Firstpage
220
Lastpage
228
Abstract
Software traceability (as required by DOD STD 2167A for software developed for the Department of Defense) sound like a good idea from the sponsor´s point of view, and it seems like a natural (and even useful) task for the developer. The author takes a closer look at how you do it and whether it is helpful or it is simply another documentation chore. The article is derived from lessons learned in practice and from reviewing the research work of the students from several semesters of a Johns Hopkins University graduate course on software engineering
Keywords
military computing; software engineering; DOD STD 2167A; Department of Defense; Johns Hopkins University graduate course; documentation chore; research work; software engineering; software traceability; students; Documentation; Embedded software; Flowcharts; Laboratories; Physics; Prototypes; Software engineering; Software testing; US Department of Defense; Weapons;
fLanguage
English
Publisher
ieee
Conference_Titel
Systems Integration, 1992. ICSI '92., Proceedings of the Second International Conference on
Conference_Location
Morristown, NJ
Print_ISBN
0-8186-2697-6
Type
conf
DOI
10.1109/ICSI.1992.217299
Filename
217299
Link To Document