Software Configuration Management: State of the Art, State of the Practice

Frühauf, Karol; Yeller, Andreas

doi:10.1007/3-540-48253-9_15

Cited by 6 publications

(4 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The query below obtains all the versions currently under development. In this situation, it would return the versions 6 (3,6,6) and 7 (3,6,7), since they were not promoted yet to state stable.…”

Section: Symbol Meaningmentioning

confidence: 99%

Using the Temporal Versions Model in a Software Configuration Management Environment

Silva

Costa²,

Edelweiss³

et al. 2003

Anais Do XVII Simpósio Brasileiro De Engenharia De Software (SBES 2003)

View full text Add to dashboard Cite

Temporal Versions Model (TVM) is an object-oriented data model with versioning facilities, allowing revisions and project alternatives, and temporal features, used to maintain the history of the system evolution. This paper presents TVM under a Software Configuration Management (SCM) perspective, compares this model with available SCM tools, and describes why TVM is adequate to be used as the basis of an SCM environment. A modeling example and the implementation of TVM on a commercial Database Management System (DBMS), which is an ongoing work, are also presented.

show abstract

Section: Symbol Meaningmentioning

confidence: 99%

Using the Temporal Versions Model in a Software Configuration Management Environment

Silva

Costa²,

Edelweiss³

et al. 2003

Anais Do XVII Simpósio Brasileiro De Engenharia De Software (SBES 2003)

View full text Add to dashboard Cite

show abstract

“…Developing complex software nowadays requires that multiple views and versions of the software can be developed in parallel and merged as supported by views and managed by version control systems [10]. For complex software, living with inconsistencies at least temporarily is inevitable, as enforcing consistency may lead to loss of important information [9] and is hence neither always possible nor desirable.…”

Section: Introductionmentioning

confidence: 99%

“…However, working with multiple versions in parallel and changing each version on its own for longer periods of time can introduce substantial conflicts that are difficult and expensive to resolve. Therefore, it is necessary to manage consistency when combining views and versions using merge approaches [10,16].…”

Section: Introductionmentioning

confidence: 99%

Towards Development with Multi-Version Models: Detecting Merge Conflicts and Checking Well-Formedness

Barkowsky¹,

Giese²

2022

Preprint

View full text Add to dashboard Cite

Developing complex software requires that multiple views and versions of the software can be developed in parallel and merged as supported by views and managed by version control systems. In this context, this paper considers monitoring merging and related consistency problems permanently at the level of models and abstract syntax to permit early and frequent conflict detection while developing in parallel. The presented approach introduces multi-version models based on typed graphs that permit to store changes and multiple versions in one graph in a compact form and allow (1) to study well-formedness for all versions without the need to extract each version individually, (2) to report all possible merge conflicts without the need to merge all pairs of versions, and (3) to report all violations of well-formedness conditions that will result for merges of any two versions independent of any merge decisions without the need to merge all pairs of versions. The paper defines the related concepts and algorithms operating on multi-version models, proves their correctness w.r.t. the usually employed three-way-merge, and reports on preliminary experiments concerning the scalability. This work was developed mainly in the course of the project modular and incremental Global Model Management (project number 336677879) funded by the DFG.

show abstract

“…The architecture of our code warehouse as depicted in Figure 1 explains the flow of complex data like source code from a configuration management system (CMS) repository into our code warehouse and beyond to support decisions. Data sources with source code content are typically known as configuration management systems (CMS) with the well-known representatives CVS, Subversion, or SourceSafe (Frühauf & Zeller, 1999). Typically, they manage several versions of a software system in order to step back to previous versions if unsolvable problems occur.…”

Section: Introductionmentioning

confidence: 99%

Morphology, Processing, and Integrating of Information from Large Source Code Warehouses for Decision Support

Rech

Processing and Managing Complex Data for Decision Support

View full text Add to dashboard Cite

Source code occurs in diverse programming languages with documentation using miscellaneous standards, comments in individual styles, extracted metrics or associated test cases that are hard to exploit through information retrieval or knowledge-discovery techniques. Typically, the information about object-oriented source code for a software system is distributed across several different sources, which makes processing complex. In this chapter we describe the morphology of object-oriented source code and how we (pre-) process, integrate and use it for knowledge discovery in software engineering in order to support decision-making regarding the refactoring, reengineering and reuse of software systems.

show abstract

Software Configuration Management: State of the Art, State of the Practice

Cited by 6 publications

References 14 publications

Using the Temporal Versions Model in a Software Configuration Management Environment

Using the Temporal Versions Model in a Software Configuration Management Environment

Towards Development with Multi-Version Models: Detecting Merge Conflicts and Checking Well-Formedness

Morphology, Processing, and Integrating of Information from Large Source Code Warehouses for Decision Support

Contact Info

Product

Resources

About