J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development, " Proc. TAPSOFT'95, Aarhus (DK), May 1995, LNCS N.915, pp.62-81.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....according to specific application profiles. 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. In our ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development, " Proc. TAPSOFT'95, Aarhus (DK), May 1995, LNCS N.915, pp.62-81.

....be widely emphasized and demonstrated, and the industrial world. There are some reasons, perhaps mistakes that make f.m. refused (see e.g. 45] for practical use: ffl most of them are only formal; it is not taken into account the environment (the kind of user) by which they should be used. In [27]: Formal notations are alien to most programmers who have little training and skill in mathematics. Conversely, Some advocates of f.m. take a very dogmatic position, that absolutely everything must be proved, to the highest possible degree of mathematical rigor ffl formalisms cannot ....

....starts with the determination of the so called problem context or problem frame ( 25] Furthermore, many times this domain is informal and it is described in a very abstract way. So, how to capture requirements is a very delicate point, on which both people working on formal methods ([27], 25] 26] and people working on s.e. also using the word requirement engineering [8] are debating. In [26] Functional) requirements are located in the environment, which is distinguished from the machine to be built. A requirement is a condition over phenomena of the environment. A ....

J.Goguen and Luqi. Formal methods and social context in software development. In M.I.Schwartzbach P.D. Mosses, M. Nielsen, editor, Proc. of TAPSOFT '95, pages 62--81, Berlin, 1995. LNCS 915, Springer Verlag.

....sceptically by industry. Instead, one can view formal analysis (or propertychecking ) of systems as an advanced or more effective form of testing whose objective is not necessarily to have a strong assurance of correctness, but rather to eliminate more bugs, earlier in the design process [2]. At present, a developer wishing to incorporate verification capabilities into a CAD or CASE tool, or any application, will face a difficult choice between creating a verification engine from scratch and adapting parts of one or more existing tools. Developing a verification engine from scratch ....

J. A. Goguen and Luqi, Formal methods and social context in software development. Proceedings TAPSOFT'95, Lecture Notes in Computer Science 915. Springer-Verlag, pp. 62--81, 1995.

....sceptically by industry. Instead, one can view formal analysis (or propertychecking ) of systems as an advanced or more effective form of testing whose objective is not necessarily to have a strong assurance of correctness, but rather to eliminate more bugs, earlier in the design process [3]. At present, a developer wishing to incorporate verification capabilities into a CAD or CASE tool, or any application, will face a difficult choice between creating a verification engine from scratch and adapting parts of one or more existing tools. Developing a verification engine from scratch ....

J. A. Goguen and Luqi, Formal methods and social context in software development. Proceedings TAPSOFT'95, Lecture Notes in Computer Science 915. Springer-Verlag, pp. 62-- 81, 1995.

....telephony. It also includes observations about how this domain should be formalized, including critiques of some popular approaches. 1. Introduction In the evolution of formal methods for software engineering, the time has come to develop formal methods for particular application domains [10,24]. This paper concerns the domain of customer oriented telephony, i.e. software producing the externally observable behavior of voice telecommunications systems. Customer oriented telephony is worth the attention of industrial researchers and academicians alike, for the following three reasons: ....

