Abstract: A system and method for generating a consistent graphical expression of source code which is independent of the source language and of a particular programmer's style. The system first provides an intermediary pattern language which is source language independent into which the source code is translated. This pattern language is directly mapped to a set of predetermined graphical patterns having a series of attributes. The pattern language is nested in the sense that certain expressions may contain certain other expressions. This translates directly to graphical containment. Attributes are computed starting with the most nested parts of the pattern language translation. The attributes of the more nested parts having been thus computed may be used in the computation of the attributes of less nested parts of the expression. Once all attributes are computed, a mapping to display directives is performed, and a graphical engine produces an actual display.

Abstract: A system and method for identifying indirect messaging relationships between software process. Within a source code repository, all occurrences of calls to interface procedures are identified together with communications objects to which these calls pertain. Each interface procedure call is categorized as either a “send” or a “receive” interface procedure call. A relationship is identified when a pair of interface procedure calls are located which pertain to the same communications object and one of the pair has a “send” type and the other of the pair has a “receive” type. By identifying pairs of this type, relationships between hierarchical software entities which contain the interface procedure calls are also simultaneously identified. Each relationship thus identified is mapped onto one or more inter-process indirect messaging relationships.

Abstract: A system and method for identifying indirect messaging relationships between software entities. Within a source code repository, all occurrences of calls to interface functions are identified together with communications objects to which these calls pertain. Each interface function call is categorized as either a “send” or a “receive” interface function call. A relationship is identified when a pair of interface function calls are located which pertain to the same communications object and one of the pair has a “send” type and the other of the pair has a “receive” type. By identifying pairs of this type, relationships between hierarchical software entities which contain the interface function calls are also simultaneously identified.