Tichy, W.F.: Software development control based on module interconnection. In: Proceedings of the IEEE 4th International Conference on Software Engineering, Pittsburgh, Pennsylvania, IEEE Computer Society Press (1979) 29--41  Home/Search   Document Not in Database   Summary   Related Articles   Check

....as well as their relationships. A system model is usually described at the level of source objects (in particular, program source code) but it may also contain rules for producing the derived objects. The system modeling language may be either specific (for design and implementation objects [12, 13]) or it may deal with arbitrary software objects [14 16] A great variety of tools have been developed for SCM, see e.g. the Ovum reports [17] for information about commercial tools. The services provided by SCM systems may be classified according to the functions introduced in Section 4.1 ....

....specifically with design objects, and languages for arbitrary software objects. With respect to system modeling, it is instructive to study the evolution of the Adele system. An early version of the Adele system [13] offered a predefined module interconnection language derived from Intercol [12]. However, this made it difficult to model non code objects; for example, even a simple textual document was required to have an interface and a body. Furthermore, the user was forced to adopt the predefined language for programming in the large. Thus, more flexibility and generality is required. ....

Tichy, W.F.: Software development control based on module interconnection. In: Proceedings of the IEEE 4th International Conference on Software Engineering, Pittsburgh, Pennsylvania, IEEE Computer Society Press (1979) 29--41

....memory, however its side effect descriptions are mixed with source code so that the reembedding of a part of the system may not be as easy as with CoSy. CoSy also allows much more kinds of embedding than JADE, and allows flexible configuration and non deterministic execution. In early works of [Tic79] and [DK76] they define the concepts of a Module Interconnection Language. This specification language consists of simple inputoutput specification but is dependent on the implementation language of the modules, because it includes its type concept. In many aspects CoSy has inherited from IDL ....

Walter F. Tichy. Software Development Control Based on Module Interconnection. In Proc. of the 4th International Conference on Software Engineering, Sep 1979.

....be represented by objects and relationships in the repository underlying the SCM system. In the context of this paper, it is important to distinguish between two kinds of system modeling approaches: System models dealing with design (and implementation) objects. Examples include e.g. Intercol [15], Adele [4] and PCL [17] Systems are described in terms of modules, export and import interfaces, subsystems, etc. These system modeling approaches compete with architectural languages. Compared to these, they are less expressive with respect to system composition and consistency. On the other ....

....man s architecture description language . That is, the user can adopt that language as an option in the absence of a full fledged architecture description language. This lesson has been learned e.g. in Adele. Adele I [4] offered a predefined module interconnection language derived from Intercol [15]. This made it difficult to model non design objects, and it forced the user to adopt the predefined language for programming in the large. For example, even a simple textual document was required to have an interface and a body. In Adele II [5] there is a predefined system model that the user ....

W. F. Tichy. Software development control based on module interconnection. In Proc. IEEE 4th International Conference on Software Engineering, pages 29--41, Pittsburgh, PA, Sept. 1979. IEEE Computer Society Press.

....the construction of very large systems [DeRemer76] Typically a module interconnection language specifies the interfaces between modules by the type (abstract type) range and access allowed to the data being passed. Module interconnection languages have been advocated in many different settings [Campos77, Campos78, Goodenough74, Thomas76, Tichy79]. Primarily of interest here is the use of a module interconnection language to represent families of software systems as described in [Cooprider79, Tichy80] This work used a MIL to coordinate the construction of similar software systems with different features for different target languages. The ....

Tichy, W.F., Software Development Control Based on Module Interconnection, In Proceedings of the Fourth Conference on Software Engineering, pages 29-41, IEEE Press, September, 1979.

....Chapter 2. Related Work 29 2.5.2 MILs A number of Module Interconnection Languages (MILs) have been developed to support the description of large scale program structure independent of any particular programming language or system. These include languages such as MIL75 [DK76] and INTERCOL [Tic79] and are surveyed by Prieto Diaz and Neighbors [PDN86] These languages define program structure through definition use bindings that associate definitions of program constructs such as data structures and functions with uses of those constructs. Like the module facilities of programming ....

Walter F. Tichy. Software development control based on module interconnection. In Proceedings of the Third International Conference on Software Engineering, pages 29--41. IEEE Computer Society Press, May 1979.

