D. B. Leblang and R. P. Chase, Jr.. "Computer-Aided Software Engineering in a Distributed Workstation Environment". In Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pp. 104--112, May 1984.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....an infrastructural data model, intended for use in creating more complex data models for specific uses or environments. Since these systems provide fundamental data model building blocks, they are a good test of the uniformity of containment data modeling. As a scalability test, the models of DSEE [9], ClearCase [8] and DeltaV [1] are presented, and aspects of the evolution of these complex models are discussed. The last set of models contrast the data models of two different system types, the version graph system CoMa [18] and the change based system PIE [5] and demonstrate that ....

....the assumptions of each to be compared. 4.2 Tracing the Evolution of Data Models Since all of the systems modeled so far have been relatively simple, it is reasonable to be curious about how well containment modeling handles more complex systems. We address this issue by examining the DSEE [9], ClearCase [8,19] and DeltaV [1] systems, modeled in Figure 4 Figure 6. Together they form a direct intellectual lineage, with DSEE and ClearCase having the same initial system architect, David Leblang, and with ClearCase influencing DeltaV via the direct involvement of Geoff Clemm, who was ....

[Article contains additional citation context not shown here]

D. B. Leblang and J. R. P. Chase, "Computer-Aided Software Engineering in a Distributed Workstation Environment," Proc. ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Pittsburgh, PA, April, 1984, pp. 104-112.

....are described individually in Section 4.1. Subsequently, they are compared in Section 4.2 where we also draw some conclusions with respect to a layered architecture for uniform version management. 4.1 Version Models in SCM Systems 4.1. 1 ClearCase ClearCase [36] 14] is a successor of DSEE [37], 38] 32] which was developed in the mid 1980s. It is a commercial SCM system that versions file based data. Both files and directories are versioned items (total versioning) whose version spaces are represented by version graphs. Selective deltas are used to store versions efficiently. ....

D.B. Leblang and R.P. Chase, "Computer-Aided Software Engineering in a Distributed Workstation Environment," Proc. ACM SIGSOFT/SIGPLAN Software Eng. Symp. Practical Software Devdop- ment Environments, P. Henderson, ed., ACM SIGPLAN Notices, vol. 19, no. 5, pp. 104-112, May 1984.

....These systems are described indi vidually in Section IV A. Subsequently, they are compared in Section IV B, where we also draw some conclusions with respect to a layered architecture for uniform version man agement. A. Version Models in CM Systems ClearCase [36] 14] is a successor of DSEE [37], 38] 32] which was developed in the mid 80 s. It is a commer cial SCM system that versions file based data. Both files and directories are versioned items (total versioning) whose version spaces are represented by version graphs. Selective deltas are used to store versions efficiently. ....

David B. Leblang and Robert P. Chase, "Computer-aided soft- ware engineering in a distributed workstation environment," in Proceedings of the ACM SIGSOFT/SIGPLAN Software Engi- neering Symposium on Practical Software Development Environments, Peter Henderson, Ed., Pittsburgh, Pennsylvania, May 1984, ACM SIGPLAN Notices 19(5), pp. 104-112.

....is safe to re use a derived file from a different build. ClearCASE is a commercial SCM system that integrates version management with building, and that addresses many of Make s shortcomings [1] It is based on many of the ideas in the earlier DOMAIN Software Engineering Environment (DSEE) system [8, 7]. Unlike RCS and CVS, ClearCASE provides transparent access to older file versions. However, older versions are almost never accessed directly in practice. Instead, a ClearCASE view is used to transparently map an unversioned file name to a versioned one. The rules governing a view can be ....

David B. Leblang and Robert P. Chase, Jr. Computer-aided software engineering in a distributed workstation environment. SIGPLAN Notices, 19(5):104--112, May 1984.

....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, sometimes also for modules, as well as allowing the ....

David B. Leblang and Robert P. Chase, Jr. Computer-aided software engineering in a distributed workstation environment. In ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Pittsburgh (PA), USA, 1984.

