Auflistung nach Schlagwort "consistency"
1 - 3 von 3
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragChecking Consistency and Completeness of Software Systems(Software Engineering and Software Management 2019, 2019) Sneed, HarryThe 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.
- KonferenzbeitragOOLH: A formal framework for specifying system requirements(SIGSAND-EUROPE 2008: Proceedings of the Third AIS SIGSAND European Symposium on Analysis, Design, Use and Societal Impact of Information Systems, 2008) Hon, Yuen Man; Gayen, Jan-Tecker; Ehrich, Hans-DieterMost of the system requirements are written in natural language. It is not easy for the system development team to understand this document unambiguously without domain specific knowledge. It is difficult to check the correctness of these requirements. A formal framework called Object Oriented Lastenheft (German for re- quirements specification) (OOLH) is proposed as a solution to handle these problems 1. This framework provides well-defined mathematical concepts to formulate system requirements. These well-formalized system requirements can be analyzed and understood easier and their consistency can be checked based on the mathematical concepts. A tool, called OOLH tool, is implemented to support analyzing, verifying and checking consistency of formulas in OOLH. Logical formulas can be transformed into decision tables and truth tables. The expected behavior or a design can be specified in decision tables in this tool, such that the correctness of requirements can be verified.
- KonferenzbeitragA Summary of ReVision: History-based Model Repair Recommendations(Software Engineering 2023, 2023) Ohrndorf, Manuel; Pietsch, Christopher; Kelter, Udo; Grunske, Lars; Kehrer, TimoThis work reports recent research results on history-based model repair recommendations in Model-Driven Engineering (MDE), originally published in Reference [Oh21]. Models in MDE are primary development artifacts that are heavily edited in all software development stages and can become temporarily inconsistent during editing. Model repair tools can support developers by proposing a list of the most promising repairs. Such repair recommendations will only be accepted in practice if the generated proposals are plausible and understandable and the set as a whole is manageable. Our interactive repair tool ReVision [Oh18], aims at generating repair proposals for inconsistencies introduced by past incomplete edit steps. Such an incomplete edit step is either undone or extended to the full execution of a consistency-preserving edit operation. We evaluate our approach using histories of real-world models from popular open-source modeling projects. Our experimental results confirm our hypothesis that most of the inconsistencies can be resolved by complementing incomplete edits. In fact, 92.2% of the proposed complementations could be observed in the model history.