# Software Engineering 2: Specification of Systems and Languages (Texts in Theoretical Computer Science. An EATCS Series)

# Software Engineering 2: Specification of Systems and Languages (Texts in Theoretical Computer Science. An EATCS Series)

Language: English

Pages: 780

ISBN: 3540211500

Format: PDF / Kindle (mobi) / ePub

The art, craft, discipline, logic, practice and science of developing large-scale software products needs a professional base. The textbooks in this three-volume set combine informal, engineeringly sound approaches with the rigor of formal, mathematics-based approaches.

This volume covers the basic principles and techniques of specifying systems and languages. It deals with modelling the semiotics (pragmatics, semantics and syntax of systems and languages), modelling spatial and simple temporal phenomena, and such specialized topics as modularity (incl. UML class diagrams), Petri nets, live sequence charts, statecharts, and temporal logics, including the duration calculus. Finally, the book presents techniques for interpreter and compiler development of functional, imperative, modular and parallel programming languages.

This book is targeted at late undergraduate to early graduate university students, and researchers of programming methodologies. Vol. 1 of this series is a prerequisite text.

On a Method of Multiprogramming (Monographs in Computer Science)

iPad All-in-One For Dummies (4th Edition)

The Computer and the Brain (3rd Edition) (The Silliman Memorial Lectures Series)

Machine Learning: Hands-On for Developers and Technical Professionals

c_expr e n d = / * same as: */ if b _ e x p r t h e n c_expr e l s e s k i p e n d if b _ e x p r _ l t h e n c _ e x p r _ l elsif b _ e x p r _ 2 t h e n c _ e x p r _ 2 elsif b _ e x p r _ 3 t h e n c _ e x p r _ 3 elsif b _ e x p r _ n t h e n c _ e x p r _ n e n d c a s e expr of c h o i c e _ p a t t e r n _ l —>• e x p r _ l , c h o i c e _ p a t t e r n _ 2 —>• e x p r _ 2 , c h o i c e _ p a t t e r n _ n _ o r _ w i l d _ c a r d —>• e x p r _ n end Operator/Operand Expressions We

and account names as well as money amounts, as needed. The bank state also records the bank's own profit (interest income) and fee (income) accounts. The bank charges the customer a fixed fee, say d : $, for certain transactions (open, close, statement and transfer), a fixed daily interest, say i : /, on negative accounts, and offers a fixed, lower yield, y : Y, on positive accounts. Thus the transactions also need to record the day on which a transaction is issued. We assume all such day

405-411,434,508]. When you study and apply theories of, for example, real-time, safetycritical, embedded systems, then you will need a deeper seriousness about time t h a n t h a t presented here! A more serious t r e a t m e n t of time is presented in Chap. 15. 5 . 1 . 3 "A-Series" a n d "B-Series" M o d e l s of T i m e Colloquially, in ordinary, everyday parlance, we think of time as a dense series of time points. We often illustrate time by a usually horizontal line with an arrow pointing

pairs of times or pairs of locations (in space) and yields truth when the pair of time points, respectively the pair of locations, are sufficiently close to one another, (b) Assume also a mathematical, i.e., a non-RSL, function V (and, if need be, another such function TV) which applies to arbitrary functions and yields their definition information that must be remembered 5.6 Exercises 141 sets (respectively their image, i.e., range, sets). Finally, recall the notion of Afunctions (Vol. 1,

are of pragmatic nature, and why they might not be formalisable? Exercise 6.2 User-Friendliness and Pragmatics. Try to find, from the literature, characterisations of the concept of user-friendly software (systems). Discuss which aspects of those characterisations are of pragmatic nature. The next exercises (Exercises 6.3-6.5) form a preamble for the subsequent design of STIL: a simply typed imperative language. Future exercises relate to the design of STIL and are as follows: • • • • • • • •