Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andre Karlsson, Svein O. Hallsteinsen, and Per Holager. Change Oriented Versioning in a Software Engineering Database. In Software Configuration Management Workshop, Princeton, New Jersey, USA, October 1989.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....down in several components, each of which may exist in several component versions. A component version is an unbreakable, unambiguous configuration item. In the SCM domain, the common method for identifying component versions is attribution, as found in ADELE [15] the Context Model [39] EPOS [32], JASON [58] or SHAPE [33] Using attribution, every component version is identified by a conjunction of attribute value pairs describing its features; version selection is done through a (boolean) attribute expression which must be satisfied by the selected versions similar to a classical ....

Lie, A., Conradi, R., Didriksen, T. M., Karlsson, E.-A., Hallsteinsen, S. O., andHolager, P. Change oriented versioning in a software engineering database. In Proc. 2nd International Workshop on Software Configuration

....relies on a filename, its version and, perhaps, the file s extension. Allowing configuration items to have attributes other than those above allows more powerful means for identifying a configuration item. Systems like Adele [Estublier94] shape [Lampen88, Mahler94] Inscape [Perry89a] and EPOS [Lie89] allow configuration items to be tagged with attributes (sometimes called meta data) describing their properties, rather than their content. For example, attributes such as author, version, and time do not a#ect what a configuration item contains, but describe certain properties of it. Using ....

A. Lie, R. Conradi, T. M. Didriksen, and E.-A. Karlsson. Change oriented versioning in a software engineering database. Proceedings of the 2nd International Workshop on Software Configuration Management (Princeton, New Jersey). Published as ACM SIGSOFT Software Engineering Notes, 17(7):56--65, November 1989.

....down in several components, each of which may exist in several component versions. A component version is an unbreakable, unambiguous configuration item. In the SCM domain, the common method for identifying component versions is attribution, as found in ADELE [15] the Context Model [39] EPOS [32], JASON [58] or SHAPE [33] Using attribution, every component version is identified by a conjunction of attribute value pairs describing its features; version selection is done through a (boolean) attribute expression which must be satisfied by the selected versions similar to a classical ....

Lie, A., Conradi, R., Didriksen, T. M., Karlsson, E.-A., Hallsteinsen, S. O., andHolager, P. Change oriented versioning in a software engineering database. In Proc. 2nd International Workshop on Software Configuration Management (Princeton, New Jersey, Oct. 1989), W. F. Tichy, Ed., ACM Press, pp. 56--65.

....while backward deltas are stored in the original revision node data as depicted in figure 2. In our system we have an integrated editor recording operation based differences as deltas [Ols94] These change oriented deltas seems, as described by Lippe and Oestrom in [LvO92] and by Lie et al. in [ARMEA89] to have a much larger potential for supporting merging of variants than state based deltas calculated from edited files, like in RCS [Tic85] and SCCS [Roe75] Figure 1 A hierarchically structured program class Rectangle node node data program Module class Circle procedure Draw procedure ....

Lie Annund, Conradi Reidar, Didriksen Tor M., and Karlsson EvenAndr é. Change Oriented Versioning in a Software Engineering Database. In Proceedings of the2nd International Workshop on Software Configuration Management, volume 17, pages 56--65. ACM SIGSOFT Software Engineering Notes, October 1989.

....fragments. The model can be interpreted to provide the user with process assistance of some sort (guidance, control, automation) The paper will specially draw on examples from the EPOS PSEE [JC93] C 94] and its process modelling language called SPELL.EPOS has been developed at NTH in Trondheim since 1989, first as part of a national project, later as a Ph.D. project. The emphasis is flexible and evolving process support during enactment for multiple software developers, using conventional development tools and working on files in checked out workspaces. EPOS process models (task networks) are ....

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65, November 1989.

....add new attributes. 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 ....

Lie, A. et al. (1989). Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65.

....have been developed which support attribute based version identification. Each version is identified by a set of attributes such as author, creation date, language used, etc. Some of these attribute based systems can link versions with the software process activities responsible for their creation [3, 12, 13]. Rather than forcing the retrieval of a specific version using some arbitrary name, these systems allow the characteristics of the version to be used to identify it. Most version management is prescriptive, with an onus on controlling and centralising the version management process. There has ....

