F. Tichy, Software Development Control Based On System Structure Description, PhD. Thesis, Carnegie Mellon University, 1980.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the system at a particular time. Thus, snapshot systems present sets of known valid system images at a set of well known times. Analysis of historical changes: A history of versions can help answer questions about how a file reached a certain state. For example, version control systems (e.g. RCS [43], CVS [16] keep a complete record of committed changes to specific files. In addition to selective recovery, this record allows developers to figure out who made specific changes and when those changes were made. Similarly, self securing storage seeks to enable post intrusion diagnosis by ....

....which use a log structured file system to do online backup by recording the entire log to tertiary storage. Chervenak, et al. performed an evaluation of several snapshot systems [10] Version control systems are user programs that implement a versioning system on top of a traditional file system [16, 27, 43]. These systems store the current version of the file, along with differences that can be applied to retrieve old versions. These systems usually have no concept of checkpointing, and so recreating old versions is expensive. Write once storage media keeps a copy of any data written to it. The ....

W. F. Tichy. Software development control based on system structure description. PhD thesis. Carnegie-Mellon University, Pittsburgh, PA, January 1980.

....system at a particular time. Thus, snapshot systems present a set of known valid system images at a set of well known times. Analysis of historical changes: A history of versions can help answer questions about how a file reached a certain state. For example, version control systems (e.g. RCS [43], CVS [15] keep a complete record of changes to specific files. In addition to selective recovery, this record allows developers to figure out who made specific changes and when those changes were made. Similarly, self securing storage seeks to enable post intrusion diagnosis by providing a ....

....a log structured file system to do online backup by recording the entire log to tertiary storage [14, 20] Chervenak, et. al, performed an evaluation of several snapshot systems [10] Version control systems are user programs that implement a versioning system on top of a traditional file system [15, 26, 43]. These systems store the current version of the file, along with differences that can be applied to retrieve old versions. These systems usually have no concept of checkpointing, and so recreating old versions is expensive. Write once storage media keeps a copy of any data written to it. The ....

W. F. Tichy. Software development control based on system structure description. PhD thesis. Carnegie-Mellon University, Pittsburgh, PA, January 1980.

....automatic reconfiguration of a system when changes are made to a component. Also, more detailed analysis of changes to components reduces much useless compiling [24, 31] Integrated systems attempt to combine these ideas. Among the better known are System Modeller [11, 23] Tichy s work at CMU [26, 27], GANDALF [4, 9, 17] Adele [1, 2, 5, 6] DSEE [12] Jasmine [15] shape [13, 14] and Odin [3] These systems, to a greater or lesser degree, allow for the development of large projects being developed by many different programmers. They use software databases, version control for the files, ....

Walter F. Tichy. Software Development Control based on System Structure Description. PhD thesis, Carnegie-Mellon University, Pittsburgh (PA), USA, 1979.

....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 interconnection language that Draco uses for components is similar to these module connection languages. Software Components The construction of software ....

Tichy, W.F., Software Development Control Based on System Structure Description, PhD thesis, Carnegie-Mellon University, January, 1980, CMU-CS-80-120.

....design is close to the definition of software architecture 2 given by Schwanke et al. 26] who view architectures as the permitted or allowed set of connections among components. Module Interconnection Languages (MILs) such as those defined by DeRemer and Kron [7] Cooprider [5] and Tichy [29], represent early attempts to define languages for specifying architectural designs. MILs are layered on top of common programming languages. Their advantage is that they closely couple the design specification to the source code, making the specification amenable to mechanical processing ....

Tichy, W. F. Software Development Control Based on System Structure Description. Tech. Rep. CMU--CS--80--120, Computer Science Department CMU, January 1980.

....data may need to be transformed to remain consistent with the permuted extensions. At the module level, extensions by means of additional facilities are always substitutable as long as these extensions do not require additional facilities (see Tichy s definition of upward compatibility [24]) At the system level, we can relax the rule about no new required facilities for module extensions and define a notion of system compatibility in which a module is allowed additional required facilities as long as they are already required by the system or are provided internally by the ....

Walter F. Tichy. Software Development Control Based on System Structure Descriptions. Ph.D. Thesis, Computer Science Department, Carnegie-Mellon University, January 1980.

....specifications act as a useful reference for developers and maintainers, their informality implies that they cannot be mechanically checked for syntactic and semantic consistency. Module Interconnection Languages (MILs) such as those defined by DeRemer and Kron [3] Cooprider [2] and Tichy [18], represent early attempts to define languages for specifying architectural designs. MILs are layered on top of common programming languages. Their advantage is that they closely couple the design specification to the source code, making the specification amenable to mechanical processing. ....

Tichy, W. F. Software Development Control Based on System Structure Description. Tech. Rep. CMU--CS--80--120, Computer Science Department CMU, January 1980.

....existing data may need to be transformed to remain consistent with the permuted extensions. At the module level, extensions by means of additional facilities are always substitutable as long as these extensions do not require additional facilities (see Tichy s definition of upward compatibility [9]) At the system level, we can relax the rule about no new required facilities for module extensions and define a notion of system compatibility in which a module is allowed additional required facilities as long as they are already required by the system or are provided internally by the ....

Walter F. Tichy. Software Development Control Based on System Structure Descriptions. Ph.D. Thesis, Computer Science Department, Carnegie-Mellon University, January 1980.

....and data access, assignment of functionality to design elements, physical distribution, performance, and so on. Earlier textual notations for specifying architectural designs, called Module Interconnection Languages (MILs) include those by DeRemer and Kron [5] Cooprider [3] and Tichy [16]. More recent visual ones include those by Schwanke et al. 15] Penny et al. 13, 10] and the authors [9] Although these notations differ in their details, they all feature mechanisms for aggregating related software components (procedures, modules, classes, files) into composite components ....

