Changes between Version 18 and Version 19 of pathToolsFramework

Timestamp:

12/11/2013 04:03:38 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

pathToolsFramework

@@ -1 +1 @@
 = The Path Tools Framework =
 
-TODO: Description
+The Path Tools Framework comprises several development tools for supporting typical software maintenance tasks such as debugging, testing, and program comprehension. 
+It realizes our test-driven fault navigation, test quality feedback, and model-based source code editing approach. 
+
+Our implementation primarily consists of three tools that are built on top of a flexible dynamic analysis framework:
+ * ''PathMap'' is an extended test runner that analysis test case behavior and provides feedback about the entire system under observation. For example, it visualizes suspicious system parts, identifies experienced developers, derives type information, automatically creates contracts from likely invariants, reveals missing test cases and performance bottlenecks, or traces requirements down to program entities. 
+
+ * ''PathFinder'' is a lightweight back-in-time debugger for navigating through specific test case behavior and state. It assists developers not only in understanding entire execution histories but also in localizing root causes by highlighting infection chains and answering questions about corrupted object state. 
+
+ * ''PathView'' is a single-source model-based editor that allows developers to apply a direct round-trip engineering approach-changes in source code are immediately reflected in our UML-like views and vice versa. We automatically create such models based on specific test case executions and harvested type information from the entire test base. 
+
+''The Path analysis framework'' provides the basis for our tools. 
+It is an extensible realization of our incremental dynamic analysis for Smalltalk’s SUnit framework. 
+By leveraging unit tests as a basis for dynamic analysis, we can ensure reproducibility and a high degree of automation, scalability, and performance with our tools.
 
 '''Keywords:''' Software Maintenance, Testing, Debugging, Program Comprehension, Anomalies , Back-in-time, Test-driven fault navigation, Test Quality Feedback, Path Tools Framework, PathMap, PathFinder, PathView
+
+''[1. December 2013]'' We start to publish our Path tools framework.
 
 = How to Install =
@@ -102 +116 @@
 {{{
 #!div class="gallery_item"
-[[Image(typeHarvesting.png, 150px, link=wiki:path:tutorial:typeHarvesting)]]
+[[Image(traceability.png, 150px, link=wiki:path:tutorial:traceability)]]
 {{{
 #!div class="item_description"
-[wiki:path:tutorial:typeHarvesting Type Harvesting] [[br]] is a practical approach to obtain type information. 
-Based on unit tests, we automatically derive run-time types and enrich the development environment with it. 
+[wiki:path:tutorial:traceability Requirements Traceability] [[br]] combines external concerns of a system with test cases and automatically derives corresponding program entities. This allows developers to follow requirements down to their implementation without much effort. 
 }}}
 }}}
@@ -122 +135 @@
 {{{
 #!div class="gallery_item"
-[[Image(traceability.png, 150px, link=wiki:path:tutorial:traceability)]]
+[[Image(typeHarvesting.png, 150px, link=wiki:path:tutorial:typeHarvesting)]]
 {{{
 #!div class="item_description"
-[wiki:path:tutorial:traceability Requirements Traceability] [[br]] combines external concerns of a system with test cases and automatically derives corresponding program entities. This allows developers to follow requirements down to their implementation without much effort. 
+[wiki:path:tutorial:typeHarvesting Type Harvesting] [[br]] is a practical approach to obtain type information. 
+Based on unit tests, we automatically derive run-time types and enrich the development environment with it. 
 }}}
 }}}