Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In Proc. of the 6th Int'l ACM-SIGSOFT/IEEE-CS Conference on Software Engineering, Tokyo, pages 58--67, September 1982.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....to analyze di#erences in Web pages over time [13] The di#erence engine is supported by a centralized versioning repository that stores versions of documents so that they are available for comparison against future versions. Data is saved in this repository in Revision Control System (RCS) format [52]s. Meta data is saved in a relational database. The main di#erence between Versus and AIDE lies in the built in capabilities for distributed operation that Versus provides. 2.5.3 Internet Archive The goal of the Internet Archive is to build an Internet library o#ering access to collections in ....

Tichy, W. F. Design, implementation, and evaluation of a Revision Control System. In Proceedings, 6th International Conference on Software Engineering, September 13-16, 1982.

....interoperation of product and version spaces creates configurations. The most important task of a SCM system is to manage the configurations. 3.3.1. Representations in SCM systems The most common representation for integrating the product and version spaces in a SCM system is the AND OR graph [34]. A non versioned product graph is represented by an AND OR graph consisting exclusively of AND nodes and edges. Then, objects with multiple versions are represented by OR nodes, while versions of composite objects are represented by AND nodes. In practice, the OR nodes are explicitly represented ....

....specialized database. In particular, Hicks [16] listed SCM as one application of his versioned hypermedia system, but the versioning framework is not flexible enough to support the sort of fine grained revision control models needed for evolving source code [22] Widely used SCM systems like RCS [34] and CVS [23] are valued because they support version control, cooperative work, and configuration management. So it is desirable for versioned hypermedia systems to cooperate with them, rather than to reproduce their results. However, as we have discussed in the previous section about the ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th international conference on Software engineering, pages 58--67. IEEE Computer Society Press, 1982.

....only version management and source control, while others like Make address only system modeling and building. We also consider ClearCASE, which provides a more integrated solution to the core SCM problems. 2. 1 RCS and CVS RCS is a system for maintaining multiple versions of individual files [10, 11]. Its main strengths are that it is easy to use, well understood, and well documented. Its main disadvantages are two. First, it does not provide transparent access to individual file versions. That is, an explicit checkout step is required to access an older version of a file. Hence, to build an ....

W. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th International Conference on Software Engineering, pages 58--67. IEEE Computer Society Press, 1982.

....navigational tool to analyze the di#erences in Web pages over time. The di#erence engine is supported by a centralized versioning repository that stores versions of documents so that they are available for comparison in the future. Data is saved in this repository in Revision Control System (RCS) [17] format. Meta data is saved in a relational database. The Internet Archive [12, 4, 15] goal is to build an Internet library for o#ering access to collections in digital format. The main focus is on long term preservation of selected contents and o#ering access to collected items. We have ....

Walter F. Tichy. Design, implementation, and evaluation of a Revision Control System. In Proceedings, 6th International Conference on Software Engineering, September 13-16, 1982.

....changes for a large system is a non trivial task, as its different components will evolve differently. Existing version control and software configurations systems have succeeded in solving some of the problems of dealing with this evolution. Pure version control systems such as sccs [22] and rcs [28, 30], using delta techniques to save storage space, keep track of the changes made by the different programmers to a file. Other space saving techniques have also been developed [8, 16, 18, 29] Software configuration systems such as make [7] allow for the automatic reconfiguration of a system when ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In 6th International Conference on Software Engineering, pages 58--67, Tokyo, Japan, Sept. 1982.

....its hypermedia database, version control responsibility must be shared between Chimera, its client applications, and external object managers. For example, when making links between source code files, version control responsibility for the files will rest with a revision control system such as RCS [59], while responsibility for versioning the relations between the files will reside with Chimera. We envision each Chimera concept becoming capable of multiple versions. This raises issues of consistency maintenance when a concept instance is changed. For example, when an anchor is deleted, it must ....

Tichy, W. F. (1982). Design, Implementation, and Evaluation of a Revision Control System. In Proceedings of the Sixth International Conference on Software Engineering, pp. 58-67. Tokyo, Japan.

....and many newer systems approach the core SCM problems in essentially the same way that they do. We also consider ClearCASE, which takes a more ambitious, integrated approach to solving the core SCM problems. 2. 1 RCS and CVS RCS is a system for maintaining multiple versions of individual files [16, 17]. Its main strengths are that it is easy to use, well understood, and well documented. Its main disadvantages are two. First, it does not provide transparent access to individual file versions. That is, an explicit checkout step is required to access an older version of a file. Hence, to build an ....

W. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th International Conference on Software Engineering, pages 58--67. IEEE Computer Society Press, 1982.