Tichy, W. F. Software Development Control Based on System Structure Description. Tech. Rep. CMU--CS--80--120, Computer Science Department CMU, January 1980.

....and family model environments. Obviously, no cooperation or communication mechanisms are needed for the individual environments. Only relatively simple mechanisms are needed in a family situation where both cooperation and communication function at an informal level. For example, SCCS [19] or RCS [23] provide minimal coordination among developers in UNIX environments; electronic mail is used to some advantage within DSEE [10] to support communication among project developers about various important project events. However, a much richer set of policies and their supporting mechanisms and ....

....relationships so that they can be automatically determined. Moreover, current mechanisms tend to concentrate on relationships of versions independent of their use and ignore contextual relationships. Note that there is some consideration of their use in the emphasis on resource dependence: Tichy [23] has a notion of upward compatibility that depends upon the resources provided as well as those depended upon. However, this concept falls short of what is needed in the tools to manage the building of systems from components. Invariant [15] the version management part of Inscape, defines ....

Walter F. Tichy. Software Development Control Based on System Structure Description. Ph.D. Thesis, Computer Science Department, Carnegie-Mellon University, January 1980.

.... [15] 4 Preliminary Groundwork The approach I present in the next section is based on the approach that I have previously taken in the Inscape Environment: specifying module interfaces in Instress [14] reasoning about the composition of components in the construction and evolution of systems [17], and reasoning about the relationships among component interfaces [13] 4.1 Interface Specifications Instress module specifications contain three components: predicate definitions, data specifications, and operation specifications. Predicates may be defined as primitive (that is, uninterpreted) ....

Walter F. Tichy. Software Development Control Based on System Structure Descriptions. Ph.D. Thesis, Computer Science Department, Carnegie-Mellon University, January 1980.

....Those that arose from early work into the difficulties found in programming in the large and those whose main concern is the field of dynamic reconfiguration. Those that fall into the first area are known as Module Interconnection Languages (MILs) MIL75 [DK76] Cooprider s MIL [Coo79] INTERCOL [Tic80],Jasmine [MW86] SySL [TS89] they allow the description of large software projects in terms of interconnected modules and the relationships that exist between these modules. Languages concerned with dynamic reconfiguration are known as configuration programming languages (Conic [JMS89] and have ....

....variability must be expressible. It must also be possible to associate attributes (names allowed values) to provide non functional information. The family level : This level is concerned with modelling a group or family of related software systems. This level is also recognized by INTERCOL [Tic80] and NuMIL [Nar85] This reflects the fact that system evolution results in several software systems which have evolved from a common base. A generic system structure is instantiated by giving it a type and mapping the identified structural entities onto a set of logical system components. Logical ....

Walter F. Tichy. Software Development Control Based on System Structure. PhD thesis, Carnegie-Mellon University, 1980.

....object reference method is described in detail. Early work on MILs was performed by DeRemer and Kron [DeKr75] Shortly after, project Gandalf focused on the software development environment itself [HaNo86, Notk85] implementing a MIL known as Intercol for describing the structure of an application [Tich80], and permitting mixed language programming (subject to the restriction that the language processors be created to conform to Gandalf interfacing structures. Most recently, environments and languages such as Inscape and SLI are appearing [Perr89, WWRT91] in which developers can express not only ....

Tichy, Walter F. Software Development Control Based on System Structure Description. Carnegie-Mellon University Dept. of Computer Science Report CMU-CS-80-120, (January 1980).

....for the Driver module and two primitive implementations for the Factorial module. PACKAGE specifications typically consist of a series of declarations of modules and their implementations. Modules may have multiple associated implementations that are either composite or primitive. Unlike INTERCOL [27] and the previous version of the software packager [1] instances of modules within composite implementations do not need to specify which implementation should be used. The choice is determined by the packager tool. The PACKAGE specification enumerates all possible implementations of modules ....

....Many configuration management tools present similar organizations of software structures using hierarchical file systems with enhancements for handling alternatives. For example, NMAKE depends on a standard directory structure for organizing product implementation alternatives. INTERCOL [27] presents a similar structure with implementation choices within the configuration language. Our approach is similar, but the choice of implementation for a component is not specified explicitly in the structure, rather it is left to the packager. Many programming systems support the separation of ....

[Article contains additional citation context not shown here]

Tichy, W., Software Development Control Based on System Structure Description, Carnegie Mellon University Computer Science Department, January 1980.

No context found.

F. Tichy, Software Development Control Based On System Structure Description, PhD. Thesis, Carnegie Mellon University, 1980.

No context found.

Tichy, W., Software Development Control Based on System Structure Description, Carnegie Mellon University Computer Science Department, January 1980.

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