Module Interconnection Languages

Abstract

Module interconnection languages are considered essential tools in the development of large software systems. The current state of the art in software development environments is due mainly to the pioneering work on module interconnection languages of the late 1970s and early 1980s. Module Interconnection Languages (MILs) provide formal grammer constructs for deciding the various module interconnection specifications required to assemble a complete software system. An MIL code listing is a formal description of the global structure of a software system. Automatic processing of these formal descriptions results in a verification of system integrity and intermodular compatibility. An MIL can be considered a structural design language because it states what the system modules are and how they fit together to implement the system's function. This is architectural design information. MILs are not concerned with what the system does (specification of information), how the major parts of the system are embedded into the organization (analysis of information), or how the individual modules implement their function (detailed design information). The major payoff of using MILs is during system design but substantial payoffs are also obtained during system integration, evolution, and maintenance.

Evaluation of Selected Control Programming Languages for Process Engineers by Means of Cognitive Effectiveness and Dimensions

“…For assessing the programming lan-guages' modularity (R1.2), both their degree of abstraction (CD) and their complexity management (CE) have to be considered. It was shown, that modularity is very much related to abstraction [47], but the criterion complexity management additionally analyzes the visual modularity. The requirement modifiability (R1.1) can be evaluated by the cognitive dimension viscosity.…”

A case study in re-engineering to enforce architectural control flow and data sharing

“…Module systems and module interconnection languages (MILs) support system composition from separate modules [60]. ArchJava differs from module systems in that the former make data and control flow explicit through architectural connections, while the latter use import/export connections primarily to make names and types defined in one module visible to client modules [51].…”

Software Architecture and Software Configuration Management

“…The term module interconnection language [5] denotes a group of languages that were developed from the mid 70s to the mid 80s. The first module interconnection languages were designed to add architectural information that could not be expressed in contemporary programming languages.…”