wiki:path:pathView

Version 10 (modified by michael.perscheid, 10 years ago) ( diff )

--

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.

Description

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. 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 views of classes and methods step by step. In doing so, static analysis techniques and our 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. They provide an always up-to-date documentation in form of class diagrams; they help in program comprehension by selecting and presenting methods and classes for a specific concern at once; they allow developers to discuss about architectural decisions; 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 and everything that is required is source code and test cases.

See also the following tutorials: Model-based Source Code Editing and Type Harvesting.

Screenshot

How to Use

start from browser left click menu or start by opening pathview and drag'n'drop or start from pathFinder now hidden feature !!! but cool :D

  • First, you need a proper Path project that is selected as current. For more information see PathProject.
  • To start PathFinder choose the tool either in the world docking bar at the top (Apps -> PathFinder) or in the world menu (open... -> PathFinder).
  • After that, you will see a tool as in the screenshot above with a large white space in the middle.
  • In order to get the execution history of a specific test case, please click on the rectangle in the upper left corner and choose the corresponding test case from the list.
  • Afterwards, the executed call tree is presented in the former white area below and developers can start exploring its execution history.

User Interface

Control Panel

Attachments (5)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.