bug 419235: [proposal] polarsys.chess
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419235
diff --git a/polarsys.chess/proposal.html b/polarsys.chess/proposal.html
index 0d01664..d903757 100644
--- a/polarsys.chess/proposal.html
+++ b/polarsys.chess/proposal.html
@@ -52,7 +52,7 @@
<p>
The CHESS (Composition with Guarantees for High-integrity Embedded
Software Components Assembly) project (<a
- href="../CHESS-Proposal-Text/www.autosar.org">www.chess-project.org</a>)
+ href="http://www.chess-project.org">www.chess-project.org</a>)
is a proposed open source project under the <a
href="http://polarsys.org/">Polarsys Top Level Project</a>.
</p>
@@ -61,7 +61,7 @@
This proposal is in the Project Proposal Phase (as defined in the
Eclipse Development Process) and is written to declare its intent and
scope. We solicit additional participation and input from the
- Eclipsecommunity. Please send all feedback to the <a
+ Eclipse community. Please send all feedback to the <a
href="http://www.eclipse.org/forums/eclipse.proposals">Eclipse
Proposals</a> Forum.
</p>
@@ -75,7 +75,7 @@
solutions to help build such complex systems. Addressing domain
specific modeling (like component description and interaction,
real-time constraints, ...) while keeping the flexibility and
- genericity offered by languages like UML is a challenge in a context
+ generality offered by languages like UML is a challenge in a context
where software must be qualified according to safety and reliability
standards.</p>
@@ -91,7 +91,7 @@
systems for different domains. The methodology is particularly suited
for space systems and industrial domains.</p>
- <p>Thanks to a dedicated MARTE and UML profiles and associated
+ <p>Thanks to a dedicated MARTE and UML profile and associated
tooling, CHESS addresses solutions to problems of property-preserving
component assembly in real-time and dependable embedded systems, and
supports the description, verification, and preservation of real-time
@@ -101,13 +101,13 @@
<p>CHESS also addresses the description and verification of system
and component dependability properties (like fault, error, failures
- and failures propagations); however it worth mentioning here that the
+ and failures propagations); however it is worth mentioning here that the
dependability support (also described later in the proposal) is not
part of the current CHESS contribution.</p>
- <p>CHESS tooling extend Papyrus editor to properly support the
- CHESS methodology, in particular by allowing working with new views on
- the system including requirements, system, components, deployment and
+ <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>
<h2>Description</h2>
@@ -123,7 +123,7 @@
profile, (2) an extension to the Papyrus UML graphical editor that
supports the notion of design views, (3) a model validator that
assesses the well-formedness of the model before model transformations
- can be undertaken, and (4) as set of model to model and model to text
+ can be undertaken, and (4) a set of model to model and model to text
transformations, the former for the purpose of model-based
schedulability and dependability analysis and the latter for code
generation toward multiple language targets.</p>
@@ -184,7 +184,7 @@
separation of concerns principle.</p>
<p>The functional view allows the functional specification of the
- CHESS components (see Figure 1and Figure 2).</p>
+ CHESS components (see Figure 1 and Figure 2).</p>
<p>
<img width="400" src="CHESS%20proposal%2020131008_file/image002.png" />
@@ -196,15 +196,15 @@
<img width="400" src="CHESS%20proposal%2020131008_file/image004.jpg" />
</p>
- <p>Figure 2_ Component View - Functional View - Component Instances</p>
+ <p>Figure 2: Component View - Functional View - Component Instances</p>
<p>The extra functional view (see Figure 3) 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, also the possibility for the
- user to specify probabilistic values about their occurrence and
- propagation (also between the components).</p>
+ 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></p>
@@ -216,7 +216,7 @@
Instances</p>
<p>The deployment view (Figure 4) is used to describe the hardware
- platform where the software runs (i.e. CPUs, busses) and software to
+ 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>
@@ -231,7 +231,7 @@
<p>The analysis view (Figure 5) 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 need to be evaluated.</p>
+ interest (i.e. reliability or availability) that needs to be evaluated.</p>
<p>
<img width="400" src="CHESS%20proposal%2020131008_file/image010.jpg" />
@@ -245,8 +245,8 @@
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 ensure that the user model
- conforms with the constraints imposed by the CHESS methodology, for
+ 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></p>
@@ -311,7 +311,7 @@
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 propagated the results back to
+ the PSM, then QVT-o traces are used to propagate the results back to
the PIM model</p>
<p>
@@ -327,7 +327,7 @@
<p>Adding CHESS to the PolarSys portfolio is a good way to serve
the Space industry community which has expressed interest in and
- support for the CHESS concept, method, and features, and to reachout
+ support for the CHESS concept, method, and features, and to reach out
to new industry domains likes Aerospace, Railway, Automotive or
Telecommunications, some of which have already been exposed to CHESS
with good reverberations.</p>
@@ -374,13 +374,13 @@
<dt>Lei PI, INTECS</dt>
<dd>Lei is involved in Topcased since 2006, he will contribute to
- the smooth integration of CHESS projects in the Polarsys bundles.</dd>
+ smooth the integration of CHESS projects in the Polarsys bundles.</dd>
<dt>Alessandro Zovi, University of Padova</dt>
<dd>Alessandro was a key developer of the CHESS toolset and in
that effort he acquired profound knowledge of the Eclipse stack and
of the Papyrus internals. He will coordinate with Stefano Puri in all
- the activities related with the CHESS devolution to Polarsys.</dd>
+ the activities related with the CHESS evolution to Polarsys.</dd>
</dl>
<p>We welcome additional committers and contributions.</p>
@@ -392,7 +392,7 @@
System and Software Engineering field. She is Methodologies and
R&D Manager at Intecs, where she is involved both in technical
leadership and management activities in the context of several
- international industrial and research projects. Mrs. Mazzini took his
+ international industrial and research projects. Ms. Mazzini took her
master degree in Computer Science at Pisa University in Italy.</dd>
<dt>Tullio Vardanega, University of Padova</dt>
@@ -414,29 +414,32 @@
<p>The following Architecture Council members will mentor this
project:</p>
<ul>
- <li>Mentor 1</li> Mentor 2
- <li>
- </li>
- </ul>
+ <li>Mentor 1</li>
+ <li>Mentor 2</li>
+ </ul>
<h2>Interested Parties</h2>
<p>The following individuals, organisations, companies and projects
have expressed interest in this project:</p>
- <p>CNES</p>
-
- <p>Airbus</p>
-
- <p>Astrium</p>
-
- <p>Obeo</p>
+ <ul>
+ <li>CNES</li>
+
+ <li>Airbus</li>
+
+ <li>Astrium</li>
+
+ <li>Obeo</li>
+ </ul>
<h2>Project Scheduling</h2>
- <p>Creation - November 2013</p>
+ <ul>
+ <li>Creation - November 2013</li>
- <p>CHESS roadmap</p>
-
+ <li>CHESS roadmap</li>
+ </ul>
+
<h2>Changes to this Document</h2>
<table border="0" cellpadding="0">
@@ -466,6 +469,14 @@
transformations.</p>
</td>
</tr>
+ <tr>
+ <td>
+ <p>18-October-2013</p>
+ </td>
+ <td>
+ <p>Document Review.</p>
+ </td>
+ </tr>
</tbody>
</table>
@@ -479,9 +490,9 @@
available at <a href="http://www.chess-project.org/page/results">http://www.chess-project.org/page/results</a>
</li>
<li>A. Burns, B. Dobbing, T. Vardanega. Guide to the Use of the
- Ada Ravenscar Profile in High Integrity Systems. Techinal Report
- YCS-2003-348. University of York (UK), 2003. available at<a
- href="http://www.cs.york.ac.uk/ftpdr/reports/YCS-2003-348.pdf">http://www.cs.york.ac.uk/ftpdr/reports/YCS-2003-348.pdf</a>
+ 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>
</li>
<li>Universidad de Cantabria. Mast: Modeling and Analysis Suite
for Real-Time Applications. <a href="http://mast.unican.es/">http://mast.unican.es/</a>