J. A. Goguen and Luqi. Formal methods and social context in software development. In Proceedings of the Sixth International Conference on Theory and Practice of Software Development (TAPSOFT '95), pages 62-81. Springer Verlag LNCS 915, 1995.

.... provide a full PM language (PML) We are therefore investigating an integration of SLTL with an existing conventional PML, which aims at an eclectic multi paradigm approach for process modelling similar to SOCCA [10] Our approach exactly meets the demands recently expressed by Goguen and Luqi in [11] for the emerging paradigm of Domain Specific Formal Methods: the essence of their proposal is to use formal methods on a large or huge grain level rather than on elementary statements, thus to support programming with whole subroutines and modules as the elementary building blocks. This is ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development", (invited talk) 6th Int. Conf. on Theory and Practice of Software Development (TAPSOFT'95), Aarhus (Denmark), May 1995, LNCS N.915, pp.62-81.

....regarded sceptically by industry. Instead, one can view formal analysis (or propertychecking ) of systems as an advanced or more e ective form of testing whose objective is not necessarily to have a strong assurance of correctness, but rather to eliminate more bugs, earlier in the design process [10]. At present, a developer wishing to incorporate veri cation capabilities into a CAD or CASE tool, or any application, will face a dicult choice between Work funded by ESPRIT Framework IV Grant LTR 26241 creating a veri cation engine from scratch and adapting parts of one or more existing ....

J. A. Goguen and Luqi, Formal methods and social context in software development. Proceedings TAPSOFT'95, Lecture Notes in Computer Science 915. Springer-Verlag, pp. 62-81, 1995.

....it should obey, the context where the system is going to be used, etc. Unfortunately, requirements cannot be confined to the initial phase of the development of software systems nor they can be viewed as static expressions. An examination of the situated nature of requirements is given in [396, 400]. In a real project requirements go on throughout the project and are subject to change. Keeping track of requirements evolution, of how they affect the other phases of the system development, and of how they are considered and incorporated in the design, specification, and production of the ....

J. Goguen and Luqi. Formal Methods and Social Context in Software Development. In P. D. Mosses, M. Nielsen, and M. I. Schwartzbach, editors, TAPSOFT'95: Theory and Practice of Software Development. 6th International Joint Conference CAAP/FASE, pages 62--81. Springer LNCS 915, 1995. \Phi.

....and the pressure for marketable solutions and routine application has increased. But again, it seems that new technology can not be thought without the contributions from theoretical and conceptual work. The question is therefore anew what formal methods can do in the future. Goguen and Luqi in [18] began their talk with Formal methods have not been accepted to the extent for which many computing scientists hoped. Tony Hoare in his brilliant lecture at FME 96 [20] with the suggestive title How did software get so reliable without proof admits a large gap between theory and practice . ....

....and failures, but these have nearly always been attributable to inadequate analysis of requirements or inadequate management control. It has turned out that the world just does not suffer significantly from the kind of problem that our research was originally intended to solve. Goguen and Luqi in [18] take a completely different view: Failures of large software development projects are common today, due to the ever increasing size, complexity and cost of software systems. Although billions are spent each year on software in the US alone, many software systems do not actually satisfy users ....

[Article contains additional citation context not shown here]

J.A. Goguen and Luqi. Formal Methods and Social Context in Software Development. In P.D. Mosses, M. Nielsen, and M.I. Schwartzbach, editors, Proc. of TAPSOFT '95, number 915 in Lecture Notes in Computer Science, pages 62--81. Springer Verlag, Berlin, 1995.

....tools deal effectively with the complexity of the application. For the NewCoRe project, these requirements led to a decision in favor of SDL. The three identified requirements can be assumed to be general requirements for the applicability of formal methods and their tools in the industry. Goguen [37] lists five requirements for the success of domain specific tools: 1. a narrow, well defined, well understood problem domain is addressed 2. there is a community of users with potential financial resources who understand the domain 3. the tool has a graphical user interface that is intuitive to ....

J. Goguen and Luqi. Formal methods and social context in software development. In TAP-SOFT'95: 6th International Conference on Theory and Practice of Software Development, number 915 in Lecture Notes in Computer Science, pages 62--81. Springer-Verlag, May 1995.

..... 15 9 The Correct Granny s Freephone Service . 1 Motivation In his invited talk at TAPSOFT 95, Joseph Goguen claimed that practical success of formal methods is bound to a tool supported domain specific paradigm (cf. [GoLu95]) which he characterized as follows: 1. a narrow, well defined, well understood problem domain is addressed; there may already be a successful library for this domain, 2. there is a community of users who understand the domain, have good communication among themselves, and have potential ....

....single aspects of the environment. 6 The Metalevel Specification Language The practical success of a specification language depends on an appropriate choice of notation 5 , on the flexibility to allow loose specifications 6 , and, additionally, on the availability of adequate tool support ([GoLu95]) 5 I) Thou shalt choose an appropriate notation 6 II) Thou shalt formalize but not overformalize We use a natural language like macro language based on a linear time variant of Kozen s mu calculus [Koze83] which comes together with efficient verification tools based on model checking: ....