....were introduced. The importance of module interconnection structures for programming in the large was first recognized by DeRemer and Kron [9] Several variants of module interconnection languages [30] 28] have been defined that support various features of programming in the large (e.g. Intercol [44], PIC [46] and NuMIL [27] This corresponds to the module structure in our categorization. When systems became distributed, programmers needed to consider dynamic structure and communication, coordination, and synchronization. Functional components needed to be allocated within the dynamic ....

W. Tichy. Software development control based on module interconnection. In Proceedings of the Third International Conference on Software Engineering, pages 29-41, IEEE Computer Society Press, May 1979.

....Languages (MIL s) They consist of formal grammar constructs, deciding on the specifications required to interconnect modules and produce the overall system. Since the notion of MIL s was introduced in 1975 [DeRemer75] they have evolved through several stages [Thomas76, Cooprider79, Tichy79] and recently attention has been paid to the possibilities of system building from reusable components. 28 MIL descriptions are concerned with the exchange of resources, where a resource is any named entity from a programming language, for example a variable or type, which can be provided by a ....

Tichy, W.F. "Software Development Control Based on Module Interconnection", Proc. 4th International Conf. on Software Engineering, pp.29-41 (September 1979).

....a module uses a resource, it has access to that resource; and so on. Since DeRemer and Kron s MIL, MILs have been developed for specific languages, like Mesa [MMS79] and Ada [CE78] and have provided a base from which to support software construction [Th76] version control [Co79] system families [Ti79], and dynamic configuration [MKS89] Enough examples are available to develop models of the design space [Pe87, PN86] These early module interconnection languages require considerable prior agreement between the developers of different modules. For example, they assume that simple name matching ....

Walter F. Tichy. "Software Development Control Based on Module Interconnection". Proc. 4th International Conference on Software Engineering, Munich, 1979, pp. 29-41.

....of Thomas [13] whose rigorous approach helped develop a number of useful results for the theoretical foundations of MILs. In 1979, Cooprider made further progress by integrating version control and system construction facilities with a module interconnection language [14] Tichy s work on INTERCOL[15] added capabilities to model families of systems and modules and, along with Cooprider s work, formed the basis of the Gandalf system. NuMIL [16] was developed as a basis for improving the quality of software 5 maintenance in large software systems. Its major influence was to separate ....

Tichy, W.F. "Software development control based on module interconnection ". in Proc. 4th Int. Conf. on Software Eng. 1979. Munich.

....Languages An alternative to the use of module interfaces for describing system composition is to use a special language for the task. These are sometimes called module interconnection languages (MILs) Representative examples of early language designs include MIL75 and Intercol [DK76, Tic79, PDN86] A more recent example is the module description features of Standard ML (SML) MTH90] Module interconnection languages partially separate the description of a system configuration from the parts of the system that are being composed. Some also provide parameterization features for ....

Walter F. Tichy. Software development control based on module interconnection. In Proceedings of the Third International Conference on Software Engineering, pages 29-- 41. IEEE Computer Society Press, May 1979.

....Chapter 2. Related Work 29 2.5.2 MILs A number of Module Interconnection Languages (MILs) have been developed to support the description of large scale program structure independent of any particular programming language or system. These include languages such as MIL75 [DK76] and INTERCOL [Tic79] and are surveyed by Prieto Diaz and Neighbors [PDN86] These languages define program structure through definition use bindings that associate definitions of program constructs such as data structures and functions with uses of those constructs. Like the module facilities of programming ....

Walter F. Tichy. Software development control based on module interconnection. In Proceedings of the Third International Conference on Software Engineering, pages 29--41. IEEE Computer Society Press, May 1979.

....e.g. What varieties of X could be built, on the assumption that all the compilations succeed . We conclude that any build system will need to perform abstract interpretation, and it is fortunate that deductive systems are quite amenable to this. We note that module interconnection languages [Tich79] [Somm92] are more concerned with expressing detailed module compatibilities that they are with defining the derivation dependencies of items (i.e. how and from what an item can be derived) In DERIVE, module compatibilities must be encoded in shared attributes, which can be structured (as ....

W. F. Tichy, "Software Development Control based on Module Interconnection ", Proceedings of the 4th International Conference on Software Engineering, pp. 29-41, IEEE Munich (1979).

....to that resource; and so on. Since DeRemer and Kron s MIL, MILs have been developed for specific languages, like Mesa [Mitchell et al. 79] and Ada [Campos Estrin 78] and have provided a base from which to support software construction [Thomas 76] version control [Cooprider 79] system families [Tichy 79] and dynamic configuration [Magee et al. 89] Enough examples are available to develop models of the design space [Perry 87, Prieto Diaz Neighbors 86] These early module interconnection languages require considerable prior agreement between the developers of different modules. For example, ....

Walter F. Tichy. Software Development Control Based on Module Interconnection. Proc. 4th International Conference on Software Engineering, Munich, 1979, pp. 29-41.

No context found.

Walter F. Tichy. Software Development Control Based on Module Interconnection. In Proc. of the 4th International Conference on Software Engineering, Sep 1979.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC