Method integration and support for distributed software development: An overview

Kramer, Jeff; Finkelsteiin, Anthony; Nuseibeh, Bashar

doi:10.1007/bfb0030524

Cited by 3 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Finkelstein and others' ViewPoints [48] allow multiple forms of partial specification; each ViewPoint might be recorded in a different notation. Easterbrook and Nuseibeh [49] discuss how different ViewPoints are reconciled via consistency checking rules.…”

Section: Software Behavioural Viewsmentioning

confidence: 99%

See 1 more Smart Citation

Behavioural Views for Software Requirements Engineering

1999

View full text Add to dashboard Cite

This paper introduces the idea of a software behavioural view: intuitively, this is a complete description of the behaviour of the system observable from a specific point of view. We believe that a fully developed methodology based on views would significantly reduce the complexity of creating and understanding software requirements. In this paper we take the first steps towards such a methodology. We define a formal notation, Viewcharts, with a well-defined semantics based on Statecharts. Viewcharts gives a means for precisely describing views and their compositions. We show that Viewcharts reasonably capture the informal idea of a view by giving an example: a manufacturing control system. We show that Viewcharts have some advantages over Statecharts; in particular, Viewcharts add name space control to limit the scope of broadcast communication, solving a problem with Statecharts presented by Harel.

show abstract

Section: Software Behavioural Viewsmentioning

confidence: 99%

“…Finkelstein and others' Viewpoints [48] allow different views to be recorded in different notations. The scoping mechanism of Viewcharts is conceptually simpler but of more limited applicability than either of these approaches.…”

Section: Related Workmentioning

confidence: 99%

Behavioural Views for Software Requirements Engineering

1999

View full text Add to dashboard Cite

show abstract

“…However, this is rarely the case. Current attempts of integrating formalisms (Ambriola et al, 1997;Kramer et al, 1996) indicate that the transition from one formalism to another is a key element to the efficient application of formal methods. This has also been observed as part of our work (Droschl, 1999c).…”

Section: Proof Vs Testingmentioning

confidence: 99%

A Case Study on the Application of PVS to Requirements Analysis

Droschl¹

1999

AJIS

View full text Add to dashboard Cite

This paper presents the results of a formal methods case study in which the Prototype Verification System (PVS) has been used for requirements analysis of one module of a physical access control system. PVS is a tool for writing formal specifications and constructing proofs. Previously, the same requirements have been analyzed by means of testing supported by the IFAD Toolbox for VDM-SL. The capabilities of the two formal methods are compared.

show abstract

“…Interest in merging formal methods is growing [4,8,20,23,24,34,35]. Our work is closely related to [34] which deals with composing partial specifications, that are written in different specification languages.…”

Section: Related Workmentioning

confidence: 99%

“…In formal methods there is a variety of features [25] and tools [15]. From what has been said above, it should have become clear, that it is unreasonable to expect one single tool to be used for the whole of a formal development project [4,20,23,24,34,35]. It has been shown that not all formalisms are equally well suited for the various issues arising in projects applying formal methods.…”

Section: Why Vdm and Pvs ?mentioning

confidence: 99%

On the Integration of Formal Methods: Events and Scenarios in PVS and VDM

Droschl

1999

Electronic Workshops in Computing

View full text Add to dashboard Cite

Tool support is known to be one of the success factors in formal specification based analysis and -program development. This paper investigates tool support in the context of a case study where a wide range of tool features is required: For an access control, C++ code has to be developed based on the user's requirements expressed in natural language.The access control has been classified a mixed data-control problem. This paper discusses (1) why VDMTools and PVS have been selected and (2) how they can be used together. Another aspect is the use of VDM as a framework for modeling event based systems. In our approach to tool integration, two specifications are considered to share a common part. For the present application this part consists of the scenario of all possible events.

show abstract

Method integration and support for distributed software development: An overview

Cited by 3 publications

References 9 publications

Behavioural Views for Software Requirements Engineering

Behavioural Views for Software Requirements Engineering

A Case Study on the Application of PVS to Requirements Analysis

On the Integration of Formal Methods: Events and Scenarios in PVS and VDM

Contact Info

Product

Resources

About