|
From: <lko...@us...> - 2010-05-23 15:30:42
|
Revision: 805
http://scstudio.svn.sourceforge.net/scstudio/?rev=805&view=rev
Author: lkorenciak
Date: 2010-05-23 15:30:36 +0000 (Sun, 23 May 2010)
Log Message:
-----------
added help files
Modified Paths:
--------------
trunk/doc/help/membership/membership.html
Added Paths:
-----------
trunk/doc/help/time_consistency/
trunk/doc/help/time_consistency/time_consistency.html
trunk/doc/help/time_syntax/
trunk/doc/help/time_syntax/time_syntax.html
trunk/doc/help/time_tighten/
trunk/doc/help/time_tighten/time_tighten.html
trunk/doc/help/time_trace_race/
trunk/doc/help/time_trace_race/time_race.html
Modified: trunk/doc/help/membership/membership.html
===================================================================
--- trunk/doc/help/membership/membership.html 2010-05-22 20:53:18 UTC (rev 804)
+++ trunk/doc/help/membership/membership.html 2010-05-23 15:30:36 UTC (rev 805)
@@ -7,7 +7,7 @@
</HEAD>
<BODY LANG="en-US" DIR="LTR" STYLE="border: none; padding: 0in">
<h1>Membership</FONT></h1>
-<P >The problematic of
+<P >The problem of
membership is deciding whether given bMSC is contained in given HMSC.
It is possible to check both untimed and timed cases of bMSCs and
HMSCs.<BR></P>
Added: trunk/doc/help/time_consistency/time_consistency.html
===================================================================
--- trunk/doc/help/time_consistency/time_consistency.html (rev 0)
+++ trunk/doc/help/time_consistency/time_consistency.html 2010-05-23 15:30:36 UTC (rev 805)
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+ <TITLE>Time Consistency</TITLE>
+ <meta name="author" content="Martin Chmelik">
+ <LINK href="../help.css" rel="stylesheet" type="text/css"/>
+</HEAD>
+<BODY>
+<H1>Time Consistency</H1>
+<P>Time consistency is problem of deciding whether introduced time constraints in MSC are in conflict. MSC is time consistent if it is without such conflicting time constraints.</P>
+<p> The motivation for time consitency is following. It can easily happen that user can sapecify too restrictive time constraint and cause that the set of executions which satisfy MSC is empty. The time consistency property checks such situations.
+<H2>Basic Message Sequence Chart</H2>
+<P>Time consistent property is violated for BMSC B when there is no time assignment for B.</P>
+<P>The time assignment for BMSC (resp. HMSC path) is an assignment of time value to every event such that it satisfies all constraints in given BMSC (resp. HMSC path). I.e. for every constraint which restricts two events, the difference of values assigned by assignment to these events must be included in the interval set of this constraint.</P>
+<P>An example of time inconsistent BMSC is depicted on the next picture.</P>
+<img src="pictures/simple_non_fifo.png" border="0" alt="Example of a non-fifo design" title="Example of a non-fifo design">
+
+<H2>High-level MSC</H2>
+
+<P>HMSC violates time consistent property if exists path from start node to end node for which there is no time assignment.</P>
+<P>An example of time inconsistent HMSC is depicted on the next picture.</P>
+<img src="pictures/fifo1.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+<img src="pictures/fifo2.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+
+
+</BODY>
+</HTML>
Added: trunk/doc/help/time_syntax/time_syntax.html
===================================================================
--- trunk/doc/help/time_syntax/time_syntax.html (rev 0)
+++ trunk/doc/help/time_syntax/time_syntax.html 2010-05-23 15:30:36 UTC (rev 805)
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+ <TITLE>Correct Time Constraint Syntax</TITLE>
+ <meta name="author" content="Lubos Korenciak">
+ <LINK href="../help.css" rel="stylesheet" type="text/css"/>
+</HEAD>
+<BODY>
+<H1>Correct Time Constraint Syntax</H1>
+<P>The correct time constraint syntax algorithm is used for checking whether introduced time constraints are correct to use in SCStudio. The main motivation for such test is to rule out time constraints which are either not allowed by standard or ambiguous.
+</P>
+<P>The following conditions must hold for every time constraint to suffice correct time constraint algorithm:
+<ul>
+<li>if the constraint is in BMSC it has to restrict events which are visually ordered </li>
+<li>if the constraint is in HMSC and it restricts nodes A and B, every path going through A must go through B (and other way around) and it cannot go twice through A (B) without going through node B (A) in between.</li>
+</ul> </p>
+
+<P>An example of a time constraint can be seen on the next picture. Receive events of HTTP Response and HTTP request messages are not visually ordered. Thus the time constraint does not satisfy the Correct Time Constraint Syntax property. </P>
+<img src="pictures/simple_non_fifo.png" border="0" alt="Example of a wrong time constraint" title="Example of a non-fifo design">
+
+<P>On the next picture we see that there exists path which goes twice through node Connection denied and thus the introduced time constraint also does not satisfy Correct Time Constraint Syntax property.</P>
+
+<img src="pictures/fifo1.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+
+<P>The last example depicts HMSC where exist path which goes through node A of but does not go through node B. Since there is introduced time constraint restricting these nodes it violates Correct Time Constraint Syntax property.</P>
+<img src="pictures/fifo2.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+
+</BODY>
+</HTML>
Added: trunk/doc/help/time_tighten/time_tighten.html
===================================================================
--- trunk/doc/help/time_tighten/time_tighten.html (rev 0)
+++ trunk/doc/help/time_tighten/time_tighten.html 2010-05-23 15:30:36 UTC (rev 805)
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+ <TITLE>Tighten Time</TITLE>
+ <meta name="author" content="Lubos Korenciak">
+ <LINK href="../help.css" rel="stylesheet" type="text/css"/>
+</HEAD>
+<BODY>
+<H1>Tighten Time</H1>
+<P>The purpose of tighten time algorithm is to shorten interval sets of time constraints to minimal possible values. It deletes the values of time constraints which cannot be used due to other more restrictive time constraints.
+</P>
+<H3> Basic MSC</H3>
+<P>After tighten time algorithm, every constraint contains only values in interval sets for which exists valid time assignment.</p>
+<P>The time assignment for BMSC (resp. HMSC path) is an assignment of time value to every event such that it satisfies all constraints in given BMSC (resp. HMSC path). I.e. for every constraint which restricts two events, the difference of values assigned by assignment to these events must be included in the interval set of this constraint.</P>
+
+<P>An example of a tighten time algorithm on BMSC:</P>
+<img src="pictures/simple_non_fifo.png" border="0" alt="Example of a non-fifo design" title="Example of a non-fifo design">
+
+
+<H3> High-level MSC</H3>
+<P>After tighten time algorithm, every constraint contains only values in interval sets for which exists valid time assignment for some path from the start node to the end node.</p>
+<P>An example of tighten time algorithm on HMSC:</P>
+
+<img src="pictures/fifo1.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+<img src="pictures/fifo2.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+</BODY>
+</HTML>
Added: trunk/doc/help/time_trace_race/time_race.html
===================================================================
--- trunk/doc/help/time_trace_race/time_race.html (rev 0)
+++ trunk/doc/help/time_trace_race/time_race.html 2010-05-23 15:30:36 UTC (rev 805)
@@ -0,0 +1,24 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+ <TITLE>Time Race</TITLE>
+ <meta name="author" content="Lubos Korenciak">
+ <LINK href="../help.css" rel="stylesheet" type="text/css"/>
+</HEAD>
+<BODY>
+<H1>Time Race</H1>
+
+<P> Informally, two events are in race if they are specified by user to perform in some order, but there is a possibility that they can perform in inverse order.</P>
+<P> The introduction of time constraints can eliminate some race conditions. For example consider next two pictures. In the first one there is a race between HTTP Request and HTTP Response receive events. However on the second one the added time constraint caused that the BMSC is time race free. </P>
+<img src="pictures/simple_non_fifo.png" border="0" alt="Example of a non-fifo design" title="Example of a non-fifo design">
+
+<P>BMSC B (or HMSC path p) contains time race if there are two visually ordered events in B (or p), but there exists time assignment which assigns visually preceding event larger time value than the value assigned to subsequent event.</P>
+<P>HMSC contains time race if there exists path which contains time race. </P>
+<P>The time assignment for BMSC (resp. HMSC path) is an assignment of time value to every event such that it satisfies all constraints in given BMSC (resp. HMSC path). I.e. for every constraint which restricts two events, the difference of values assigned by assignment to these events must be included in the interval set of this constraint.</P>
+<P>Time Race algortihm checks the same as the <a href="../race/race.html">race checker</a>, but takes into account also time constraints.</P>
+<P>The next example shows HMSC which contains race condition, but which is time race free.</P>
+<img src="pictures/simple_non_fifo.png" border="0" alt="Example of a non-fifo design" title="Example of a non-fifo design">
+
+</BODY>
+</HTML>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|