....systems are described individually in Section IV A. Subsequently, they are compared in Section IV B, where we also draw some conclusions with respect to a layered architecture for uniform version management. A. Version Models in SCM Systems ClearCase ClearCase [36] 14] is a successor of DSEE [37], 38] 32] which was developed in the mid 80s. It is a commercial SCM system that versions le based data. Both les and directories are versioned items (total versioning) whose version spaces are represented by version graphs. Selective deltas are used to store versions eciently. Versions of ....

David B. Leblang and Robert P. Chase, \Computer-aided software engineering in a distributed workstation environment," in Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Peter Henderson, Ed., Pittsburgh, Pennsylvania, May 1984, ACM SIGPLAN Notices 19(5), pp. 104-112.

....is safe to reuse a derived file from a different build. ClearCASE is a commercial SCM system that integrates version management with building, and that addresses many of Make s shortcomings [1] It is based on many of the ideas in the earlier DOMAIN Software Engineering Environment (DSEE) system [12, 13]. ClearCASE provides access to file versions primarily through its view mechanism. A view is a set of rules that transparently map unversioned file names to versioned names. The rules governing a view can be specified in a variety of ways. They include provisions for always accessing the latest ....

D. B. Leblang and R. P. Chase, Jr. Computer-aided software engineering in a distributed workstation environment. SIGPLAN Notices, 19(5):104--112, May 1984.

....production since the middle of 1981. Thousands of networks and over 20,000 workstations have been installed. The largest single network consists of more than 1800 nodes. Contact: Paul H. Levine, Apollo Computer, Inc. Chelmsford, Massachusetts 01824 References: 146] 147] 148] 149] [150], 151] 152] 153] 154] 155] 156] 2.18 DUNIX Main Goal DUNIX integrates several computers connected by a local area network into a single UNIX machine providing access and location transparency. In addition, the complexity of the kernel is supposedly reduced. Advantages DUNIX meets ....

D.B. Leblang and R.P. Chase, "Computer-Aided Software Engineering in a Distributed Workstation Environment ", In Proc. SIGSOFT/SIGPLAN Software Engineering Symp. on Practical Software Environments, pages 104--112, 1984.

.... [28] For the production of systems, automation is provided by tools like make [29] distributed and parallel builds on heterogeneous platforms were provided by [64] and [65] and before that reproducibility and traceability from a system to its components was supported by bill of materials in [66]. Flexible and powerful system models have been proposed by both [66] and [67] Support for specifying process aspects of the configuration management activities was investigated in [68] 5.2 Present Several problems are presently being worked on in the academic world and are giving insight that ....

.... like make [29] distributed and parallel builds on heterogeneous platforms were provided by [64] and [65] and before that reproducibility and traceability from a system to its components was supported by bill of materials in [66] Flexible and powerful system models have been proposed by both [66] and [67] Support for specifying process aspects of the configuration management activities was investigated in [68] 5.2 Present Several problems are presently being worked on in the academic world and are giving insight that will mature into results to be adopted in the next few years. In ....

[Article contains additional citation context not shown here]

D. B. Leblang, R. P. Jr. Chase, Computer-Aided Software Engineering in a Distributed Workstation Environment, Proc. of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, April 1984, ACM SIGPLAN Notices, 19(5), May 1984.

....equivalent to, and component of relationships [Katz 89] have been proposed. Implementation Schemes: Implementation of versions in terms of deltas to support the incremental addition of data to a version has primarily been studied for the software engineering environment [Rochkind 75, Leblang 84] There has been relatively little effort on developing versioning systems that support the evolutionary nature of the design process, i.e. the incremental addition of data to an individual version. The subject of constraint management has been a very active area in engineering automation, and ....

Leblang, D.B. and R.P. Chase, "Computer Aided Software Engineering in a Distributed Workstation Environment," Proceedings of the ACM SIGPLAN/SIGSOFT Conference on Practical Software Development Environments, pp 104-112, April 1984.

