Orthogonal version management

Orthogonal version management. Reichenberger, C. In ACM SIGSOFT Software Engineering Notes, of SCM '89, pages 137--140, New York, NY, USA, 1989. ACM. ACM ID: 73361

Paper doi abstract bibtex

One part of the “Software Configuration Management” — software version control — is the task of controlling different versions of documents. Most existing version control systems accomplish this task by managing variant and revision trees of single documents. The structure of these trees depends on the chronological evolution of the software project. We call this form of organization “intermixed organization” of variants and revisions. This paper points out the disadvantages of that organization, introduces a new way of version management - the “orthogonal organization” - and then compares the two organizations by means of an example.

@inproceedings{reichenberger_orthogonal_1989,
	address = {New York, NY, USA},
	series = {{SCM} '89},
	title = {Orthogonal version management},
	isbn = {0-89791-334-5},
	url = {http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361},
	doi = {http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361},
	abstract = {One part of the “Software Configuration Management” — software version control — is the task of controlling different versions of documents. Most existing version control systems accomplish this task by managing variant and revision trees of single documents. The structure of these trees depends on the chronological evolution of the software project. We call this form of organization “intermixed organization” of variants and revisions. This paper points out the disadvantages of that organization, introduces a new way of version management - the “orthogonal organization” - and then compares the two organizations by means of an example.},
	urldate = {2011-02-09TZ},
	booktitle = {{ACM} {SIGSOFT} {Software} {Engineering} {Notes}},
	publisher = {ACM},
	author = {Reichenberger, C.},
	year = {1989},
	note = {ACM ID: 73361},
	keywords = {design, management, not-completed, software configuration management, version control},
	pages = {137--140}
}

Downloads: 0

{"_id":"ySFFsnGDNSWjNd2Er","bibbaseid":"reichenberger-orthogonalversionmanagement-1989","downloads":0,"creationDate":"2017-01-26T00:06:42.119Z","title":"Orthogonal version management","author_short":["Reichenberger, C."],"year":1989,"bibtype":"inproceedings","biburl":"http://bibbase.org/zotero/quinn_d","bibdata":{"bibtype":"inproceedings","type":"inproceedings","address":"New York, NY, USA","series":"SCM '89","title":"Orthogonal version management","isbn":"0-89791-334-5","url":"http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361","doi":"http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361","abstract":"One part of the “Software Configuration Management” — software version control — is the task of controlling different versions of documents. Most existing version control systems accomplish this task by managing variant and revision trees of single documents. The structure of these trees depends on the chronological evolution of the software project. We call this form of organization “intermixed organization” of variants and revisions. This paper points out the disadvantages of that organization, introduces a new way of version management - the “orthogonal organization” - and then compares the two organizations by means of an example.","urldate":"2011-02-09TZ","booktitle":"ACM SIGSOFT Software Engineering Notes","publisher":"ACM","author":[{"propositions":[],"lastnames":["Reichenberger"],"firstnames":["C."],"suffixes":[]}],"year":"1989","note":"ACM ID: 73361","keywords":"design, management, not-completed, software configuration management, version control","pages":"137--140","bibtex":"@inproceedings{reichenberger_orthogonal_1989,\n\taddress = {New York, NY, USA},\n\tseries = {{SCM} '89},\n\ttitle = {Orthogonal version management},\n\tisbn = {0-89791-334-5},\n\turl = {http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361},\n\tdoi = {http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361},\n\tabstract = {One part of the “Software Configuration Management” — software version control — is the task of controlling different versions of documents. Most existing version control systems accomplish this task by managing variant and revision trees of single documents. The structure of these trees depends on the chronological evolution of the software project. We call this form of organization “intermixed organization” of variants and revisions. This paper points out the disadvantages of that organization, introduces a new way of version management - the “orthogonal organization” - and then compares the two organizations by means of an example.},\n\turldate = {2011-02-09TZ},\n\tbooktitle = {{ACM} {SIGSOFT} {Software} {Engineering} {Notes}},\n\tpublisher = {ACM},\n\tauthor = {Reichenberger, C.},\n\tyear = {1989},\n\tnote = {ACM ID: 73361},\n\tkeywords = {design, management, not-completed, software configuration management, version control},\n\tpages = {137--140}\n}\n\n","author_short":["Reichenberger, C."],"key":"reichenberger_orthogonal_1989","id":"reichenberger_orthogonal_1989","bibbaseid":"reichenberger-orthogonalversionmanagement-1989","role":"author","urls":{"Paper":"http://doi.acm.org.myaccess.library.utoronto.ca/10.1145/72910.73361"},"keyword":["design","management","not-completed","software configuration management","version control"],"downloads":0,"html":""},"search_terms":["orthogonal","version","management","reichenberger"],"keywords":["design","management","not-completed","software configuration management","version control"],"authorIDs":[],"dataSources":["sEHiQiuaak2HNiigP"]}