1995
DOI: 10.1142/s021819409500006x
|View full text |Cite
|
Sign up to set email alerts
|

How to Combine Nonmonotonic Logic and Rapid Prototyping to Help Maintain Software

Abstract: This paper explores the possibility of automated support for detecting inconsistencies in software systems and requirements. The inconsistencies are introduced when the environment of the software system changes. We refer to the software environment as its context. We review the recent research progress on nonmonotonic logics, pointing out the significance of these results to software maintenance. We explain how a practical implementation of such logics can be obtained via a simple extension to logic programmi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
6
0

Year Published

1999
1999
2004
2004

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 15 publications
(6 citation statements)
references
References 0 publications
0
6
0
Order By: Relevance
“…For example, in the logic programming realm, the use of extra-logical operators, embedded in the syntax of the language, are common, like the use of not operator in some implementations of Prolog. Similar attempts are reported in the software engineering domain [30], whereas in [6] the authors use techniques from Answer Set Programming (ASP), which allow to draw conclusions based on the lack of evidence of the contrary. Their approach augments the semantics of SW languages' constructs, in particular that of the DAML daml:subClassOf, with ASP programs to be fed into an ASP solver in order to allow drawn, default inferences to be dropped if opposite knowledge is found in the knowledge source.…”
Section: Knowledge Representation and Reasoning On The Semantic Webmentioning
confidence: 95%
“…For example, in the logic programming realm, the use of extra-logical operators, embedded in the syntax of the language, are common, like the use of not operator in some implementations of Prolog. Similar attempts are reported in the software engineering domain [30], whereas in [6] the authors use techniques from Answer Set Programming (ASP), which allow to draw conclusions based on the lack of evidence of the contrary. Their approach augments the semantics of SW languages' constructs, in particular that of the DAML daml:subClassOf, with ASP programs to be fed into an ASP solver in order to allow drawn, default inferences to be dropped if opposite knowledge is found in the knowledge source.…”
Section: Knowledge Representation and Reasoning On The Semantic Webmentioning
confidence: 95%
“…The use of default rules has been proposed for the maintenance of software 6,13 in general, and requirements engineering 3,20,21 in particular. When the requirements of a software product are collected, it is usual that potential stakeholders have conflicting requirements for the system to be developed.…”
Section: Introductionmentioning
confidence: 99%
“…Moreover default reasoning can be used to represent and reason with conflicting knowledge without being faced with the trivialization problems of first order logic (where any conclusion can be drawn from an inconsistent knowledge base). These features have led to the use of default reasoning in a variety of applications including requirements and software engineering (Luqi and Cooke, 1995;Zowghi and Offen, 1997;Antoniou, 1998).…”
Section: Introductionmentioning
confidence: 99%