....to also support multiple users (as opposed to earlier single user systems) and often included management of the software artifacts. ISTAR [27] is a representative IPSE that emphasized integration of managerial as well as engineering tasks and tools 1 . Other systems from that era include DSEE [69] and NSE [53] 1.1 Process Modeling In order to provide comprehensive project support, SE researchers and developers had to observe and understand project development processes. This marked the beginning of the process era [70] pioneered by Humphrey [55] and Lehman [71] The realization that ....

David B. Leblang and Robert P. Chase, Jr. Computer-aided software engineering in a distributed workstation environment. In Peter Henderson, editor, ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pages 104--112. ACM Press, April 1984. Special issue of SIGPLAN Notices, 19(5), May 1984.

....is safe to reuse a derived file from a di#erent build. ClearCASE is a commercial SCM system that integrates version management with building, and that addresses many of Make s shortcomings [1] It is based on many of the ideas in the earlier DOMAIN Software Engineering Environment (DSEE) system [8, 9]. ClearCASE provides access to file versions primarily through its view mechanism. A view is a set of rules that transparently map unversioned file names to versioned names. The rules governing a view can be specified in a variety of ways. They include provisions for always accessing the latest ....

D. B. Leblang and R. P. Chase, Jr. Computer-aided software engineering in a distributed workstation environment. SIGPLAN Notices, 19(5):104--112, May 1984.

....or whether different versions of M(X) use a different set of software units. Revise A Figure 6: Version control of a module A Y D A A A D D D Y Y Y Modify A and Y Freeze A C X (a) c) b) d) C C C C C X X X X X A A A D D D Y Y Y 6 Like DSEE [Leblang 84] SHAPE [Mahler 88] and Adele [Estublier 85] we use version selection rules to make the selection of versions more flexible. But since versions are selected by the uses links in our framework, we associate these rules with uses links instead of putting them in a separate description. A version ....

....of files or individual objects, that are generated by other programmers. Our framework also enables us to reduce the interference between programmers, and increase the sharing of software artifacts more naturally. Our scenario for cooperative programming follows the general strategy of DSEE [Leblang 84] and SHAPE [Mahler 88] Programmers should use the older but more stable versions of code from their colleagues, and work on the newer but experimental versions of their own code. But instead of dealing with files, our framework allows a programmer to choose and use modules generated by other ....

[Article contains additional citation context not shown here]

David B. Leblang and Robert P. Chase, Jr., "Computer-Aided Software Engineering in a Distributed Workstation Environment," in SIGPLAN Notices, vol. 19, No. 5, pp. 104-113, April 1984.

....output files can also be destroyed. TREC associates dependency information with each file, rather than relying on a static description in a separate file. Several systems have attempted to extend the automatic control of derived objects beyond the simple (but powerful) model used by make. DSEE [Leblang Chase Jr. 1984, Leblang McLean Jr. 1985] Odin [Clemm Osterweil 1990] and Vesta [Levin McJones 1993, Heydon et al. 1997] provide tools for modeling the behavior of programs, enabling the concise specification of derivation rules, and distributing changes to developers. Their declarative style suits ....

D. B. Leblang and R. P. Chase Jr. "Computer-Aided Software Engineering in a Distributed Workstation Environment". In Proceedings BIBLIOGRAPHY 201 of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pp. 104--112, May 1984.

....of using workareas instead of workspaces is that we can handle the sharing of software artifacts between programmers more naturally. If two programmers use the same version of a subsystem, then they will automatically shared all the source objects and derived objects of that subsystem. In DSEE [14] and SHAPE [17] the sharing of derived objects is handled by more complicated mechanisms. Different kinds of software units need different data attributes and different implementation of their operations. For example, some software units used in a C program may contain YACC code instead of plain ....

....approach. The parameters for system building are stored on software units instead of passed as arguments to functions. Early version control systems like SCCS [20] and RCS [24] handle the versions of files only. CVS [3] enhances RCS by letting programmers handle versions of directories. DSEE [14] allows version selection in terms of threads that refers to files or other threads. ClearCase [1] enhances the functionality of DSEE and runs on several platforms without special supports from the underlying operating system. Version control in terms of objects is studied in the area of software ....

