Zur Kurzanzeige

dc.contributor.authorSneed, Harry
dc.contributor.editorBecker, Steffen
dc.contributor.editorBogicevic, Ivan
dc.contributor.editorHerzwurm, Georg
dc.contributor.editorWagner, Stefan
dc.date.accessioned2019-03-14T11:49:19Z
dc.date.available2019-03-14T11:49:19Z
dc.date.issued2019
dc.identifier.isbn978-3-88579-686-2
dc.identifier.issn1617-5468
dc.identifier.urihttp://dl.gi.de/handle/20.500.12116/20899
dc.description.abstractThe following paper presents the current state of the author’s research on the subject of static software tracing, a research which dates back to the year 2000 when the author was requested to predict the costs of software maintenance projects. The goal of static tracing is to link the software artifacts produced in software development with the original requirements. These artifacts are linked by comparing the data names they use, i.e. their operands, with the nouns in the requirement text. Artifacts that have data names similar to those used in the requirement texts are considered to be implementations of those requirements.en
dc.language.isoen
dc.publisherGesellschaft für Informatik e.V.
dc.relation.ispartofSoftware Engineering and Software Management 2019
dc.relation.ispartofseriesLecture Notes in Informatics (LNI) - Proceedings, Volume P-292
dc.subjectRequirement models
dc.subjectDesign models
dc.subjectCode models
dc.subjectTest models
dc.subjectModel comparison
dc.subjecttracing requirements
dc.subjectlinking software artifacts
dc.subjectconsistency
dc.subjectcompleteness
dc.titleChecking Consistency and Completeness of Software Systemsen
dc.typeText/Conference Paper
dc.pubPlaceBonn
mci.reference.pages129-132
mci.conference.sessiontitleSession 12: Software Management II, Security und Technologietransfer
mci.conference.locationStuttgart, Germany
mci.conference.date18.-22. Februar 2019
dc.identifier.doi10.18420/se2019-39


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige