D. Leblang and R. Chase, `Parallel software configuration management in a network environment', IEEE Software, 20, (11), 28--35 (1987).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....to group sets of versions that are consistent with each other into configurations. This would enable programmers to reconstruct a system using the correct versions of the objects that comprise the system. This notion of configurations is supported by many software development systems(e.g. DSEE [Leblang and Chase, Jr. 87] A recent survey by Katz gives a comprehensive overview of version and configuration management systems [Katz 90] Supporting configurations reduces the problem of consistency to the problem of explicitly naming the set of consistent versions in configuration objects. This basically solves the ....

Leblang, D. B., and Chase, R. P., Jr. "Parallel Software Configuration Management in a Network Environment." IEEE Software 4, 6, November 1987, pp. 28-35.

....of tools away from where they would normally run. The simplest is remote job control, such as UNIX rsh, which invokes a program or script on a specified host. It can be used to take advantage of tools that do not operate on the user s machine. Some environments, 35 such as Spice [15] and DSEE [43], automatically distribute tool executions to other hosts on a local area network. Their main goal is to achieve load balancing, e.g. for a large system build. These approaches seem limited to batch tools, such as compilers, with no user interaction. Batch tools inherently do not admit sharing of ....

David B. Leblang and Robert P. Chase, Jr. Parallel software configuration management in a network environment. IEEE Software, 4(6):28--35, November 1987.

....selection is the result of applying a single default rule, i.e. select the most recent version . In [4] no precaution was made to handle the case when some or all of the filters failed to produce a nonempty set. Another frequently used approach is to use rules. For example in the system DSEE [10] there is defined a set of rules which are interpreted sequentially until the sought component is selected. The language for writing rules allows defining default rules, dynamic rules (e.g. select the most recent version) and conditional rules (if then) Despite the fact that such kinds of rules ....

....there is proposed an orthogonal organization of variants and revisions. A variety of architectural relations can be defined between variants and families. The fact that architectural relations can be defined between variants and families allows our model to be more generic as e.g. those of [1, 10, 11, 18] in the sense that several models are usually needed to describe the information contained in our model. In particular, they allow architectural relations to be defined only between component families. Being essentially a graph search, it is inevitable to have a method for selecting a proper ....

[Article contains additional citation context not shown here]

D.B. Leblang and R.P. Chase. Parallel software configuration management in a network environment. IEEE Software, 4(6):28--35, 1987.

....that resembles software components. Units relate to other units by uses links; selecting a specific version of a unit propagates proper selections to all units that it uses. However POEM seems to have no support for part whole relations that are important to express a hierarchical structure. DSEE [13] relies on a centralised system model meaning that version selection engines are required to be able to recreate context for milestones and releases. As already noted modifying the software design structure means changing the system model which creates the problem of ensuring the synchronisation: ....

D. B. Leblang and R. P. C. Jr. Parallel Software Configuration Management in a Network Environment. IEEE Software, pages 28--35, Nov. 1987.

....vehicles for dynamic re configuration. They do not address the issues listed above which we felt were critical to our needs. 3. Languages to support version management. These ranged from very simple languages such as Make [9] through more abstract system building languages such as DSEE [10] to database configuration languages such as that provided by the Adele system [11] These languages were more relevant to our work as we planned to integrate PCL to version management systems and provide a system building facility. As discussed later, we have adopted the attributed model of ....

Leblang, D.B. and R.P. Chase, "Parallel Software Configuration Management in a Network Environment". IEEE Software, 1987. 4 (6): p. 28-35.

....through all of their life cycle, i.e. from requirements through coding and testing to documentation and user manuals. This covers a wide span of quite different systems ranging from simple tool kit like systems as UNIX [1] and A Programmer s Workbench [2] to fully integrated systems as DSEE [3] and Mj lner [4] In this field many different problems are encountered such as configuration management, version control, uniform descriptions, using data bases as the means of integration, problems arising from the distribution of a project on many different workstations, dealing with ....

: David B. Leblang, Robert P. Chase, Jr.: Parallel Software Configuration Management in a Network Environment, IEEE Software, November 1987.

....state the restructuring made between 1.3 and 1.4 of ComPack. This means that preserving context must be handled by the selection mechanism. As already mentioned in section 5.1 I think this leads back into the unfortunate use of tags . Explicit configuration objects are used for instance in DSEE [Leblang et al. 87] and Mj lner ORM [Gustavsson90] Tichy emphasise that a software object can be a configuration as well and uses it in his AND OR graph [Tichy88] A baseline configuration object is a better solution than tags but still has some of the deficiencies: We must remember to create one, put it under ....

David B. Leblang, Robert P. Chase Jr., Parallel Software Configuration Management in a Network Environment, IEEE Software, Nov. 1987, p. 28-35

....building easier, it provides for a high degree of reuse. One can reuse a software system model, built generic configuration and configuration requirements. The fact that architectural relations can be defined between variants and families allows our model to be more generic as for example [1, 5]. One model created for presented method usually has to be described by more than one model in above citied approaches, because in them architectural relations can be defined only between component families. Besides defining relations, the software engineer can specify conditions which must be ....

D.B. Leblang and R.P. Chase. Parallel software configuration management in a network environment. IEEE Software, 4(6):28--35, 1987.

....reliability and high availability as machines and network links fail. For example, Mercury [23] is a multiple user, language oriented environment that depends on a special distributed algorithm that simulates a small shared memory to guarantee consistency among module interfaces; DSEE s database [27], on the other hand, is a simple extension of Apollo s network file system. Distributed Model = network mechanisms , distributed objects ) The project management model is orthogonal to the progression from the extended toolkit model to the distributed model. These ....

David B. Leblang and Robert P. Chase, Jr.. "Parallel Software Configuration Management in a Network Environment", IEEE Software ,November1987.pp28-35.

....and dragging down the speedup curve. The speedup of lsmake is substantially higher than any other parallel make facility reported so far. For instance, the pmake facility in Sprite using kernel supported process migration [9] and the load build system (more sophisticated make) in Apollo Domain [20] do not exceed speedups of 5 or 6. As discussed in Section 4.5, we believe that the higher performance of lsmake is attributable to the lower overhead of remote execution in Utopia, and the asynchronous nature of task dispatching adopted in Utopia. These measures not only keep all the remote hosts ....

David B. Leblang and Jr. Robert P. Chase. Parallel software configuration management in a network environment. IEEE Software, 20(11), Nov. 1987.

....analysis algorithm to guarantee consistency among module interfaces; Mercury supports a cache consistency protocol that maintains global attribute consistency to the degree possible given network partitions. Sun Microsystem s Network Software Environment (NSE) provides most of facilities of DSEE [40], and adds multi user integration environments [2] that require extensions to Sun s network file system (NSF) to support loop back mount structures. Distributed Model = distributed objects , network mechanisms , high reliability and availability ) As in the preceding ....

David B. Leblang and Robert P. Chase, Jr.. "Parallel Software Configuration Management in a Network Environment", IEEE Software, 4:6 (November 1987). pp 28-35.

....mean delays by 35 50 compared to non preemptive migration where jobs can only be migrated before they have started. Many implementations and algorithms for load balancing have been proposed. Early efforts include Leblang and Chase s implementation of a parallel make on a network of workstations [LC87] and Theimer s techniques for finding hosts for remote execution [TL89] A more recent study by Kunz using an artificial workload [Kun91] examines the use of different host workload descriptors to determine where to schedule processes. He discovers that using the node with the minimal number of ....

D. B. Leblang and R. P. Chase, Jr. Parallel software configuration management in a network environment. Software, 4(6):28--35, November 1987.

No context found.

D. Leblang and R. Chase, `Parallel software configuration management in a network environment', IEEE Software, 20, (11), 28--35 (1987).

No context found.

D.B. Leblang and R.P. Chase. Parallel software configuration management in a network environment. IEEE Software, 4(6):28--35, 1987.

No context found.

D.B. LEBLANG, R.P. CHASE. Parallel software configuration management in a network environment. IEEE Software, 4(6):28--35, 1987.

No context found.

David B. Leblang and Robert P. Chase, Jr. Parallel Software Configuration Management in a Network Environment. IEEE Software 4(6):28-35, November, 1987.

No context found.

D.B. Leblang and R.P. Chase, "Parallel Software Configuration Management in a Network Environment," IEEE Software, pp. 28-35, November 1987.

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