[Article contains additional citation context not shown here]

David B. Leblang and Robert P. Chase, Jr., "Computer -Aided Software Engineering in a Distributed Workstation Environment," in SIGPLAN Notices, vol. 19, No. 5, pp. 104-113, April 1984.

....5.4 Source file representation Systems that store many versions of source files customarily provide a mechanism to store only the version to version changes (or deltas ) rather than complete copies of each version. Experience with conventional source code control systems [Tichy] Rochkind] LeBlang and Chase] has shown that the reduction in storage can be quite substantial. We therefore augmented the simple source storage scheme described in section 5.2 with what is generally called a delta engine . Recall that in Vesta repositories derived files may be deleted when space becomes limited, but source ....

....modified to access repository objects. The concept of immutability and the source derived distinction have no special status; they are simply properties attached to certain object types. 6.3 Hybrids Between these two extremes lie systems that combine aspects of each. These systems (such as DSEE [LeBlang and Chase] ClearCase [Atria Software] and TeamNet [TeamOne] begin with a file based approach and tend to retain the file naming regime of the platform under them. Sometimes the naming is introduced seamlessly, so that unmodified tools can access repository objects; in other cases, special tools must be ....

[Article contains additional citation context not shown here]

David B. LeBlang and Robert P. Chase, Jr. Computeraided software engineering in a distributed workstation environment. SIGPLAN Notices 19, 5, May 1984.

....failure mode cone curved 4 Related Work and Discussion Up to date there hardly exists computer supported maintenance or even concepts for maintenance of FMEA data. Ideas for notification mainly originate in the context of versioning. They come from CAD and software engineering environments [2] [7]. In contrast to the CAD domain, there is no configuration problem for FMEA cases, because there are no alternative versions of an FMEA case. And as a facilitation compared to software development, the relatively fix structure of an FMEA case implies much of the semantics of the contained data. ....

David Leblang and Robert Chase. Computeraided software engineering in a distributed workstation environment. In Proc. of the ACM SIGPLAN /SIGSOFT Conference on Practical Software Development Environments, pages 104--112, April 1984.

....is notification, so that cooperating programmers can be kept informed of what each other is doing. NSE provides a general notification mechanism, but at a rather coarse grain basically at the level of checking a component in or out. The Apollo Domain Software Engineering Environment (DSEE) Leblang 84] provides a similar notification scheme, but at the less coarse grain of dependencies among individual files. Our Mercury system permits the programmers to select either coarse or fine grain, where in the fine grained case programmers are automatically informed when changes 4 to interfaces of ....

David B. Leblang and Robert P. Chase, Jr. Computer-Aided Software Engineering in a Distributed Workstation Environment. In Peter Henderson (editor), SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pages 104-112. ACM Press, April, 1984. Special issue of SIGPLAN Notices, 19(5), May 1984.

....Much of the past and current work in version and configuration management has addressed the problem of keeping track of how components are derived and maintaining that level of consistency. We have systems that manage version and configuration histories for example SCCS [23] RCS [25] NSE [12], etc by effectively keeping either a tree or a graph representing the derivation history of source versions. We have various tools that provide automated derivation of secondary objects 1 for example, various forms of Make [7, etc] or such opportunistic processors as Marvel [10] to ....

David B. Leblang and Gordon D. McLean, Jr. "Computer-Aided Software Engineering in a Distributed Workstation Environment", Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, SIGPLAN Notices, 19:5 (May 1984). pp. 104-112.

....Composite Object service, which may allow versions of composite objects or compositions of different versions. Other closely related services are the Name and Query services. Draft November 24, 1993 Edition 45 4. 16.8 Examples The set of systems which address versioning includes: PCTE [35] DSEE [58]; ATIS [26] NSE [1] Aspect [44] and Damokles [28] 4.17 Composite Object Service This service creates, manages, accesses, and deletes composite objects, i.e. objects composed of other objects. This may be used to form configurations. It may be an intrinsic part of the data model or a separate ....

