|
||||||||||||
|
Description:
How it works
|
||||||||||||
| In
the Rigi system, artifacts are stored in an underlying repository and manipulated
through rigiedit, which provides editing,
manipulation, annotation, hypertext, and exploration capabilities. Rigi
also includes parsers which extract artifacts
from the subject software. A domain model
specifies the entity types and relationships of interest. The input stream
is fed into rigiedit to visually represent the initial graph.
To manage the complexity of the graph, rigiedit allows you to select, filter, layout, and edit the graph to identify pertinent subsystems (automatically or manually collapse related artifacts into subsystems). These subsystems typically represent concepts such as abstract data types or personnel assignments.
The newly created, simpler, hierarchical graph can be navigated, analyzed, and presented using various automatic or user-guided graphical layouts. Rigi can save different perspectives of this hierarchy in a reloadable view.
Standard graphs such as the call graph, which shows procedures calling procedures, are quick to produce. You can easily report the dependencies of a subsystem upon its neighboring artifacts. You can also write scripts in Tcl/Tk using the Rigi Command Library to define and automate common operations on your graphs. You can even design your own menus and widgets to customize your working environment around your own visualization needs. The discovered structural information is useful for making informed development and management decisions. It also serves as up-to-date and accurate documentation, since it is derived from the actual source code. Thus, Rigi aids both the understanding of legacy software systems where the existing documentation may be missing or lacking, and reengineering tasks that require design information of existing software. For a more detailed explanation of Rigi, you can also try the list demo. What
it is |
||||||||||||
|
|
||||||||||||