[Article contains additional citation context not shown here]

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development, " (invited talk) 6th Int. Conf. on Theory and Practice of Software Development (TAPSOFT'95), Aarhus (Denmark), May 1995, LNCS N.915, pp.62-81.

....loose description of the purposes it should meet. This will be demonstrated following a user session, where an optimized tool for the heterogeneous verification of a specification implementation relation is developed. Our approach exactly meets the demands recently expressed by Goguen and Luqi in [GoLu95] for the emerging paradigm of Domain Specific Formal Methods: 1. a narrow, well defined, well understood problem domain is addressed, for which a successful library may already exist, 2. there is a community of users who understand the domain, 3. the tool has a graphical user interface that is ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development, " (invited talk) 6th Int. Conf. on Theory and Practice of Software Development (TAPSOFT'95), Aarhus (Denmark), May 1995, LNCS N.915, pp.62-81.

....to do their job efficiently and to take advantage of powerful tools. To make the use of formal approaches more appealing to software designers and testers, it is beneficial to encapsulate formal methods concepts and or algorithms: users do not have to know how it works, or even that it is there [5]. By using the approach advocated in this paper several important steps in the testing process, namely the source code annotation, the generation of test oracles, the test trace collection and test trace analysis can be automated and hidden from the service designer and tester. We informally ....

J. Goguen and Luqi. Formal methods and social context in software development. In TAP-SOFT'95: 6th International Conference on Theory and Practice of Software Development, number 915 in Lecture Notes in Computer Science, pages 62--81. Springer-Verlag, May 1995.

....prototyping facility. One should note here that the number of individual algorithms, many of which can be automatically generated (see[9] may, like in the CATS case, grow very large. 3 Evaluation and Perspectives Our approach exactly meets the demands recently expressed by Goguen and Luqi in [1] for the emerging paradigm of Domain Specific Formal Methods: the essence of their proposal is to use formal methods on a large or huge grain level rather than on elementary statements, thus to support the programming with whole subroutines and modules as the elementary building blocks. This is ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development," (inv. talk) TAPSOFT'95, Aarhus (DK), May 1995, LNCS N.915, pp.62-81.

....to do their job efficiently and to take advantage of powerful tools. To make the use of formal approaches more appealing to software designers and testers, it is beneficial to encapsulate formal methods concepts and or algorithms: users do not have to know how it works, or even that it is there (Goguen Luqi 1995). By using the approach advocated in this paper several important steps in the testing process, namely the source code annotation, the generation of test oracles, the test trace collection and test trace analysis can be automated and hidden from the service designer and tester. We informally ....

Goguen, J. & Luqi (1995), Formal methods and social context in software development, in `TAP-SOFT'95: 6th International Conference on Theory and Practice of Software Development', number 915 in `Lecture Notes in Computer Science', Springer-Verlag, pp. 62--81.

....X OPEN Company Ltd. 5 Bavarian Research Institute for Knowledge Based Systems Hardware Software codesign, where the integration of heterogeneous domains is a key point. 8 Experience and Perspectives The presented approach exactly meets the demands recently expressed by Goguen and Luqi in [GoLu95] for the emerging paradigm of Domain Specific Formal Methods: The essence of their proposal is to use formal methods on a large or huge grain level rather than on elementary statements, thus to support the programming with whole subroutines and modules as the elementary building blocks. This is ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development, " (invited talk) 6th Int. Conf. on Theory and Practice of Software Development (TAPSOFT'95), Aarhus (Denmark), May 1995, LNCS N.915, pp.62-81.

....according to specific application profiles. 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 [GoLu95] 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. In our ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development, " (invited talk) 6th Int. Conf. on Theory and Practice of Software Development (TAPSOFT'95), Aarhus (Denmark), May 1995, LNCS N.915, pp.62-81.

....can at best reflect a snapshot of the client s needs. This suggests that the picture we present here needs to be augmented to accommodate changes in requirements, and that mechanisms are required to ensure that code (and proofs of correctness) keep in step with changes in requirements, cf. GL 95] The problem of writing the original requirements specification and ensuring that it is an accurate reflection of needs is the topic of requirements engineering [Dav 90] For some work on formal requirements analysis, see [RAHL 94] Li 94] and [AR 95] As suggested in the previous section, a ....

