Commit 24306e9b authored by Yuri Blankenstein's avatar Yuri Blankenstein
Browse files

Merge branch 'develop' into 'master'

v0.1-RC1

See merge request !19
parents d0d0fa1d 6f5dda80
Pipeline #4895 passed with stage
in 0 seconds
......@@ -26,7 +26,7 @@ This content is produced and maintained by the {trace} project.
== Trademarks
{trace} and TRACE4CPS are trademarks of the Eclipse Foundation. Eclipse,
{trace} and TRACE4CPS(TM) are trademarks of the Eclipse Foundation. Eclipse,
and the Eclipse Logo are registered trademarks of the Eclipse Foundation.
Other names may be trademarks of their respective owners.
......
......@@ -24,4 +24,4 @@
// If we use this attribute in a heading, we need to encapsulate the whole heading text in pass:normal[...] macro due to bug
// https://github.com/asciidoctor/asciidoctor/issues/1173 (Replacements in an attribute value not substituted in headings (section titles))
:trace: Eclipse TRACE4CPS
:trace: Eclipse TRACE4CPS(TM)
......@@ -27,4 +27,4 @@ ifndef::trace4cps-binary-prefix[:trace4cps-binary-prefix: eclipse-trace4cps-incu
// If we use this attribute in a heading, we need to encapsulate the whole heading text in pass:normal[...] macro due to bug
// https://github.com/asciidoctor/asciidoctor/issues/1173 (Replacements in an attribute value not substituted in headings (section titles))
:trace: Eclipse TRACE4CPS
:trace: Eclipse TRACE4CPS(TM)
......@@ -17,7 +17,7 @@ indexterm:[legal]
The material in this documentation is Copyright (c) 2021 Contributors to the Eclipse Foundation.
Eclipse TRACE4CPS and TRACE4CPS are trademarks of the Eclipse Foundation.
{trace} and TRACE4CPS(TM) are trademarks of the Eclipse Foundation.
Eclipse, and the Eclipse Logo are registered trademarks of the Eclipse Foundation.
Other names may be trademarks of their respective owners.
......
......@@ -11,12 +11,12 @@
include::_initCommon.adoc[]
[[release-notes]]
== pass:normal[{trace}^TM^ release notes]
== pass:normal[{trace} release notes]
The release notes of {trace}^TM^ are listed below, in reverse chronological order.
The release notes of {trace} are listed below, in reverse chronological order.
[[release-notes-v0.1]]
=== Version 0.1
The first release of the {trace}^TM^ project.
The first release of the {trace} project.
This version is a port of https://esi.nl/research/output/tools/trace[ESI TRACE v2.0] that is prepared for its release to the Eclipse foundation.
......@@ -16,23 +16,23 @@ include::_initCommon.adoc[]
:!table-caption:
:xrefstyle: short
= pass:normal[{trace}^TM^]
= pass:normal[{trace}]
*{trace}^TM^* is a *customizable, domain-independent and source-independent Gantt chart viewer* with mathematically-founded analysis support.
*{trace}* is a *customizable, domain-independent and source-independent Gantt chart viewer* with mathematically-founded analysis support.
{trace} supports the visualization of activities on resources as a function of time (Gantt charts), as well as the visualization of continuous signals.
{trace} also supports several analysis techniques to identify bottlenecks, check formally-specified (performance) properties, and analyze resource usage.
A key feature of {trace} is the ability to configure the identification, selection and visualization of such information to match any specific application domain.
[WARNING]
====
The {trace}^TM^ project is currently in the link:https://wiki.eclipse.org/Development_Resources/Process_Guidelines/What_is_Incubation[Incubation Phase].
The {trace} project is currently in the link:https://wiki.eclipse.org/Development_Resources/Process_Guidelines/What_is_Incubation[Incubation Phase].
image::{imgsdir}/eclipse-incubation.png[width=300]
====
== Visualization and analysis of concurrent system activities
{trace}^TM^ helps us to understand complicated behavior over time for all kinds of systems through its domain-independent capabilities for visualizing and analyzing concurrent activities that are encoded in execution traces.
{trace} helps us to understand complicated behavior over time for all kinds of systems through its domain-independent capabilities for visualizing and analyzing concurrent activities that are encoded in execution traces.
{trace} supports claims on resources, events, dependencies, and continuous signals.
<<fig-trace>> shows a typical {trace} Gantt chart of an application that iteratively executes activities A-G.
......@@ -52,11 +52,11 @@ An example is a situation in which many concurrent activities share resources.
Unforeseen interactions may arise due to the specific timing of the activities.
Moreover, if the timing of the activities changes (e.g. due to an upgrade to the computational platform), the interactions may also change, which could result in significantly different behavior.
Insight into the hows and whys of a system’s behavior over time is of paramount importance for making effective (design) choices and trade-offs in all phases of the system lifecycle, from the design of a new system to the maintenance of an old legacy system.
{trace}^TM^ can help with this.
{trace} can help with this.
== Execution traces to capture behavior over time
{trace}^TM^ works with execution traces.
{trace} works with execution traces.
These capture (a single) system behavior over time.
An execution trace contains time-stamped data for claims, events and signals.
{trace} extends this with concepts from the Y-chart paradigm and a number of user-defined attributes (e.g. the name of the activity) in order to be tailored to a specific problem domain.
......@@ -83,7 +83,7 @@ To provide feedback on the system under analysis (star-2 in <<fig-ychart>>), {tr
== Visualization and analysis of execution traces
{trace}^TM^ provides insights into the system dynamics of all kinds of systems through the visualization and analysis of execution traces (<<fig-workflow>>).
{trace} provides insights into the system dynamics of all kinds of systems through the visualization and analysis of execution traces (<<fig-workflow>>).
{trace}' Gantt chart view offers coloring, grouping and filtering options.
This visualization alone is already very powerful and can bring quick insights into the system dynamics.
{trace} also provides several analysis methods, which sets it apart from other Gantt-chart visualization tools.
......@@ -114,7 +114,7 @@ Resource-usage analysis::
image::{imgsdir}/workflow.png[width=414]
[[installation]]
== pass:normal[Installation of {trace}^TM^]
== pass:normal[Installation of {trace}]
The {trace} P2 update site contains all plugins and features, for easy integration into OSGi-based applications.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment