<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Towards a formal language for systemic requirements</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Yann</forename><surname>Hourdel</surname></persName>
							<email>yann.hourdel@polytechnique.edu</email>
							<affiliation key="aff0">
								<orgName type="department">LIX</orgName>
								<orgName type="institution">École Polytechnique</orgName>
								<address>
									<postCode>91128</postCode>
									<settlement>Palaiseau Cedex</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Towards a formal language for systemic requirements</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">43B0F35FCF03DCDE1672DAB307C93466</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T22:26+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Systems modeling</term>
					<term>Systems architecture</term>
					<term>Systems Engineering</term>
					<term>Architecture framework</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This work is an attempt to contribute to the field of systems architecture. More precisely, it deals with complex 1 engineered systems analysis. Many informal methods for architecting such systems have been described over the past decade, but a lot of specific points still need to be clarified by a precise (mathematically formalized) definition. In particular, the languages used to manipulate system properties during systemic analysis are one big issue to be tackled. Our approach is the following: we take the framework described in [6] and reviewed in [4] as a starting point, and build a formal language to express functional (behaviour) requirements on models. The result is a formal language that allows architects to manipulate precise constraints on their models and, more importantly, translate them across subsequent systemic levels.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Introduction</head><p>In this work, systems are seen as black boxes. Their behaviour is only functional, so we will only express functional constraints on them. This kind of constraints is one perfect thing to be formalized, since it is very close to mathematical notions. Moreover, let us precise some important points:</p><p>-This work only deals with deterministic systems, for which we are able to describe the set of possible executions. -In this work, time is considered discrete. That allows us to speak about the previous or next instant of an t.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Notations</head><p>In the present work, the concatenation of two vectors A and B will be noted</p><formula xml:id="formula_0">A ⊗ B.</formula><p>More generally, we will note f ⊗ g : A ⊗ C → B ⊗ D the concatenation of f : A → B and g : C → D.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Preliminary definitions</head><p>In this section, we recall the definitions introduced in <ref type="bibr" target="#b2">[3]</ref> and reviewed in <ref type="bibr" target="#b3">[4]</ref> to formalize the notion of system, a timed extension of Mealy machines to model heterogeneous integrated systems and their integration.</p><p>Definition 1 (Type). The notion of type will be the classical "set of values" one.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.1">Time</head><p>Time is an underlying, yet very important, point of our formal approach. Indeed, real-life systems are naturally described according to various types of "times". As a result, we need to deal uniformaly with both continuous and discrete times.</p><p>While this problem has been shown hard by <ref type="bibr" target="#b1">[2]</ref>, some solutions have been found in studies like <ref type="bibr" target="#b4">[5]</ref> to introduce formal models for mixed discrete-continuous systems. We give here a set of definitions to handle such systems. Informally, as very well expressed in <ref type="bibr" target="#b2">[3]</ref>, time is "a linear quantity composed of ordered moments, pairs of which define durations".</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 2 (Time reference).</head><p>A time reference is an infinite set T together with an internal law + T : T × T → T and a pointed subset (T + , 0 T ) satisfying the following conditions:</p><formula xml:id="formula_1">-upon T + : • ∀a, b ∈ T + , a + T b ∈ T + closure (∆ 1 ) • ∀a, b ∈ T + , a + T b = 0 T =⇒ a = 0 T ∧ b = 0 T initiality (∆ 2 ) • ∀a ∈ T + , 0 T + T a = a neutral to left (∆ 3 ) -upon T : • ∀a, b, c ∈ T, a + T (b + T c) = (a + T b) + T c associativity (∆ 4 ) • ∀a ∈ T, a + T 0 T = a neutral to right (∆ 5 ) • ∀a, b, c ∈ T, a + T b = a + T c =⇒ b = c cancelable to left (∆ 6 ) • ∀a, b ∈ T, ∃c ∈ T + , (a + T c = b) ∨ (b + T c = a) linearity (∆ 7 )</formula><p>Definition 3 (Time scale). A time scale is any subset T of a time reference T such that:</p><formula xml:id="formula_2">-T has a minimum m T ∈ T -∀t ∈ T, T t+ = {t ∈ T | t ≺ t } has a minimum called succ T (t)</formula><p>-∀t ∈ T , when m T ≺ t, the set T t− = {t ∈ T | t ≺ t} has a maximum called pred T (t) -the principle of induction<ref type="foot" target="#foot_4">2</ref> is true on T.</p><p>The set of all time scales on T is noted T s(T ).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.2">Dataflows</head><p>Together with this unified definition of time, we need a definition of data that allows to handle the heterogeneity of data among real-life systems. We rely on the previous definitions to describe data carried by dataflows.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 4 ( -alphabet).</head><p>A set D is an -alphabet if ∈ D. For any set B, we can define an -alphabet by B = B ∪ { }.</p><p>Definition 5 (System dataset). A system dataset, or dataset, is a pair D = (D, B) such that:</p><p>-D is an -alphabet -B, called data behavior, is a pair (r, w) with r : D → D and w : D×D → D such that<ref type="foot" target="#foot_5">3</ref> : </p><formula xml:id="formula_3">• r( ) = (R1) • r r(d) = r(d) (R2) • r w(d, d ) = r(d ) (R3) • w r(d ), d = d (W1) • w w(d, d ), r(d ) = w(d, d )<label>(W2</label></formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.3">Systems and integration operators</head><p>Given the previous definitions, we are now able to give a mathematical definition of systems. Informally, our definition is very similar to timed Mealy machines with two important differences: the set of states may be infinite and the transfer function transforms dataflows. The key point is to see those systems as black boxes that just behave the way they are supposed to.</p><p>Definition 8 (System). A system is a 7-tuple ∫ = (T, X, Y, Q, q 0 , F, δ) where:</p><p>-T is a time scale, -X, Y are input and output datasets,</p><formula xml:id="formula_4">-Q is a nonempty -alphabet 4 of states, -q 0 is an element of Q, called initial state, -F : X × Q × T → Y describes a functional behavior, -δ : X × Q × T → Q describes a state behavior.</formula><p>Figure <ref type="figure" target="#fig_1">1</ref> illustrates this definition. Example 1. A very basic radiator with an internal thermostat placed in a room can be modeled as a system S = (T, X, Y, Q, q 0 , F, δ) with:</p><formula xml:id="formula_5">Y(t) Q(t) X(t)</formula><formula xml:id="formula_6">-T ∼ N -X = room temperature ∼ R -Y = {heat, nothing} -Q = {q on , q of f } -q 0 = q of f -F(x(t), q(t)) = heat if q(t) = q on ∅ otherwise -δ is a follows: q of f q on x(t) &lt; θ ⊥ x(t) &gt; θ</formula><p>It is important to understand here that at each time instant of the time scale, the state of the system changes instantly and before F computes the resulting output. At m Ts , the beginning of the time scale, the state of the system is q 0 . But as soon as the first input data arrives, at succ T (m Ts ), the state of ∫ changes so that the functional behaviour ignores q 0 . Figure <ref type="figure" target="#fig_2">2</ref> illustrates this behaviour and we give the following formal definition for timed executions of systems. Definition 9 (Execution of a system). Let ∫ = (T, X, Y, Q, q 0 , F, δ) be a system. Let In ∈ X T be an input dataflow for ∫ and Ĩn = In T . The execution of ∫ on the input dataflow In is the 3-tuple (In, S, Out) where:</p><p>-S ∈ Q T is recursively defined by:</p><formula xml:id="formula_7">• S(m T ) = δ Ĩn(m T ), q 0 , m T • ∀t ∈ T, S(t + ) = δ Ĩn(t + ), S(t), t + where t + = succ T (t) -Out ∈ Y T is defined by: • Out(m T ) = F Ĩn(m T ), q 0 , m T • ∀t ∈ T, Out(t + ) = F Ĩn(t + ), S(t), t + where t + = succ T (t)</formula><p>In, S and Out are respectively input, state and output dataflows. We note exec(∫ ) the set of possible executions of ∫ .</p><p>Definition 10 (Product of systems on a time scale).</p><formula xml:id="formula_8">Let (∫ i ) i = (T, X i , Y i , Q i , q 0i , F i , δ i ) i be n systems of time scale T. The product ∫ 1 ⊗• • •⊗∫ n is the system T, X, Y, Q, q 0 , F, δ</formula><p>where:</p><formula xml:id="formula_9">-X = X 1 ⊗ • • • ⊗ X n and Y = Y 1 ⊗ • • • ⊗ Y n -Q = Q 1 × • • • × Q n and q 0 = (q 01 , . . . , q 0n ) = q 01...n -F x 1...n , q 1...n , t = F 1 (x 1 , q 1 , t), . . . , F n (x 1 , q 1 , t) -δ x 1...n , q 1...n , t = δ 1 (x 1 , q 1 , t), . . . , δ n (x 1 , q 1 , t)</formula><p>Remark 1. This definition can be extended to systems that do not share a time scale, thanks to a technical operator introduced in <ref type="bibr" target="#b2">[3]</ref>. This operator builds a timed-extension of a system, which is a system that has an equivalent inputoutput behaviour as the original system, but on a wider time scale. Figure <ref type="figure" target="#fig_3">3</ref> illustrates this idea.</p><p>Definition 11 (Feedback of a system). Let ∫ = T, (D×In, I), (D×Out, O), Q, q 0 , F, δ be a system such that there is no instantaneous influence of dataset D from -I is the restriction of I to In, and O is the restriction of O to Out -F (x ∈ In, q ∈ Q, t) = F (d x,q,t , x), q, t Out -δ (x ∈ In, q ∈ Q, t) = δ (d x,q,t , x), q, t where d x,q,t stands for F ( , x), q, t D . Figure <ref type="figure">4</ref> Definition 12 (Abstraction of a transfer function). Let F : X T → Y T be a transfer function. Let A x : X T → Y a Ta be an abstraction for input dataflows and A y : Y T → Y a Ta an abstraction for output dataflows. The abstraction of F for input and output abstractions (A x , A y ) with events E is the new transfer function Definition 13 (Abstraction of a system). Let ∫ = T, X, Y, Q, q 0 , F, δ be a system. ∫ = T a , X a ⊗ E, Y a , Q a , q a0 , F a , δ a is an abstraction of ∫ for input and output abstractions (A x , A y ) if, and only if:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Proceedings of the</head><formula xml:id="formula_10">F a : (X a ⊗ E) T → Y a Ta defined by: ∀x ∈ X T , ∃e ∈ E Ta , F a A x (x T ) ⊗ e = A y F (x)</formula><formula xml:id="formula_11">∃A q : Q T → Q a</formula><p>Ta , for all execution (x, q, y) of ∫ , ∃E ∈ E Ta , A x (x T ) ⊗ E, A q (q), A y (y) is an execution of ∫ . Conversely, ∫ is a concretization of the system ∫ .</p><p>A system captures the behavior of a system that can be observed (functional and states behavior, called together systemic behavior ). From this definition, we can start expressing behaviour properties.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Systemic behaviour properties: a formal semantics</head><p>The goal of this section is to be able to describe the behaviour of such a system, in order to express properties and constraints on it. To do so, we will define a semantics of systems and provide a formal definition of "properties". The idea here is that systems are described by executions, so we must use timed properties. We will first describe our property syntax language, then our property semantics.</p><p>Definition 14 (System property formulas). Let ∫ = (T, X, Y, Q, q 0 , F, δ) be a system. The set P (∫ ) of property formulas over ∫ , similar to LTL<ref type="foot" target="#foot_8">6</ref> , is inductively defined as follows.</p><p>Here are the atomic formulas, where (x, q, y) ∈ X × Q × Y :</p><p>-input(x), which means that the current input of ∫ has to be x -istate(q), which means that the current state of ∫ has to be q -ouput(y), which means that the current output of ∫ has to be y And here are the operators, where (φ, φ 1 , φ 2 ) ∈ P (∫ ) 3 :</p><formula xml:id="formula_12">-¬φ -φ 1 ∧ φ 2 -</formula><p>φ, which means that φ has to hold at the next state of the execution -φ 1 Uφ 2 , which means that φ 2 eventually has to hold and until it does, φ 1 has to hold (φ 1 can hold further)</p><p>Definition 15 (Other system property formulas). Let ∫ = (T, X, Y, Q, q 0 , F, δ) be a system. Let (φ, φ 1 , φ 2 ) ∈ P (∫ ) 3 .</p><p>The previously defined language P (∫ ) can be extended with the following operators:</p><formula xml:id="formula_13">- -⊥ -φ 1 ∨ φ 2 -φ 1 ⇒ φ 2 7</formula><p>-♦φ, which means that φ has to hold now or in a future state of the execution -φ, which means that φ has to hold for the entire subsequent execution -φ 1 Rφ 2 , which means that φ 1 has to hold until and including a state when φ 2 holds, which is not forced to happen if φ 1 holds forever P (∫ ) is the syntax of our properties language. It gives us a way to express properties on executions of ∫ . We are now able to define our semantics. The following rules describe the satisfaction of P (∫ ) formulas using only the first set of operators, but such rules could be easily extended to the extended set of operators. Definition 16 (system property satisfaction). Let ∫ be a system. The satisfaction of a P (∫ ) formula φ by an execution e of ∫ , written e φ, is defined according to the following rules:</p><p>[AI] (x 0 , , ), . . . input(x 0 )</p><p>[AS] ( , q 0 , ), . . . istate(q 0 )</p><p>[AO] ( , , y 0 ), . . . In this case, φ is said to be a behaviour constraint on ∫ .</p><p>Example 2. Unsing our previous example 1, with θ ⊥ = 15 and θ = 20, here are some behaviour constraints one would want to express on the system:</p><formula xml:id="formula_14">-∫ ¬♦ istate(q of f ) ∧ output(heat) -∫ ¬♦ input(10) ∧ istate(q of f )</formula><p>or, even more generally:</p><p>-∀θ &gt; θ , ∫ ¬♦ input(θ) ∧ istate(q on )</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Computation rules over behaviour constraints</head><p>We give here a minimalist set of computation rules to establish proofs about system behaviours. A more advanced set of rules might be needed to ease such proofs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Proposition 1 (Product of two systems). Let</head><formula xml:id="formula_15">∫ 1 = (T, X 1 , Y 1 , Q 1 , , , ) and ∫ 2 = (T, X 2 , Y 2 , Q 2 , , , ) be two systems. Let (x 1 , x 2 ) ∈ X 1 × X 2 , (y 1 , y 2 ) ∈ Y 1 × Y 2 and (q 1 , q 2 ) ∈ Q 1 × Q 2 . ∫ 1 input(x 1 ) ∫ 2 input(x 2 ) [PI] ∫ 1 ⊗ ∫ 2 input(x 1 ⊗ x 2 ) ∫ 1 output(y 1 ) ∫ 2 output(y 2 ) [PO] ∫ 1 ⊗ ∫ 2 output(x 1 ⊗ x 2 )</formula><p>Proceedings of the Posters Workshop at CSD&amp;M 2013 ∫ 1 istate(q 1 ) ∫ 2 istate(q 2 ) [PS] ∫ 1 ⊗ ∫ 2 istate((q 1 , q 2 ))</p><p>Definition 18 (Composition of two systems). Let ∫ 1 = (T, X 1 , Y 1 , Q 1 , , , ) and ∫ 2 = (T, X 2 , Y 2 , Q 2 , , , ) be two systems such that Y 1 = X 2 . We note ∫ 2 • ∫ 1 the composition of ∫ 1 and ∫ 2 , obtained by "pluging" the output of ∫ 1 to the input of ∫ 2 .</p><p>Proposition 2 (Composition of two systems). Let ∫ 1 = (T 1 , X 1 , Y 1 , Q 1 , , , ) and ∫ 2 = (T 2 , X 2 , Y 2 , Q 2 , , , ) be two systems such that T 1 = T 2 and Y 1 = X 2 . Let (x, y, q 1 , q</p><formula xml:id="formula_16">2 ) ∈ X 1 × Y 2 × Q 1 × Q 2 ). ∫ 1 input(x) [WI] ∫ 2 • ∫ 1 input(x) ∫ 2 output(y) [WO] ∫ 2 • ∫ 1 output(y) ∫ 1 istate(q 1 )</formula><p>∫ 2 istate(q 2 ) [WS] ∫ 2 • ∫ 1 istate((q 1 , q 2 ))</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Conclusion</head><p>In this work we built a semantics of systems and provided a formal definition of "properties" as timed behaviour constraints. The next step is to build a more advanced refinement computation language that could let modelers obtain a system from a set of such constraints.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>) Definition 6 (</head><label>6</label><figDesc>Dataflow). Let T be a time scale. A dataflow over (D, T) is a mapping X : T → D. Definition 7 (Sets of dataflows). The set of all dataflows over (D, T) is noted D T . The set of all dataflows over D with any possible time scale on time reference T is noted D T = T∈T s(T ) D T .</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Illustration of a system</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Transitions of a system throughout its time scale</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>YFig. 3 .</head><label>3</label><figDesc>Fig. 3. Product of systems</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 5 Fig. 4 .Fig. 5 .</head><label>545</label><figDesc>Figure 5 illustrates this definition.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>, e i+1 , . . .) φ 2 ∧ ∀k ∈ {0, . . . , i}, (e k , e k+1 , . . .) φ 1 [AU] e 0 , e 1 , . . . φ 1 Uφ 2</figDesc><table><row><cell>output(y 0 )</cell><cell cols="4">[e φ] ⇒ ⊥ [AN] e ¬φ</cell></row><row><cell>e φ 1 e φ 1 ∧ φ 2 e φ 2 [AW]</cell><cell>e 1 , e 2 , . . . , e 1 , e 2 , . . .</cell><cell>φ</cell><cell>φ</cell><cell>[AC]</cell></row><row><cell>∃i ≤ 0, (e i</cell><cell></cell><cell></cell><cell></cell><cell></cell></row></table><note>Definition 17 (system behaviour constraint). Let ∫ be a system. Let φ be a P (∫ ) formula. We say that ∫ satisfies φ, which is noted ∫ φ, iif ∀e ∈ exec(∫ ), e φ</note></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">large, integrated, dense and heterogeneousProceedings of the Posters Workshop at CSD&amp;M</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2013" xml:id="foot_1"></note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_2">Proceedings of the Posters Workshop at CSD&amp;M 2013</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_3">Towards a formal language for systemic requirements</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_4">For A ⊂ T, m T ∈ A &amp; ∀t ∈ A, succ T (t) ∈ A ⇒ A = T.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_5">These axioms give a relevant semantics and are necessary to define consistent projections of dataflows on time scales.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_6">Defining Q as an -alphabet (therefore containing ) and not just as a set will make it possible to define a dataflow of states, which is convenient.Proceedings of the Posters Workshop at CSD&amp;M 2013</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_7">As explained informally in<ref type="bibr" target="#b2">[3]</ref>, this condition makes it possible to define a unique feedback, i.e. without having to solve a fixed point equation that could lead to zero or multiple solutions Proceedings of the Posters Workshop at CSD&amp;M 2013</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_8">see<ref type="bibr" target="#b0">[1]</ref> </note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_9">We can also accept φ1 ⊗ φ2 or any other "usual" operators Proceedings of the Posters Workshop at CSD&amp;M 2013</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<ptr target="http://en.wikipedia.org/wiki/Linear_temporal_logic" />
		<title level="m">LTL</title>
				<imprint>
			<date type="published" when="2012-10-31">31/10/2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">A survey on continuous time computations</title>
		<author>
			<persName><forename type="first">O</forename><surname>Bournez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M.-L</forename><surname>Campagnolo</surname></persName>
		</author>
		<idno>CoRR, abs/0907.3117</idno>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Modeling of complex systems ii: A minimalist and unified semantics for heterogeneous integrated systems</title>
		<author>
			<persName><forename type="first">B</forename><surname>Golden</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Aiguier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Krob</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Applied Mathematics and Computation</title>
		<imprint>
			<biblScope unit="volume">218</biblScope>
			<biblScope unit="issue">16</biblScope>
			<biblScope unit="page" from="8039" to="8055" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">A minimalist formal framework for systems design</title>
		<author>
			<persName><forename type="first">B</forename><surname>Golden</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Hourdel</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The theory of hybrid automata</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">A</forename><surname>Henzinger</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 11th Annual IEEE Symposium on Logic in Computer Science, LICS &apos;96</title>
				<meeting>the 11th Annual IEEE Symposium on Logic in Computer Science, LICS &apos;96<address><addrLine>Washington, DC, USA</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE Computer Society</publisher>
			<date type="published" when="1996">1996</date>
			<biblScope unit="page">278</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<author>
			<persName><forename type="first">D</forename><surname>Krob</surname></persName>
		</author>
		<title level="m">Éléments de systémique -architecture des systèmes</title>
				<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