J. Goguen and Luqi. Formal methods and social context in software development. Proc. 6th Joint Conf. on Theory and Practice of Software Development, TAPSOFT'95, Aarhus. Springer LNCS 915, 62--81 (1995).

....spreadsheet are represented as sequences of zeroes and ones, and adding columns is achieved by manipulating these sequences in structured ways. To design and build effective software systems, the software engineer must 1 master both the technical and the social aspects of the relevant information [10]. Large complex software systems fail more often than seems to be recognised, and experience suggests that many of these failures are due to a mismatch between the social and technical aspects of a supposed solution, i.e. due to the tension between information as situated and as structured ....

Joseph Goguen and Luqi. Formal methods and social context in software development. In Peter Mosses, Mogens Nielsen, and Michael Schwartzbach, editors, Proceedings, Sixth International Joint Conference on Theory and Practice of Software Development (TAPSOFT 95), pages 62--81. Springer, 1995. Lecture Notes in Computer Science, Volume 915.

....already provided by lileanna, with its powerful module composition facilities, which are now being applied to avionics software, in particular, to digital signal processing modules for navigation, etc. It would also be interesting to further explore our ideas on hyperrequirements and social issues [15]. ....

Joseph Goguen and Luqi. Formal methods and social context in software development. In Peter Mosses, Mogens Nielsen, and Michael Schwartzbach, editors, Proceedings, Sixth International Joint Conference on Theory and Practiceof Software Development (TAPSOFT 95), pages 62--81. Springer, 1995. Lecture Notes in Computer Science, Volume 915.

....Programming is a skill, and to be really good at it can take years of hard work. One must learn how to use tools like configuration managers and debuggers. For large programs, one must learn how to work in a team; and for really large projects, management and other social issues are often dominant [7]. One must learn discipline and organisation, and how to read and write documentation. One must keep learning new languages, tools, concepts, algorithms, and skills; sometimes one must even invent these things. Software Engineering is a difficult area requiring diverse skills and knowledge, and ....

....and knowledge, and the material taught in our course provides little help with those aspects that are not formal and cannot be formalized. It is unhealthy to confuse a formal notation with a formal method. A method should say how to do something, whereas a notation allows one to say something [7]. Thus, OBJ is only a notation, but using it as described in our course and book gives a method for proving properties of imperative programs. This method is not completely mechanical, because some of the problems involved are uncomputable (such as finding loop invariants) although of course, the ....

Joseph Goguen and Luqi. Formal methods and social context in software development. In Peter Mosses, Mogens Nielsen, and Michael Schwartzbach, editors, Proceedings, Sixth International Joint Conference on Theory and Practice of Software Development, pages 62--81. SpringerVerlag Lecture Notes in Computer Science 915, 1995.

.... fur Programmiersysteme Universitat Passau D 94030 Passau (Germany) fsteffen,tiziana,classen,deepthoug fmi.uni passau.de 1 Motivation In his invited talk at TAPSOFT 95, Joseph Goguen claimed that practical success of formal methods is bound to a tool supported domain specific paradigm (cf. [1]) which he characterized as follows: 1. a narrow, well defined, well understood problem domain is addressed; there may already be a successful library for this domain, 2. there is a community of users who understand the domain, have good communication among themselves, and have potential ....