....a navigational tool to analyze the di#erences in Web pages over time. The di#erence engine is supported by a centralized versioning repository that stores versions of documents so that they are available for comparison in the future. Data is saved in this repository in Revision Control 3 System [17] format. Meta data is saved in a relational database. The goal of the Internet Archive [12, 5, 15] is to build an Internet library o#ering access to collections in digital format. The main focus is on long term preservation of selected contents and access to collected items. Our focus is on ....

Walter F. Tichy. Design, implementation, and evaluation of a Revision Control System. In Proceedings, 6th International Conference on Software Engineering, September 13-16,

....by defining several units together with their interfaces and then by composing those units. This led him to propose a modular approach to programming based on the notion of program composition. He formalized this idea 2 RCS is the Revision Control System developed by W. F. Tichy (see [31]) 27 by interpreting logic programs as elements of an algebra and by modeling their composition in term of the operators of the algebra. The distinguishing property of this approach is that it extends logic programming with modular constructs without any need to extend the language of Horn ....

W. F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In Proc. of the 6th Int. Conf. on Software Engineering, IEEE, Tokyo, 1982.

....or general epidemic propagation #Demers et al. 1988#. By comparing the remote history with the local one, an instance of the editor can determine if there are outstanding updates and whether these updates con#ict with other updates. This concept was #rst used in software repositories #e.g. RCS #Tichy, 1982# and CVS #Berliner, 1990##. If di#erent parallel versions of an object exist in the local storage the editor has the problem of determining whichversion to display.We de#ne the branch of the version tree that was #rst displayed as the current branch on the local machine #see Figures 1 and 2#. ....

Tichy, W. F. #1982#: Design, Implementation, and Evaluation of a Revision Control System. Proceedings of 6th International Conference on Software Engineering #Tokyo, Japan#, September 1982. pp. 58#67.

....only version management and source control, while others like Make address only system modeling and building. We also consider ClearCASE, which provides a more integrated solution to the core SCM problems. 2. 1 RCS and CVS RCS is a system for maintaining multiple versions of individual files [11, 12]. Its main strengths are that it is easy to use, well understood, and well documented. Its main disadvantages are two. First, it does not provide transparent access to individual file versions. That is, an explicit checkout step is required to access an older version of a file. Hence, to build an ....

W. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th International Conference on Software Engineering, pages 58--67. IEEE Computer Society Press, 1982.

....processes and tools depend on the ability to recreate snapshots of the software at different points in time. A version control system (VCS) tracks each change a developer makes to the system and, as a result, can recreate a consistent snapshot at any point in time. Examples of VCSs include RCS [13] and SCCS [14] While this basic functionality of VCSs is essential for version control, there is much data in a VCS that is ignored when simply using it to extract snapshots of source code. For instance, A VCS tags each change with a substantial amount of additional contextual information. ....

W.F. Tichy, Design, Implementation, and Evaluation of a Revision Control System, in Proceedings of the Sixth International Conference on Software Engineering. 1982: Tokyo, Japan. p. 58---67.

....system can be used to verify a program against its specifications or a run of a previous version. In addition, the log can be used to detect the use of non portable functions, or programs that have been infected by viruses. Environment modelling and re creation Revision control systems such as [Tic82] can use the log of a system s compilation process to determine the exact environment that was used to create the program, including the compilers and tools used and all included files and libraries. Operating Systems Review, 28(4) 56 63, October 1994. Copyright c 1994 by the Association for ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system,. In Proceedings of the 6th International Conference on Software Engineering. IEEE, September 1982. 63

....strategies for building a feature based configuration management system using several commercial systems. These systems are expensive, and licensing arrangements typically confine their use to specific machines. To be able to demonstrate the system we developed, it was implemented using RCS [84], a commonly available version management tool. Our system, IronMan, provides native level support for the activities described in the evaluation framework from Section 4.2.1. In this chapter, we describe the mechanisms that IronMan provides in supporting feature based software development. Then ....

W.F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. Proceedings of the 6th International Conference on Software Engineering, pages 58--67, September 1982.

....Early work within the eld of SCM focused on e cient storage techniques through delta storage: Only the di erences between two consecutive versions are stored. E cient delta storage techniques are not within the scope of the present work, and therefore le level versioning is delegated to RCS [Tic82b, Tic85] Thus a component versions substance attribute is represented as a list of ( lename, RCS version identity) pairs. Furthermore, using RCS has the advantage that Ragnarok supports both binary and text les. However, interfacing RCS is troublesome because Ragnarok has to execute RCS in a ....

Walter F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In 6th Conference on Software Engineering, Tokyo, Japan, 1982.

....on the WorldWideWeb [7] Implementation A software component is in the prototype defined by a list of files (being the substance of the component) and a list of references to part components and a list of references to components referenced. Versions of individual files are handled by RCS [22, 23]: When a component checks in the RCS ci command is issued to all files in the file list, and the prototype stores the resulting revision numbers for the files. The present prototype adheres to the lock modify unlock policy for granting permission to modify substance of a component i.e. only a ....

