| Plaice, J., Wadge, W., `A New Approach to Version Control', IEEE Transactions on Software Engineering, Vol. 19, No. 3, March 1993, pp.268~276 |
....on how this problem can be tackled are given in [14, 13] where a formalism called Multidimensional XML (MXML) is presented. MXML was influenced by Intensional HTML (IHTML) 17, 6, 16] IHTML is a Web authoring language, based on and extending ideas proposed for a software versioning system in [12], that allows a single Web page to have different variants and to dynamically adapt itself to a given context. The main difference between IHTML and MXML is a projection of the difference between HTML and XML, that is, focusing on encoding structure rather than on presentation. In this paper, we ....
J. Plaice and W. W. Wadge. A New Approach to Version Control. IEEE Transactions on Software Engineering, 19(3):268--276, 1993.
....information. In addition, our model retains OEM labeled edges and attaches context metadata to a new type of edges; graph models such as OEM become special cases of the model we propose. Our work was in uenced by Intensional HTML [16] a Web authoring language that incorporates ideas presented in [13] and allows a single Web page to have di erent variants and to dynamically adapt itself to a user de ned context. Our previous work on Multidimensional XML (MXML) 14, 11, 12] has also played a major role in shaping the data model we describe in this paper. MXML is an extension of XML that treats ....
J. Plaice and W. W. Wadge. A New Approach to Version Control. IEEE Transactions on Software Engineering, 19(3):268-276, 1993.
....context specifiers to qualify elements and attribute values, and specify the contexts under which the document and its components have meaning. MXML was influenced by Intensional HTML (IHTML) 12] a Web authoring language, based on and extending ideas proposed for a software versioning system [9]. IHTML allows a single Web page to have different variants and to dynamically adapt itself to a given context. In this paper, a) we motivate the use of and specify MXML syntax and semantics by reviewing and further extending the formalism presented in [11, 10] b) we clarify how the structure ....
J. Plaice and W. W. Wadge. A New Approach to Version Control. IEEE Transactions on Software Engineering, 19(3):268--276, 1993.
....Moreover, the language supports intensional operators that work along each di erent dimension. A language in the spirit of GLU has also been developed in the logic programming domain [14] An area in which multidimensionality appears to o er signi cant bene ts is the area of version control [16]. The intensional versioning approach described in [16] has recently found applications in the evolving area of Internet computing. One example application in this domain is the development of the language IHTML (Intensional HTML) 20, 8, 7, 18] a high level Web authoring language. The main ....
....that work along each di erent dimension. A language in the spirit of GLU has also been developed in the logic programming domain [14] An area in which multidimensionality appears to o er signi cant bene ts is the area of version control [16] The intensional versioning approach described in [16] has recently found applications in the evolving area of Internet computing. One example application in this domain is the development of the language IHTML (Intensional HTML) 20, 8, 7, 18] a high level Web authoring language. The main advantage of IHTML over HTML is that it allows practical ....
J. Plaice and W. W. Wadge. A New Approach to Version Control. IEEE Transactions on Software Engineering, 19(3):268-276, 1993.
....encapsulation must be provided; default definitions must be provided. Specific intensional programming languages (SIPL) As the GIPL is being developed, the existing intensional programming formalisms will be translated into the GIPL. These include: intensional versioning (Plaice and Wadge [57]) intensional attribute grammars (Tao and Wadge) intensional spreadsheets (Du and Wadge [21] intensional scientific programming (Paquet and Plaice) intensional reactive programming (Gagn and Plaice [31] Of course, nothing will prevent us from combining these different approaches. ....
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 3(19):268 276, 1993.
....reasons (smooth incorporation of a new version, ability to cancel changes) The interested readers are referred to [5, ch. 5] for an introduction to the subject. Specific research works are described in [8] on version management for sets of modified objects, 4] on consistency maintenance, and [13] about sub versions, to mention only a few. Another important direction is that of Adaptive Programs (AP) An information system is described by: Class dictionary graphs and AP s. An AP is described by: An operation, Propagation patterns, wrapping code [10] 11] A class dictionary graph ....
J. Plaice, W. Wadge, "A new Approach to Version Control", IEEE tran. on Software Eng', vol. 19, num. 3, p. 268-276, 1993.
....dimensions. Intensional programming (in the sense of Lucid) has been successfully applied to resolve problems with a new perspective that enables a more natural understanding of problems of intensional nature. Such problems include topics as diverse as reactive programming, software configuration [8], tensor programming [7] distributed operating systems [6] However, these projects have all been developed in isolation. GLU is the most general intensional programming tool presently available [4] However, experience has shown that, while being very efficient, the GLU system suffers from a ....
....version selection correspond more to an aggregation process than to a selection process: All versions that correspond to the version description are chosen, and these are all coalesced into a single version. This has been implemented in the Lemur system using an intensional versioning technique [8]. A highly modular design and complete specification of generic software interfaces enables the GEE to accept other garbage collecting algorithms with minimal programming cost and replacement overhead. A thorough analysis of the different requirements of each intended application of intensional ....
[Article contains additional citation context not shown here]
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 3(19):268--276, 1993.
.... Keywords Software configuration management, version control, software engineering 1 INTRODUCTION Today a wide selection of commercially available configuration management systems exist; one web site catalogs over 50 such packages [4] The technology of these systems is well understood [1, 3, 6, 7, 8, 10], but the actual use patterns and motivations for fine grain operations such as check in are not. For example, we expect a check in when the modification of an item is complete but motivations for check ins due to incremental changes are less predictable. We have observed differences in ....
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Trans. on Software Engineering, 19(3):268--276, Mar. 1993.
....becomes indispensable to identify and locate the actually requested service based on an identification scheme, which still needs to be formally defined. Version management in the WOS has been informally presented in (Ben Lamine and Plaice 1998) It follows from previous work on software versioning (Plaice and Wadge 1993) and intensional programming (Paquet 1999) in particular the Lucid programming language (Wadge and Ashcroft 1985) An intensional programming system is characterized by two operations, lookup and eval which define interactions with possibly multiple warehouses and definition catalogs. These ....
Plaice, J. and W. Wadge. 1993. "A new approach to version control." IEEE Transactions of Software Engineering 19, no. 3:268--276.
....features. Zeller focuses on building consistent product configurations as sets. While he presents techniques for composing systems and managing version histories, the set representation does not directly support hierarchical aggregation or variational derivation relationships. Plaice and Wadge [43] present another approach for organizing software versions to implement various configurations of a design. In their work, globally unique names and an ordered version derivation path identify the appropriate version of a component for a configuration. The proper version is identified by matching ....
John Plaice and William W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 19(3):268--276, Mar 1993.
....families are represented. A family of software components comprises versions of a software component. Actually, we can always consider versions to be revisions. However, they are grouped into subsets called variants within a family. This is a conceptual novelty comparing to related works, e.g. [14], where revisions and variants are treated at the same level as components. Similar concepts were employed in [15] where there is proposed an orthogonal organization of variants and revisions. A variety of architectural relations can be defined between variants and families. The fact that ....
J. Plaice and W.W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 19(3):268--275, 1993.
....user interface are independent aspects, it does not make sense to develop a joint version labeled with DB = DELPHIGUI = MOTIF . Instead, Plaice et al. suggest to use the more general revision in terms of the ordering relation if no revision exactly matching the specification is available [PW93]. Though we consider their selection principle to be very powerful, we doubt that their ordering relation is easy to compute. In our paper, we introduce an abstract labeling algebra without these drawbacks and present a practical implementation, the ALEX version manager. In our work we introduce a ....
....it equally supports versioned systems within any technical design process. 4 Related Work Plaice et al. have introduced a very general model for managing versions of versioned elements. They presented a non lattice version algebra because their versioning operator is non commutative [PW93]. We found that attribute valuepairs instead of the single identifiers in their paper allow for the definition of a commutative versioning operator within a version lattice. In this lattice, version expressions can be reduced to a simple normal form, which makes computing equality and the version ....
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 19(3), pp.268 -- 276, 1993.
No context found.
J. A. Plaice and W. W. Wadge, `A new approach to version control', IEEE Trans. Software Engineering, (1993).
....programming [4] corresponds to building programs whose behavior depends on an implicit multidimensional context; changing a context may in uence the behavior of a program, which can test the current context to adapt its behavior or modify the context as it sees t. Intensional versioning [5] is the dual to intensional programming; the de nitions of all identi ers are assumed to vary through the set of possible contexts; we say that the identi ers are versioned. ISE is an attempt to create the rst imperative scripting language that combines intensional programming and intensional ....
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 3(19):268-276, 1993.
....engine, etc. from the standard one. The French version of a web page will di er in many places from its English counterpart. We cannot change the car or the page by swapping a single component. Our approach to diversity is based a parametric model rst presented by J. Plaice and the author in [3]. The members of a family are determined by (and can be generated from) the values of a collection of parameters. These parameters (also called dimensions) are global in principle, any component can be sensitive to (altered by changing) any of the parameters. The rst Web authoring system based ....
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Transactions on Software Engineering, 3(19):268-276, 1993.
....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 approach to software con guration (i.e. pick the version of each module which best approximates the requested version of the whole system) It was only after these tools were in use that the ....
....than any other existing version (i.e. any other existing version which re nes to the requested version also re nes to this one) If such a version exists, it is used in place of the requested version. If not, it is an error. The re nement ordering for versions in IHTML 1 is fully described in [16] and [20] The IHTML 2 set is fully described in Section 3.1.1. The basic idea is that versions are ordered by the re nement operator , with rules such as ; and (2.4) The complete set of rules de nes a partial order for versions. Given a requested version R, and a set of existing ....
[Article contains additional citation context not shown here]
J. Plaice and W.W. Wadge. A New Approach to Version Control. IEEE Transactions on Software Engineering, pages 268-276, March 1993.
....a service or a program is thus versioned. Moreover, in contrast to object oriented programming, we propose to rather manage diversity and internal behavior than to hide them. Version management in the WOS has been informally presented in [3] It follows from previous work on software versioning [7] and intensional programming [6] in particular the Lucid programming language [1] An intensional programming system is characterized by two operations, lookup and eval which define interactions with possibly multiple warehouses and definition catalogs. These catalogs are basically tagged ....
J. Plaice and W.W. Wadge. A new approach to version control. IEEE Transactions of Software Engineering, 19(3):268--276, 1993.
....it from other forms of parameter selection. One is version refinement and the other is best fit. We describe these attributes and their significance in detail below. 3. 1 Intensional Versioning The intensional (possible worlds) approach to versioning was originally developed by Wadge and Plaice [11] for use in configuring families of programs from families of components. Most software configuration tools work bottom up, and allow the user to create a variant of the program by selecting different variants of the components. In [11] by contrast, each variant is described determined by ....
....to versioning was originally developed by Wadge and Plaice [11] for use in configuring families of programs from families of components. Most software configuration tools work bottom up, and allow the user to create a variant of the program by selecting different variants of the components. In [11], by contrast, each variant is described determined by version expression assigning values to parameters. For example, the expression processor:ppc OS:8 language:french might indicate the french language version for a PPC macintosh running OS 8. A particular version of a program is ....
J. Plaice and W. W. Wadge, A New Approach to Version Control, IEEE Transactions on Software Engineering, March 1993, 268-276.
No context found.
J. Plaice and W. W. Wadge. A new approach to version control. IEEE Trans. on Soft. Eng., 19(3), March 1993.
....if the partial order approach is used, then a general mechanism called the variant substructure principle can be used. When version V of a structured module is being built, then version V of each of its component modules is requested, and the most relevant approximation of each is returned. See (Plaice and Wadge 1993). To conclude this section, it is natural for any given module to have a version space, and for versions to be designated by abbreviations that describe the essential attributes that those versions must provide, and that the complete version descriptions be completed automatically. When several ....
Plaice, J. and Wadge, W.W. 1993. A new approach to version control. IEEE Transactions of Software Engineering, 19(3):268--276.
.... Eduction, a form of demand driven lazy evaluation, was first proposed for the execution of dataflow languages (Wadge and Ashcroft 1985) Since then, it has been generalized for many other computer problems (Orgun and Ashcroft 1996) The eductive process for software configuration is as follows (Plaice and Wadge 1993). A version of a system is requested from a warehouse, in this case a software repository. To build that version, appropriate versions of a set of subsystems must be requested. For each subsystem, the versions of its own subsystems must be requested, and this process takes place in turn until ....
....the evolving Web that offers us the unique opportunity of incrementally building these eductive engines, adding functionality as needed and as further provided by technological advances. Furthermore, version spaces can be structured so that they can be used by a wide variety of applications (Plaice and Wadge 1993). In fact, much of our current research deals with the interoperability of version spaces of different entities, which will be a key issue for the successful development of the WOS. ....
Plaice, J. and Wadge, W.W. 1993. A new approach to version control. IEEE Transactions of Software Engineering, 19(3):268--276.
....the partial order approach is used, then a general mechanism called the variant substructure principle can be used. When version of a structured module is being built, then version of each of its component modules is requested, and the most relevant approximation of each is returned. See (Plaice and Wadge 1993). To conclude this section, it is natural for any given module to have a version space, and for versions to be designated by abbreviations that describe the essential attributes that those versions must provide, and that the complete version descriptions be completed automatically. When several ....
Plaice, J. and Wadge, W.W. 1993. A new approach to version control. IEEE Transactions of Software Engineering, 19(3):268--276.
....despite its theoretical advances, Chronolog has not been evaluated in practical applications of significant size, that would help reveal its potential as well as its deficiencies. Another area in which intensional programming appears to offer significant benefits is the area of version control [PW93]. The intensional versioning approach described in [PW93] has recently found applications in the evolving area of Internet computing. One example application in this domain is the development of the language IHTML (Intensional HTML) Yil97] a high level Web authoring language. The advantage of ....
....evaluated in practical applications of significant size, that would help reveal its potential as well as its deficiencies. Another area in which intensional programming appears to offer significant benefits is the area of version control [PW93] The intensional versioning approach described in [PW93] has recently found applications in the evolving area of Internet computing. One example application in this domain is the development of the language IHTML (Intensional HTML) Yil97] a high level Web authoring language. The advantage of IHTML over conventional HTML is that it allows practical ....
J. Plaice and W. W. Wadge. A New Approach to Version Control. IEEE Transactions on Software Engineering, 19(3):268--276, 1993.
No context found.
Plaice, J., Wadge, W., `A New Approach to Version Control', IEEE Transactions on Software Engineering, Vol. 19, No. 3, March 1993, pp.268~276
First 50 documents
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