Towards an ontology of software maintenance

Kitchenham, Barbara; Travassos, Guilherme Horta; Mayrhauser, A. von; Niessink, Frank; Schneidewind, Norman F.; Singer, Janice; Takada, Shingo; Vehvilainen, Risto; Yang, Hongji

doi:10.1002/(sici)1096-908x(199911/12)11:6<365::aid-smr200>3.0.co;2-w

Cited by 144 publications

(91 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…An ontology-based framework for software maintenance was developed by Kitchenham et al [24]. These authors developed the ontology for four reasons, consistent with the purpose of benchmarks:…”

Section: Strategies and Frameworkmentioning

confidence: 99%

See 1 more Smart Citation

Toward a framework for evaluating extreme programming

Williams¹,

Krebs²,

Layman³

et al. 2004

"8th Internation Conference on Empirical Assessment in Software Engineering (EASE 2004)" Workshop - 26th International Conferen

View full text Add to dashboard Cite

show abstract

Section: Strategies and Frameworkmentioning

confidence: 99%

“…As such, benchmarks in the form of ontology-based frameworks 1 have been published in software engineering [16,21,24,43]. The purpose of these frameworks is to reveal factors which might influence when and how a certain process/practice is beneficial compared with other processes/practices.…”

Section: Introductionmentioning

confidence: 99%

Toward a framework for evaluating extreme programming

Williams¹,

Krebs²,

Layman³

et al. 2004

"8th Internation Conference on Empirical Assessment in Software Engineering (EASE 2004)" Workshop - 26th International Conferen

View full text Add to dashboard Cite

show abstract

“…Kitchenham et al [49] propose an ontology to identify a number of factors that influence maintenance. The ontology has Modification Activity as an entity, specialized by Enhancement and Correction entities.…”

Section: Change Classificationmentioning

confidence: 99%

“…The ontology has Modification Activity as an entity, specialized by Enhancement and Correction entities. In Corrections, a defect such a discrepancy between the required behavior of a product/application and the observed behavior is corrected [49]. Enhancements might be changes in the implementation or they might be requirements changes which are adding new requirements or changing existing requirements.…”

Section: Change Classificationmentioning

confidence: 99%

See 1 more Smart Citation

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Following the evolution of the business needs, the requirements of software systems change continuously and new requirements emerge frequently. Requirements documents are often textual artifacts with structure not explicitly given. When a change in a requirements document is introduced, the requirements engineer may have to manually analyze all the requirements for a single change. This may result in neglecting the actual impact of a change. Consequently, the cost of implementing a change may become several times higher than expected. Objective: In this paper, we aim at improving change impact analysis in requirements by using formal semantics of requirements relations and requirements change types. Method: In our previous work we present a requirements metamodel with commonly used requirements relation types and their semantics formalized in first-order logic. In this paper the classification of requirements changes based on structure of a textual requirement is provided with formal semantics. The formalization of requirements relations and changes is used for propagating proposed changes and consistency checking of proposed changes in requirements models. The tool support for change impact analysis in requirements models is an extension of our Tool for Requirements Inferencing and Consistency Checking (TRIC). Results: The described approach for change impact analysis helps in the elimination of some false positive impacts in change propagation, and enables consistency checking of changes. Conclusion: We illustrate our approach in an example which shows that the formal semantics of requirements relations and change classification enables change alternatives to be proposed semi-automatically, the reduction of some false positive impacts and contradicting changes in requirements to be determined.

show abstract

Kitchenham, Barbara

2002

Encyclopedia of Software Engineering

View full text Add to dashboard Cite

Towards an ontology of software maintenance

Cited by 144 publications

References 9 publications

Toward a framework for evaluating extreme programming

Toward a framework for evaluating extreme programming

Change impact analysis for requirements: A metamodeling approach

Kitchenham, Barbara

Contact Info

Product

Resources

About