Bjrn Munch. Versioning in Software Engineering Databases --- The Change-Oriented Way. PhD thesis, Division of Computer Systems and Telematics, Norwegian Institute of Technology, October 1993.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....model and programmatic interface should not themselves contain any restrictive policy decisions. For example, if the repository model only provided a facility to store versions of artifacts as a traditional version tree, it would be very difficult to implement the more advanced change set policy [35] Similarly, if the functions in the programmatic interface automatically created a new version of an artifact whenever one of its constituent parts is modified, CM policies in which the evolution of an artifact is explicitly managed by a user would, once again, be difficult if not ....

.... [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 respect to distribution, some of the CM systems are only suited for use at a single site (e.g. EPOS [35] ShapeTools [31] SourceSafe [32] others incorporate a simple, sometimes Web based, client server interface (e.g. DCVS [7] Perforce [38] WWCM [25] and yet others provide more advanced distribution mechanisms such as replication (e.g. ClearCase Multisite [2] Continuus DCM [13] PVCS ....

B.P. Munch, "Versioning in a Software Engineering Database---the Change-Oriented Way," PhD thesis, DCST, NTH, Trondheim, Norway, Aug. 1993.

....the option to abort, which has no further effect, or continue, which informs the other developers that parallel work is now ensuing. Coven suffers drawbacks similar to CVS: it requires extra manual actions and it provides, via e mail, limited information concerning direct conflicts only. EPOS [30] and Adele [17] do not directly address awareness, but rather provide sophisticated mechanisms to coordinate artifact sharing among workspaces. EPOS supports four different policies that can be instituted among different pairs of workspaces: 1) all artifacts are shared immediately, 2) artifacts ....

B.P. Munch. Versioning in a Software Engineering Database - the Change-Oriented Way. Ph.D. Thesis, DCST, NTH, 1993.

....interwoven throughout its implementation, functionality related to its policy (such as the rules for updating a version tree or selecting artifacts) could not be easily extracted for reuse and had to be reimplemented in Subversion. A number of projects have attempted to address this issue. EPOS [8] and ICE [21] for instance, provide logic based infrastructures upon which to implement new configuration management systems by specifying their policies as logical constraints. Another approach, NUCM [16] provides a programmatic approach that reuses a generic repository and supports ....

....Concurrency action No locking Evolution action Store new version as an independent change depending on the baseline Placement action No placement 5 Related Work Several previous projects have explored the issue of easing the development of new configuration management systems. ICE [21] EPOS [8,19], and NUCM [16] were among the first to provide a generic (also called unified) configuration management model upon which to build new configuration management systems. ICE and NUCM, however, have the problem that a configuration management policy is treated as a single monolithic unit. Some reuse ....

B.P. Munch. Versioning in a Software Engineering Database - the ChangeOriented Way. Ph.D. Thesis, DCST, NTH, 1993.

....model and programmatic interface should not themselves contain any restrictive policy decisions. For example, if the repository model only provided a facility to store versions of artifacts as a traditional version tree, it would be very difficult to implement the more advanced change set policy [35]. Similarly, if the functions in the programmatic interface automatically created a new version of an artifact whenever one of its constituent parts is modified, CM policies in which the evolution of an artifact is explicitly managed byauserwould, once again, be difficult if not impossible to ....

.... [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 respect to distribution, some of the CM systems are only suited for use at a single site (e.g. EPOS [35], ShapeTools [31] SourceSafe [32] others incorporate a simple, sometimes Web based, client server interface (e.g. DCVS [7] Perforce [38] WWCM [25] and yet others provide more advanced distribution mechanisms such as replication (e.g. ClearCase Multisite [2] Continuus DCM [13] PVCS ....

B.P. Munch. Versioning in a Software Engineering Database --- the Change-OrientedWay. PhD thesis, DCST, NTH, Trondheim, Norway, August 1993.

....this work and draws some conclusions. In Appendix A, each DVS functionality is presented in details in the form of a user manual. 2 Related Work in Distributed CM Distribution is a relatively new feature in CM systems. In fact, many commercial and research systems, such as CCC Harvest [28] EPOS [23], JavaSafe [18] NSE [10] Sablime [4] ShapeTools [19] SourceSafe [20] TrueChange [29] and VOODOO [27] do not yet provide any real support for distribution. Those systems that do, appear to suffer from one or more of the following significant problems. 1. Distribution is grafted onto an ....

B. Munch. Versioning in a Software Engineering Database --- the Change Oriented Way. PhD thesis, DCST, NTH, Trondheim, Norway, Aug. 1993.

....the retrieved version, and finally submits the changed version as a new immutable version v i 1 . Note that any version v i can be retrieved at any time. Intensional versioning supports flexible, automatic construction of consistent versions in a large version space. The term potential versions [17] emphasizes that a certain version may not have been explicitly constructed before. In intensional versioning, the version set is defined by a composite predicate: V = fvjc(v)g This means that all versions belong the version set which meet the constraint c. A specific version v is then ....

B. P. Munch. Versioning in a Software Engineering Database --- the Change Oriented Way. PhD thesis, NTH, Trondheim, Norway, Aug. 1993. 265 p. (PhD thesis NTH 1993:78).

.... due to its use have also been reported for large software products [Spe92] Til92] Some tools have been developed [Lit93] Vo92] Recently, different, independent research have shown a growing interest in CPP, taking it as a case study or seeing it from a reengineering point of view [Spu92] [Mun93] [Sin93] Fav93] Kro94] Liv94] Zel94] Fav94] Sne95] Fav95] 1. While PITS deals with programs, PITL deals with program families. 3 I.2) CPP Features In this section the main features of mechanisms provided by CPP are presented. The reader is invited to consult C programming language ....

....#else . #endif. While porting is an important aspect, other goals lead to variations in the source text of programs. Typical examples are optional code for debugging purposes (the traditional #ifdef DEBUG . #endif sequence [Aba89] adaptation to natural languages, time space trade off, etc. [Mun93] [Sin93] Zel94] I.4) CPP drawbacks While widely used, it is well known that CPP is a problematic tool [Til92] Gen89] Sin93] Kro94] Some incomprehensible cpp pieces of code are reproduced in [Spe92] To get a better feeling for what can dive maintainers headaches the reader is invited to ....

[Article contains additional citation context not shown here]

B.P. Munch; "Versioning in Software Engineering Database : the Change Oriented Way" , PhD dissertation, Division of Computer Systems and Telematics, The Norwegian Institute of Technology, 1993.

....in Section 6 how we used NUCM to construct a number of CM systems, and conclude in Section 7 with a brief look at future work. 2 Related Work in Distributed CM Distribution is a relatively new feature in CM systems. In fact, many commercial and research systems, such as CCC Harvest [42] EPOS [33], JavaSafe [26] NSE [15] Sablime [4] ShapeTools [28] SourceSafe [30] TrueChange [43] and VOODOO [40] do not yet provide any real support for distribution. Those systems that do, appear to su#er from one or more of the following significant problems. 1. Distribution is grafted onto an ....

B.P. Munch. Versioning in a Software Engineering Database --- the Change Oriented Way. PhD thesis, DCST, NTH, Trondheim, Norway, August 1993.

....be implemented using NUCM and conclude in Section 7 with a brief look at future work. 2 Related Work in Distributed CM Distribution is a relatively new feature in CM systems. In fact, many of the most widely known commercial and research systems, such as ADC [22] CCC Harvest [21] NSE [10] EPOS [15], and ShapeTools [14] do not yet provide any real support for distribution. Those that do, appear to suffer from one or more of the following significant problems. 1. Distribution is grafted onto an existing, nondistributed architecture. Typically, the CM system is augmented with a simple ....

B.P. Munch. Versioning in a Software Engineering Database---the Change Oriented Way. PhD thesis, DCST, NTH, Trondheim, Norway, August 1993.

....The constraint language of Z0 being too low level, we propose some extensions for a better expression of access functions; the query language is also under design. Concerning versioning, we integrate the concept of dimension used by software engineering, databases and CAD researchers [Ber88][Mun93][Gad93] Tan93] Sci94] This concept can be used to model also low level mechanisms of CPP. Temporal databases use one or two temporal dimensions; they are the only ones which propose query languages in a versioned context. Work in this area consists of extending algebras to take temporal ....

....programming languages. Finally CPP preprocessor has been closely studied as representing the state of practice in PITL. We propose to adapt to PITL techniques developed for PITS: slicing and partial evaluation. Recent works led independently also show an increasing interest in studying CPP [Mun93][Kro94] Zel94] ....

B.P. Munch; "Versioning in Software Engineering Database : the Change Oriented Way" , PhD dissertation, Division of Computer Systems and Telematics, The Norwegian Institute of Technology, 1993.

....the Schema Manager, Execution Manager, and Planner with domain knowledge. The overall architecture is shown together with the EPOSDB architecture in Figure 1. 3 Product Support This section discusses the EPOS product support and product model, as well as various aspects of the supporting EPOSDB (Munch, 1993). The main task of the product support is to manage storage of, and access to, an evolving, complex product. The product may consist of files and or database objects. Cooperating transactions and workspace control are also strongly related to product support; these topics are discussed in the ....

....Thus, we can add user defined type information without affecting the DBMS semantics. The same can be done for longfields. This technique is used by SPELL to add e.g. procedures. 3. 4 Change Oriented Versioning EPOSDB implements Change Oriented Versioning (COV) Holager, 1988; Lie et al. 1989; Munch et al. 1993). COV considers a set of physical changes to a set of database fragments as one logical (or functional) change. COV is largely independent of the data model, and enables uniform versioning of entities and relationships, including schema level information. In COV, a version is not an explicit ....

[Article contains additional citation context not shown here]

Munch, B. P. (1993). Versioning in a Software Engineering Database --- the Change Oriented Way. PhD thesis, DCST, NTH, Trondheim, Norway. 265 p. (PhD thesis NTH 1993:78).

No context found.

Bjrn Munch. Versioning in Software Engineering Databases --- The Change-Oriented Way. PhD thesis, Division of Computer Systems and Telematics, Norwegian Institute of Technology, October 1993.

No context found.

Munch B.P., Versioning in a Software Engineering Database - the Change-Oriented Way. Ph.D. Thesis, DCST, NTH, 1993.

No context found.

B. P. Munch. Versioning in a Software Engineering Database --- the Change Oriented Way. PhD thesis, NTH, Trondheim, Norway, Aug. 1993. 265 p. #PhD thesis NTH 1993:78#.

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