Specification and Transformation of Programs: A Formal Approach to Software DevelopmentSpringer Science & Business Media, 2012. gada 6. dec. - 493 lappuses "Specification and transformation of programs" is short for a methodology of software development where, from a formal specification of a problem to be solved, programs correctly solving that problem are constructed by stepwise application of formal, semantics-preserving transformation rules. The approach considers programming as a formal activity. Consequently, it requires some mathematical maturity and, above all, the will to try something new. A somewhat experienced programmer or a third- or fourth-year student in computer science should be able to master most of this material - at least, this is the level I have aimed at. This book is primarily intended as a general introductory textbook on transformational methodology. As with any methodology, reading and understanding is necessary but not sufficient. Therefore, most of the chapters contain a set of exercises for practising as homework. Solutions to these exercises exist and can, in principle, be obtained at nominal cost from the author upon request on appropriate letterhead. In addition, the book also can be seen as a comprehensive account of the particular transformational methodology developed within the Munich CIP project. |
No grāmatas satura
11. lappuse
... basic rules ) ; the degree of automatization assumed for an implemented support system ( exclusively user - driven , semi - automatic , fully automatic ) . For further details on the different approaches to transformational programming ...
... basic rules ) ; the degree of automatization assumed for an implemented support system ( exclusively user - driven , semi - automatic , fully automatic ) . For further details on the different approaches to transformational programming ...
12. lappuse
... basic rules which , for practical purposes , may be extended at will by rules specifically tailored to particular problem domains [ Bauer et al . 79 ] . Basically , in CIP the development process is exclusively guided by the user , who ...
... basic rules which , for practical purposes , may be extended at will by rules specifically tailored to particular problem domains [ Bauer et al . 79 ] . Basically , in CIP the development process is exclusively guided by the user , who ...
13. lappuse
... basic philosophy of applicative programming is similar to that of logic programming . Here too , efficiency - oriented aspects of control are left to a suitable implementation , and the focus of interest is the essence of an algorithm .
... basic philosophy of applicative programming is similar to that of logic programming . Here too , efficiency - oriented aspects of control are left to a suitable implementation , and the focus of interest is the essence of an algorithm .
15. lappuse
... basic rules of chess also knows what “ attack ” means in this context : in order to not attack each other , two queens must not be placed in the same row ( rank ) , the same column ( file ) , or the same diagonal . Denoting positions on ...
... basic rules of chess also knows what “ attack ” means in this context : in order to not attack each other , two queens must not be placed in the same row ( rank ) , the same column ( file ) , or the same diagonal . Denoting positions on ...
20. lappuse
... Basic Notions In a more narrow sense , requirements engineering is also used to characterize the initial phase in the traditional life cycle model for software development . In [ IEEE 83 ] this phase is characterized as The period of ...
... Basic Notions In a more narrow sense , requirements engineering is also used to characterize the initial phase in the traditional life cycle model for software development . In [ IEEE 83 ] this phase is characterized as The period of ...
Saturs
1 | |
19 | |
Formal Problem Specification | 56 |
Basic Transformation Techniques | 149 |
From Descriptive Specifications to Operational Ones | 189 |
Modification of Applicative Programs | 263 |
Rearrangement of Statements | 339 |
4 | 345 |
Transformation of Data Structures | 352 |
3 | 359 |
4 | 381 |
6 | 398 |
Complete Examples | 404 |
References | 456 |
Index | 475 |
Citi izdevumi - Skatīt visu
Specification and Transformation of Programs: A Formal Approach to Software ... Helmut A. Partsch Ierobežota priekšskatīšana - 1990 |
Specification and Transformation of Programs: A Formal Approach to Software ... Helmut A. Partsch Ierobežota priekšskatīšana - 1990 |
Bieži izmantoti vārdi un frāzes
abstract algebraic types algorithm amount(firstt applicability conditions arbitrary arguments assertion axioms based on BOOL Bauer binary tree bintree buffer clist command constructs data structures data types defined definedness definition denotes derive directed graphs dummy E₁ elem element elsf embedding emptyq endoftype example expression false finite firstu folding formal specification funct f function function composition further given hib(a imperative program implementation input instantiation introduced isdef(b language lob(a mmap mode mset natmap natsequ natural numbers node nodemap nodesequ nodeset object kinds Obviously oldbal operations particular Partsch Petri net predicate preds(x priority queues problem program transformations properties respective restt Sect semantic sequ sequence simplification sort step strategy string subst Syntactic constraints t₁ t₂ tail recursion technique termstring transformation rules transition true tuple unfold unfold/fold universal quantification variant yields