检索结果-内蒙古大学图书馆

Specifying and checking method call sequences of Java programs

SOFTWARE QUALITY JOURNAL 2007年第1期15卷 7-25页

作者： Cheon, Yoonsik Perumandla, Ashaveena Univ Texas Dept Comp Sci El Paso TX 79968 USA

In a pre and postcondition-style specification, it is difficult to specify the allowed sequences of method calls, referred to as protocols. The protocols are essential properties of reusable object-oriented classes and application frameworks, and the approaches based on the pre and postconditions, such as design by contracts (DBC) and formal behavioral interface specification languages (BISL), are being accepted as a practical and effective tool for describing precise interfaces of (reusable) program modules. We propose a simple extension to the Java Modeling Language (JML), a BISL for Java, to specify protocol properties in an intuitive and concise manner. The key idea of our approach is to separate protocol properties from functional properties written in pre and post-conditions and to specify them in a regular expression-like notation. The semantics of our extension is formally defined and provides a foundation for implementing runtime checks. Case studies have been performed to show the effectiveness our approach. We believe that our approach can be adopted by other BISLs.

关键词： method call sequence specification runtime checking assertion pre and postconditions programming by contract JML language

来源：评论

学校读者我要写书评

暂无评论

Specifying and checking method call sequences of Java programs

Specifying and checking method call sequences of Java progra...

引用

International Conference on Software Engineering Research and Practice (SERP'05)

作者： Cheon, Yoonsik Perumandla, Ashaveena Univ Texas Dept Comp Sci El Paso TX 79968 USA

关键词： method call sequence specification runtime checking assertion pre and postconditions programming by contract JML language

来源：评论

学校读者我要写书评

暂无评论

Design by contract to improve software vigilance

引用

IEEE TRANSACTIONS ON SOFTWARE ENGINEERING 2006年第8期32卷 571-586页

作者： Le Traon, Yves Baudry, Benoit Jezequel, Jean-Marc France Telecom R&D F-22307 Lannion France Univ Rennes 1 IRISA F-35042 Rennes France

Design by contract is a lightweight technique for embedding elements of formal specification ( such as invariants, pre and postconditions) into an object-oriented design. When contracts are made executable, they can play the role of embedded, online oracles. Executable contracts allow components to be responsive to erroneous states and, thus, may help in detecting and locating faults. In this paper, we define Vigilance as the degree to which a program is able to detect an erroneous state at runtime. Diagnosability represents the effort needed to locate a fault once it has been detected. In order to estimate the benefit of using Design by contract, we formalize both notions of Vigilance and Diagnosability as software quality measures. The main steps of measure elaboration are given, from informal definitions of the factors to be measured to the mathematical model of the measures. As is the standard in this domain, the parameters are then fixed through actual measures, based on a mutation analysis in our case. Several measures are presented that reveal and estimate the contribution of contracts to the overall quality of a system in terms of vigilance and diagnosability.

关键词： object-oriented design methods programming by contract diagnostics metrics

来源：评论

学校读者我要写书评

暂无评论

A framework for conceptual modeling in OOP

引用

JOURNAL OF THE FRANKLIN INSTITUTE-ENGINEERING AND APPLIED MATHEMATICS 2006年第4-5期343卷 532-544页

作者： Al-Ahmad, Walid New York Inst Technol Sch Engn & Technol Manama Bahrain

There are several language constructs and mechanisms that provide some sort of support for conceptual modeling in object-oriented programming: the Liskov substitution principle, the Meyer programming by contract, the Beta inner construct, interfaces in C# and Java, and the separation of subtype hierarchies from subclass hierarchies as in Timor and Sather. All these mechanisms and constructs are powerful and useful tools to enforce the conceptual modeling trait of the inheritance mechanism in object-oriented programming. Their purpose is to ensure semantic compatibility of classes related by an inheritance hierarchy. When applied independently, these mechanisms can lead to more correct inheritance hierarchies that are easy to understand, use, and extend. This article discusses the different mechanisms and studies the interaction between them. It investigates whether conceptual modeling can be satisfactorily achieved by using such tools. It will be shown that the interaction between these tools might lead to contradictions and might prevent legitimate inheritance hierarchies. This article proposes a framework for a conceptual modeling mechanism that will better support conceptual modeling at the language level. (C) 2006 The Franklin Institute. Published by Elsevier Ltd. All rights reserved.

关键词： programming by contract Liskov substitution principle inheritance conceptual modeling

来源：评论

学校读者我要写书评

暂无评论

How the design of JML accommodates both runtime assertion checking and formal verification

引用

SCIENCE OF COMPUTER programming 2005年第1-3期55卷 185-208页

作者： Leavens, GT Cheon, Y Clifton, C Ruby, C Cok, DR Iowa State Univ Dept Comp Sci Ames IA USA Univ Texas Dept Comp Sci El Paso TX 79968 USA Eastman Kodak Co Res & Dev Labs Rochester NY USA

Specifications that are used in detailed design and in the documentation of existing code are primarily written and read by programmers. However, most formal specification languages either make heavy use of symbolic mathematical operators, which discourages use by programmers, or limit assertions to expressions of the underlying programming language, which makes it difficult to write exact specifications. Moreover, using assertions that are expressions in the underlying programming language can cause problems both in runtime assertion checking and in formal verification, because such expressions can potentially contain side effects. The Java Modeling Language, JML, avoids these problems. It uses a side-effect free subset of Java's expressions to which are added a few mathematical operators (such as the quantifiers \forall and \exists). JML also hides mathematical abstractions, such as sets and sequences, within a library of Java classes. The goal is to allow JML to serve as a common notation for both formal verification and runtime assertion checking;this gives users the benefit of several tools without the cost of changing notations. (C) 2004 Elsevier B.V. All rights reserved.

关键词： specification languages runtime assertion checking formal methods program verification programming by contract Java language JML language

来源：评论

学校读者我要写书评

暂无评论

Constructing contracts: Making discrete mathematics relevant to beginning programmers

引用

Journal on Educational Resources in Computing 2005年第2期5卷 3–es页

作者： Timothy S. Gegg-Harrison Winona State University Winona MN

Although computer scientists understand the importance of discrete mathematics to the foundations of their field, computer science (CS) students do not always see the relevance. Thus, it is important to find a way to show students its relevance. The concept of program correctness is generally taught as an activity independent of the programming process, hence many CS students perceive it as unnecessary, and even irrelevant. The concept of contracts, on the other hand, is generally taught as an integral part of the programming process. Most CS students have little difficulty understanding the need to establish contracts via preconditions and postconditions. In order to improve teaching program correctness concepts, we implemented ProVIDE, an enhanced integrated development environment (IDE). ProVIDE assists student programmers in contract construction. Rather than asking for both a precondition and postcondition for each of the student's methods, ProVIDE asks the student to simply supply a postcondition. ProVIDE then helps the student construct the appropriate precondition by leading him or her through an axiomatic proof of the method's correctness. Thus, the proof of of the method's correctness is a side-effect of the student's need to construct an appropriate precondition.

关键词： Formal methods axiomatic semantics loop invariants program verification programming by contract programming tools weakest preconditions

来源：评论

学校读者我要写书评

暂无评论

How the design of JML accommodates both runtime assertion checking and formal verification

How the design of JML accommodates both runtime assertion ch...

引用

1st International Symposium on Formal Methods for Components and Objects

作者： Leavens, GT Cheon, Y Clifton, C Ruby, C Cok, DR Iowa State Univ Sci & Technol Dept Comp Sci Ames IA 50011 USA Eastman Kodak Co Res & Dev Labs Rochester NY 14650 USA

ISBN: (纸本)3540203036

Specifications that are used in detailed design and in the documentation of existing code are primarily written and read by programmers. However, most formal specification languages either make heavy use of symbolic mathematical operators, which discourages use by programmers, or limit assertions to expressions of the underlying programming language, which makes it difficult to write complete specifications. Moreover, using assertions that are expressions in the underlying programming language can cause problems both in runtime assertion checking and in formal verification, because such expressions can potentially contain side effects. The Java Modeling Language, JML, avoids these problems. It uses a side-effect free subset of Java's expressions to which are added a few mathematical operators (such as the quantifiers \forall and \exists). JML also hides mathematical abstractions, such as sets and sequences, within a library of Java classes. The goal is to allow JML to serve as a common notation for both formal verification and runtime assertion checking;this gives users the benefit of several tools without the cost of changing notations.

关键词： Formal methods Java language JML language Program verification programming by contract Runtime assertion checking Specification languages

来源：评论

学校读者我要写书评

暂无评论

Black-box testing using flowgraphs: an experimental assessment of effectiveness and automation potential

引用

Software Testing, Verification and Reliability 2001年第4期10卷

作者： Stephen H. Edwards Department of Computer Science Virginia Tech 660 McBryde Hall Blacksburg VA 24061–0106 U.S.A.

A black-box testing strategy based on Zweben et al.'s specification-based test data adequacy criteria is explored. The approach focuses on generating a flowgraph from a component's specification and applying analogues of white-box strategies to it. An experimental assessment of the fault-detecting ability of test sets generated using this approach was performed for three of Zweben et al.'s criteria using mutation analysis. By using precondition, postcondition and invariant checking wrappers around the component under test, fault detection ratios competitive with white-box techniques were achieved. Experience with a prototype test set generator used in the experiment suggests that practical automation may be feasible. Copyright © 2000 John Wiley & Sons, Ltd.

关键词： automatic testing object-oriented testing test data adequacy formal specification programming by contract interface violation detection self-checking software

来源：评论

学校读者我要写书评

暂无评论

programming by contract

引用

COMPUTER 1996年第3期29卷 109-111页

作者： McKim, JC Dept. of Comput. & Inf. Sci. Hartford Graduate Center CT USA

Why can't software be more like hardware? has been the software engineer'slament for nearly as long as there have been large software systems. In particular, why isn't therea software components industry to rival the existing hardware components industry? Hardwarecomponents come with the following attributes: an interface that hides detail that would onlyconfuse or at least distract me; an unambiguous interface specification written in a language I canunderstand (in the case of the integrated circuit, this may be a fairly complex language, but it'sone I expect to learn if I'm going to work with that hardware); a guarantee-the component has beentested and/or validated against its specification. All three items-especially the last one-arenotably lacking for software components. Indeed, software tends to come with an antiguarantee,otherwise known as a disclaimer. All of the above points rely on a rigorous specification of thehardware component's interface. In a nutshell, programming by contract is about providing just suchspecifications for software components (that is, classes), and it provides the best hope of a basisfor a true software component industry. The discussion focuses on object oriented software.

关键词： Economics Object Oriented programming contracts Formal Specification User Interfaces DP Industry Object Oriented Software programming by contract Large Software Systems Software Components Industry Hardware Components Industry Interface Unambiguous Interface Specification Guarantee Software Components Disclaimer Rigorous Specification Classes contracts Computer Industry Application Software

来源：评论

学校读者我要写书评

暂无评论

建议与咨询留下您的常用邮箱和电话号码，以便我们向您反馈解决方案和替代方法

时间限定

文献类型

馆藏选择

核心期刊

语言

文献类型

帮助

文字说明：

检索规则说明：

检索范例：

分类表

所选分类

限定检索结果

文献类型

馆藏范围

日期分布

学科分类号

主题

机构

作者

语言

请选择保存的检索档案：

请选择收藏分类：

通借通还

建议与咨询 留下您的常用邮箱和电话号码，以便我们向您反馈解决方案和替代方法

时间限定

文献类型

馆藏选择

核心期刊

语言

文献类型

帮助

文字说明：

检索规则说明：

检索范例：

分类表

所选分类

限定检索结果

文献类型

馆藏范围

日期分布

学科分类号

主题

机构

作者

语言

请选择保存的检索档案： 新增检索档案 确定 取消

请选择收藏分类： 新增自定义分类 确定 取消

通借通还

建议与咨询留下您的常用邮箱和电话号码，以便我们向您反馈解决方案和替代方法

请选择保存的检索档案：

请选择收藏分类：