....commit a change before his own working copies have been updated i.e. are identical to the latest version. In essence this feature of CVS prevents developers from having version control in workspace i.e. to use the versioning ability to create intermediate versions during experiments. CVS, RCS [22, 23], and MicroSoft Visual SourceSafe [17] relies on tags to define context. For example in a release situation all relevant files are tagged with a symbolic name. Tags have a number of deficiencies: A very pragmatic but nonetheless important consideration is that you have to remember to do the ....

W. F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In 6th Conference on Software Engineering, Tokyo, Japan, 1982.

....for the construction and location of derived components. The ability to share components reliably has two major benefits. First, it permits components to be constructed as incremental modifications to existing components. This is similar to the way in which versioning systems such as RCS [14] use diffs to encode changes to text files, but it differs by being proactive rather than retroactive. In addition, arbitrary component types can be constructed incrementally in the Forest environment, leaving details to component implementations. The second benefit is the ability to share large ....

Design, Implementation, and Evaluation of a Revision Control System, Walter F. Tichy, Proceedings 6th International Conference on Software Engineering, Tokyo, Japan, September 1982, 58-67.

....a computer to perform. For maintaining software structure, a tool might ease access to a language s features, help reveal structural properties of a program, or aid in the keeping track of auxiliary information related to system structure and evolution. For example, the Revision Control System [Tichy 82] captures the change history of a program and allows versions to be tracked. If errors are introduced into a tracked program, earlier program versions can be retrieved to return to a working version or help find the change that caused the error. Like a language, a tool can make methods easier to ....

W. F. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th International Conference on Software Engineering, September 1982.

....in Section 2.5. Different design concepts may be alike in certain respects, in which case they will share the representations that describe the common aspects. Our data model keeps track of versioning relationships for both representations and design versions. Version control system such as RCS [16] and Sherpa [12] only keep track of version relationships for individual representations. For example, observe the situation of an engineer who designed a new cylinder for our aircraft engine. As she worked, she created several versions of the design. The geometry of the first version was drawn ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In International Conference on Software Engineering, 1982.

....the similar fashion. Related work and discussions Over the last two decades or so, there have been continued efforts in providing configuration management support for software development. This has resulted in a range of configuration management tools, from earlier tools such as SCCS [9] and RCS [10, 11] to recent systems like Adele [12] and ClearCase [13] These tools focus on the configuration management issues, and have led to the relative maturity of software configuration management techniques. Due to this focus, however, most of these tools do not address issues of computer aided software ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th ACM/IEEE International Conference on Software Engineering, pages 58--67, Tokyo, Japan, September 1982.

....control responsibility must be shared between Chimera and its client applications. As an example, Chimera will undoubtedly be used to create relations between source code files. Version control responsibility for the files alone will rest with an existing revision control system such as RCS [36]. Responsibility for versioning the relations between the files will reside with Chimera. Each concept within Chimera shall be capable of multiple versions. This raises significant issues of consistency maintenance when a concept instance is changed. For example, when an anchor is deleted, it ....

W. F. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the Sixth International Conference on Software Engineering, pages 58--67, Tokyo, Japan, September 1982.

....instead. 7 The notion of variants is discussed in more detail in section 5.6. 5.1 Motivation Why the demand for preserving the context One major achievement is, in my opinion, that the implementation of a version gets closer to an intuitive notion of the version of a component . In RCS [Tichy82] CVS [Berliner90] the three dimensional graph model of Bendix [Bendix95] and generally approaches based on selection rules for creating configurations the problem is, that the only way to preserve the context of a component is by tagging i.e. invent tags which must be associated with every ....

....on the object. In order to change an object you must lock the object first, and only one person at the time is allowed to do so. As long as a person holds the lock no one else can change the object. This mechanism serialises all access to an object. A well known tool using this scheme is RCS [Tichy82] Copy modify merge: In this approach several persons are allowed to modify an object concurrently but they all operate on a copy. When done each must merge their changes into a new version (This step can not be done concurrently) CVS uses this approach [Berliner90] Both have benefits and ....

[Article contains additional citation context not shown here]

Walter F. Tichy, Design, Implementation, and Evaluation of a Revision Control System, 6th Conference on Software Engineering, Tokyo, Japan, 1982

