Merge remote-tracking branch 'origin/master' into bug_561630
diff --git a/community.html b/community.html
index c2413e3..0b49ef9 100644
--- a/community.html
+++ b/community.html
@@ -10,7 +10,7 @@
<body>
<header>
<div class="logo-left width">
- <a href="index.html"><img src="images/chess-logo.png" alt="CHESS logo" width=""></a>
+ <a href="index.html"><img src="images/logo_chess_350.gif" alt="CHESS logo" width=""></a>
</div>
</header>
<nav>
@@ -42,14 +42,14 @@
<section id="content">
<article class="expanded">
<p>
- Learn about PolarSys CHESS, download a draft of user manual, get the latest downloads, and more.
+ Learn about CHESS, download a draft of user manual, get the latest downloads, and more.
Join the community, connect with other CHESS users, get support and service.
</p>
<table border="0" cellspacing="0"; style="border-style:none; margin : 10px; width: 70%;">
<tr>
- <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="http://polarsys.org/forums/index.php/f/9/"><img src="images/forum.png" alt="Forum" width="60"></a></td>
+ <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="https://www.eclipse.org/forums/index.php/f/529/"><img src="images/forum.png" alt="Forum" width="60"></a></td>
<td style="border-bottom: 1px solid #ccc;">Consult the CHESS forum and ask questions about the tool</td>
</tr>
<!--
@@ -59,15 +59,15 @@
</tr>
-->
<tr>
- <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="http://polarsys.org/wiki/CHESS"><img src="images/Wiki_puzzle.svg.png" alt="Wiki" width="60"></a></td>
+ <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="https://wiki.eclipse.org/CHESS"><img src="images/Wiki_puzzle.svg.png" alt="Wiki" width="60"></a></td>
<td style="border-bottom: 1px solid #ccc;">Wiki prodiving additional resources to follow and contribute to CHESS.</td>
</tr>
<tr>
- <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS"><img src="images/buggie.png" alt="Bugzilla" width="60"></a></td>
+ <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess"><img src="images/buggie.png" alt="Bugzilla" width="60"></a></td>
<td style="border-bottom: 1px solid #ccc;">Bugzilla for bug reporting and enhancement requests.</td>
</tr>
<tr style="height:50px;">
- <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="http://polarsys.org/mailman/listinfo/chess-dev"><img src="images/enveloppe.png" alt="Mailing-list" width="60"></a></td>
+ <td style="border-bottom: 1px solid #ccc; height:80px;" width="20px"><a href="https://accounts.eclipse.org/mailing-list/chess-dev"><img src="images/enveloppe.png" alt="Mailing-list" width="60"></a></td>
<td style="border-bottom: 1px solid #ccc;">Subscribe to the developers mailing-list to be warned about technical announcements.</td>
</tr>
</table>
@@ -98,7 +98,7 @@
<hr style="background:#DFE8F2; border:0; height:1px" />
<br />
<p>
- CHESS is in PolarSys since november 2013.
+ CHESS has been in the Polarsys Working Group from 2013 to 2019.
</p>
</th>
</tr>
@@ -109,63 +109,69 @@
<div class="clear"></div>
</div>
<footer>
- <div class="footer-content width">
+ <div class="footer-content width">
<ul>
- <li><h4>PolarSys</h4></li>
- <li><a href="http://www.polarsys.org/about-us">About</a></li>
- <li><a href="http://www.polarsys.org/contact-us">Contact Us</a></li>
- <li><a href="http://www.polarsys.org/projects/polarsys.chess">CHESS Project Page</a></li>
+ <li><h4>Eclipse Foundation</h4></li>
+ <li><a href="https://www.eclipse.org/org/">About</a></li>
+ <li><a href="https://www.eclipse.org/org/foundation/contact.php">Contact Us</a></li>
+ <li><a href="https://projects.eclipse.org/projects/polarsys.chess">CHESS
+ Project Page</a></li>
</ul>
- <ul>
- <li><h4>Legal</h4></li>
- <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
- <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
- <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
- <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a></li>
+ <ul>
+ <li><h4>Legal</h4></li>
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy
+ Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms
+ of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright
+ Agent</a></li>
+ <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse
+ Public License</a></li>
<li><a href="http://www.eclipse.org/legal/">Legal Resources</a></li>
- </ul>
+ </ul>
<ul>
<li><h4>Useful Links</h4></li>
- <li><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS">Report a Bug</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS">Documentation</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS/Technical_Information">How to Contribute</a></li>
- <li><a href="http://polarsys.org/mailman/listinfo/chess-dev">Mailing List</a></li>
- <li><a href="http://polarsys.org/forums/index.php/f/9/">Forum</a></li>
+ <li><a
+ href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess">Report
+ a Bug</a></li>
+ <li><a href="https://wiki.eclipse.org/CHESS">Documentation</a></li>
+ <li><a
+ href="https://wiki.eclipse.org/CHESS/Technical_Information">How
+ to Contribute</a></li>
+ <li><a href="https://accounts.eclipse.org/mailing-list/chess-dev">Mailing
+ List</a></li>
+ <li><a href="https://www.eclipse.org/forums/index.php/f/529/">Forum</a></li>
</ul>
<ul class="endfooter">
- <li><h4>Other</h4></li>
+ <li><h4>Other</h4></li>
+ <li><a href="https://es.fbk.eu/">Fondazione Bruno Kessler</a></li>
<li><a href="http://www.intecs.it/">Intecs</a></li>
<li><a href="http://www.unipd.it">University of Padova</a></li>
+ <li><a href="http://www.mdh.se/">Mälardalen University</a></li>
</ul>
<table>
<tr>
- <td>
- <a href="http://www.polarsys.org/"><img src="images/polarsys.png" alt="PolarSys logo" width="250"></a>
- <br />
- <br />
- </td>
+ <td><a href="https://www.yourkit.com"><img
+ src="images/yklogo.png" alt="YourKit logo"
+ style="width: 25%; height: 25%"></a> <br /> <font size="2">Thanks
+ YourKit for providing us free licenses of <a
+ href="https://www.yourkit.com/java/profiler/">YourKit Java
+ Profiler</a>
+ </font></td>
<td>
<div class="right-footer">
- <a href="http://www.eclipse.org/"><img src="images/eclipse.png" alt="Eclipse logo"></a>
- <br />
- Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br /> All Rights Reserved.
+ <a href="http://www.eclipse.org/"><img
+ src="images/eclipse.png" alt="Eclipse logo"></a> <br />
+ Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br />
+ All Rights Reserved.
</div>
</td>
- </tr>
- <tr>
- <td>
- <a href="https://www.yourkit.com"><img src="images/yklogo.png" alt="YourKit logo" style="width: 25%; height: 25%"></a>
- <br />
- <font size="2">Thanks YourKit for providing us free licenses of <a href="https://www.yourkit.com/java/profiler/">YourKit Java Profiler</a></font>
- </td>
- <td>
- </td>
- </tr>
+ </tr>
</table>
-
- <div class="clear"></div>
- </div>
-
- </footer>
+
+ <div class="clear"></div>
+ </div>
+
+ </footer>
</body>
</html>
\ No newline at end of file
diff --git a/download.html b/download.html
index a25327f..e0c2151 100644
--- a/download.html
+++ b/download.html
@@ -2,22 +2,23 @@
<html>
<link rel="icon" type="image/png" href="favicon.ico" />
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>CHESS</title>
- <link rel="stylesheet" href="styles.css" type="text/css" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>CHESS</title>
+<link rel="stylesheet" href="styles.css" type="text/css" />
</head>
<body>
- <header>
+ <header>
<div class="logo-left width">
- <a href="index.html"><img src="images/chess-logo.png" alt="CHESS logo" width=""></a>
+ <a href="index.html"><img src="images/logo_chess_350.gif"
+ alt="CHESS logo" width=""></a>
</div>
- </header>
+ </header>
- <nav>
+ <nav>
<div class="width">
<ul>
<li class="start"><a href="index.html">Home</a></li>
- <li class="divider-vertical-second-menu"></li>
+ <li class="divider-vertical-second-menu"></li>
<li><a href="features.html">Features</a></li>
<li class="divider-vertical-second-menu"></li>
<li><a href="start.html">Getting Started</a></li>
@@ -25,98 +26,144 @@
<li><a href="events.html">Events</a></li>
<li class="divider-vertical-second-menu"></li>
<li class="end"><a href="community.html">Community</a></li>
- <li style="text-align:right;"><a href="download.html" class="box">Download</a></li>
- <li style="float:none;"><br style="clear:both;" /></li>
- </ul>
+ <li style="text-align: right;"><a href="download.html"
+ class="box">Download</a></li>
+ <li style="float: none;"><br style="clear: both;" /></li>
+ </ul>
</div>
- </nav>
+ </nav>
<div id="hrdiv">
<img src="images/bg_breadcrumb.jpg" width="" alt="" height="" />
</div>
- <div id="body" class="width-started">
- <p>PolarSys CHESS 0.10.0 has been released, see links below to download a full Eclipse CHESS distribution and the model examples. </br>
- If you want to install the CHESS plugins by using the Eclipse update site feature, check the <a href="start.html">Getting Started page</a></br>
- For release details, please check the
- <a href="https://www.polarsys.org/projects/polarsys.chess/releases/0.10.0"> <b>release plan</b>.</a>
-
- <h3>CHESS Eclipse full distribution:</h3>
-
- <li><a href="http://download.polarsys.org/chess/core/releases/0.10.0/PolarsysCHESS0.10.0-win32-x86_64.zip">CHESS0.10.0 Windows 64 bit</a></li>
- <li><a href="http://download.polarsys.org/chess/core/releases/0.10.0/PolarsysCHESS0.10.0-linux-x86_64.tar.gz">CHESS0.10.0 Linux 64 bit</a></li></br>
-
- <h4>Previous versions:</h4>
- <li><a href="http://download.polarsys.org/chess/core/releases/0.9.0/PolarsysCHESS0.9.0-win32-x86_64.zip">CHESS0.9.0 Windows 64 bit</a></li>
- <li><a href="http://download.polarsys.org/chess/core/releases/0.9.0/PolarsysCHESS0.9.0-linux-x86_64.tar.gz">CHESS0.9.0 Linux 64 bit</a></li></br>
-
-
- <h3>CHESS model examples</h3>
- <li><a href="http://download.polarsys.org/chess/models/ProtectedOperationSample.zip">Producer-Consumer</a></li>
- <li><a href="http://download.polarsys.org/chess/models/IndustrialDrive.zip">IndustrialDrive</a></li>
- <li><a href="http://download.polarsys.org/chess/models/WBS.zip">Wheel Braking System (example about contract-based design)</a></li>
- <li><a href="http://download.polarsys.org/chess/models/HBS.zip" title="Model from «L. Bressan, A. L. de Oliveira, L. Montecchi, B. Gallina. A Systematic Process for Applying the CHESS Methodology in the Creation of Certifiable Evidence. In: 14th European Dependable Computing Conference (EDCC 2018). Iasi, Romania, September 10-14, 2018»">Hybrid Braking System (example about safety analysis with CHESS-FLA and CHESS-SBA)</a></li></br>
- <div class="clear"></div>
- </div>
-
- <footer>
- <div class="footer-content width">
+ <div id="body" class="width-started">
+ <p>
+ CHESS 1.0.0 has been released! </br></br> The key features of the new version
+ are:
<ul>
- <li><h4>PolarSys</h4></li>
- <li><a href="http://www.polarsys.org/about-us">About</a></li>
- <li><a href="http://www.polarsys.org/contact-us">Contact Us</a></li>
- <li><a href="http://www.polarsys.org/projects/polarsys.chess">CHESS Project Page</a></li>
+ <li>Improved support for contract-based design analysis and model
+ checking (integration with OCRA, nuXmv, xSAP tools).</li>
+ <li>Support for FTA, FMEA.</li>
+ <li>Support for parameterized architecture and trade-off
+ analysis.</li>
+ <li>Automatic generation of Mobius SAN models.</li>
+ <li>CHESSML dependability profile extension for security.</li>
+ <li>Automatic generation of diagrams and documentation.</li>
+ </ul> See
+ links below to download a full Eclipse CHESS distribution and the
+ model examples. </br> If you want to install the CHESS plugins by using the
+ Eclipse update site feature, check the <a href="start.html">Getting
+ Started page</a></br> For release details, please check the <a
+ href="https://projects.eclipse.org/projects/polarsys.chess/releases/1.0.0">
+ <b>release plan</b>.
+ </a>
+ <h3>CHESS Eclipse full distribution:</h3>
+
+ <li><a
+ href="http://download.eclipse.org/chess/core/releases/1.0.0/CHESS-1.0.0-win32.win32.x86_64.zip">CHESS-1.0.0
+ Windows 64 bit</a></li>
+ <li><a
+ href="http://download.eclipse.org/chess/core/releases/1.0.0/CHESS-1.0.0-linux.gtk.x86_64.zip">CHESS-1.0.0
+ Linux 64 bit</a></li> </br>
+
+ <h4>Previous versions:</h4>
+ <li><a
+ href="http://download.eclipse.org/chess/core/releases/0.10.0/PolarsysCHESS0.10.0-win32-x86_64.zip">CHESS0.10.0
+ Windows 64 bit</a></li>
+ <li><a
+ href="http://download.eclipse.org/chess/core/releases/0.10.0/PolarsysCHESS0.10.0-linux-x86_64.tar.gz">CHESS0.10.0
+ Linux 64 bit</a></li> </br>
+
+
+ <h3>CHESS model examples</h3>
+ <li><a
+ href="http://download.eclipse.org/chess/models/ProtectedOperationSample.zip">Producer-Consumer
+ (example about schedulability analysis)</a></li>
+ <li><a
+ href="http://download.eclipse.org/chess/models/IndustrialDrive.zip">IndustrialDrive
+ (example about schedulability and E2E response time analyses) </a></li>
+ <li><a href="http://download.eclipse.org/chess/models/WBS.zip">Wheel
+ Braking System (example about contract-based design)</a></li>
+ <li><a
+ href="http://download.eclipse.org/chess/models/SenseSpacecraftRate.zip">Sense
+ Spacecraft Rate (example about contract-based design, model checking
+ and fault tree analysis)</a></li>
+ <li><a href="http://download.eclipse.org/chess/models/HBS.zip"
+ title="Model from «L. Bressan, A. L. de Oliveira, L. Montecchi, B. Gallina. A Systematic Process for Applying the CHESS Methodology in the Creation of Certifiable Evidence. In: 14th European Dependable Computing Conference (EDCC 2018). Iasi, Romania, September 10-14, 2018»">Hybrid
+ Braking System (example about safety analysis with CHESS-FLA and
+ CHESS-SBA)</a></li> </br>
+ <div class="clear"></div>
+ </div>
+
+ <footer>
+ <div class="footer-content width">
+ <ul>
+ <li><h4>Eclipse Foundation</h4></li>
+ <li><a href="https://www.eclipse.org/org/">About</a></li>
+ <li><a
+ href="https://www.eclipse.org/org/foundation/contact.php">Contact
+ Us</a></li>
+ <li><a
+ href="https://projects.eclipse.org/projects/polarsys.chess">CHESS
+ Project Page</a></li>
</ul>
- <ul>
- <li><h4>Legal</h4></li>
- <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
- <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
- <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
- <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a></li>
+ <ul>
+ <li><h4>Legal</h4></li>
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy
+ Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms
+ of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright
+ Agent</a></li>
+ <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse
+ Public License</a></li>
<li><a href="http://www.eclipse.org/legal/">Legal Resources</a></li>
- </ul>
+ </ul>
<ul>
<li><h4>Useful Links</h4></li>
- <li><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS">Report a Bug</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS">Documentation</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS/Technical_Information">How to Contribute</a></li>
- <li><a href="http://polarsys.org/mailman/listinfo/chess-dev">Mailing List</a></li>
- <li><a href="http://polarsys.org/forums/index.php/f/9/">Forum</a></li>
+ <li><a
+ href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess">Report
+ a Bug</a></li>
+ <li><a href="https://wiki.eclipse.org/CHESS">Documentation</a></li>
+ <li><a
+ href="https://wiki.eclipse.org/CHESS/Technical_Information">How
+ to Contribute</a></li>
+ <li><a
+ href="https://accounts.eclipse.org/mailing-list/chess-dev">Mailing
+ List</a></li>
+ <li><a href="https://www.eclipse.org/forums/index.php/f/529/">Forum</a></li>
</ul>
<ul class="endfooter">
<li><h4>Other</h4></li>
+ <li><a href="https://es.fbk.eu/">Fondazione Bruno Kessler</a></li>
<li><a href="http://www.intecs.it/">Intecs</a></li>
<li><a href="http://www.unipd.it">University of Padova</a></li>
+ <li><a href="http://www.mdh.se/">Mälardalen University</a></li>
</ul>
<table>
<tr>
- <td>
- <a href="http://www.polarsys.org/"><img src="images/polarsys.png" alt="PolarSys logo" width="250"></a>
- <br />
- <br />
- </td>
+ <td><a href="https://www.yourkit.com"><img
+ src="images/yklogo.png" alt="YourKit logo"
+ style="width: 25%; height: 25%"></a> <br /> <font size="2">Thanks
+ YourKit for providing us free licenses of <a
+ href="https://www.yourkit.com/java/profiler/">YourKit Java
+ Profiler</a>
+ </font></td>
<td>
<div class="right-footer">
- <a href="http://www.eclipse.org/"><img src="images/eclipse.png" alt="Eclipse logo"></a>
- <br />
- Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br /> All Rights Reserved.
+ <a href="http://www.eclipse.org/"><img
+ src="images/eclipse.png" alt="Eclipse logo"></a> <br />
+ Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br />
+ All Rights Reserved.
</div>
</td>
</tr>
- <tr>
- <td>
- <a href="https://www.yourkit.com"><img src="images/yklogo.png" alt="YourKit logo" style="width: 25%; height: 25%"></a>
- <br />
- <font size="2">Thanks YourKit for providing us free licenses of <a href="https://www.yourkit.com/java/profiler/">YourKit Java Profiler</a></font>
- </td>
- <td>
- </td>
- </tr>
</table>
-
- <div class="clear"></div>
- </div>
-
- </footer>
+
+ <div class="clear"></div>
+ </div>
+
+ </footer>
</body>
</html>
diff --git a/events.html b/events.html
index d420956..307d56c 100644
--- a/events.html
+++ b/events.html
@@ -9,7 +9,7 @@
<body>
<header>
<div class="logo-left width">
- <a href="index.html"><img src="images/chess-logo.png" alt="CHESS logo" width=""></a>
+ <a href="index.html"><img src="images/logo_chess_350.gif" alt="CHESS logo" width=""></a>
</div>
</header>
<nav>
@@ -43,7 +43,7 @@
<table>
<tr>
<th>
- PolarSys CHESS events coming soon!
+ CHESS events coming soon!
<!--
<h3>2015</h3>
<h5>June</h5>
@@ -76,63 +76,69 @@
<div class="clear"></div>
</div>
<footer>
- <div class="footer-content width">
+ <div class="footer-content width">
<ul>
- <li><h4>PolarSys</h4></li>
- <li><a href="http://www.polarsys.org/about-us">About</a></li>
- <li><a href="http://www.polarsys.org/contact-us">Contact Us</a></li>
- <li><a href="http://www.polarsys.org/projects/polarsys.chess">CHESS Project Page</a></li>
+ <li><h4>Eclipse Foundation</h4></li>
+ <li><a href="https://www.eclipse.org/org/">About</a></li>
+ <li><a href="https://www.eclipse.org/org/foundation/contact.php">Contact Us</a></li>
+ <li><a href="https://projects.eclipse.org/projects/polarsys.chess">CHESS
+ Project Page</a></li>
</ul>
- <ul>
- <li><h4>Legal</h4></li>
- <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
- <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
- <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
- <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a></li>
+ <ul>
+ <li><h4>Legal</h4></li>
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy
+ Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms
+ of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright
+ Agent</a></li>
+ <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse
+ Public License</a></li>
<li><a href="http://www.eclipse.org/legal/">Legal Resources</a></li>
- </ul>
+ </ul>
<ul>
<li><h4>Useful Links</h4></li>
- <li><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS">Report a Bug</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS">Documentation</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS/Technical_Information">How to Contribute</a></li>
- <li><a href="http://polarsys.org/mailman/listinfo/chess-dev">Mailing List</a></li>
- <li><a href="http://polarsys.org/forums/index.php/f/9/">Forum</a></li>
+ <li><a
+ href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess">Report
+ a Bug</a></li>
+ <li><a href="https://wiki.eclipse.org/CHESS">Documentation</a></li>
+ <li><a
+ href="https://wiki.eclipse.org/CHESS/Technical_Information">How
+ to Contribute</a></li>
+ <li><a href="https://accounts.eclipse.org/mailing-list/chess-dev">Mailing
+ List</a></li>
+ <li><a href="https://www.eclipse.org/forums/index.php/f/529/">Forum</a></li>
</ul>
<ul class="endfooter">
- <li><h4>Other</h4></li>
+ <li><h4>Other</h4></li>
+ <li><a href="https://es.fbk.eu/">Fondazione Bruno Kessler</a></li>
<li><a href="http://www.intecs.it/">Intecs</a></li>
<li><a href="http://www.unipd.it">University of Padova</a></li>
+ <li><a href="http://www.mdh.se/">Mälardalen University</a></li>
</ul>
<table>
<tr>
- <td>
- <a href="http://www.polarsys.org/"><img src="images/polarsys.png" alt="PolarSys logo" width="250"></a>
- <br />
- <br />
- </td>
+ <td><a href="https://www.yourkit.com"><img
+ src="images/yklogo.png" alt="YourKit logo"
+ style="width: 25%; height: 25%"></a> <br /> <font size="2">Thanks
+ YourKit for providing us free licenses of <a
+ href="https://www.yourkit.com/java/profiler/">YourKit Java
+ Profiler</a>
+ </font></td>
<td>
<div class="right-footer">
- <a href="http://www.eclipse.org/"><img src="images/eclipse.png" alt="Eclipse logo"></a>
- <br />
- Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br /> All Rights Reserved.
+ <a href="http://www.eclipse.org/"><img
+ src="images/eclipse.png" alt="Eclipse logo"></a> <br />
+ Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br />
+ All Rights Reserved.
</div>
</td>
- </tr>
- <tr>
- <td>
- <a href="https://www.yourkit.com"><img src="images/yklogo.png" alt="YourKit logo" style="width: 25%; height: 25%"></a>
- <br />
- <font size="2">Thanks YourKit for providing us free licenses of <a href="https://www.yourkit.com/java/profiler/">YourKit Java Profiler</a></font>
- </td>
- <td>
- </td>
- </tr>
+ </tr>
</table>
-
- <div class="clear"></div>
- </div>
-
- </footer>
+
+ <div class="clear"></div>
+ </div>
+
+ </footer>
</body>
</html>
\ No newline at end of file
diff --git a/features.html b/features.html
index c4b0dd5..248e4af 100644
--- a/features.html
+++ b/features.html
@@ -3,19 +3,20 @@
<link rel="icon" type="image/png" href="favicon.ico" />
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>CHESS</title>
- <link rel="stylesheet" href="styles.css" type="text/css" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>CHESS</title>
+<link rel="stylesheet" href="styles.css" type="text/css" />
</head>
<body>
- <header>
+ <header>
<div class="logo-left width">
- <a href="index.html"><img src="images/chess-logo.png" alt="CHESS logo" width=""></a>
+ <a href="index.html"><img src="images/logo_chess_350.gif"
+ alt="CHESS logo" width=""></a>
</div>
- </header>
- <nav>
-
+ </header>
+ <nav>
+
<div class="width">
<ul>
<li class="start"><a href="index.html">Home</a></li>
@@ -27,212 +28,597 @@
<li><a href="events.html">Events</a></li>
<li class="divider-vertical-second-menu"></li>
<li class="end"><a href="community.html">Community</a></li>
- <li style="text-align:right;"><a href="download.html" class="box">Download</a></li>
- <li style="float:none;"><br style="clear:both;" /></li>
- </ul>
+ <li style="text-align: right;"><a href="download.html"
+ class="box">Download</a></li>
+ <li style="float: none;"><br style="clear: both;" /></li>
+ </ul>
</div>
-
- </nav>
+
+ </nav>
<div id="hrdiv">
<img src="images/bg_breadcrumb.jpg" width="" alt="" height="" />
</div>
- <div id="body" class="width-started">
+ <div id="body" class="width-started">
<article class="expanded">
<ul class="tabs">
- <li>
- <input name="tabs" id="tab1" checked="" type="radio">
+ <li><input name="tabs" id="tab1" checked="" type="radio">
<label for="tab1">Features</label>
<div id="tab-content1" class="tab-content">
<p>
<h3>CHESS Profile</h3>
- <p>
- The CHESS UML profile:
- <ul class="listInTabs">
- <li>restricts the set of MARTE, SysML and UML entities that can be created in the CHESS model, </li>
- <li>provides the set of stereotypes required to enable the user to work with the CHESS
- component model, </li>
- <li>provides some MARTE stereotypes extensions to allow the specification of
- computation-independent real-time properties, </li>
- <li>defines a new set of stereotypes for the support of dependability modeling and contract-based design.</li>
- </ul>
- </p>
- <p>
- <h3>CHESS Editor</h3>
- <p>
- The CHESS editor extends the Papyrus UML editor and is activated when a CHESS model is created
- or opened (see <a href="#figure1">Figure 1</a>).
- </p>
- <p>
- A CHESS model is a UML model with the CHESS profile applied to it; creating a CHESS model and
- applying the CHESS profile can be done using a dedicated wizard.
- </p>
- <p>
- The CHESS editor allows working with the Papyrus UML by using the CHESS design views.
- Each design view applies specific constraints on the UML diagrams and entities that can be
- created, viewed or edited in that view.
- </p>
- <p>
- The CHESS editor allows switching between views. It also keeps the status of the current view
- and during the modeling activity prevents the modeler from violating the constraints defined for
- the current diagram-view pair.
- </p>
- <p>
- The native Papyrus palettes have been customized in order to show only the entities that are
- allowed to be created in the current diagram view.
- </p>
- <p>
- <h4>CHESS Views</h4>
- <p>
- The views defined in CHESS are the requirement, system, component, deployment and analysis views.
- </p>
- <p>
- The requirement view is used to model requirements by using the standard requirement diagram
- from SysML.
- </p>
- <p>
- </p>
- <p>
- The system view is used to model system entities by using SysML; it is an ongoing development
- that has been recently introduced in CHESS in order to support the system to software
- co-engineering phase.
- </p>
- <p>
- The component view is used to model CHESS software components (also called the PIM model):
- is actually composed by two sub-views, the functional and the extra-functional ones, according
- to the CHESS separation of concerns principle.
- </p>
- <p>
- The functional view allows the functional specification of the CHESS components (see <a href="#figure1">Figure 1</a>
- and <a href="#figure2">Figure 2</a>).
- </p>
- <p>
-
- <a id="figure1"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Component View Types" src="images/compFunViewTypes.png" width="85%"/></a>
- <div class="caption">Figure 1: Component View - Functional View - Component Types</div>
- </p>
- <p>
- <a id="figure2"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Component View Instances" src="images/compFunViewInstances.png" width="85%"/></a>
- <div class="caption">Figure 2: Component View - Functional View - Component Instances</div>
- </p>
- <p>
- The extra functional view (see <a href="#figure3">Figure 3</a>) allows the specification of real time properties
- like periodic and sporadic activation patterns, worst-case execution time and deadline.
- Regarding dependability it supports the specification of error models (i.e. fault-error-failure
- chains) for software and offers the possibility for the user to specify probabilistic values
- related to fault occurrence and failure propagation between components.
- </p>
- <p>
- <a id="figure3"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Component View Extra Functional View" src="images/compExtraFunViewInstances.jpg" width="85%"/></a>
- <div class="caption">Figure 3: Component View - Extra Functional View - Component Instances</div>
- </p>
- <p>
- The deployment view (<a href="#figure4">Figure 4</a>) is used to describe the hardware platform where the software runs
- (i.e. CPUs, buses) and software to hardware components allocation. Dependability properties can be
- provided for the hardware as for the software components. Moreover failures propagation from hardware to
- software can be specified.
- </p>
- <p>
- <a id="figure4"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Deployment View" src="images/deplView.jpg" width="85%"/></a>
- <div class="caption">Figure 4: Deployment View - HW Component instance and SW allocation</div>
- </p>
- <p>
- The analysis view (<a href="#figure5">Figure 5</a>) is used to provide information needed to run the specific analysis;
- in particular it is currently useful to set the information about the dependability measure of interest
- (i.e. reliability or availability) that needs to be evaluated.
- </p>
- <p>
- <a id="figure5"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Analysis View" src="images/analView.jpg" width="85%"/></a>
- <div class="caption">Figure 5: Analysis View</div>
- </p>
- <p>
- <h3>Model validator</h3>
- <p>
- For reasons of practicality, not all the constraints posed by the CHESS methodology on the model
- formalisms and contents can be enforced on the fly during user modeling; some of them must be
- checked in a batch mode. To this end the CHESS editor extends the standard UML model validator
- which ad-hoc checks that the user model conforms with the constraints imposed by the CHESS
- methodology, for example the well-formedness of entities, attributes, relations.
- </p>
- <p>
- <a id="figure6"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="Invoking CHESS model validator" src="images/callModelValidator.png" width="85%"/></a>
- <div class="caption">Figure 6: Invoking CHESS model validator</div>
- </p>
- <p>
- <h3>Model transformations</h3>
- <p>
- CHESS supports model-based analysis of the systems for schedulability, dependability, as
- well as code generation from model. Both features are implemented through model transformations
- which are invoked through the CHESS editor menu.
- <p>
- Dependability analysis currently supported are:
- <ul class="listInTabs">
- <li>failure propagation analysis,</li>
- <li>state-based quantitative analysis.</li>
- </ul>
- </p>
- Integration with OCRA external tool for formal verification of contract refinement is implemented.
- </p>
- <h4>Schedulability Analysis and Ada 2005 Code Generation</h4>
- <p>
- Schedulability analysis allows the calculation of the worst case response time for each declared
- periodic or sporadic activity. The analysis results are back propagated to the proper PIM
- components, also a summary report is provided to the user (see <a href="#figure7">Figure 7</a>). The intent of the
- back-propagation feature is that the user need not be concerned with the specifics of the
- analysis tool and need not learn its input and output formats: back-propagation decorates
- the user model with the relevant information that results from the analysis in full transparency
- from the analysis engine and its actual operation.
- </p>
- <p>
- <a id="figure7"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Schedulability Analysis Report" src="images/schedAnalReport.png" width="85%"/></a>
- <div class="caption">Figure 7: Schedulability Analysis Report</div>
- </p>
- <p>
- The real-time properties of interest like period, offset and minimal inter-arrival time are
- specified in the model through a dedicated declarative language defined in the CHESS profile.
- The aforementioned properties are then automatically applied to the model implementation through
- model transformation in accord with the computational model chosen by the user. At the present
- time, CHESS supports the Ravenscar Computational Model [1] which meets the requirements of a
- large spectrum of real-time application domains. The generated implementation (called the PSM,
- for platform-specific model) is then given in input to the schedulability analysis and it also
- used during the code generation phase:
- </p>
- <p>
- The preservation of other real-time properties related to the execution time like WCET and
- deadline is also enforced in the generated code through dedicated checks by using specific
- API of the target run-time environment (this feature is an on-going development).
- </p>
- <p>
- This approach guarantees the preservation of the real-time properties statically assumed in the
- PIM and PSM models, and verified by the analysis down to the code.
- </p>
- <p>
- The schedulability analysis is performed by using an adaptation of the third-party MAST tool
- developed and distributed by the University of Cantabria [2].
- </p>
- <p>
- Regarding the transformation chain (<a href="#figure8">Figure 8</a>), first the CHESS PIM is transformed into the
- PSM model by using QVT-o. Then the PSM is transformed into the MAST input by using Acceleo and
- Java. Regarding the back propagation, Java is used first to load the MAST results into the PSM,
- then QVT-o traces are used to propagate the results back to the PIM model.
- </p>
- <p>
- <a id="figure8"><img style="background: #fff; box-shadow: 0px 0px 6px #111;" alt="CHESS Transformation chain" src="images/transChain.png" width="85%"/></a>
- <div class="caption">Figure 8: Transformation chain</div>
- </p>
- <p>
- [1]A. Burns, B. Dobbing, T. Vardanega. Guide to the Use of the Ada Ravenscar Profile in High Integrity Systems. Technical Report YCS-2003-348. University of York (UK), 2003. Available at <a href="http://www.sigada.org/ada_letters/jun2004/ravenscar_article.pdf"> http://www.sigada.org/ada_letters/jun2004/ravenscar_article.pdf.</a> </br>
-
-
- [2]Universidad de Cantabria. Mast: Modeling and Analysis Suite for Real-Time Applications. <a href="http://mast.unican.es/"> http://mast.unican.es/</a>
-
- </p>
- </li>
-
-
-
-
+ <p>The CHESS UML profile:
+ <ul class="listInTabs">
+ <li>restricts the set of MARTE, SysML and UML entities that
+ can be created in the CHESS model,</li>
+ <li>provides the set of stereotypes required to enable the
+ user to work with the CHESS component model,</li>
+ <li>provides some MARTE stereotypes extensions to allow the
+ specification of computation-independent real-time properties,</li>
+ <li>defines a new set of stereotypes for the support of
+ dependability modeling and contract-based design.</li>
+ </ul>
+ <p></p>
+ <p>
+ <h3>CHESS Editor</h3>
+ <p>
+ The CHESS editor extends the Papyrus UML editor and is activated
+ when a CHESS model is created or opened (see <a href="#figure1">Figure
+ 1</a>).
+ </p>
+ <p>A CHESS model is a UML model with the CHESS profile applied
+ to it; creating a CHESS model and applying the CHESS profile can
+ be done using a dedicated wizard.</p>
+ <p>The CHESS editor allows working with the Papyrus UML by
+ using the CHESS design views. Each design view applies specific
+ constraints on the UML diagrams and entities that can be created,
+ viewed or edited in that view.</p>
+ <p>The CHESS editor allows switching between views. It also
+ keeps the status of the current view and during the modeling
+ activity prevents the modeler from violating the constraints
+ defined for the current diagram-view pair.</p>
+ <p>The native Papyrus palettes have been customized in order
+ to show only the entities that are allowed to be created in the
+ current diagram view.</p>
+ <p>
+ <h4>CHESS Views</h4>
+ <p>The views defined in CHESS are the requirement, system,
+ component, deployment and analysis views.</p>
+ <p>The requirement view is used to model requirements by using
+ the standard requirement diagram from SysML.</p>
+ <p></p>
+ <p>The system view is used to model system entities by using
+ SysML; it is an ongoing development that has been recently
+ introduced in CHESS in order to support the system to software
+ co-engineering phase.</p>
+ <p>The component view is used to model CHESS software
+ components (also called the PIM model): is actually composed by
+ two sub-views, the functional and the extra-functional ones,
+ according to the CHESS separation of concerns principle.</p>
+ <p>
+ The functional view allows the functional specification of the
+ CHESS components (see <a href="#figure1">Figure 1</a> and <a
+ href="#figure2">Figure 2</a>).
+ </p>
+ <p>
+
+ <a id="figure1"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Component View Types"
+ src="images/compFunViewTypes.png" width="85%" class="center"/></a>
+ <div class="caption">Figure 1: Component View - Functional
+ View - Component Types</div>
+ </p>
+ <p>
+ <a id="figure2"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Component View Instances"
+ src="images/compFunViewInstances.png" width="85%" class="center"/></a>
+ <div class="caption">Figure 2: Component View - Functional
+ View - Component Instances</div>
+ </p>
+ <p>
+ The extra functional view (see <a href="#figure3">Figure 3</a>)
+ allows the specification of real time properties like periodic
+ and sporadic activation patterns, worst-case execution time and
+ deadline. Regarding dependability it supports the specification
+ of error models (i.e. fault-error-failure chains) for software
+ and offers the possibility for the user to specify probabilistic
+ values related to fault occurrence and failure propagation
+ between components.
+ </p>
+ <p>
+ <a id="figure3"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Component View Extra Functional View"
+ src="images/compExtraFunViewInstances.jpg" width="85%" class="center"/></a>
+ <div class="caption">Figure 3: Component View - Extra
+ Functional View - Component Instances</div>
+ </p>
+ <p>
+ The deployment view (<a href="#figure4">Figure 4</a>) is used to
+ describe the hardware platform where the software runs (i.e.
+ CPUs, buses) and software to hardware components allocation.
+ Dependability properties can be provided for the hardware as for
+ the software components. Moreover failures propagation from
+ hardware to software can be specified.
+ </p>
+ <p>
+ <a id="figure4"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Deployment View" src="images/deplView.jpg"
+ width="85%" class="center"/></a>
+ <div class="caption">Figure 4: Deployment View - HW
+ Component instance and SW allocation</div>
+ </p>
+ <p>
+ The analysis view (<a href="#figure5">Figure 5</a>) is used to
+ provide information needed to run the specific analysis; in
+ particular it is currently useful to set the information about
+ the dependability measure of interest (i.e. reliability or
+ availability) that needs to be evaluated.
+ </p>
+ <p>
+ <a id="figure5"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Analysis View" src="images/analView.jpg" width="85%" class="center"/></a>
+ <div class="caption">Figure 5: Analysis View</div>
+ </p>
+ <p>
+ <h3>Contract-based design</h3>
+ <p>The contract-based design enriches the system architecture
+ model with expressions asserting the expected properties of the
+ system, its components and environment. In order to allow
+ compositional reasoning, the property of a component are
+ restricted to its interface considering the component as a black
+ box (without constraining the internal variables of the
+ component) and are structured into contracts, pairs of properties
+ representing an assumption and a guarantee of the component: an
+ assumption is an assertion on the behaviour of the component
+ environment, while a guarantee is an assertion on the behaviour
+ of the component provided that the entire set of assumptions
+ holds.</p>
+ <p>The contract specification can further be enriched by
+ categorising contracts into strong and weak to allow for better
+ support for specification of reusable components behaviour. Such
+ components are intended to work in different environments, and
+ often exhibit environment-specific behaviours and assumptions.</p>
+ <h3>Model validator</h3>
+ <p>For reasons of practicality, not all the constraints posed
+ by the CHESS methodology on the model formalisms and contents can
+ be enforced on the fly during user modeling; some of them must be
+ checked in a batch mode. To this end the CHESS editor extends the
+ standard UML model validator which ad-hoc checks that the user
+ model conforms with the constraints imposed by the CHESS
+ methodology, for example the well-formedness of entities,
+ attributes, relations.</p>
+ <p>
+ <a id="figure6"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="Invoking CHESS model validator"
+ src="images/callModelValidator.png" width="85%" class="center"/></a>
+ <div class="caption">Figure 6: Invoking CHESS model
+ validator</div>
+ </p>
+ <p>
+ <h3>Model transformations</h3>
+ <p>CHESS supports model-based analysis of the systems for
+ schedulability, dependability, as well as code generation from
+ model. Both features are implemented through model
+ transformations which are invoked through the CHESS editor menu.
+
+
+
+
+ <p>Dependability analysis currently supported are:
+ <ul class="listInTabs">
+ <li>failure propagation analysis,</li>
+ <li>state-based quantitative analysis.</li>
+ </ul>
+ </p>
+ Integration with OCRA external tool for formal verification of
+ contract refinement is implemented.
+ </p>
+ <h4>Schedulability Analysis and Ada 2005 Code Generation</h4>
+ <p>
+ Schedulability analysis allows the calculation of the worst case
+ response time for each declared periodic or sporadic activity.
+ The analysis results are back propagated to the proper PIM
+ components, also a summary report is provided to the user (see <a
+ href="#figure7">Figure 7</a>). The intent of the
+ back-propagation feature is that the user need not be concerned
+ with the specifics of the analysis tool and need not learn its
+ input and output formats: back-propagation decorates the user
+ model with the relevant information that results from the
+ analysis in full transparency from the analysis engine and its
+ actual operation.
+ </p>
+ <p></p>
+ <a id="figure7"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Schedulability Analysis Report"
+ src="images/schedAnalReport.png" width="85%" class="center"/></a>
+ <div class="caption">Figure 7: Schedulability Analysis
+ Report</div>
+ <p></p>
+ <p>The real-time properties of interest like period, offset
+ and minimal inter-arrival time are specified in the model through
+ a dedicated declarative language defined in the CHESS profile.
+ The aforementioned properties are then automatically applied to
+ the model implementation through model transformation in accord
+ with the computational model chosen by the user. At the present
+ time, CHESS supports the Ravenscar Computational Model [1] which
+ meets the requirements of a large spectrum of real-time
+ application domains. The generated implementation (called the
+ PSM, for platform-specific model) is then given in input to the
+ schedulability analysis and it also used during the code
+ generation phase:</p>
+ <p>The preservation of other real-time properties related to
+ the execution time like WCET and deadline is also enforced in the
+ generated code through dedicated checks by using specific API of
+ the target run-time environment (this feature is an on-going
+ development).</p>
+ <p>This approach guarantees the preservation of the real-time
+ properties statically assumed in the PIM and PSM models, and
+ verified by the analysis down to the code.</p>
+ <p>The schedulability analysis is performed by using an
+ adaptation of the third-party MAST tool developed and distributed
+ by the University of Cantabria [2].</p>
+ <p>
+ Regarding the transformation chain (<a href="#figure8">Figure
+ 8</a>), first the CHESS PIM is transformed into the PSM model by
+ using QVT-o. Then the PSM is transformed into the MAST input by
+ using Acceleo and Java. Regarding the back propagation, Java is
+ used first to load the MAST results into the PSM, then QVT-o
+ traces are used to propagate the results back to the PIM model.
+ </p>
+ <p>
+ <a id="figure8"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="CHESS Transformation chain" src="images/transChain.png"
+ width="85%" class="center"/></a>
+ <div class="caption">Figure 8: Transformation chain</div>
+ <p></p>
+ <p>
+ [1]A. Burns, B. Dobbing, T. Vardanega. Guide to the Use of the
+ Ada Ravenscar Profile in High Integrity Systems. Technical Report
+ YCS-2003-348. University of York (UK), 2003. Available at <a
+ href="http://www.sigada.org/ada_letters/jun2004/ravenscar_article.pdf">
+ http://www.sigada.org/ada_letters/jun2004/ravenscar_article.pdf.</a>
+ <br> [2]Universidad de Cantabria. Mast: Modeling and
+ Analysis Suite for Real-Time Applications. <a
+ href="http://mast.unican.es/"> http://mast.unican.es/</a>
+
+ </p></li>
+
+ <li><input name="tabs" id="tab2" type="radio"> <label
+ for="tab2">System-Level Design</label>
+ <div id="tab-content2" class="tab-content">
+ <h2>System Design</h2>
+ <h3>System Definition</h3>
+ <h4>Requirements Specification</h4>
+ <p>Requirements can be represented in the model by using the
+ SysML standard support, i.e. by using the Requirements Diagram
+ and Requirement SysML construct. CHESS comes with a dedicated
+ view/package called “RequirementView”, where the SysML
+ Requirement Diagram and then the requirements can be created.
+
+ Requirements available in the CHESS model can then be linked to
+ other architectural entities by using the standard SysML support,
+ so in particular by allocating requirements to components using
+ the Satisfy relationships.</p>
+ <h4>System Component Definition</h4>
+ <p>During this activity, the architecture of the system, i.e.
+ its constituent components and their relationships, is produced.
+ The definition of the system architecture foresees the design of
+ components in isolation, i.e. components designed out of any
+ particular context (to exploit their reuse), or the
+ identification (reuse) of the components from existing
+ libraries/models. The hierarchical modelling of the entire system
+ architecture is supported to be able to manage the complexity of
+ the system itself, where the hierarchy can be obtained by using a
+ top-down or bottom-up design process, where the later in
+ particular can be realized by following a design by reuse
+ approach.</p>
+ <p>A component must come with typed input/output ports
+ representing the boundary of the component itself, where ports
+ represent interaction points through which the component can
+ exchange information with the context. It is worth noting that
+ the modelling of the component boundary cannot be limited to the
+ identification of the input/output ports of the component itself;
+ additional information about the possible (functional and
+ extra-functional) behaviours of the component and the expected
+ behaviours of the context must be provided, e.g. to be able to
+ evaluate if a given component can collaborate in a given
+ scenario. This relevant part of the specification of the
+ component boundary can be performed by using the contract-based
+ approach. When a component has been defined, then it can be
+ instantiated as part of the given system under design and
+ connected to the other instances already identified.</p>
+ <p>The system is modelled, i.e. it is decomposed, as a
+ collaboration of instances of components. The decomposition of
+ the architecture can proceed at any level, i.e. a system
+ component can be also decomposed, according to its complexity.
+ Different instances of the same component (and different ports
+ with the same type) can be represented as a single instance with
+ multiplicity greater than 1. SysML, the OMG general-purpose
+ modelling language for systems engineering, is proposed in CHESS
+ for the modelling of the system and its constituent components.
+ In particular, SysML Block Definition Diagram is used to model
+ the system and its components, while a SysML Internal Block
+ Diagram can be associated to the system or component and used to
+ model its input/output ports, its decomposition into parts and
+ how the parts are connected.</p>
+
+ <h3>Requirements Formalization</h3>
+ <p>This activity has the goal of translating the informal
+ requirements allocated to system components into formal
+ properties. Formal properties are textual expressions specified
+ in a restricted grammar so that their semantics is formally
+ defined (in rigorous mathematical terms). Such expressions refer
+ to the elements of the system component interface defined in the
+ previous activity. CHESS supports the specification of
+ well-formed formal properties with the help of an automated
+ completion feature that suggests the possible continuations of a
+ partial specification. Formal properties can be further
+ structured into contracts.</p>
+
+ <a id="figure1"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="Property Editor with “completion assistance”"
+ src="images/contract-editor.png" width="85%" class="center"/></a>
+ <div class="caption">Property Editor with “completion
+ assistance”</div>
+
+ <h3>Requirements Early Validation</h3>
+ <p>This validation is done by checking if a specific guarantee
+ of the contract satisfies the assumption of another contract.</p>
+
+ <h3>Functional Refinement</h3>
+ <p>The architectural refinement defines in detail how the
+ different parts of the system are connected and interact to
+ fulfill the system requirements. To refine the architecture, the
+ sub-requirements and sub-components of the system must be
+ identified. Allocation of requirements/sub-requirements to
+ sub-components must be managed, as well as formalization of
+ sub-requirements. In case of reuse of components (as
+ sub-components), associated satisfied requirements and
+ implemented contracts are reused. Information about requirements
+ refinement can be managed in CHESS by using the SysML standard
+ support.</p>
+
+ <h4>Parameters and Configurations</h4>
+ <p>The parameterization of an architecture is the procedure to
+ define and use a (possibly infinite) set of parameters to set the
+ number of components, the number of ports, the connections, and
+ the static attributes of components. The instantiation of an
+ architecture is the procedure to assign the values of the
+ parameters used in the input parameterized architecture. The
+ outcome is an architecture with a fixed number of components,
+ ports, connections, and static attributes of components.</p>
+
+ <h4>Contract Refinement</h4>
+ <p>The contract refinement requires one prior phase, the
+ definition of the contract. Contracts refinement must follow the
+ requirements refinement. Indeed, a contract is implicitly linked
+ to the formalized requirements (via its assumption and guarantee
+ properties); so, the requirements referred by contracts appearing
+ in a refinement relationship should also have a corresponding
+ refinement traced.</p>
+ <h3>Component’s Nominal and Faulty Behaviour Definition</h3>
+ <p>System component static definition, i.e. its properties,
+ ports, contracts, can be enriched with behavioural models by
+ means of UML state machine diagrams. In CHESS, state machine
+ diagrams can be used to model the nominal and the faulty
+ behaviour of the component. Nominal state machine are basically
+ standard UML ones. In CHESS, by using a subset of the UML support
+ for state machine modelling, it is also possible to use model
+ transformation to automatically generate an SMV (the input
+ language of nuXmv) representation of the modelled nominal state
+ machines, together with the components structure definition (this
+ is then used to perform automatic generation of fault tree. In
+ nominal state machines, each transition comes with a guard and an
+ effect. The guard is a boolean condition upon the values of
+ components properties. The effect must be expressed by using the
+ SMV language, to model component properties assignment.</p>
+
+ <a id="figure1"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="Example of nominal state machine" src="images/chess-FSM.png"
+ width="85%" class="center"/></a>
+ <div class="caption">Example of nominal state machine (using
+ SMV as action language)</div>
+
+ <p>The behavioural model of the component can be enriched with
+ the faulty behaviour. Faulty behaviour is modelled in CHESS by
+ using the dedicated dependability profile. The CHESS
+ dependability profile enables dependability architects to model
+ dependability information necessary to conduct dependability
+ analysis, basically by allowing the modelling of failure modes
+ and criticality, the failure behaviours for a component in
+ isolation (so how events can lead to components failure modes)
+ and the failure modes propagation between connected components
+ (via components ports).</p>
+
+ <h3>Functional Early Verification</h3>
+ <h4>Contract-Based Verification of Refinement</h4>
+
+ <p>If assumptions and guarantees are formal properties, which
+ means they are specified in a formal language such as some
+ specific kind of temporal logic, the architectural decomposition
+ can be verified by checking that the contract refinement is
+ correct: this consists of checking that, for all composite
+ components, the contract of the composite component is ensured by
+ the contracts of the subcomponents –considering their
+ interconnection as described by the architecture -and that the
+ assumption of each subcomponent is ensured by the contracts of
+ the other sibling subcomponents and the assumption of the
+ composite component.</p>
+ <a id="figure2"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="An example of the result of the check
+ contract refinement shown in the Trace View."
+ src="images/contract-refinement.png" width="85%" class="center"/></a>
+ <div class="caption">An example of the result of the check
+ contract refinement shown in the Trace View. In this case, it is
+ possible to see that one refinement is failed, and the counter
+ example.</div>
+
+ <h4>Contract-based Verification of Refinement for Strong and
+ Weak Contracts</h4>
+
+ <p>Strong and weak contracts are introduced to support
+ out-of-context reasoning and component reuse across variety of
+ environments. While strong contracts must hold in all
+ environments, the weak ones are environment-specific. Prior to
+ performing the refinement check using strong and weak contracts,
+ contracts must be created and allocated to the component types,
+ which represent out-of-context components. At the component type
+ level, the user indicates if a contract is strong or weak. When
+ the component type is instantiated in a particular system to a
+ component instance, all the strong, and a subset of weak
+ contracts can be identified as relevant in the particular system
+ in which the component is instantiated. Identifying which are
+ those relevant weak contracts can be done manually on the
+ component instance level.</p>
+
+ <h4>Contract-Based Verification of State Machines</h4>
+
+
+ <p>As a further verification step, CHESS enables to verify
+ whether the behavioural specification of the system, specified by
+ state machines, is compliant with the contract specification.</p>
+ <p>
+ <a id="figure3"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="An example of the result of the check contract implementation shown in the “Trace” view. "
+ src="images/contract-implementation.png" width="85%" class="center"/></a>
+ <div class="caption">An example of the result of the check
+ contract implementation shown in the “Trace” view. It is possible
+ to see that four contracts are not satisfied by the state
+ machines of their associated component and one contract not.</div>
+
+ <h4>Model Checking</h4>
+
+ <p>Besides the verification of contracts, the user may want to
+ verify other properties on the state machine. The specifications
+ to be checked on the FSM can be expressed in temporal logics like
+ Computation Tree Logic (CTL), Linear Temporal Logic (LTL)
+ extended with Past Operators, and Property Specification Language
+ (PSL) that includes CTL and LTL with Sequential Extended Regular
+ Expressions (SERE), a variant of classical regular expressions.
+ It is also possible to analyse quantitative characteristics of
+ the FSM by specifying real-time CTL specifications.</p>
+ <p>CTL and LTL specifications are evaluated by nuXmv to
+ determine their truth or falsity in the FSM. When a specification
+ is discovered to be false, nuXmv constructs and prints a
+ counterexample, i.e. a trace of the FSM that falsifies the
+ property.</p>
+ <p>There are three possible model checking available:</p>
+ <ul class="listInTabs">
+ <li>check ctlspec: it performs fair CTL model checking. A
+ CTL specification is given as a formula in the temporal logic
+ CTL. A CTL formula is true if it is true in all initial states.
+ </li>
+ <li>check invar: it performs model checking of invariants.
+ Invariants are propositional formulas which must hold
+ invariantly in the model.</li>
+ <li>check ltlspec: it performs LTL model checking. An LTL
+ formula is true if it is true at the initial time.</li>
+ </ul>
+ <h2>Safety Analysis</h2>
+ <h3>Model-Based Safety Analysis</h3>
+ <h4>Fault injection</h4>
+ <p>The faulty behaviour for a component is provided through a
+ state machine, the latter tagged with the
+ <<ErrorModel>> stereotype defined in the CHESS
+ dependability profile13. In the error model, the information
+ about the error states can be provided by using the
+ <<ErrorState>> stereotype. Then, for a given error
+ state, the effect upon a property of the component, and so the
+ effect on its nominal behaviour, can be also provided by using
+ pre-defined effects:</p>
+ <ul class="listInTabs">
+ <li>StuckAt: models the effect of being stuck at a fixed
+ value.
+ <li>StuckAtFixed: models the effect of being stuck at a
+ fixed random value.</li>
+ <li>Inverted: models the effect of being stuck at the
+ inverted last value.</li>
+ <li>RampDown: models the effect of decreasing the value of a
+ property by a certain value.</li>
+ </ul>
+ <a id="figure1"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="State machine modelling faulty behaviour"
+ src="images/chess-fault-injection.png" width="85%" class="center"/></a>
+ <div class="caption">State machine modelling faulty
+ behaviour</div>
+ <h4>Fault-tree generation and FMEA generation</h4>
+ <p>Once the system architecture has been provided, by mean of
+ components definition and their nominal and error models, the
+ fault tree generation can be obtained by invoking the xSAP
+ symbolic model checker through the CHESS environment. Please
+ refer to the CHESS User Manual for instructions on how to
+ configure the analysis.</p>
+ <p>Once the analysis is executed, the fault tree is
+ automatically shown in a dedicated panel in the frontend. If
+ fault probabilities have been specified during the configuration
+ of the error model, the fault tree will report their combination.
+ The fault tree can be examined, in particular the minimal cut-set
+ and so the basic fault conditions which can led to the top-level
+ failure.</p>
+ <a id="figure1"><img
+ style="background: #fff; box-shadow: 0px 0px 6px #111;"
+ alt="A fault tree visualized in the CHESS Editor View"
+ src="images/chess-FTA.png" width="85%" class="center"/></a>
+ <div class="caption">A fault tree visualized in the CHESS
+ Editor View; note the probabilities associated to the top and
+ basic events</div>
+ <p>Along with the fault-tree generation, it is possible to
+ generate the FMEA table. FMEA analysis is configured in a similar
+ mode as the fault-tree analysis, see the CHESS User Manual for
+ details.</p>
+ <h3>Contract-Based Safety Analysis</h3>
+ <p>The contract-based safety analysis identifies the component
+ failures as the failure of its implementation in satisfying the
+ contract. When the component is composite, its failure can be
+ caused by the failure of one or more subcomponents and/or the
+ failure of the environment in satisfying the assumption. As
+ result, this analysis produces a fault tree in which each
+ intermediate event represents the failure of a component or its
+ environment and is linked to a Boolean combination of other
+ nodes; the top-level event is the failure of the system
+ component, while the basic events are the failures of the leaf
+ components and the failure of the system environment.</p>
+
+ <h2>Safety Case</h2>
+ <p>In most industries, a well-structured Safety-Case, i.e. a
+ concluding argument that the system to be released for public
+ usage is sufficiently safe, is required by safety standards and
+ certification authorities. Standards mentioning the obligation
+ for a Safety Case include IEC 61508, ISO 26262 and many more. The
+ notion of a Safety Case is not formally defined by the standards
+ and therefore varies among different standards, regions and
+ industry branches – it can even depend on the company who creates
+ it or on the safety assessor or local certification authority.
+ Where this term is in use, it refers at least to a collection of
+ all relevant output documents from the safety process, from which
+ an external assessor can conclude that everything has been done
+ to assure that the product is safe in its practical application.</p>
+
+ <h3>Document Generation</h3>
+ <p>As part of the evidences to be used at support of the
+ safety case, the tool can generate a document summarizing the
+ modelling of the system components and the verification,
+ validation, and analysis results. The generated document is
+ composed by a list of sections. The first section includes the
+ diagrams that are not associated to a specific component, such as
+ the block definition diagrams.</p>
+ </div></li>
+
+
<!--li>
<input name="tabs" id="tab2" type="radio">
<label for="tab2">Example</label>
@@ -255,71 +641,81 @@
</p>
</div>
</li-->
-
+
</ul>
- </article>
- </div>
-
+ </article>
+ </div>
+
<div class="clear"></div>
-
- <footer id="footer-features">
- <div class="footer-content width">
+
+ <footer id="footer-features">
+ <div class="footer-content width">
<ul>
- <li><h4>PolarSys</h4></li>
- <li><a href="http://www.polarsys.org/about-us">About</a></li>
- <li><a href="http://www.polarsys.org/contact-us">Contact Us</a></li>
- <li><a href="http://www.polarsys.org/projects/polarsys.chess">CHESS Project Page</a></li>
+ <li><h4>Eclipse Foundation</h4></li>
+ <li><a href="https://www.eclipse.org/org/">About</a></li>
+ <li><a
+ href="https://www.eclipse.org/org/foundation/contact.php">Contact
+ Us</a></li>
+ <li><a
+ href="https://projects.eclipse.org/projects/polarsys.chess">CHESS
+ Project Page</a></li>
</ul>
- <ul>
- <li><h4>Legal</h4></li>
- <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
- <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
- <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
- <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a></li>
+ <ul>
+ <li><h4>Legal</h4></li>
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy
+ Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms
+ of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright
+ Agent</a></li>
+ <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse
+ Public License</a></li>
<li><a href="http://www.eclipse.org/legal/">Legal Resources</a></li>
- </ul>
- <ul>
- <li><h4>Useful Links</h4></li>
- <li><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS">Report a Bug</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS">Documentation</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS/Technical_Information">How to Contribute</a></li>
- <li><a href="http://polarsys.org/mailman/listinfo/chess-dev">Mailing List</a></li>
- <li><a href="http://polarsys.org/forums/index.php/f/9/">Forum</a></li>
- </ul>
+ </ul>
+ <ul>
+ <li><h4>Useful Links</h4></li>
+ <li><a
+ href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess">Report
+ a Bug</a></li>
+ <li><a href="https://wiki.eclipse.org/CHESS">Documentation</a></li>
+ <li><a
+ href="https://wiki.eclipse.org/CHESS/Technical_Information">How
+ to Contribute</a></li>
+ <li><a
+ href="https://accounts.eclipse.org/mailing-list/chess-dev">Mailing
+ List</a></li>
+ <li><a href="https://www.eclipse.org/forums/index.php/f/529/">Forum</a></li>
+ </ul>
<ul class="endfooter">
<li><h4>Other</h4></li>
+ <li><a href="https://es.fbk.eu/">Fondazione Bruno Kessler</a></li>
<li><a href="http://www.intecs.it/">Intecs</a></li>
<li><a href="http://www.unipd.it">University of Padova</a></li>
+ <li><a href="http://www.mdh.se/">Mälardalen University</a></li>
</ul>
<table>
<tr>
- <td>
- <a href="http://www.polarsys.org/"><img src="images/polarsys.png" alt="PolarSys logo" width="250"></a>
- <br />
- <br />
- </td>
+ <td><a href="https://www.yourkit.com"><img
+ src="images/yklogo.png" alt="YourKit logo"
+ style="width: 25%; height: 25%"></a> <br /> <font size="2">Thanks
+ YourKit for providing us free licenses of <a
+ href="https://www.yourkit.com/java/profiler/">YourKit Java
+ Profiler</a>
+ </font></td>
<td>
<div class="right-footer">
- <a href="http://www.eclipse.org/"><img src="images/eclipse.png" alt="Eclipse logo"></a>
- <br />
- Copyright © <span id="year">2016</span> The Eclipse Foundation. <br /> All Rights Reserved.
+ <a href="http://www.eclipse.org/"><img
+ src="images/eclipse.png" alt="Eclipse logo"></a> <br />
+ Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br />
+ All Rights Reserved.
</div>
</td>
</tr>
- <tr>
- <td>
- <a href="https://www.yourkit.com"><img src="images/yklogo.png" alt="YourKit logo" style="width: 25%; height: 25%"></a>
- <br />
- <font size="2">Thanks YourKit for providing us free licenses of <a href="https://www.yourkit.com/java/profiler/">YourKit Java Profiler</a></font>
- </td>
- <td>
- </td>
- </tr>
</table>
-
- <div class="clear"></div>
- </div>
-
- </footer>
+
+ <div class="clear"></div>
+ </div>
+
+ </footer>
</body>
</html>
\ No newline at end of file
diff --git a/images/Parsley.JPG b/images/Parsley.JPG
new file mode 100644
index 0000000..d993642
--- /dev/null
+++ b/images/Parsley.JPG
Binary files differ
diff --git a/images/chess-FSM.png b/images/chess-FSM.png
new file mode 100644
index 0000000..8953b8c
--- /dev/null
+++ b/images/chess-FSM.png
Binary files differ
diff --git a/images/chess-FTA.png b/images/chess-FTA.png
new file mode 100644
index 0000000..9b3ceb1
--- /dev/null
+++ b/images/chess-FTA.png
Binary files differ
diff --git a/images/chess-fault-injection.png b/images/chess-fault-injection.png
new file mode 100644
index 0000000..ad3421d
--- /dev/null
+++ b/images/chess-fault-injection.png
Binary files differ
diff --git a/images/contract-editor.png b/images/contract-editor.png
new file mode 100644
index 0000000..957d0af
--- /dev/null
+++ b/images/contract-editor.png
Binary files differ
diff --git a/images/contract-implementation.png b/images/contract-implementation.png
new file mode 100644
index 0000000..24b6bfb
--- /dev/null
+++ b/images/contract-implementation.png
Binary files differ
diff --git a/images/contract-refinement.png b/images/contract-refinement.png
new file mode 100644
index 0000000..0fc093a
--- /dev/null
+++ b/images/contract-refinement.png
Binary files differ
diff --git a/images/installingChess.jpg b/images/installingChess.jpg
index 143164c..2d0a76a 100644
--- a/images/installingChess.jpg
+++ b/images/installingChess.jpg
Binary files differ
diff --git a/images/installingEnvironment1.jpg b/images/installingEnvironment1.jpg
index ae04950..1b1d482 100644
--- a/images/installingEnvironment1.jpg
+++ b/images/installingEnvironment1.jpg
Binary files differ
diff --git a/images/installingPapyrus.jpg b/images/installingPapyrus.jpg
index bc1dfb0..f582e5d 100644
--- a/images/installingPapyrus.jpg
+++ b/images/installingPapyrus.jpg
Binary files differ
diff --git a/index.html b/index.html
index b8d0297..fc159b1 100644
--- a/index.html
+++ b/index.html
@@ -11,7 +11,7 @@
<body>
<header>
<div class="logo-left width">
- <a href="index.html"><img src="images/chess-logo.png" alt="CHESS logo" width=""></a>
+ <a href="index.html"><img src="images/logo_chess_350.gif" alt="CHESS logo" width=""></a>
</div>
</header>
<nav>
@@ -46,7 +46,7 @@
<table>
<tr>
<th>
- <h3>A new version of the PolarSys CHESS toolset is available! See the <a href="start.html"><b>getting started page</b>.</a></h3>
+ <h3>A new version of the CHESS toolset is available! See the <a href="start.html"><b>getting started page</b>.</a></h3>
<!--
<ul>
@@ -90,22 +90,20 @@
components at the level of component design down to the execution level.
</p>
<p>
- CHESS also addresses the description and verification of system and component dependability
- properties (like fault, error, failures and failures propagations) through a dedicated UML profile for dependability
- and seamless integration with embedded and external dependability tools enabling failure propagation and
- state based analysis.
+ CHESS enables the design of safety-critical systems implementing the contract-based paradigm. The structural and behavioural aspects are verified interacting respectively with contract-based verification tools (such as <a href="https://ocra.fbk.eu/">OCRA</a>) and model checking tools (such as <a href="https://nuxmv.fbk.eu/">nuXmv</a>).
</p>
<p>
- CHESS also provides a profile allowing contract-based design and dedicated model transformation enabling
- seamless integration with external tools for the verification of contracts specification.
- </p>
+ CHESS also addresses the description and verification of system and component dependability
+ properties (like fault, error, failures and failures propagations) through a dedicated UML profile for dependability
+ and seamless integration with embedded and external dependability tools, such as <a href="https://xsap.fbk.eu/">xSAP</a>, enabling failure propagation and
+ state based analysis.
+ </p>
<p>
CHESS tooling extends Papyrus editor to properly support the CHESS methodology, in particular
allowing working with different views on the model including requirements, system, components,
deployment and analysis view.
</p>
-
-
+
<h3>Description</h3>
<p>
CHESS implements the CHESS UML/SysML profile, a specialization of the Modeling and Analysis of
@@ -134,17 +132,9 @@
<li>
<h4>News</h4>
<ul>
- <li><b>CHESS tool v.0.10.0 is available!</b></li>
+ <li><b>CHESS tool v.1.0.0 is available!</b></li>
</ul>
- </li>
- <li>
- <br />
-
- <a href="http://www.eclipse.org/projects/what-is-incubation.php"><img src="images/egg-incubation.png" alt="incubation"/></a>
-
-
- </li>
-
+ </li>
</ul>
</aside>
@@ -155,61 +145,67 @@
<footer>
<div class="footer-content width">
<ul>
- <li><h4>PolarSys</h4></li>
- <li><a href="http://www.polarsys.org/about-us">About</a></li>
- <li><a href="http://www.polarsys.org/contact-us">Contact Us</a></li>
- <li><a href="http://www.polarsys.org/projects/polarsys.chess">CHESS Project Page</a></li>
+ <li><h4>Eclipse Foundation</h4></li>
+ <li><a href="https://www.eclipse.org/org/">About</a></li>
+ <li><a href="https://www.eclipse.org/org/foundation/contact.php">Contact Us</a></li>
+ <li><a href="https://projects.eclipse.org/projects/polarsys.chess">CHESS
+ Project Page</a></li>
</ul>
- <ul>
- <li><h4>Legal</h4></li>
- <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
- <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
- <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
- <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a></li>
+ <ul>
+ <li><h4>Legal</h4></li>
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy
+ Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms
+ of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright
+ Agent</a></li>
+ <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse
+ Public License</a></li>
<li><a href="http://www.eclipse.org/legal/">Legal Resources</a></li>
- </ul>
+ </ul>
<ul>
<li><h4>Useful Links</h4></li>
- <li><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS">Report a Bug</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS">Documentation</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS/Technical_Information">How to Contribute</a></li>
- <li><a href="http://polarsys.org/mailman/listinfo/chess-dev">Mailing List</a></li>
- <li><a href="http://polarsys.org/forums/index.php/f/9/">Forum</a></li>
+ <li><a
+ href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess">Report
+ a Bug</a></li>
+ <li><a href="https://wiki.eclipse.org/CHESS">Documentation</a></li>
+ <li><a
+ href="https://wiki.eclipse.org/CHESS/Technical_Information">How
+ to Contribute</a></li>
+ <li><a href="https://accounts.eclipse.org/mailing-list/chess-dev">Mailing
+ List</a></li>
+ <li><a href="https://www.eclipse.org/forums/index.php/f/529/">Forum</a></li>
</ul>
<ul class="endfooter">
- <li><h4>Other</h4></li>
+ <li><h4>Other</h4></li>
+ <li><a href="https://es.fbk.eu/">Fondazione Bruno Kessler</a></li>
<li><a href="http://www.intecs.it/">Intecs</a></li>
<li><a href="http://www.unipd.it">University of Padova</a></li>
+ <li><a href="http://www.mdh.se/">Mälardalen University</a></li>
</ul>
<table>
<tr>
- <td>
- <a href="//www.polarsys.org/"><img src="images/polarsys.png" alt="PolarSys logo" width="250"></a>
- <br />
- <br />
- </td>
+ <td><a href="https://www.yourkit.com"><img
+ src="images/yklogo.png" alt="YourKit logo"
+ style="width: 25%; height: 25%"></a> <br /> <font size="2">Thanks
+ YourKit for providing us free licenses of <a
+ href="https://www.yourkit.com/java/profiler/">YourKit Java
+ Profiler</a>
+ </font></td>
<td>
<div class="right-footer">
- <a href="http://www.eclipse.org/"><img src="images/eclipse.png" alt="Eclipse logo"></a>
- <br />
- Copyright © <span id="year">2016</span> The Eclipse Foundation. <br /> All Rights Reserved.
+ <a href="http://www.eclipse.org/"><img
+ src="images/eclipse.png" alt="Eclipse logo"></a> <br />
+ Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br />
+ All Rights Reserved.
</div>
</td>
- </tr>
- <tr>
- <td>
- <a href="https://www.yourkit.com"><img src="images/yklogo.png" alt="YourKit logo" style="width: 25%; height: 25%"></a>
- <br />
- <font size="2">Thanks YourKit for providing us free licenses of <a href="https://www.yourkit.com/java/profiler/">YourKit Java Profiler</a></font>
- </td>
- <td>
- </td>
- </tr>
+ </tr>
</table>
-
- <div class="clear"></div>
+
+ <div class="clear"></div>
</div>
-
+
</footer>
</body>
</html>
\ No newline at end of file
diff --git a/index.php b/index.php
deleted file mode 100644
index 09cf2a3..0000000
--- a/index.php
+++ /dev/null
@@ -1,38 +0,0 @@
-<?php
-/*******************************************************************************
- * Copyright (c) 2014 Eclipse Foundation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Denis Roy (Eclipse Foundation) - initial implementation
- *******************************************************************************/
-
- require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
- require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
- require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
- $App = new App();
- $Menu = new Menu();
- $Nav = new Nav();
- include($App->getProjectCommon());
-
- #
- # Begin: page-specific settings. Change these.
- $pageTitle = "Polarsys Template";
- $pageKeywords = "Polarsys,template";
- $pageAuthor = "Denis Roy";
-
-
- $html = <<<EOF
- <h2>About this template</h2>
- <p>This is simply a blank template. You can place common elements in _projectCommon.php as it is referenced by this file.</p>
- <p>For help with the template, you can <a href="https://polarsys.org/cgit/cgit.cgi/polarsys.org">browse other Polarsys project website code</a>, read
- about the <a href="https://polarsys.org/wiki/The_Forge">Polarsys Forge</a> or ask webmaster@eclipse.org.</p>
-
-EOF;
-
-
- $App->generatePage("polarsys", $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
-?>
diff --git a/publis/CHESSMLprofile.pdf b/publis/CHESSMLprofile.pdf
index 66cbdb3..6007b45 100644
--- a/publis/CHESSMLprofile.pdf
+++ b/publis/CHESSMLprofile.pdf
Binary files differ
diff --git a/publis/CHESSToolset_UserGuide.pdf b/publis/CHESSToolset_UserGuide.pdf
deleted file mode 100644
index 73730bc..0000000
--- a/publis/CHESSToolset_UserGuide.pdf
+++ /dev/null
Binary files differ
diff --git a/publis/CHESS_ArchitecturalPatternsGuides.pdf b/publis/CHESS_ArchitecturalPatternsGuides.pdf
new file mode 100755
index 0000000..511b352
--- /dev/null
+++ b/publis/CHESS_ArchitecturalPatternsGuides.pdf
Binary files differ
diff --git a/publis/CHESS_ContractBasedAnalysisModelCheckingSafetyAnalysis.pdf b/publis/CHESS_ContractBasedAnalysisModelCheckingSafetyAnalysis.pdf
new file mode 100755
index 0000000..68743b3
--- /dev/null
+++ b/publis/CHESS_ContractBasedAnalysisModelCheckingSafetyAnalysis.pdf
Binary files differ
diff --git a/publis/CHESS_DependabilityGuide.pdf b/publis/CHESS_DependabilityGuide.pdf
new file mode 100755
index 0000000..548de45
--- /dev/null
+++ b/publis/CHESS_DependabilityGuide.pdf
Binary files differ
diff --git a/publis/CHESS_MobiusIntegrationGuide.pdf b/publis/CHESS_MobiusIntegrationGuide.pdf
new file mode 100755
index 0000000..3079210
--- /dev/null
+++ b/publis/CHESS_MobiusIntegrationGuide.pdf
Binary files differ
diff --git a/publis/CHESS_RuntimeMonitoringGuide.pdf b/publis/CHESS_RuntimeMonitoringGuide.pdf
new file mode 100755
index 0000000..5700652
--- /dev/null
+++ b/publis/CHESS_RuntimeMonitoringGuide.pdf
Binary files differ
diff --git a/publis/CHESS_SWDevelopmentGuide.pdf b/publis/CHESS_SWDevelopmentGuide.pdf
new file mode 100755
index 0000000..fefb155
--- /dev/null
+++ b/publis/CHESS_SWDevelopmentGuide.pdf
Binary files differ
diff --git a/publis/CHESS_ToolsetGuide.pdf b/publis/CHESS_ToolsetGuide.pdf
new file mode 100755
index 0000000..ec211dc
--- /dev/null
+++ b/publis/CHESS_ToolsetGuide.pdf
Binary files differ
diff --git a/start.html b/start.html
index 52c77ed..7b754d5 100644
--- a/start.html
+++ b/start.html
@@ -3,19 +3,20 @@
<link rel="icon" type="image/png" href="favicon.ico" />
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>CHESS</title>
- <link rel="stylesheet" href="styles.css" type="text/css" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>CHESS</title>
+<link rel="stylesheet" href="styles.css" type="text/css" />
</head>
<body>
- <header>
+ <header>
<div class="logo-left width">
- <a href="index.html"><img src="images/chess-logo.png" alt="CHESS logo" width=""></a>
+ <a href="index.html"><img src="images/logo_chess_350.gif"
+ alt="CHESS logo" width=""></a>
</div>
- </header>
- <nav>
-
+ </header>
+ <nav>
+
<div class="width">
<ul>
<li class="start"><a href="index.html">Home</a></li>
@@ -27,210 +28,273 @@
<li><a href="events.html">Events</a></li>
<li class="divider-vertical-second-menu"></li>
<li class="end"><a href="community.html">Community</a></li>
- <li style="text-align:right;"><a href="download.html" class="box">Download</a></li>
- <li style="float:none;"><br style="clear:both;" /></li>
- </ul>
+ <li style="text-align: right;"><a href="download.html"
+ class="box">Download</a></li>
+ <li style="float: none;"><br style="clear: both;" /></li>
+ </ul>
</div>
-
- </nav>
+
+ </nav>
<div id="hrdiv">
<img src="images/bg_breadcrumb.jpg" width="" alt="" height="" />
</div>
- <div id="body" class="width-started">
+ <div id="body" class="width-started">
<article class="expanded">
<ul class="tabs">
- <li>
- <input name="tabs" id="tab1" checked="" type="radio">
+ <li><input name="tabs" id="tab1" checked="" type="radio">
<label for="tab1">Installation</label>
<div id="tab-content1" class="tab-content">
- This page provides all the information needed to setup the PolarSys CHESS tool.
- Please refer also to the provided <a href="publis/CHESSToolset_UserGuide.pdf"><b>user guide</b></a> to check the extensions currently available for CHESS.
+ This page provides all the information needed to setup the
+ CHESS tool. Please refer also to the provided <a
+ href="publis/CHESS_ToolsetGuide.pdf"><b>user guide</b></a> to
+ check the extensions currently available for CHESS.
<h3>Needed environment</h3>
<p>
- A Java 7 JRE/JDK is recommended for CHESS v0.10.0.<br />
+ A Java 8 JRE/JDK is recommended for CHESS v1.0.0.<br />
</p>
-
+
<p>
- You can download the CHESS Eclipse full distribution from the <a href="download.html">Download page</a>; in this case you have only to uncompress the provided archive to start using the CHESS tool.<br />
+ You can download the CHESS Eclipse full distribution from the <a
+ href="download.html">Download page</a>; in this case you have
+ only to uncompress the provided archive to start using the CHESS
+ tool.<br>
</p>
-
+
+ <p>If you want to install CHESS with the provided update site
+ please follow the steps detailed below:</p>
+
<p>
- If you want to install CHESS with the provided update site please follow the steps detailed below:
+ CHESS Eclipse plugins v1.0.0 has to be installed on top of
+ Eclipse Neon 3 platform available from: <a
+ href="https://www.eclipse.org/downloads/packages/release/neon/3/eclipse-modeling-tools">https://www.eclipse.org/downloads/packages/release/neon/3/eclipse-modeling-tools</a>.
</p>
-
- <p>
- CHESS Eclipse plugins v0.10.0 has to be installed on top of Eclipse Luna 4.4 SR2 platform available from:
- <a href="http://www.eclipse.org/downloads/packages/eclipse-modeling-tools/lunasr2">http://www.eclipse.org/downloads/packages/eclipse-modeling-tools/lunasr2</a>.
- </p>
- <p>
- Once Eclipse Luna has been installed, additional Eclipse tools have to be installed by using the standard
- Eclipse new software installation feature:
- <ul class="listInTabs">
- <li>Launch Eclipse Luna (eclipse.exe)</li>
- <li>From the main Eclipse window select the Help->Install new software… -> menu item</li>
- <li>From the "Install" window select "Luna"
- (http://download.eclipse.org/releases/luna) in the "Work with" field,
- then wait for the list of available sites to appear in the area below.
- <br>
- <img src="images/installingEnvironment1.jpg" width="85%">
- <div class="caption">Figure 1: Installing the environment</div>
- </li>
- <li>Expand the “Modeling” category and check the following plugins:
- <ul class="listInTabs">
- <li>Acceleo Core SDK</li>
- <li>ATL SDK</li>
- <li>QVT Operational SDK</li>
- </ul>
- <li>Click Next and then Finish to terminate the install procedure.</li>
- <li>Restart Eclipse, when prompted, in order to apply the changes.</li>
- </ul>
- </p>
- <p>
- Then install <b>Papyrus</b> and <b>MARTE</b> following these steps:
- <ul class="listInTabs">
- <li>from the main Eclipse window select the Help->Install new software… -> menu item</li>
- <li>From the "Install" window Add "Papyrus"
- (http://download.eclipse.org/modeling/mdt/papyrus/updates/releases/luna)
- in the "Work with" field, then wait for the list of available sites to
+
+ <p>First EMF Parsley SDK and Ecore Diagram Editor have to be
+ uninstalled.</p>
+ <p>
+ <ul class="listInTabs">
+ <li>From the main Eclipse window select the
+ Help->Installation Details</li>
+ <li>From the "Installed Software" Select the two
+ "EMF Parsley SDK" plug-ins.</li>
+ <li>Click Uninstall...</li>
+ <li>From the "Installed Software" Select
+ "Ecore Diagram Editor".</li>
+ <li>Click Uninstall...</li>
+ <li>Restart Eclipse, when prompted, in order to apply the
+ changes.
+ </ul>
+ <br> <img src="images/Parsley.jpg" width="85%">
+ <div class="caption">Figure 1: Uninstalling Parsley and
+ Ecore Diagram Editor plug-ins</div>
+ <br>
+
+ <p>
+ Then, Install the plug-ins downloading <a
+ href="https://CHESS.p2f">CHESS.p2f</a>. To import the file,
+ follow these steps inside Eclipse:
+ <ul class="listInTabs">
+ <li>go to File/Import...</li>
+ <li>select Install/Install Software Items from File and
+ click Next</li>
+ <li>select the given file CHESS.p2f from the filesystem</li>
+ <li>uncheck "Install latest version of selected
+ software" and proceed with Next/Next/Finish</li>
+ </ul>
+
+
+ <h3>Installing the SDE and EST plug-ins</h3>
+
+ <p>SDE and EST plug-ins can be installed by using the standard
+ Eclipse update-site feature.
+ <ul class="listInTabs">
+ <li>From the main Eclipse window select the Help->Install
+ new software… -> menu item</li>
+ <li>From the "Install" window Add "SDE"
+ (https://es-static.fbk.eu/tools/devel_sde/) in the "Work
+ with" field, then wait for the list of available sites to
appear in the area below, and select them all.</li>
- <li>Click Next and then Finish to terminate the install procedure.</li>
- <li>Restart Eclipse, when prompted, in order to apply the changes.
- <br>
- <img src="images/installingPapyrus.jpg" width="85%">
- <div class="caption">Figure 2: Papyrus installation window</div>
- </li>
- </ul>
- </p>
- <!--
- <h3>Installing MAST (required by the schedulability analysis)</h3>
- <p>
- Download the binary distribution of MAST from
- <a href="http://mast.unican.es/#downloading"><b>http://mast.unican.es/#downloading</b></a>
- and extract it in the folder "<your Eclipse folder>/mast/windows" or
- "<your Eclipse folder>/mast/linux" depending on your operating system.
- <br><img src="images/alert_transparent.gif" width="60">
- Currently the latest MAST version supported by the CHESS toolset is 1.4.0.0\1.
- </p>
- -->
-
- <h3>Installing the CHESS plugins</h3>
- <p>
- CHESS plug-ins can be installed by using the standard Eclipse update-site feature.
- </p>
- <p>
- The CHESS update-site is available through http:
- <br>the URL is <tt>https://www.polarsys.org/chess/updatesite/0.10.0/ </tt>
- <ul class="listInTabs">
- <li>Launch Eclipse Luna</li>
- <li>From the main menu select Help->Install new software… -></li>
- <li>Click "Add…", then select the CHESS update site or digit
- "https://www.polarsys.org/chess/updatesite/0.10.0/"
- (the first time you are using it) in the Location field, and click Ok.</li>
- <li>In the Install window uncheck the "Group Items by Category" option (see Figure 3).</li>
- <li>In the Install window check the CHESS Polarsys features (see Figure 3), and click Next and
- Finish to terminate the installation.</li>
- <li>Restart Eclipse.</li>
- </ul>
- <br>
- <img src="images/installingChess.jpg" width="85%">
- <div class="caption">Figure 3: Installing the CHESS plug-ins</div>
- </p>
- </div>
- </li>
- <li>
- <input name="tabs" id="tab2" type="radio">
- <label for="tab2">Documentation</label>
+ <li>Click Next and then Finish to terminate the install
+ procedure.</li>
+ <li>From the "Install" window Add "EST"
+ (https://es-static.fbk.eu/tools/devel_est/) in the "Work
+ with" field.</li>
+ <li>Deselect the checkbox "Group items by
+ category", wait for the list of available sites to appear
+ in the area below, and select only the first and last items.</li>
+ <li>Click Next and then Finish to terminate the install
+ procedure.</li>
+ <li>Restart Eclipse, when prompted, in order to apply the
+ changes.
+ </ul>
+ <h3>Installing the CHESS plug-ins</h3>
+ <p>CHESS plug-ins can be installed by using the standard
+ Eclipse update-site feature.</p>
+ <p>
+ The CHESS update-site is available through http: <br>the URL
+ is
+ <tt>https://download.eclipse.org/chess/core/releases/1.0.0/updateSite/</tt>
+ <ul class="listInTabs">
+ <li>Launch Eclipse Neon</li>
+ <li>From the main menu select Help->Install new software… -></li>
+ <li>Click "Add…", then select the CHESS update
+ site or digit
+ "https://www.eclipse.org/chess/updatesite/1.0.0//"
+ (the first time you are using it) in the Location field, and
+ click Ok.</li>
+ <li>In the Install window uncheck the "Group Items by
+ Category" option (see Figure 3).</li>
+ <li>In the Install window check the CHESS features
+ (see Figure 3), and click Next and Finish to terminate the
+ installation.</li>
+ <li>Restart Eclipse.</li>
+ </ul>
+ <br> <img src="images/installingChess.jpg" width="85%">
+ <div class="caption">Figure 2: Installing the CHESS plug-ins</div>
+ </div></li>
+ <li><input name="tabs" id="tab2" type="radio"> <label
+ for="tab2">Documentation</label>
<div id="tab-content2" class="tab-content">
- <p>Check the CHESS user guide available
- <a href="publis/CHESSToolset_UserGuide.pdf"><b>here</b>.</a>
- The user guide will introduce you to the entire CHESS design flow, starting from the creation of a CHESS project to the different CHESS modelling steps and tool features, with step-by-step examples.
- </p>
- <!--
- <h3>CHESS Documentation</h3>
- <p style="text-align: left; padding:10px;">
- Here is some text....
- </p>
- -->
- <p>Check the CHESS Modelling Language profile definition available
- <a href="publis/CHESSMLprofile.pdf"><b>here</b>.</a></p>
- </div>
- </li>
- <li>
- <input name="tabs" id="tab3" type="radio">
- <label for="tab3">Model Examples</label>
+ <p>
+ Find below a list of documents that guide that introduce you to CHESS
+ <h4>Modeling and overview of tool features</h4>
+ Check out the CHESS user guide available <a href="publis/CHESS_ToolsetGuide.pdf"><b>here</b>.</a>
+ The user guide will introduce you to the entire CHESS design
+ flow, starting from the creation of a CHESS project to the
+ different CHESS modelling steps and tool features, with
+ step-by-step examples
+ </p>
+ <p>
+ <h4>CHESS Modelling Language profile</h4>
+ Check out the CHESS Modelling Language profile
+ definition available <a href="publis/CHESSMLprofile.pdf"><b>here</b>.</a>
+ </p>
+ <p>
+ <h4>CHESS Support to System-Level Analysis</h4>
+ CHESS provides a variety of model-based analysis, using
+ different backend tools (OCRA, nuXmv, xSAP). The following document guides the user
+ along a system-level design flow from requirements specification and validation, to
+ contract-based architectural design, to components implementation and verification, to
+ fault injection and model-based safety analysis. Check out the guide available
+ <a href="publis/CHESS_ContractBasedAnalysisModelCheckingSafetyAnalysis.pdf"><b>here</b></a>.
+ </p>
+ <p>
+ <h4>CHESS Support to Dependability Analysis</h4>
+ Check out the guide available
+ <a href="publis/CHESS_DependabilityGuide.pdf"><b>here</b></a>
+ to support state-based quantitative analysis and Failure Logic Analysis (FLA)
+ based upon FPTC - Fault Propagation and Transformation Calculus
+ </p>
+ <p>
+ <h4>CHESS Support to Stochastic Analysis</h4>
+ CHESS supports modelling of safety and security concerns and automated transformations
+ to SAN models for reliability analysis with the MOBIUS tool.
+ Check out the guide available
+ <a href="publis/CHESS_MobiusIntegrationGuide.pdf"><b>here</b></a>
+ </p>
+ <p>
+ <h4>CHESS Support to Software Development and Analysis</h4>
+ Check out the guide available
+ <a href="publis/CHESS_SWDevelopmentGuide.pdf"><b>here</b></a>
+ for Schedulability Analysis and End2End Response Time Analysis
+ with MAST
+ </p>
+ <p>
+ <h4>CHESS Support to Architectural Patterns</h4>
+ The CHESS tool includes a library of design patterns to be instantiated in a model.
+ Check out the guide available
+ <a href="publis/CHESS_ArchitecturalPatternsGuides.pdf"><b>here</b></a>
+ </p>
+ <p>
+ <h4>CHESS Support to Runtime Monitoring</h4>
+ The CHESS tool includes includes trace analysis and back propagation support.
+ Check out the guide available
+ <a href="publis/CHESS_RuntimeMonitoringGuide.pdf"><b>here</b></a>
+ </p>
+ </div></li>
+ <li><input name="tabs" id="tab3" type="radio"> <label
+ for="tab3">Model Examples</label>
<div id="tab-content3" class="tab-content">
- <p>CHESS model examples are available in the <a href="download.html"><b>download</b></a> page; you can import them in your workspace as existing projects and then navigate the models, through the available diagrams. The provided examples can also be used to test the CHESS model driven features, like the analysis and code generation.</p>
-
- </div>
- </li>
+ <p>
+ CHESS model examples are available in the <a href="download.html"><b>download</b></a>
+ page; you can import them in your workspace as existing projects
+ and then navigate the models, through the available diagrams. The
+ provided examples can also be used to test the CHESS model driven
+ features, like the analysis and code generation.
+ </p>
+
+ </div></li>
</ul>
- </article>
- </div>
-
- <div class="clear"></div>
-
- <footer id="footer-start">
- <div class="footer-content width">
+ </article>
+ </div>
+
+ <footer id="footer-start">
+ <div class="footer-content width">
<ul>
- <li><h4>PolarSys</h4></li>
- <li><a href="http://www.polarsys.org/about-us">About</a></li>
- <li><a href="http://www.polarsys.org/contact-us">Contact Us</a></li>
- <li><a href="http://www.polarsys.org/projects/polarsys.chess">CHESS Project Page</a></li>
+ <li><h4>Eclipse Foundation</h4></li>
+ <li><a href="https://www.eclipse.org/org/">About</a></li>
+ <li><a href="https://www.eclipse.org/org/foundation/contact.php">Contact Us</a></li>
+ <li><a href="https://projects.eclipse.org/projects/polarsys.chess">CHESS
+ Project Page</a></li>
</ul>
- <ul>
- <li><h4>Legal</h4></li>
- <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
- <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
- <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
- <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a></li>
+ <ul>
+ <li><h4>Legal</h4></li>
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy
+ Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms
+ of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright
+ Agent</a></li>
+ <li><a href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse
+ Public License</a></li>
<li><a href="http://www.eclipse.org/legal/">Legal Resources</a></li>
- </ul>
+ </ul>
<ul>
<li><h4>Useful Links</h4></li>
- <li><a href="http://polarsys.org/bugs/describecomponents.cgi?product=CHESS">Report a Bug</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS">Documentation</a></li>
- <li><a href="http://polarsys.org/wiki/CHESS/Technical_Information">How to Contribute</a></li>
- <li><a href="http://polarsys.org/mailman/listinfo/chess-dev">Mailing List</a></li>
- <li><a href="http://polarsys.org/forums/index.php/f/9/">Forum</a></li>
+ <li><a
+ href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Chess">Report
+ a Bug</a></li>
+ <li><a href="https://wiki.eclipse.org/CHESS">Documentation</a></li>
+ <li><a
+ href="https://wiki.eclipse.org/CHESS/Technical_Information">How
+ to Contribute</a></li>
+ <li><a href="https://accounts.eclipse.org/mailing-list/chess-dev">Mailing
+ List</a></li>
+ <li><a href="https://www.eclipse.org/forums/index.php/f/529/">Forum</a></li>
</ul>
<ul class="endfooter">
- <li><h4>Other</h4></li>
+ <li><h4>Other</h4></li>
+ <li><a href="https://es.fbk.eu/">Fondazione Bruno Kessler</a></li>
<li><a href="http://www.intecs.it/">Intecs</a></li>
<li><a href="http://www.unipd.it">University of Padova</a></li>
<li><a href="http://www.mdh.se/">Mälardalen University</a></li>
</ul>
<table>
<tr>
- <td>
- <a href="http://www.polarsys.org/"><img src="images/polarsys.png" alt="PolarSys logo" width="250"></a>
- <br />
- <br />
- </td>
+ <td><a href="https://www.yourkit.com"><img
+ src="images/yklogo.png" alt="YourKit logo"
+ style="width: 25%; height: 25%"></a> <br /> <font size="2">Thanks
+ YourKit for providing us free licenses of <a
+ href="https://www.yourkit.com/java/profiler/">YourKit Java
+ Profiler</a>
+ </font></td>
<td>
<div class="right-footer">
- <a href="http://www.eclipse.org/"><img src="images/eclipse.png" alt="Eclipse logo"></a>
- <br />
- Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br /> All Rights Reserved.
+ <a href="http://www.eclipse.org/"><img
+ src="images/eclipse.png" alt="Eclipse logo"></a> <br />
+ Copyright ©<span id="year">2016</span> The Eclipse Foundation. <br />
+ All Rights Reserved.
</div>
</td>
- </tr>
- <tr>
- <td>
- <a href="https://www.yourkit.com"><img src="images/yklogo.png" alt="YourKit logo" style="width: 25%; height: 25%"></a>
- <br />
- <font size="2">Thanks YourKit for providing us free licenses of <a href="https://www.yourkit.com/java/profiler/">YourKit Java Profiler</a></font>
- </td>
- <td>
- </td>
- </tr>
+ </tr>
</table>
-
- <div class="clear"></div>
+
+ <div class="clear"></div>
</div>
-
+
</footer>
</body>
</html>
diff --git a/styles.css b/styles.css
index b8c2ec1..c12daa0 100644
--- a/styles.css
+++ b/styles.css
@@ -592,7 +592,7 @@
}
#footer-features {
- margin: 410em auto 0;
+ margin: 480em auto 0;
background-image:linear-gradient(to left, #FFCC00, white 90%);
border-top: 8px solid #FFCC00;
}
@@ -600,7 +600,7 @@
#footer-start {
/*margin: 165em auto 0;*/
/*margin: 300em auto 0;*/
- margin: 256em auto 0;
+ margin: 170em auto 0;
background-image:linear-gradient(to left, #FFCC00, white 90%);
border-top: 8px solid #FFCC00;
}