....has a much wider application profile, as we illustrate in Sec. 3 by means of a completely different domain: the construction of intelligent network (IN) telecommunication services. 1 Other systems fitting this description are, e.g. CAPS, ControlH and MetaH, AMPHION, Panel, and DSDL (see [1]) 2 The MetaFrame Environment IN META Frame CompGen CUTIP StatEval Hypertext Tool Data Management System Graphical User Interface Design Data Data Project Management Tool Management System Design Meta Data Repository Tools Repository Tool Meta Data Repository Synthesis Component CATS ....

J.A. Goguen, Luqi: "Formal Methods and Social Context in Software Development," (invited talk) 6th Int. Conf. on Theory and Practice of Software Development (TAPSOFT '95), Aarhus (Denmark), May 1995, LNCS N.915, pp.62-81.

....Since that paper was written, a major computer company has defaulted on an 8 billion dollar contract to build the next generation U.S. air traffic control system. In many such cases, problems with requirements, that is, customer needs, have been implicated as a major source of difficulty. See [16, 18, 22] for discussions of the importance of requirements in developing systems, and of social factors in requirements. An adequate theory of information would have to take account of social context, including how information is produced and used, rather than merely how it is represented; that is, it ....

....open; that is, this list of qualities applies to itself. These qualities can be applied in many ways. For example, they lead to some basic limitations of formalization. Because any formalization is information, it must be emergent, contingent, local, open and vague; for further discussion, see [16, 22]. We can also apply the list to obtain qualities of category systems, signs, interpretations, texts, etc. We can also use the qualities of information to understand why it is not possible to completely formalize requirements: it is because they cannot be fully separated from their social context. ....

Joseph Goguen and Luqi. Formal methods and social context in software development. In Peter Mosses, Mogens Nielsen, and Michael Schwartzbach, editors, Proceedings, Sixth International Joint Conference on Theory and Practice of Software Development (TAPSOFT 95), pages 62--81. Springer, 1995. Lecture Notes in Computer Science, Volume 915.

....The social situatedness of information means that to some degree, it is irreducibly informal. However, there are some advantages to informality and situatedness for requirements engineering, including greater flexibility and efficiency. This paper is an overview, drawn mainly from [6, 7] and [8]. 2 Understanding Requirements Requirements are properties that a system should have in order to succeed in the environment where it will be used. This definition (from [5] refers to a system s context of use, and thus to the social as well as the technical. Much of the information needed for ....

....for first order logic can be difficult to work with. Formal notations can also capture higher levels of meaning, e.g. they can express security requirements, but such notations are even more difficult. The orderliness of social life (due to accountability) and the Henley Regatta example in [8] suggest that social interaction might be formalizable; but there are limits to how successful any such formalization can be. In particular, it will not be easy to formalize domains where there are many ad hoc special cases, or where much of the knowledge is tacit. Formalization will be more ....

[Article contains additional citation context not shown here]

Joseph Goguen and Luqi. Formal methods and social context in software development. In Mosses, Nielsen and Schwartzbach, editors, TAPSOFT 95, 62--81. Springer, 1995. LNCS 915.

....on change, which is inevitable and unending in software development. Moreover, since large complex systems are inevitably embedded in complex evolving social contexts, they will necessarily co evolve with those contexts, in the sense that each will affect the evolution of the other. See [10, 12] for further discussion of evolution and social context. The ubiquity of change motivates the use of iterative lifecycle processes, and especially prototyping, i.e. quickly building and evaluating a series of prototypes, which are concrete executable models of selected aspects of a system [21] ....

....in [22] this structure can be applied to give a model for evolving module graphs. Work on capturing domain knowledge has used methods from sociology, particularly ethnomethodology and its disciplines of conversastion and interaction analyses. Further information on this research may be found in [9, 10, 12]. We are also developing a system called toor to support tracing dependencies among evolving objects, and in particular, to show how decisions are grounded in prior objects [23] This approach, called hyperrequirements, builds on parameterized programming and hyperprogrammming, and is intended to ....

Joseph Goguen and Luqi. Formal methods and social context in software development. In Mosses, Nielsen, and Schwartzbach, editors, Proceedings, TAPSOFT 95, pages 62--81. Springer, 1995. LNCS 915.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC