ROCHKIND, M. J. The source code control system. IEEE Transactions on Software Engineering 1, 4 (Dec. 1975), 364--370.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of XPath data model and query language to support transaction time semantics. In our approach, we instead support XPath XQuery without any extension to XML data models or query languages. An archiving technique for scientific data was presented in [11] based on an extension of the SCCS [12] scheme. This approach timestamps elements only when they are different from the parent elements, so the structure of the representation is not fixed; this makes it difficult to support queries in XPath XQuery, which, in fact, is not discussed in [11] The scheme we use here to publish the ....

M.J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, 1975.

....or storage costs. We now describe a few of them in more detail. Software Revision Control Systems: As mentioned in the introduction, delta compression techniques were pioneered in the context of systems used for maintaining the revision history of software projects and other documents [8, 40, 45]. In these systems, multiple, often almost identical, versions of each object have to be stored in order to allow the users to retrieve past versions. For example, the RCS (Revision Control System) package [45] uses the diff delta compressor to reduce storage requirements. For more discussion on ....

M. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1:364--370, December 1975.

....different lock granularities and different locking levels (e.g. multiple read locks vs. single write locks) However, these locking strategies assume that locks are hold for relatively short times (some seconds) only. In software development, version control systems like RCS [Tic85] or SCCS [Roc75] employing a pessimistic locking concept on a per file, per class, or per method basis are used. However, changes to source code may require some days or weeks. We call such changes long transactions. Such long transactions lock certain source code parts for a long time. For example, one person ....

M.J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1(4):364-- 370, 1975.

....carries the correct set of locks. Several different locking constraint modules exist that range from not enforcing any locking at all (e.g. in case of a change set policy) to enforcing the simultaneous locking of all baselines and all changes (e.g. in case of a policy like the one in SCCS [10]) Perhaps the most commonly used strategies are to either lock a single node, or to lock a node and its branch. Locking constraints are specified independently from any hierarchy constraints and therefore cannot cross different levels in the storage hierarchy. Nonetheless, attaching the ....

M.J. Rochkind, The Source Code Control System. IEEE Transactions on Software Engineering, 1975. SE-1(4): p. 364-370.

.... detecting maximally matching regions of a file at an arbitrarily fine granularity without alignment. However, delta compression continued to rely on the alignment of data, as in database records [23] and the grouping of data into block or line granularity, as in source code control systems [22, 25], to simplify the combinatorial task of finding the common and different strings between versions. Efforts to generalize delta compression to un aligned data and to minimize the granularity of the smallest change resulted in algorithms for compressing data at the granularity of a byte. Early ....

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE1 (4):364--370, December 1975.

....was achieved by letting programmers trace back from those software classes in the source code that had been changed, to requirements. The result from back tracing was analyzed and verified with each programmer. Each source code file in the PMR project comprises one and only one C class and SCCS [14] is used for version management of each individual file. Whenever a programmer is about to modify a C class, the corresponding source file first has t o be checked out from SCCS, the modification performed and then the file checked in again. The result is a complete log over all modifications ....

Rochkind, M.J. The Source Code Control System. IEEE Transactions on Software Engineering, 1(4):364--370, 1975.

....such 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 ....

Marc F. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, Dec. 1975.

....The next section describes in part the somewhat serendipitous path that led to IHTML. 2. 3 Version Control In the process of implementing a Lucid interpreter, Plaice and Wadge found that they needed a source code version control system with more exibility than the existing tools such as SCCS [14] and RCS [15] They needed variant control as well as revision control, and a convenient means for merging development streams. Sloth, Lemur , and Marmoset were developed to ll this need [16, 17] They are successive re nements of the basic idea of combining versioned modules using a best t ....

....in the short term, this approach quickly leads to trouble. It becomes impossible in practice to maintain the site in any consistent way. The maintenance problem has been documented extensively in the software development world, as can be seen from the number of publications addressing the problem ([14], 15] and many others) The same issues confront the Web site developer. The solution is to ensure that there is only one copy of the parts that pages have in common, whether that is the overall format of a page, an image, a link, or some fragment of text. However, standard HTML does not ....

M. F. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364-370, December 1975.

....where x denotes the objects to be managed. Typical values of x are engineering data [2] product data [3] software configuration [4] workflow [5] software process [6] and project [7] Initially, small tools were realized which provided support for specific problems, e.g. SCCS [8] for maintaining versions of text files and Make [9] for maintaining consistency between source and derived objects (e.g. for controlling the execution of compile and link steps in the case of large programs composed 1.1. INTRODUCTION 3 of many files) Over the years, the tools became more and ....