Leblang D. B. and R. P. Chase, Computer-Aided Software Engineering in a Distributed Workstation Environment, ACM SIGPLAN Notices, pp 104-112, May 1984.

....were introduced. Both SCCS and RCS have been used extensively in managing versions of programs with an emphasis on managing evolution over time. The approaches to revision control found in SCCS and RCS have been generalized to support development on networked workstations (on a local area network) [7, 8, 9]. Further generalization to Wide Area Networks is reported in [10] where bandwidth limitations are overcome through discretionary, but controlled replication of files, as required. The evolution of revision control, from one that is centred on a single file tree in a time sharing system, to a ....

D.B. Leblang and R.P. Chase Jr., Computer Aided Software Engineering in a Distributed Workstation Environment, Sigplan Notices, Vol. 19, No. 4, 1984, pp. 104--112.

....When the dependency structure or the compilation methods changes, the description must be updated to reflect these changes. This, however, introduces the additional complexity of having to handle versions of systemdescriptions. Conventional configuration management systems like Make [10] and DSEE [11] are based on configuration structures which are directed acyclic graphs. These structures are described in a single text file together with information about the actions that have to be performed to compile, link and load the system together. This model of configuration management has a simple ....

: Leblang, David B. & Chase, Robert P. Jr.: Computer-Aided Software Engineering in a Distributed Workstation Environment, ACM SIGPLAN Notices, Vol. 19, No. 5, May 1984.

....operating systems. The next step forward was motivated by a need to state more properties about the elements and to automate certain activities. This led to attributed file systems to aid in configuration management [7] and extensions to the operating system to make version control transparent [8]. Still, this is not sufficient as we need much more elaborated ways to express the structural relations between components and the operational information to support automatic transformations. So it was natural to investigate approaches which support this like data bases [9] and hypertext systems ....

: Leblang, David B. and Chase, Robert P. Jr.: Computer-Aided Software Engineering in a Distributed Workstation Environment, in proceedings of the ACM SIGSOFT Software Engineering Symposium on Practical Software Development Environments, May 1984.

....rather than on procedures to manipulate them. All of the following systems provide good support for building; they differ primarily in how systems are specified, how version selection is accomplished, and what kinds of consistency are guaranteed. Adams and Solomon CAPITL Page 21 DSEE. DSEE [14, 15] is a commercial environment that manages software in a network of distributed (Apollo) workstations. It supports a notion of time travel by compactly storing versions of source files and providing a tool, the History Manager, that associates symbolic attributes with particular versions. A ....

D. B. Leblang and R. P. Chase, Jr., Computer-Aided Software Engineering in a Distributed Workstation Environment, SIGPLAN Notices Notices 19, 5 (Apr. 1984), 104-112 .

....versions of modules. A distinguished programmer called the Release Master is informed of syntactic interface errors between modules; the Release Master is responsible for communicating with the programmers responsible for these modules. DSEE The Apollo Domain Software Engineering Environment [8] also combines Make like facilities with version control. In addition, DSEE provides a monitoring mechanism that allows programmers and managers to request that they be notified when selected modules are changed. Masterscope Interlisp s Masterscope tool [14] automatically maintains ....

David B. LeBlang and Robert P. Chase, Jr. Computer-Aided Software Engineering in a Distributed Workstation Environment. In Proceedings of the SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, April 1984, 104-112. SIGPLAN Notices 19:5 (May 1984).

....1996, Squ 1996] While this approach provides weaker consistency semantics, it is easier to deploy given the current Web infrastructure. 4 Related Work Several systems have attempted to extend the automatic control of derived objects beyond the simple (but powerful) model used by make. DSEE [Leblang Chase 1984, Leblang McLean 1985] Odin [Clemm Osterweil 1990] and Vesta [Levin McJones 1993, Heydon et al. 1997] provide tools for modeling the behavior of programs, enabling the concise specification of derivation rules, and distributing changes to developers. Their declarative style suits ....