Lie, A., R. Conradi, T.M. Didriksen, and E.-A. Karlsson. 1989, Change-oriented Versioning in a Software Engineering Database. in Proc. 2nd Int. Workshop on Software Configuration Management. Princeton, N.J.: ACM Press. p. 56--65.

....representation forms such as text or abstract syntax trees. The storage form is also very compact since it utilizes deltas constructed by the editor and a high degree of sharing between versions. In our implementation editors use change oriented deltas as described in [Magnusson93] and also in [Lie89] 9 All information (evolution graph, full node information, deltas and structure) is stored by the server in one Unix file using a special format (Treefile) The server reads this information from the file and communicates it to the requesting client. The client interprets this information and ....

Lie, A., Conradi, R., Didriksen T., M., Karlsson, E.-A.: Change Oriented Versioning in Software Engineering Database, ACM SIGSOFT Software Engineering Notes, Vol 17, No 7, Nov 1989.

....a script to call tools, and PRE POST conditions to express constraints. The process model is defined by an object oriented and reflective process modelling language, called SPELL [12] 36] The task networks and all associated model information reside in a subdatabase under the versioned EPOSDB [51] [55] under the control of a special project task. See subsection 3.2. 3.1. Consistency Model for Products The EPOS consistency model is minimally defined by the EPOSDB data model, being a structurally object oriented data model with explicit relations. However, consistency is mainly 320 ....

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pp. 56-65 (1989).

....[5] The aim of this paper is to give a framework for tools dedicated to the manipulation of versions in most applications, where potentially numerous configurations are managed and manipulated simultaneously. In this sense, it differs from previous works, 19] 22] 3] 23] 7] 21] 20] [24], 2] which are often related to specific applications and or don t address the issue of manipulating many contexts of version at the user s level. In section 1 it is shown that, to develop such a framework, contexts of versions should be organized relatively to applications needs rather than to ....

....object versions implies that the system must maintain a huge number of links between object versions, as it is shown in [11] Thus, the update or the deletion of a configuration which is not a leaf of the derivation tree is usually not allowed in those models. In task oriented models, 21] 20] [24], 2] object versions are defined as the result of a change operation, and thus they are identified by the transaction that created them. Contexts are clearly defined: a context includes the versions of different objects resulting of a transaction applied to an existing context. Thus, it is not ....

Lie (A.), Conradi (R.), Didriksen (T. M.) and Karlsson (E.-A.). -- Change oriented versioning in a software engineering database. In : Proc. 2nd Int'l Work. on Softw. Config. Managt.. -- Princeton (USA), Oct. 1989.

....provided; instead all needed transaction management features have to be programmed in the process programming language. A further problem is the need to map the type systems of various languages to the common data model provided by E. 3.4 EPOS 3.4. 1 General Characteristics and Architecture EPOS [34, 35, 42, 77, 78] is a multi user process oriented software development environment providing basic facilities such as process modeling and configuration management (CM) It has a layered architecture consisting of a common user interface to various programming tools, of an activity manager, and a planner. The ....

A. Lie, R. Conradi, T.M. Didriksen, E.-A. Karlsson, Change Oriented Versioning in a Software Engineering Database. In W.F. Tichy (ed.), Proc. 2 nd Intl. Workshop on Software Configuration Management, Princeton, USA, October 1989, ACM SIGSOFT Software Engineering Notes, 14:7, November 1989.

