Patterns for b: bridging formal and informal development

Authors:
Edward Chan;Ken Robinson;Brett Welch
Affiliations:
School of Computer Science & Engineering, The University of New South Wales, Australia;School of Computer Science & Engineering, The University of New South Wales, Australia;School of Computer Science & Engineering, The University of New South Wales, Australia
Venue:
B'07 Proceedings of the 7th international conference on Formal Specification and Development in B
Year:
2007

Citing 3
Cited 2

Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
UML-B: Formal modeling and design aided by UML

ACM Transactions on Software Engineering and Methodology (TOSEM)
Reuse of specification patterns with the B method

ZB'03 Proceedings of the 3rd international conference on Formal specification and development in Z and B

Event-B Patterns for Specifying Fault-Tolerance in Multi-agent Interaction

Methods, Models and Tools for Fault Tolerance
Documenting the Progress of the System Development

Methods, Models and Tools for Fault Tolerance

Quantified Score

Hi-index	0.00

Visualization

Abstract

Patterns capture the shape of particular specifications, providing starting points for developers. The most well known design patterns in software are those of the Gang of Four (GoF), Gamma, Helm, Johnson & Vlissides[4], who have provided a set of patterns for Object-Oriented development. Starting with these patterns as a motivation, this paper discusses various issues concerning the concept of patterns for the B Method (B) and explores a number of patterns that could be used with B. The paper presents a number of case studies to illustrate use of the patterns, and discusses future exploration of design patterns for B. A motivation for the development of patterns for B is to enable reuse and also to make B more accessible to developers from the more informal side of software development.