D. B. Leblang and R. P. Chase, Jr.. "Computer-Aided Software Engineering in a Distributed Workstation Environment". In Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pp. 104--112, May 1984.

....extended toolkit model to the distributed model. These environments provide additional support for coordinating changes by assigning tasks to individual programmers. In DSEE, structures and mechanisms are provided for assigning and completing tasks that may be composed of subtasks and activities [28]. CMS adds a modification request (MR) tracking system on top of SCCS in which individual programmers are assigned particular change requests and the changes are associated with particular sets of SCCS versions. Project Management Model = support activity coordination , activity ....

David B. Leblang and Robert P. Chase, Jr.. "Computer-Aided Software Engineering in a Distributed Workstation Environment", SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments , Pittsburgh, PA, April 1984. pp 104-112. Proceedings published as SIGPLAN Notices, 19:5 (May 1984).

....family of works appears in applications area, like CASE, where context management has been for a long time under consideration. Development of source code managers, like RCS [Tic82] or SCCS [Roc75] has led to development of configuration managers based on the version server approach [Log90] [LC84]. Then software configuration managers including both file versions and context management were designed. In [Rei89] orthogonality between versioning and object grouping is established. MSK89] presents a similar approach: project revisions are organized into a tree of development paths. KA91] ....

D.B. Leblang and P.C. Chase. Computer-aided software engineering in a distributed workstation environment. Proc. ACM Symposium on Practical Software Development Environments, pp. 104--112, Pittsburgh 1984.

....changes to large software systems. Most such tools provide a framework in which programmers can reserve modules 1 for change and in which the changes themselves occur outside of the tool. Examples include SCCS [Rochkind 75] Cedar s System Modeller [Lampson 83] Darwin [Minsky 85] and DSEE [Leblang 84] When a change is to be made to a module, a programmer reserves the module, obtains an official copy of the module, and then proceeds by making changes with an editor. The tool has no knowledge of the changes as they are being made, though in most cases it notices the differences between the two ....

David B. Leblang and Gordon D. McLean, Jr. Computer-Aided Software Engineering in a Distributed Workstation Environment, Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, SIGPLAN Notices, 19:5 (May 1984). pp. 104-112.

....with CM systems that provide configuration context information on a per process basis, i.e. where client and server processes will have different views of the CM repository. For example, both the Sun Network Software Environment [5] and HP Apollo s Domain Software Engineering Environment [11] have CM systems which make use of per process context information. 3.3.2 End User Services Integration Some of the variation of related services provided in CASE and CM tools is illustrated through a representative sampling of CASE and CM tools depicted in Figure 3 4. This sampling shows how ....

Leblang, D.; & Chase, R. "Computer-Aided Software Engineering in a Distributed Workstation Environment." Proceedings of the SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Pittsburgh, PA., April, 1984, 104-112.

....needs to be incorporated into the system or how it is to be done. Furthermore, it is extremely difficult to reconstruct previous versions should the current system prove to be unusable. 3. 2 Basic Version Control Systems such as SCCS [10] RCS [11] Cedar s System Modeler [5] and Apollo s DSEE [6] provide basic version control. The three kinds of versions (successive, parallel and composed versions) are supported within the version control system. Versions are distinguished by their version identifiers which in their simplest form are a pair of numbers separated by dots for example, ....

David B. Leblang and Gordon D. McLean, Jr. "Computer-Aided Software Engineering in a Distributed Workstation Environment", Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, SIGPLAN Notices, 19:5 (May 1984). pp. 104-112.

....It is a mere optimization aspect. Since the advent of Make [Feldman79] the ancestor of most configuration management tools, much work has been put into improving the implementation of these principles. More recent systems, like DSEE, has also focused on configuration management in distributed [LC84] and heterogeneous [Lubkin91] environments. These aspects of course give some new possibilities and pose new problems to be solved, but at the bottom line it is still the same old song. The original concepts from Make of description, instantiation, and build are still valid and complete. It is ....