....namely, in Section 7.2. isilYly itv em i fragment versioned item Fig. 8. Delta storage. presentation will be primarily based on the revised implementation of the EPOS configuration management system (ECM) as described in [15] 45] the initial implementation is described in [46] 16] [47]) UVM is similar to ICE (see Section 4) which was developed much later than Munch s ECM implementation. Both share the same fundamental design decisions. However, UVM still differs from ICE with respect to the following points: UVM is based on a different kind of logic (propositional 3 valued ....

A. Lie, R. Conradi, T.M. Didriksen, E.-A. Karlsson, S.O. Hallsteinsen, and P. Holager, "Change Oriented Versioning in a Software Engineering Database," Proc. Second Int'l Workshop Software Configuration Management, W.F. Tichy, ed., pp. 56-65, Nov. 1989.

No context found.

Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andr Karlsson, Svein O. Hallsteinsen, and Per Holager, "Change oriented versioning in a software engineering database," in Proceedings of the 2nd International Workshop on Software Configuration Management, Walter F. Tichy, Ed., Princeton, New Jersey, Nov. 1989, ACM Software Engineering Notes 14 (7), pp. 56-65.

....we will refer to the EPOS implementation at various points in the following sections. Our presentation will be primarily based on the revised implementation of the EPOS con guration management system (ECM) as described in [15] 45] the initial implementation is described in [46] 16] [47]) UVM is similar to ICE (see Section IV) which was developed much later than Munch s ECM implementation. Both share the same fundamental design decisions. However, UVM still di ers from ICE with respect to the following points: UVM is based on a di erent kind of logic (propositional 3 valued ....

Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andre Karlsson, Svein O. Hallsteinsen, and Per Holager, \Change oriented versioning in a software engineering database," in Proceedings of the 2nd International Workshop on Software Con- guration Management, Walter F. Tichy, Ed., Princeton, New Jersey, Nov. 1989, ACM Software Engineering Notes 14 (7), pp. 56-65.

....be recorded separately. In EPOS, we provide the user with CM facilities to control and maintain evolving versioned products or configurations. In the EPOS CM system we try to cover all the aspects of version control listed above. This is accomplished by the change oriented versioning (COV) model [2, 3] COV can be most easily understood as an extension and generalization of conditional compilation. COV can be considered to be dual to conventional component based versioning models, which we will call version oriented versioning (VOV) COV unifies conditional compilation and revision changes, and ....

Lie, A., Conradi, R., Didriksen, T.M., Karlsson, E.A., Hallsteinsen, S.O., and Holager, P.: 'Change Oriented Versioning in a Software Engineering Database'. in Tichy, W.F. (Ed.): Proc. 2nd Int. Workshop on Software Configuration Management, Princeton, (see also ACM SIGSOFT Software Engineering Notes, 17(7), November 1989, pp. 56--65).

No context found.

Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andre Karlsson, Svein O. Hallsteinsen, and Per Holager. Change Oriented Versioning in a Software Engineering Database. In Software Configuration Management Workshop, Princeton, New Jersey, USA, October 1989.

No context found.

Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andr'e Karlsson, Svein O. Hallsteinsen, and Per Holager. Change Oriented Versioning in a Software Engineering Database. In Software Configuration Management Workshop, Princeton, New Jersey, USA, October 1989.

No context found.

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65, November 1989.

No context found.

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65, November 1989.

No context found.

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65, November 1989.

No context found.

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65, November 1989.

No context found.

Anund Lie et al. Change Oriented Versioning in a Software Engineering Database. In Walter F. Tichy (Ed.): Proc. 2nd International Workshop on Software Configuration Management, Princeton, USA, 25-27 Oct. 1989, 178 p. In ACM SIGSOFT Software Engineering Notes, 14 (7), pages 56--65, November 1989.

No context found.

Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andre Karlsson, Svein O. Hallsteinsen, and Per Holager. Change oriented versioning in a software engineering database. In Proc. 2nd International Workshop on Software Configuration Management, pages 56--65. ACM Press, October 1989.

No context found.

Anund Lie, Reidar Conradi, Tor M. Didriksen, Even-Andr e Karlsson, Svein O. Hallsteinsen, and Per Holager. Change oriented versioning in a software engineering database. In Proc. 2nd International Workshop on Software Configuration Management, pages 56--65. ACM Press, October 1989.

No context found.

Lie, A., Conradi, R., Didriksen T., M., Karlsson, E.-A.: Change Oriented Versioning in Software Engineering Database, ACM SIGSOFT Software Engineering Notes, Vol 17, No 7, Nov 1989.

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