Marc J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1(4):364-370, December 1975.

....Few Ohmges before 1.0. list of files (who checked out which version of which file) revisons of project structure Figure 5. Extended Sniff project manager Sniff is equipped with an adapter architecture that enables a developer to integrate various version control systems, such as SCCS [Roc75] and RCS [Tic85] A developer can trigger the checkin or checkout of a file in the editor. Figure 5 shows the extended user interface of the project manager. It allows to check in or out several files at once and to study the modification history of single files. 11. Implementation Aspects As ....

Rochkind M (1975): The Source Code Control System (SCCS). IEEE Transactions on Software Engineering, Vol. 1, No. 4

....where x denotes the objects to be managed. Typical values of x are engineering data [2] product data [3] software configuration [4] workflow [5] software process [6] and project [7] Initially, small tools were realized which provided support for specific problems, e.g. SCCS [8] for maintaining versions of text files and Make [9] for maintaining consistency between source and derived objects (e.g. for controlling the execution of compile and link steps in the case of large programs composed 1.1. INTRODUCTION 3 of many files) Over the years, the tools became more and ....

Marc J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1(4):364-370, December 1975.

....that have to be mapped to the commands of a specific VCS. Mappings can be defined and customized in the preferences dialog. Typically they consist of inline awk scripts but they can be implemented with any kind of shell commands. Currently adapters for ClearCase [Atr94] RCS [Tic85] and SCCS [Roc75] are provided. Configuration Management Unfortunately CMSs are too different to be integrated with an adapter interface. For this reason a CMS was implemented in SNIFF , to provide seamless integration with the programming environment. The implementation uses the VCS adapter architecture and ....

Rochkind M: The Source Code Control System (SCCS). IEEE Transactions on Software Engineering, Vol. 1, No. 4, 1975

....has been proposed in Chorel [5] the focus though is on modeling version changes for individual objects, and the performance of storing and retrieving complete document versions was not discussed. Two version management schemes used in software configuration management [11] are RCS [17] and SCCS [15]. RCS uses an edit based approach for representing multiple versions of an evolving textual object. A recent approach to XML versioning based on RCS is [13] Typically, RCS [17] stores the most current version verbatim, while previous revisions are represented via reverse edit scripts. These ....

....to apply the reverse edit script to generate the old version. The symmetric approach to the problem uses instead a forward edit script where the original versions are stored intact, and successive versions are generated by following the script. A timestamp based scheme is instead used for SCCS [15], where each textual object is marked with two timestamps (or version numbers) denoting the version lifespan of the textual object. Versions are retrieved in SCCS by scanning through the file and retrieving valid segments based on their timestamps. Both RCS and SCCS lack sophistication in their ....

M.J. Rochkind, The Source Code Control System, IEEE Transactions on Software Engineering, SE-1, 4, Dec. 1975, pp. 364-370.

....compactly and to transmit a version over a network by transmitting only the changed lines. By extending this concept of delta management over many versions, practitioners have used differencing algorithms for efficient management of document control and source code control systems such as SCCS [21] and RCS [23] Programmers and authors make small modifications to active documents and check them in to the document control system. All versions of data are kept, so that no prior changes are lost, and the versions are stored compactly, using only the changed lines, through the use of ....

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE1 (4):364--370, December 1975.

No context found.

ROCHKIND, M. J. The source code control system. IEEE Transactions on Software Engineering 1, 4 (Dec. 1975), 364--370.

No context found.

M.J. Rochkind. The Source Code Control System. IEEE Transactions on Software Engineering, SE-1(4):364--370, 1975.

No context found.

M.J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, 1975.

No context found.

M.J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, 1975.

No context found.

M.J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, 1975.

No context found.

M.J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, 1975.

No context found.

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1(4):364--370, Dec 1975.

No context found.

Rochkind M.J., The Source Code Control System. IEEE Transactions on Software Engineering, SE-1(4): 1975.

No context found.

M.J. Rochkind. The Source Code Control System. IEEE Transactions on Software Engineering, SE-1(4):364 -- 370, December 1975. 6

No context found.

Rochkind, M.J.: The Source Code Control System. IEEE Transactions on Software Engineering 1 (1975) 255--265

No context found.

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1#4#:364#370, Dec. 1975.

First 50 documents  Next 50

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