....still more general than his. Due to the nodes having arbitrary internal structures we can model exactly the same system descriptions as he can. In fact we gain conceptual clarity and simplicity by being able to confine version control related ORs to the interior of nodes. A long string of tools [LC84], LM88] Simmonds89] Sheedy91] Gordon93] shows the popularity of the static structure model. However, we have shown, as have [KM93] that this model has some serious inherent limitations. We believe that as more dynamic ways of developing software systems grow in popularity these limitations ....

: David B. Leblang, Robert P. Chase Jr.: Computer-Aided Software Engineering in a Distributed Workstation Environment, in Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, May 1984.

....of such are nmake [Fow90] imake [Ful89] makedepend, and mkmf. Tightly integrating make with repository tools have caused some problems. This has led to some systems incorporating build mechanisms similar to make, and extended the derivation model to reduce the compileand link time. e.g. DSEE [LC84]. 2.3 Configuration languages We can term a language used for controlling the product and version structure of a large program system a configuration language. Configuration languages mainly fall into two areas: Those that arose from early work into the difficulties found in ....

....the PROTEUS Configuration Language PCL. 2.4 Advanced SCM systems In addition to the mechanisms presented in the two subsections above, advanced SCM systems incorporates process and control support into the SCM framework. Examples of such systems include PCMS [MH88] Adele [BE86] DSEE [LC84], Aide De Camp (ADC) Har89] Process support includes the notion of implicit or explicit process management (PM) where the goal is to develop a generic PM model and associated environment, where project or organization specific processes can be defined, reasoned about, executed and monitored ....

David B. Leblang and Robert P. Chase, Jr. Computer-Aided Software Engineering in a Distributed Workstation Environment. ACM SIGSOFT Software Engineering Notes, 9(3):104--112, May 1984.

....[23] uses these dependencies to notify the programmers who are responsible for units that depend on units which have been changed that their unit may be affected by these changes. Whereas SCCS s facilities are static and provided only on demand, DOMAIN Software Engineering Environment (DSEE) [14] provides change notification facilities that are dynamic monitors are placed on files that are triggered when changes are made to the monitored file. Notices are then sent to the agents responsible for the monitors. The composition of systems is described by a system model a description ....

David B. Leblang and Gordon D. McLean, Jr. "Computer-Aided Software Engineering in a Distributed Workstation Environment", Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, SIGPLAN Notices, 19:5 (May 1984). pp. 104-112.

....change requests with the actual changes in the system. Horwitz [24] combines the attribute grammar and relational database models into a single integrated structure, as a proposed extension to the Synthesizer Generator [63] 4 . Finally, Apollo s Domain Software Engineering Environment (DSEE) [41] provides a comprehensive set of structures for coordinating the building and evolving of software systems; these structures support configuration control, planning and programmer interactions. 3. We say partial in the sense that Garlan s views do not help at all if the ....

David B. Leblang and Robert P. Chase, Jr.. "Computer-Aided Software Engineering in a Distributed Workstation Environment", SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments , Pittsburgh PA, April 1984. pp 104-112. SIGSOFT Software Engineering Notes, 9:3 (May 1984). SIGPLAN Notices, 19:5 (May 1984).

.... In the latter case, the version space is defined by attributes and their combination constraints (so called version rules) Thus, an n dimensional grid is appropriate to represent the version space (with each axis corresponding to one attribute) Examples of SCM systems based on SCCS RCS are DSEE [26] and its successor Clearcase [25] while EPOS [32] and ICE [44] have their roots in conditional compilation. Virtually all EDM systems are based on version graphs. Remarkably, alternatives to version graphs are not mentioned in Katz s paper at all. Both revisions and variants of individual ....

D. B. Leblang and R. P. Chase, Jr. Computer-aided Software Engineering in a Distributed Workstation Environment. In Henderson [20], pages 104--112. In ACM SIGPLAN Notices 19(5), May 1984.

