Maintaining consistency under changes to formal specifications

Ross, Kelvin; Lindsay, Peter

doi:10.1007/bfb0024667

Cited by 9 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Section 4.7 of [11]). Fine-grained process models can give better support for change management, for example, by limiting the extent to which changes need to be percolated through a design [15]. In principle, the level of granularity is determined simply by what basic tools are available.…”

Section: Discussionmentioning

confidence: 99%

“…For example, in a programming environment the objects might be individual program statements, and there might be consistency checks such as ensuring that correct syntax has been used, and completeness checks such as checking that all variables have been initialized, all paths have been tested, and so on. In a software engineering environment the objects might be coarse-grained objects such as software development documents, or finer-grained objects such as individual definitions in a specification [15].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Formal Basis for Modelling Process and Task Management Aspects of User Interface Design

Lindsay

1996

Electronic Workshops in Computing

Self Cite

View full text Add to dashboard Cite

This paper presents a method for formally specifying and reasoning about process models for interactive systems. The method addresses two important aspects of user interface design: controlled but flexible access to functionality; and provision of useful task management information, such as indicating what progress has been made towards achieving goals and what remains to be done. The method is well suited to "data intensive" applications in which the system is being used to manage complex "configurations" of interconnected objects, and for which task goals can be expressed in terms of properties of the underlying configuration of objects. The method includes proof obligations to check the accuracy of the task management information. The paper illustrates the method on a Theory Manager, which manages a store of theorems and proofs; the store has complex consistency and completeness requirements. BCS-FACS Workshop on Formal Aspects of The Human Computer Interface A Formal Basis for Modelling Process and Task Management Aspects of User Interface Design

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

A Formal Basis for Modelling Process and Task Management Aspects of User Interface Design

Lindsay

1996

Electronic Workshops in Computing

Self Cite

View full text Add to dashboard Cite

show abstract

“…Our approach is similar to earlier work done on the mural system for checking the consistency of proofs when theories change [15]. Proof attempts were represented explicitly as natural deduction style proofs that could be traversed and checked for consistency when their proof obligations changed.…”

Section: Related Workmentioning

confidence: 99%

Supporting Proof in a Reactive Development Environment

Mehta

2007

Fifth IEEE International Conference on Software Engineering and Formal Methods (SEFM 2007)

View full text Add to dashboard Cite

“…Whether an inference rule is discharged as a theorem is provided as a primitive relationship. In other work the definition of this relationship and its consequent properties have been examined in detail [12]. However for brevity, this work has been simplified to a single primitive relationship.…”

Section: Relationshipsmentioning

confidence: 99%

Models for Configuration Management of Refinement Calculus Developments

Ross

1996

Electronic Workshops in Computing

Self Cite

View full text Add to dashboard Cite

This paper considers aspects of Software Configuration Management (SCM) in its role of supporting configurations that arise in development of software using the refinement calculus. From an SCM perspective, the primary difference between formal development methods, such as the refinement calculus, and traditional development methods is the nature of relationships within the development configuration. The relationships are very precise; occur at much finer levels of granularity; and evolve through an iterative/intertwined development process. In analysing support for the refinement calculus, this paper proposes a configuration model which defines the relationships that occur during development and how these relationships evolve as development activities are applied and modifications are made. The configuration model enables properties regarding relationships to be formally inferred. The results of these inferences may be used in developing automated support for refinement calculus developments, such as change impact analysis, traceability and remanufacturing services. Models for Configuration Management of Refinement Calculus Developments In Section 7 we consider properties that are consequences of the configuration model and how they convey useful information relating to development, such as conformance to the methodology and change impact analysis. Section 8 examines how the configuration model can provide information for constructing SCM support for the refinement calculus. Finally in section 9 we present conclusions, indicate where simplifications have been incorporated into the model and review related work. Within the paper a particular presentation style has been adopted. The definitions for the configuration models are displayed in figures enclosed in oval boxes. Other supporting figures are displayed in shadowed boxes. The notation includes atomic type and primitive relationship names being underlined; activity names are capitalised; and assumption and inference rule names are shown in typed font. 2 Software Configuration Management Software Configuration Management (SCM) is the means through which the integrity and traceability of the software system are recorded, communicated and controlled during both development and maintenance [15]. SCM is concerned with the management of configurations of components which collectively represent the software development, including management of the relationships between components and management of the persons and processes involved in the development of components. 2.1 SCM Services SCM offers a wide range of services for managing software development configurations as they evolve. These services include: Repository: Efficient storage and retrieval of versions of configuration components as well as relationships between components. For example, a repository for refinement could offer storage of the versions of development components (e.g. program fragments and proofs) and relationships between component (e.g. modification between versions, refinement between program ...

show abstract

Maintaining consistency under changes to formal specifications

Cited by 9 publications

References 2 publications

A Formal Basis for Modelling Process and Task Management Aspects of User Interface Design

A Formal Basis for Modelling Process and Task Management Aspects of User Interface Design

Supporting Proof in a Reactive Development Environment

Models for Configuration Management of Refinement Calculus Developments

Contact Info

Product

Resources

About