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.

....Y, 2000 itory. Moreover, the workspace provides the data in a form (usually les) on which external tools operate (editors, compilers, debuggers, etc. A workspace may be set up by explicit check out commands which copy data from the repository typically into the le system (physical workspace [19], 13] Alternatively, an SCM system may o er a virtual workspace (virtual le system [20] 14] where an evd dynamically serves as an access lter upon all repository accesses, so called transparent versioning. Finally, the work performed by one user (or a group thereof) may be embedded in a ....

Marc J. Rochkind, \The source code control system," IEEE Transactions on Software Engineering, vol. 1, no. 4, pp. 364{ 370, Dec. 1975.

....I stated in the earlier section. 2.5. Related works The history of the research on this area is quite long. A number of serious drawbacks of Make have been pointed out, and systems aimed to overcome the problems have been developed. Although Make can be used with version control tools, like SCCS [11] or RCS [16] its capability to handle multiple versions of software components is quite limited. DSEE [7] and Cedar System Modeler [6] handle software components with versions more reliably by integrating their version control mechanism and the build process support mechanism into a single ....

Rochkind, M. J. The Source Code Control System. IEEE Transactions on Software Engineering, vol.SE-1, no.4, pages 364-370, December, 1975.

....secondary storage pages needed to store the multiversion document, and (ii) to minimize the number of pages that must be accessed to reconstruct the particular version of the document requested by a user or an application. Traditional document version management schemes, such as RCS [10] and SCCS [8], are line oriented and have performance problems. For instance, RCS [10] stores the most current version intact while all other revisions are stored as reverse editing scripts. These scripts describe how to go backward in the document s development history. For any version except the current one, ....

....editing scripts. These scripts describe how to go backward in the document s development history. For any version except the current one, extra processing is needed to apply the reverse editing script to generate the old version. Instead of appending version differences at the end like RCS, SCCS [8] interleaves editing operations among the original document source code and associates a pair of timestamps (version ids) with each document segment specifying the lifespan of that segment. Versions are retrieved from an SCCS file via scanning through the file and retrieving valid segments based ....

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

....other is efficient retrieval of document segments, instead of whole documents, which, e.g. occurs when particular sections of interest are identified through a table of contents or a keyword index. 2 Previous Work Traditional line based methods for version management, such as RCS [11] and SCCS [8], are not efficient for object oriented structured documents. In fact, since these methods store versions using editing differences, information from many such differences are often required to reconstruct a single version. This results in more I O cost and computation complexity in reconstructing ....

....as reverse editing scripts. These scripts describe how to go backward in the document s development history. For any version except the current one, extra processing is needed to apply the reverse editing script to generate the old version. Another popular text version management tool is SCCS [8]. Instead of appending version differences at the end like RCS, SCCS interleaves editing operations among original document source code and associates a pair of timestamps with each text segment specifying the lifespan of that segment. Versions are retrieved from an SCCS file via scanning through ....

[Article contains additional citation context not shown here]

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

....management (CM) has slowly but surely evolved. The marketplace for CM products is nowworth well over one billion dollars per year [8] More than one hundred commercial CM systems, representing a wide range of functionality, are currently available. While some are simple clones of SCCS [41] and RCS [47] others have pushed the state of the art quite considerably by offering a full spectrum of functionality [14] Most CM systems, however, fall somewhere in between, each providing some distinguishing combination of functionality. Despite the varietyofavailable systems, several ....

....of specific policy decisions can be explored with an early implementation. 5 Related Work In its manyyears of existence, the discipline of configuration management has produced numerous industrial and research systems. Some provide only version control facilities, e.g. RCS [47] SCCS [41], Sablime [5] others provide more complete configuration management solutions (e.g. CVS [7] CoED [6] Perforce [38] and yet others provide integrated environments that incorporate process management and or problem tracking facilities (e.g. Adele [17] ClearCase [3] Continuus [12] With ....

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

....of a software system at the source code level [4] Research and development over the past twenty five years have produced numerous contributions within the field [7] evolving CM system functionality through three distinct generations. The first generation consists of such CM systems as SCCS [31], Sablime [3] and RCS [36] The creation of this generation was a direct result of two immediate needs: to prevent multiple developers from making simultaneous changes to the same source file and to track the evolution over time of each source file. Both needs were satisfied through the automatic ....

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

....[3] and that discussed in [21] Their main focus is modeling version changes for individual objects, and the performance of storing and retrieving complete documents was not discussed. Two version management schemes that are used in software configuration management [10] are RCS [15] and SCCS [13]. RCS uses an edit based approach for representing multiple versions of an evolving textual object. Typically, RCS [15] stores the most current version verbatim, while previous revisions are represented via reverse editing scripts. These scripts describe how to go backward in the object s ....

....apply the reverse editing script to generate the old version. The symmetric approach to the problem uses instead a forward editing 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 [13], where each textual object is marked with two timestamps (or version number) denoting the lifespan of the textual object. Versions are retrieved from 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, SE1, 4, Dec. 1975, pp. 364-370.

....of a component. The structure that a version control tool imposes on the development of history steps is called a version graph and is basically linear (Figure 2. a) One version follows the other and a new version is always created from the end of the line, as is the case for the tool SCCS [26]. For simple development needs this model is sufficient even though limited. However, it cannot support maintenance (i.e. further development of) older versions, it does not handle parallel development (for instance, additional development and maintenance going on in parallel) and thus variants ....

....provide an efficient and secure storage. Today s SCM tools provide secure storage, even though some tools have occasional corruptions caused by the rather complex structures that have to be maintained. The efficient use of space to save multiple versions is assured by the use of delta techniques [26], 27] these techniques have even been refined to be applicable to binary formats 21 too [63] Workspaces have been provided to ease moving back and forth files by allowing to group them in hierarchically structured projects [28] Furthermore, mechanisms exist to coordinate groups of people by ....

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

....most of the models 10 that have been proposed frame an object model on an existing SCM instead of truly expressing an object centric view of SCM. In the following section we will examine the alternative approach. 7 An Alternative to the Di#erence Model Most SCMs are based on the di#erence model [14, 20, 33, 40]. This model recreates a version v 2 of a file from a version v 1 using a di#erence file #(v 1 , v 2 ) that encodes the transformation steps and data needed to transform v 1 into v 2 . The space where v 2 will be recreated, v # 2 , is initially empty. At the end of the transformation sequence, v 2 ....

M.J. Rochkind. The Source Code Control System. IEEE Transactions on Software Engineering, SE-1(4):364--370, 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

....of the selected file description of revisons of the selected file project structure Figure 5. Extended Sniff project manager Solution Implemented in Sniff 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

....and the network link is broken, we would encounter the concurrency problems associated with having multiple copies of a file. The obvious approach to concurrency control in this context would be the checkout model found in most version control tools and some modern database systems (e.g. [18, 11]) In this model, each prefetched file would be locked in either a read only or writable mode, depending on whether the file is only needed for reading or possibly may be updated during the disconnected process fragment. These locks would be maintained persistently until later reconnection and ....

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

....and database concurrency control, and shows how my work fits into the big picture. Early SDE research focused on exploiting generalpurpose file systems and providing a collection of independent file based tools for system building [Fel79] editing, debugging, and version control [Tic85, Roc75] The invocation of these tools, however, was left up to the user. In addition, text and binary files were the only abstractions for storing the data generated by tools. These limitations prompted the development of programming environments that automated some of the tool invocation and provided ....

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

....suppose that the object xv:c from NY and query:c from CT are not checked out. NY s process backward chains to its local configuration manager, say RCS [106] and issues a check out rule on the object. At the same time, CT backward chains locally to its private configuration manager, say SCCS [94], and issues its own check out request. This rule could further have a condition that implies firing other rules recursively, independent of any other site s process knowledge or interest. To illustrate the need for re evaluating the entire condition, it could be the case that some check out rule ....

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

....The big costs of these activities are a major reason why usually either the changes are not done, or the subsequent testing is reduced, both being unsatisfactory. There have been various efforts to solve these problems and reduce both the costs and time involved. First of all, systems like SCCS [Roc75] and RCS [Tic85] were devised to keep track of the textual changes. Other tools like MAKE [Fel79] tried to reduce the efforts necessary to reconstruct system integrity. There are other so called configuration management systems like the NuMIL prototype [NS87] whose goal is to reduce the impact of ....

M. J. Rochkind. The Source Code control System. IEEE Transactions on Software Engineering, 1:364--370, December 1975.

....that a delta is often one to two orders of magnitude smaller than the original, and significantly smaller than a direct compression of the original. For example, version control systems store multiple versions of programs, graphics, documents, and other data as deltas relative to a base version[10, 12]. Similarly, backup programs can save space by storing deltas. Checkpoints of large data spaces can be compressed dramatically by using deltas and can then be reloaded rapidly. Display updates can also be performed efficiently using a delta that exploits operations that move lines around[1] ....

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

....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 [18] and RCS [20] Programmers and authors consistently 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 ....

....existing algorithms for differencing input strings can solve the perfect differencing problem as defined above. Algorithms for this include techniques based on greedy methods [17, 19] and methods based on dynamic programming [7] These methods are widely used in source code version control systems [18, 20] and versioning editors [15] However, both dynamic programming and greedy methods for differencing use either quadratic time or linear space (or both) Consequently, these algorithms have not scaled to applications that need to version large inputs and data with arbitrary structure, as discussed ....

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

....to maintain a record of the changes ( deltas ) between different versions of components. This provides the basis for tracing the evolution of a system through its lifetime. The majority of software development companies currently use version control facilities such as RCS [6] CVS [7] or SCCS [8] to manage their documents and software, but such facilities operate at an inadequately coarse level of granularity (typically, whole documents or whole modules) and fall far short of users desires. It is worthwhile noting at this point that we consider version management as an integral part of ....

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1:24--36, 1975. 10

....attempt to maintain a record of the changes ( deltas ) between different versions of components. This provides the basis 1 for tracing the evolution of a system through its lifetime. The majority of software development companies currently use version control facilities such as RCS [20] or SCCS [16] to manage their documents and software, but such facilities operate at an inadequately coarse level of granularity (typically, whole documents or whole modules) and fall far short of users desires. 1.2 SCM for Formal Methods Formal Methods of software development have particular needs in ....

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1:24--36, 1975.

....attempt to maintain a record of the changes ( deltas ) between different versions of components. This provides the basis for tracing the evolution of a system through its lifetime. The majority of software development companies currently use version control facilities such as RCS [16] or SCCS [11] to manage their documents and software, but such facilities operate at an inadequately coarse level of granularity (typically, whole documents or whole modules) and fall far short of users desires. In defining a coherent framework within which we can provide useful traceability functions, we ....

M. J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, 1:24--36, 1975.

....of a delta is its size divided by the size of its target version. One of the primary applications of delta compression is for eciently storing multiple versions of a le. Version control systems typically support this type of compression for maintaining complete le histories. RCS [50] and SCCS [39] are two traditional systems that provide version control with delta compressed storage for a single le. More advanced version control systems such as CVS [3] and PRCS [29] have emphasized the importance of providing version control over a collection of les, as opposed to a single le, resulting ....

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

....1970s, the discipline of CM has slowly but surely evolved. The marketplace for CM products is now worth well over one billion dollars per year [BW98] More than one hundred commercial CM systems, representing a wide range of functionality, are currently available. Some are simple clones of SCCS [Roc75] and RCS [Tic85] while others have pushed the state of the art quite considerably and o er a full spectrum of functionality [Dar91] Most other CM systems fall somewhere in between, each providing some distinguishing combination of functionality. 1.1 Problem Despite the variety of available ....

....guration management [Win88, Tic89, Fei91b, Est95, Som96, Con97, 19 Mag98, Est99] a large body of work has slowly but surely evolved the state of the art towards CM systems that address all of the functionality that is identi ed in the aforementioned spectrum. In fact, since the invention of SCCS [Roc75] and RCS [Tic85] with their ability to archive and coordinate changes to an artifact, and Make [Fel79] and Build [EP84] with their ability to automate and optimize the software build process, a myriad of CM systems have become available for general use. As each system yields its own strengths ....

[Article contains additional citation context not shown here]

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

....be separated from the common code. The approaches for detecting program di#erences involve string comparison, tree comparison or a combination of these techniques [12] Program di#erences have been studied in regard to spelling correction [54, 109] parsing error correction [119] version storage [99] and other uses. String comparison finds the minimum cost sequence of edit operations to convert one string into another. The standard algorithm for string comparison is described by Wagner and Fisher [120] The user specifies the cost of insertion, replacements and deletion of particular ....

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

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.

No context found.

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

No context found.

Marc J. Rochkind. The source code control system. IEEE Transactions on Software Engineering, SE-1(4):364--370, December 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