....extensions) is one of the earliest and most successful systems for compilation management. It does not provide any selection mechanism at all. A similar compilation management system (ISE Eiffel 3 compilation manager) is used by Darwin E, when a bound configuration is being compiled. DSEE [29, 30] is another file based tool, like RCS,SCS or Make, but it has a richer functionality than any of these. DSEE can represent descent lines and variant branches like RCS SCCS, and in addition it provides a limited selection mechanism. Selection criteria can be specified by means of configuration ....

D. Leblang and R Chase. Computer aided software engineering in a distributed workstation environment. In Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering symposium on practical software development environments, April 1984. 175

....is used for configuration management, version selection, and history management. All of the following systems provide good support for building; they differ primarily in how systems are specified, how version selection is accomplished, and what kinds of consistency are guaranteed. DSEE. DSEE [30, 31] is a commercial environment that manages software in a network of distributed (Apollo) workstations. It supports a notion of time travel by compactly storing versions of source files and providing a tool, the History Manager, that associates symbolic attributes with particular versions. A ....

David B. Leblang and Robert P. Chase, Jr. Computer-aided software engineering in a distributed workstation environment. ACM SIGPLAN Notices, 19(5):104-- 112, April 1984.

....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 such as UNIX [7] and A Programmer s Workbench [8] to fully integrated systems such as DSEE [41] and Mj lner [10] 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 ....

....a) module an external description of important aspects of its contents. This opens up for a more dynamic and flexible view of a configuration where the relevant information is placed at the source of its origin and therefore is more easily maintainable. In some recent systems (Adele [9] and DSEE [41]) the construction of the configuration description has been completely automated as regards the structural part. This has been possible because they support languages in which there are primitives for describing dependency relationship (like include) which can be automatically extracted and ....

: Leblang, David B. & Chase, Robert P. Jr.: Computer-Aided Software Engineering in a Distributed Workstation Environment, ACM SIGPLAN Notices, Vol. 19, No. 5, May 1984.

No context found.

D. B. Leblang and R. P. Chase, Jr.. "Computer-Aided Software Engineering in a Distributed Workstation Environment". In Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pp. 104--112, May 1984.

No context found.

D. B. Leblang and Jr. Chase, R.P. Computer-aided software engineering in a distributed workstation environment. In P. Henderson, editor, Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, pages 104--112, Pittsburgh, PA, 34 may 1984. acm, acm.

No context found.

David B. Leblang and Robert P. Chase, Jr. Computer-aided Software Engineering in a Distributed Workstation Environment. In [Hen84], pages 104--112, 1984.

No context found.

Leblang, D.B., Chase, R.P., "Computer-Aided Software Engineering in a Distributed Workstation Environment", ACM SIGPLAN Notices, 19:5, May 1984.

No context found.

David B. Leblang and Robert P. Chase, "Computer-Aided Software Engineering in a Distributed Workstation Environment," SIGPLAN Notices, vol. 19, 5, pp. 104-113, ACM, Pittsburgh, PA., April 1984.

No context found.

Lebl84a. David B. Leblang and Robert P.Chase, "Computer -Aided Software Engineering in a Distributed Workstation Environment," SIGPLAN Notices,vol. 19, 5, pp. 104-113, ACM, Pittsburgh, PA., April 1984.

No context found.

Leblang, David B. and Chase, Robert P., "Computer-Aided Software Engineering in a Distributed Workstation Environment," SIGPLAN Notices, vol. 19, no. 5, pp. 104-112, May 1984. Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments.

No context found.

David B. LeBlang and Robert P. Chase. "Computer-Aided Software Engineering in a Distributed Workstation Environment". SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments Pittsburgh PA, April 1984. pp 104-112

No context found.

D.B. Leblang and R.P. Chase, Jr., "Computer-Aided Software Engineering in a Distributed Workstation Environment," SIGPLAN Notices, vol. 19, no. 5, pp. 104-112, May 1984.

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