....in multicast or general epidemic propagation [Demer88] By comparing the remote history with the local one, an instance of the editor can determine if there are outstanding updates and whether these updates conflict with other updates. This concept was first used in software repositories (e.g. RCS [Tichy82] and CVS [Berli90] If different parallel versions of an object exist in the local storage the editor has the problem of determining which version to display. We define the branch of the version tree that was first displayed as the current branch on the local machine (see Figures 3.1 and 3.2) ....

W. F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. Proceedings of 6th International Conference on Software Engineering (Tokyo, Japan), pages 58--67, September 1982.

....other computational aspects relative to the isa composition. Throughout this and the following section, we will assume that the hierarchies that are formed with differential programs are linear. This assumption will be lifted 2 RCS is the Revision Control System developed by W. F. Tichy (see [26]) in Section 5 where we show that that it does not involve any loss of generality as the cases of tree like and DAG like hierarchies can be characterized semantically, reasoning on linear hierarchies. We start by introducing the definition of differential programs, programs that are built over ....

W. F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In Proc. of the 6th Int. Conf. on Software Engineering, IEEE, Tokyo, 1982.

....reached at chin.huang canrem.com. His cproto program can be found in volume 31 of the comp.sources.misc archive. 4.3. 4 Source control Another tool used extensively by Gene is the CVS (Concurrent Versions System) tool by Brian Berliner [1] 6 CVS is a front end to the well known RCS utilities [15], providing useful release revision abstractions beyond the file by file revisions afforded by RCS. Among other things, CVS allowed for the easy generation of patch files against any previously released version of Tripwire (modulo the contortions necessary for the self test database) 4.3.5 ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In Proceedings of the 6th International Conference on Software Engineering. IEEE Press, September 1982.

....system (VM CM) Although, SEEs which maintain fine grained dependencies as mentioned above, are now existing [Lew88] most available VM CM models still assume a very coarse grained object model. Basically, versioned objects correspond to files whose particular contents is not considered e.g. Tic82, Fel88, BE87, ML88] Such a coarse grained version model makes it impossible to preserve inter document dependencies and to control change propagation on the fine grained level sketched above. Illustrating examples will follow in the next section. The main new features presented in this paper ....

Walter F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In Proceedings of the 6 th International Software Process Workshop, pages 58--67. ACM Press, 1982.

....system (VM CM) Although, SEEs which maintain fine grained dependencies as mentioned above, are now existing [Lew88] most available VM CM models still assume a very coarse grained object model. Basically, versioned objects correspond to files whose particular contents is not considered e.g. Tic82, Fel88, BE87, ML88] Such a coarse grained version model makes it impossible to preserve inter document dependencies and to control change propagation on the fine grained level sketched above. Illustrating examples will follow in the next section. The main new features presented in this paper ....

Walter F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In Proceedings of the 6 th International Software Process Workshop, pages 58--67. ACM Press, 1982.

.... software product that these objects comprise, both commercially and in research: The functionality of these can be summarized as follows: Repository tools Of most general interest, and thus surveyed in the project are the Source Code Control System (SCCS) Roc75] the Revision Control System (RCS) [Tic82], and the Concurrent Versions System (CVS) 2 . These systems provides mechanisms to support the checkout checkin model as discussed by Feiler in [Fei91] Build tools Typically for the system build phase is to run a makefile using make [Fel79] Make offer the following advantages: ffl Avoid ....

Walter F. Tichy. Design, Implementation, and Evaluation of a Revision Control System. In Proc. 6th Int. Conference on Software Engineering, Tokyo, Japan, September 13-16, pages 58--67, 1982.

....collaborative design, an additional 69 perspective is helpful, that of artifact specific history. The focus shifts from the individual to the shared artifact. 8.2. 2 Version Control Systems RCS is an example of a version control system and manages changes to text files, typically source code [Tichy 82] The primary use is in software version management. RCS helps users to manage changes to text files by tracking revisions. To make changes to a file, one checks it out, edits it, and checks it back in. RCS tracks the changes in delta files, similar to the unix diff command. RCS can handle ....

W.F. Tichy, Design, Implementation, and Evaluation of a Revision Control System, Proceedings of the 6th International Conference on Software Engineering, IEEE, Tokyo, Japan, September 1982, pp. .

....does not require any change to the revision list. 1 A new revision is produced at check in time: New Successor followed by Put Content. The lock reservation scheme requires a flag to be set in the revision being checked out. Again the new revision is created at check in time. SCCS[18] and RCS[23] are systems that use this kind of reservation. Finally, the template reservation scheme requires check out to create a new revision: New Successor is called with Get Content. Some information, like author and check out time, is filled into the new revision, but the content is left empty. This new ....

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In Proc. of the 6th Inter. Conf. on Software Eng., pages 58--67, Sept. 1982.

No context found.

Walter F. Tichy. Design, implementation, and evaluation of a revision control system. In Proc. of the 6th Int'l ACM-SIGSOFT/IEEE-CS Conference on Software Engineering, Tokyo, pages 58--67, September 1982.

No context found.

Tichy, W.F., Design, implementation, and evaluation of a revision control system, pp. 58-67 in Proceedings of the 6th International Conference on Software Engineering, (Tokyo, Japan, September 13-16, 1982), IEEE, New York (1982).

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