Changes between Version 8 and Version 9 of path:pathView

Timestamp:

02/20/2014 03:34:48 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathView

@@ -3 +3 @@
 = !PathView =
 
-!PathView is a single-source, round-trip engineering, and model-based code editor. In other words, it presents UML-like views of classes, methods, and their relationships that are always an up-to-date view on the source code. Each editing in model or source code will change the other representation automatically in background. For that reason, it does not matter if developers favorite code or models for programming. 
+!PathView is a single-source, round-trip engineering, and model-based code editor. 
+In other words, it presents UML-like views of classes, methods, and their relationships that are always an up-to-date view on the source code. 
+Each editing in model or source code will change the other representation automatically in background. 
+For that reason, it does not matter if developers favorite code or models for programming. 
 
 == Description ==
 
-Our !PathView tool is an editable mid-level abstraction of a system under observation in form of UML-like diagrams.
+Our !PathView tool allows developers to create editable mid-level abstractions of a system under observation in form of UML-like diagrams.
 It ensures a synchronization mechanism between the created abstraction and the underlying source code. 
-As soon as something changes other entities are also updated immediately. 
+As soon as something changes, other entities are also updated immediately. 
 Developers create such diagrams in an interactive and semi-automatic manner. 
-Starting from a static (selected classes in source code) or dynamic (test cases that cover methods of specific concerns) perspective, they refine their specific views of classes and methods step by step. 
+Starting from a static (selected classes in source code) or dynamic (test cases that cover methods of specific concerns) perspective, they refine their views of classes and methods step by step. 
 In doing so, static analysis techniques and our [wiki:path:tutorial:typeHarvesting Type Harvester] provide the necessary information for generating and syncing these diagrams automatically.
 Finally, these diagrams are helpful in many software engineering and maintenance activities.
@@ -19 +22 @@
 and they have been shown very useful in our lectures when students have to present an overview of their implemented systems.
 Besides these read-only use-cases, our !PathView also allows the development and refactoring of entire systems in such diagrams.
-In other words, there is no difference between writing source code and model-based development. 
+In other words, there is no difference between writing source code and model-based development and everything that is required is source code and test cases. 
 
 '''See also the following tutorials:'''