1995
DOI: 10.1007/3-540-59293-8_187
|View full text |Cite
|
Sign up to set email alerts
|

Formal methods and social context in software development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

1996
1996
2002
2002

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(12 citation statements)
references
References 18 publications
0
12
0
Order By: Relevance
“…This feature is essential in order to encourage experimentation with the new generation of tools, which often lack acceptance by practitioners because of their high complexities. Our approach exactly meets the description expressed by Goguen and Luqi in [6] for the emerging paradigm of Domain Specific Formal Methods, which requires formal methods to be introduced also on a large or huge grain level, to support programming with whole subroutines, modules and tools as elementary building blocks. This is precisely what METAFrame is designed for.…”
Section: Perspectivesmentioning
confidence: 65%
“…This feature is essential in order to encourage experimentation with the new generation of tools, which often lack acceptance by practitioners because of their high complexities. Our approach exactly meets the description expressed by Goguen and Luqi in [6] for the emerging paradigm of Domain Specific Formal Methods, which requires formal methods to be introduced also on a large or huge grain level, to support programming with whole subroutines, modules and tools as elementary building blocks. This is precisely what METAFrame is designed for.…”
Section: Perspectivesmentioning
confidence: 65%
“…However, while good practice reduces incompleteness, inconsistency and instability in requirements specifications, is neither feasible nor desirable to eliminate these characteristics altogether [23,24]. For example, a specification could easily be dominated and obscured by axioms defining environmental characteristics to be preserved when a new software system is installed, or axioms defining the social context [13] in which requirements are situated.…”
Section: Formal Specification Of Requirementsmentioning
confidence: 99%
“…The scale of modules can vary enormously. In particular, existing subsystems can be very large indeed [13], and a design may capture only parts of their interfaces.…”
Section: Designs Requirements and Programsmentioning
confidence: 99%
“…Formal models would provide powerful formal engines that support automatic reasoning about important properties, but the supplied VD interfaces lack domain specificity [17,27]. The many proposals, which tried to combine graphical notations with formal models, fail in addressing flexibility, i.e., the real problem: They freeze a fixed semantics and over-constrain the VD notation ( [ 16,24]).…”
Section: Introductionmentioning
confidence: 99%