7.4 Process Definitions
7.4.8 Sink Processes
Signature
102. Thejoinprocess is indexed by the unique identifier of the sink unit and evolves around a sink state jo where the sink unitu=mkSi(si).
103. It accepts input (i.e., fluids) on one channel uu[f,uid Π(u)] where f is the unique identifier of the only source unit of the sink.
104. It accepts inputs (sensing requests and controls) from and offers output (sensor read-ings and control responses) to the monitor and control process.
105. The unit u is in the set of all pipeline sink units.
102. sink: u:mkSi(si) →
103. in uu[ f,uid Π(u) ] where f:Π•{f}=xtr iΠs(u) 104. in,out mac[ uid Π(u) ] Unit
105. pre: u ∈ plus
112
Definition 106.
107.
108.
109.
110.
102.
106.
107.
108.
109.
110.
113
Discussion
33 7.4.9 Monitor & Control Process 114
111. The monitor and control behaviour is abstracted in the form of the monctrl process state and its behaviour. We do not say anything in particular about this state.
112. The monctrl behaviour communicates with all the pipeline system units.
113. The monctrl behaviour alternates, non-deterministilllay internally, between
a assessing its own state, thereby possibly changing it in preparation for external actions;
b non-deterministically, externally accepting (sense or control response) input from any pipeline unit
i. using this to update its state; or
c offering, to a chosen unit, some sensor or control request, with this choice re-flected in a changed state,
i. as output whereupon the monitoring and control behaviour resumes.
114. Assessment changes the state.
115. Update likewise, based on sensor or control responses.
116. Choice updates the state while yielding a target unit and the sensor or actuator (i.e., control) request.
115
type
111. Σ [ monitor and control state ] value
112. monctrl: Σ →in,out {mac[π]:π:Π•π ∈ pluis} Unit 113. monctrl(σ)≡
113a. monctrl(assess(σ))
113b. ⌈⌉ ⌈⌉⌊⌋ { letsocr = mac[π] ? in
113(b)i. monctrl(update socr(socr)(σ)) end 113b. | π:Π•π ∈ pluis }
113c. ⌈⌉ let (π,sroc,σ′) = choose sroc(σ) in 113(c)i. sroc ! mac[π] ; monctrl(σ′) end 114. assess: Σ → Σ
115. update socr: SoCR → Σ→ Σ 116. choose sroc: Σ → (Π ×SRoC × Σ) type
115. SoCR [ sensor or control response ]
116. SRoC [ sensor requeat or control command ]
116
34
Discussion
7.5 Discussion
117118
Part IV
A Fluid Mechanics Model
A fluid mechanics model of pipelines describe the flow of liquids in from well, through pipes, past valves, pumps or compressors, forks and joins and into sinks.
Previous models were expressed in basically the discrete mathematics and mathematical logic (formal) specification languages.
Thus they did not handle continuity, one could not integrate or take the deriva-tive of their expressions.
Fluid mechanics models are usually expressed as partial differential equations (PDEs).
8 A Fluid Mechanics Model
119Fluid mechanics is the study of fluids and the forces on them. (Fluids include liquids, gases, and plasmas.) Fluid mechanics can be divided into fluid statics, the study of fluids at rest; fluid kinematics, the study of fluids in motion; and fluid dynamics, the study of the effect of forces on fluid motion. The mathematical modelling of fluid dynamics is in particular influenced by the Dutch-Swiss mathematician Daniel Bernoulli [1700–1782]
epitomised by his book Hydrodynamica [1734], and by the French engineer and physicist Claude-Louis Navier [1785–1836] and the Irish mathematician and physicist George Gabriel Stokes [1819–1903].
From Wikipedia:
The NavierStokes equations are the set of equations that describe the motion of fluid substances such as liquids and gases. These equations state that changes in momentum (force) of fluid particles depend only on the external pressure and internal viscous forces (similar to friction) acting on the fluid. Thus, the NavierStokes equations describe the balance of forces acting at any given region of the fluid.
The NavierStokes equations are differential equations which describe the motion of a fluid. Such equations establish relations among the rates of change of the variables of interest. For example, the NavierStokes equations for an ideal fluid
35 with zero viscosity states that acceleration (the rate of change of velocity) is proportional to the derivative of internal pressure.
Bernoulli’s equations for fluid dynamics can be derived from Navier-Stokes’ equations.
8.1 Some Preliminary Thoughts
1209 Conclusion
12110 Bibliographical Notes
12210.1 The Notes
10.1.1 Domains: Methodology and Theory Papers
There are now a number of published papers on domain science & engineering from the point of view put forward in this report. In the reverse order of publication (latest first) we begin with a bracketed pair: [#,file.pdf] where # refers to the References below and file.pdfis to be prefixed by http://www.imm.dtu.dk/~dibj/ in order to create an appropriate access URL.
• [17, urbino-p.pdf] examines the relationship between the philosophical and logic notion of mereology and model-oriented treatments of parts (as here: pipeline nets and units).
• [18, human-p.pdf] examines possible bases for the research into and development of IT systems that, when developed from sound models of domains, may meet a number of ‘humanity’-related criteria.
• [16, maurer-bjorner.pdf] examines domain models as the basis for the develop-ment of domain demos, domain simulators, and domain monitors & controllers. The present paper, in its quest for domain demos etc., relies on the observatio made in [16].
• [13, 14,kiev-p1.pdf, kiev-p2.pdf] In the first of these references we methodically unravel a domain description, showing most facets of domain engineering. In the second of these papers we report on an emerging theory of domain descriptions.
• [20, db-psi09-paper.pdf] This paper posits that requirements engineering pursued without a prior phase of domain engineering from which significant parts of the requirements can be systematically “derived” may be the wrong way to develop software, cf. the next reference.
• [5, montanari.pdf] This paper outlines some of the stages and steps of domain engineering and some of the stages and steps of rquirements engineering — all around a common example.
36
• [15, bsm.pdf] This paper reviews the practical software engineering management notions of process assessment and process improvement as these notions are to be interpreted in the context of domain and requirements engineering.
• [21, wpdr.pdf] This paper, like [17], provides some insight into possible theoretical foundations for domain descriptions.
• [4,ictac-paper.pdf] This paper reviews salient aspects of domain engineering and posits a number of research topics suggested for further study.
• [12,facs-domain.pdf] This paper overviews stages and steps of domain engineering.
10.1.2 Experimental and Explorative Domain Descriptions 123
We list a number of URLs to reports that tackle individual domain descriptions. Except for the last entry below, the prefixhttp://www.imm.dtu.dk/~dibj/ should be put in front of the teletype identifiers given below in order to retrieve these reports from the Internet.
• Financial Service Industry(fsi.pdf) This 170+ page, incomplete draft report sketches varipus aspects of banking and securities trading.
• Stock Exchanges(tse-1.pdf) This 74 page report overlaps with the above but specif-ically models the Tokyo Stock Exchange Tading Rules.
• Container Line Industry (container-paper.pdf) This almost 100 page draft report models a comprehensive set of a container line (like, f.ex. the Danish Maersk Lines, http://www.maersk.com).
• Logistics(logistics.pdf) This draft document models some of the aspects of logis-tics.
• The Market: Consumers, Retailers, Wholesaler and Producers (themarket.pdf) This published paper models “a supply-chain market”.
• Window Systems, Web and Transaction Protocols(wfdftp.pdf) This incomplete report models what it (might) mean[s] to be a window system (of recursively defined windows [icons may reveal windows]), an extended SQL system, and how window editing may involve a number of [say Internet] shared “window”-like databases being updated according to the Two-phase Commit Prototocol.
• License Languages (license-languages.pdf) This paper (appearing first as [23] in [19]) models, as script languages, the commands required for (i) the downloading, editing, sub-licensing, etc. of electronic media; (ii) the creating, editing, copying, reading and trashing of public administration documents; and (iii) the computerised support of patient hospitalisaton whose actions involve anamnese, analysis, diagnos-tics, creation of treatment plans, treatments, etc.
37
• IT Security (it-security.pdf) This paper (appearing first as [31] in [19]) suggests a model for the concept of IT Security Management as described in ISO Standard ISO/IEC 17799.
• The Railway Domain (http://www.railwaydomain.org/) This Web page was estab-lished around 2003. It was intended as a focal point for acadmic R&D efforts in one or another aspect of formal software development related to one or another kind of railway and train software. Interest in this “focal point”, unfortunately, never really
“took off”.
We refer to Toward a TRain Book (http://www.railwaydomain.org/PDF/tb.pdf) as illustrating fragments of a domain model for railways systems.
10.1.3 Lecture-oriented Notes on Domain Engineering 124
There are a number of Internet-based sets of lecture note slides on Domain Science &
Engineering. We refer to:
• 2012: Towards a Theory of Domain Descriptions – a gentle introduction: tadt-s.pdf
• 2009: From Domains to Requirement. The Triptych Approach to Software Engineering:
de+re-s.pdf
10.2 References
[1] D. Bjørner. Software Engineering, Vol. 1: Abstraction and Modelling. Texts in Theoretical Computer Science, the EATCS Series. Springer, 2006. See [6, 9].
[2] D. Bjørner. Software Engineering, Vol. 2: Specification of Systems and Languages. Texts in Theoretical Computer Science, the EATCS Series. Springer, 2006. Chapters 12–14 are primarily authored by Christian Krog Madsen. See [7, 10].
[3] D. Bjørner. Software Engineering, Vol. 3: Domains, Requirements and Software Design.
Texts in Theoretical Computer Science, the EATCS Series. Springer, 2006. See [8, 11].
[4] D. Bjørner. Domain Theory: Practice and Theories, Discussion of Possible Research Topics. InICTAC’2007, volume 4701 of Lecture Notes in Computer Science (eds. J.C.P.
Woodcock et al.), pages 1–17, Heidelberg, September 2007. Springer.
[5] D. Bjørner. From Domains to Requirements. In Montanari Festschrift, volume 5065 of Lecture Notes in Computer Science (eds. Pierpaolo Degano, Rocco De Nicola and Jos´e Meseguer), pages 1–30, Heidelberg, May 2008. Springer.
[6] D. Bjørner. Software Engineering, Vol. 1: Abstraction and Modelling. Qinghua University Press, 2008.
38
[7] D. Bjørner. Software Engineering, Vol. 2: Specification of Systems and Languages.
Qinghua University Press, 2008.
[8] D. Bjørner. Software Engineering, Vol. 3: Domains, Requirements and Software Design.
Qinghua University Press, 2008.
[9] D. Bjørner. Chinese: Software Engineering, Vol. 1: Abstraction and Modelling. Qinghua University Press. Translated by Dr Liu Bo Chao et al., 2010.
[10] D. Bjørner. Chinese: Software Engineering, Vol. 2: Specification of Systems and Lan-guages. Qinghua University Press. Translated by Dr Liu Bo Chao et al., 2010.
[11] D. Bjørner. Chinese: Software Engineering, Vol. 3: Domains, Requirements and Software Design. Qinghua University Press. Translated by Dr Liu Bo Chao et al., 2010.
[12] D. Bjørner. Domain Engineering. In BCS FACS Seminars, Lecture Notes in Computer Science, the BCS FAC Series (eds. Paul Boca and Jonathan Bowen), pages 1–42, London, UK, 2010. Springer.
[13] D. Bjørner. Domain Science & Engineering – From Computer Science to The Sciences of Informatics, Part I of II: The Engineering Part. Kibernetika i sistemny analiz, (2), May 2010.
[14] D. Bjørner. Domain Science & Engineering – From Computer Science to The Sciences of Informatics Part II of II: The Science Part. Kibernetika i sistemny analiz, (2), May 2010.
[15] D. Bjørner. Believable Software Management. Encyclopedia of Software Engineering, 1(1):1–32, 2011.
[16] D. Bjørner. Domains: Their Simulation, Monitoring and Control – A Divertimento of Ideas and Suggestions. InRainbow of Computer Science, Festschrift for Hermann Maurer on the Occasion of His 70th Anniversary., Festschrift (eds. C. Calude, G. Rozenberg and A. Saloma), pages 167–183. Springer, Heidelberg, Germany, January 2011.
[17] D. Bjørner. A Rˆole for Mereology in Domain Science and Engineering. Synthese Library (eds. Claudio Calosi and Pierluigi Graziani). Springer, Amsterdam, The Netherlands, 2012.
[18] D. Bjørner. Domain Science and Engineering as a Foundation for Computation for Human-ity. Computational Analysis, Synthesis, and Design of Dynamic Systems. CRC [Francis &
Taylor], 2012. (eds.: Justyna Zander and Pieter J. Mosterman).
[19] D. Bjørner. Domain Engineering: Technology Management, Research and Engineering. A JAIST Press Research Monograph (# 4), March 2009. This Research Monograph contains the following chapters: [22, 24, 25, 26, 27, 28, 29, 30, 31, 23]. Bjørner will post you this 507 page book (with 77 fine photos of “all things Japanese”, in full colours, taken by Dines in 2006) provided you e-mail your name and address and post international reply postage coupons (http://en.wikipedia.org/wiki/International reply coupon) toDines Bjørner, Fredsvej 11, DK-2840 Holte, Denmark in the total amount of: Denmark 60.50
39 Kr., Europe 126.00 Kr., elsewhere 209.00 Kr. [Postal prices are going up.] You should also be able to obtain it from Prof. Kokichi Futatsugi, kokichi@jaist.ac.jp.
[20] D. Bjørner. The Role of Domain Engineering in Software Development. Why Current Requirements Engineering Seems Flawed! InPerspectives of Systems Informatics, volume 5947 ofLecture Notes in Computer Science, pages 2–34, Heidelberg, Wednesday, January 27, 2010. Springer.
[21] D. Bjørner and A. Eir. Compositionality: Ontology and Mereology of Domains. Some Clarifying Observations in the Context of Software Engineering inJuly 2008, eds. Martin Steffen, Dennis Dams and Ulrich Hannemann. In Festschrift for Prof. Willem Paul de Roever Concurrency, Compositionality, and Correctness, volume 5930 of Lecture Notes in Computer Science, pages 22–59, Heidelberg, July 2010. Springer.
[22] Dines Bjørner. [19] Chap. 1: On Domains and On Domain Engineering – Prerequisites for Trustworthy Software – A Necessity for Believable Management, pages 3–38. JAIST Press, March 2009.
[23] Dines Bjørner. [19] Chap. 10: Towards a Family of Script Languages – – Licenses and Contracts – Incomplete Sketch, pages 283–328. JAIST Press, March 2009.
[24] Dines Bjørner. [19] Chap. 2: Possible Collaborative Domain Projects – A Management Brief, pages 39–56. JAIST Press, March 2009.
[25] Dines Bjørner. [19] Chap. 3: The Rˆole of Domain Engineering in Software Development, pages 57–72. JAIST Press, March 2009.
[26] Dines Bjørner. [19] Chap. 4: Verified Software for Ubiquitous Computing – A VSTTE Ubiquitous Computing Project Proposal, pages 73–106. JAIST Press, March 2009.
[27] Dines Bjørner. [19] Chap. 5: The Triptych Process Model – Process Assessment and Improvement, pages 107–138. JAIST Press, March 2009.
[28] Dines Bjørner. [19] Chap. 6: Domains and Problem Frames – The Triptych Dogma and M.A.Jackson’s PF Paradigm, pages 139–175. JAIST Press, March 2009.
[29] Dines Bjørner. [19] Chap. 7: Documents – A Rough Sketch Domain Analysis, pages 179–200. JAIST Press, March 2009.
[30] Dines Bjørner. [19] Chap. 8: Public Government – A Rough Sketch Domain Analysis, pages 201–222. JAIST Press, March 2009.
[31] Dines Bjørner. [19] Chap. 9: Towards a Model of IT Security — – The ISO Information Security Code of Practice – An Incomplete Rough Sketch Analysis, pages 223–282. JAIST Press, March 2009.
40
[32] E. Evans and B. Coulbeck, editors.Pipeline Systems. Fluid Mechanics and Its Applications.
Kluwer Academic Publishers, Dordreacht, The Netherlands, March 31 1992.
[33] C. W. George, P. Haff, K. Havelund, A. E. Haxthausen, R. Milne, C. B. Nielsen, S. Prehn, and K. R. Wagner. The RAISE Specification Language. The BCS Practitioner Series.
Prentice-Hall, Hemel Hampstead, England, 1992.
[34] C. W. George, A. E. Haxthausen, S. Hughes, R. Milne, S. Prehn, and J. S. Pedersen.
The RAISE Development Method. The BCS Practitioner Series. Prentice-Hall, Hemel Hampstead, England, 1995.
[35] C. Hoare. Communicating Sequential Processes. C.A.R. Hoare Series in Computer Science.
Prentice-Hall International, 1985. Published electronically: http://www.usingcsp.com/-cspbook.pdf (2004).
[36] J. L. Kennedy. Oil and gas pipeline fundamentals. PennWell Books, Tulsa, Oklahoma, 1993.
[37] M. Mohitpour, H. Golshan, and A. Murray. Pipeline Design & Construction: A Practical Approach. American Society of Mechanicl Engineers (ASME), New York, NY 10016-5990, 3rd edition, 2006.
[38] C. C. Zhou and M. R. Hansen. Duration Calculus: A Formal Approach to Real–time Systems. Monographs in Theoretical Computer Science. An EATCS Series. Springer–
Verlag, 2004.