J. Estublier and R. Casallas, "The Adele Configuration Manager," in Configuration Management, W. F. Tichy, Ed. Chicester: John Wiley & Sons, 1994, pp. 99-133.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....are they aware of any FODA based approaches that account for the presence of multiple versions a key feature underlying Mnage. Finally, our work is related to many contributions in the field of configuration management [8] In particular, configuration management system models such as Adele [13] and Proteus PCL [29] provide similar mechanisms for modeling variation points within software configurations. While borrowing concepts from these system models, our approach is oriented at product line architectures and, as such, is rooted in architectural concepts that are not addressed by the ....

J. Estublier and R. Casalles, The Adele Configuration Manager, in Configuration Management, W.F. Tichy, Editor. 1994: p. 99-134.

....aware of versioning. This solution is adopted, e.g. by PCTE [25] and 02 [26] Version model integrated with the data model. The data model offers constructs for defining versioned object types. Furthermore, the query language is also aware of versioning. DAMOKLES [27] EXTRA V [28] and Adele [29] follow this approach. Data model on top of the version model. In this case, the version model is completely orthogonal to the data model and can thus be combined with any data model (e.g. EER, object oriented, or simply files) This solution is realized, e.g. in EPOS [15] and ICE [30] 3.2 ....

....2 This ensures that navigation (along the composition links) is unique with respect to versioning. Therefore, versioning remains transparent, and existing applications can still navigate the database without having code added which is responsible for version selection. 4.1. 3 Adele Adele [29], 40] is a commercial SCM system that is based on an object oriented data model. In contrast to PCTE, the version model is built into the data model. The schema definition language supports the definition of versioned object types. Furthermore, versioning is integrated into the query language ....

J. Estublier and R. Casallas, "The Adele Configuration Manager," Configuration Management, W.F. Tichy, ed., pp. 99-134, 1994.

....of Adele offers an out of the box system model that the user may or may not adopt. In addition, the user may define any desired system model for organizing software objects. In fact, the predefined system model is defined in terms of a database schema, i.e. on top of Adele rather than built in [27]. SCM centered software architecture avoids redundancy problems because it is based on the assumption that there is no representation of the software architecture outside the SCM system. This assumption may have been valid a long time ago, but it does not hold any more. Using the modeling ....

Estublier, J., Casallas, R.: The Adele configuration manager. [35] 99--134

....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 are pushed to ....

J. Estublier and R. Casalles, The Adele Configuration Manager, in Configuration Management, W.F. Tichy, Editor. 1994: p. 99-134.

....aware of versioning. This solution is adopted e.g. by PCTE [25] and O2 [26] Version model integrated with the data model. The data model offers constructs for defining versioned object types. Furthermore, the query language is also aware of version ing. DAMOKLES [27] EXTRA V [28] and Adele [29] follow this approach. Data model on top of the version model. In this case, the version model is completely orthogonal to the data model and can thus be combined with any data model (e.g. EER, object oriented, or simply files) This solution is realized e.g. in EPOS [15] and ICE [30] ....

....performed 2. This ensures that navigation (along the composition links) is unique with respect to versioning. Therefore, versioning remains transparent, and existing applications can still navigate the database without having code added which is responsible for version selection. Adele [29], 40] is a commercial SCM system that is based on an object oriented data model. In contrast to PCTE, the version model is built into the data model. The schema definition language supports the definition of versioned object types. Furthermore, versioning is integrated into the 2Note that the ....

Jacky Estublier and Rubby Casallas, "The Adele configuration manager," In Tichy [65], pp. 99-134.

.... simultaneous development across multiple sites on multiple development platforms, Atria has released ClearCase MultiSite to support parallel development across geographically distributed teams and Adele, from Verilog, has recently added rich workspace support to its branch and merge features [Estu94, Estu95]. New offerings or upgrades are also available from Softool (CCC Harvest) Continuus (Continuus CM) IBM (CMVC) and Legent (Endevor WSX, formerly TeamTools from TeamOne Systems) The two most common mechanisms for handling concurrent modification of software configuration items are branching ....

Jacky Estublier and Rubby Casallas. The Adele Configuration Manager. Chichester, England. 1994. pp. 99--133. 14

....type independent revision numbering schemes of software components can based. Furthermore, it is well suited to support compatibility checks the information that a part of the Thus variants are alternative implementations of the same specification in accordance with the strict definition of [16] (as opposed to the discussion in [31] because the component approach uses precise interface specification to define the contract between components. interface IDBServer revision 1, initial (methods, 1, init) protocol, 1, init) interface IDBServer revision 2 (methods, 2, ....

....revision identifications would be the same for the trunk and the branch revisions. To amend the situation, we propose a way of handling branches in development as described below. It is not as sophisticated and does not o#er as much flexibility as some of the common systems [3, 16]. However, this is not seen as a major issue because the assumed main use of this revisioning system is for release numbering where the chance that a branch will be needed is relatively small. Component branches are identified by branch tags. The pair (component name, branch tag) must be unique ....

[Article contains additional citation context not shown here]

Estublier, J. and Casallas, R.: The Adele Configuration Manager. In [47], pp. 99--134.

....frustration. This issue can be exacerbated by the use of private workspaces in revision control systems. If the programmers develop with separate, private versions of key header files, at some point their work needs to be checked in. This will lead to source code merging. Estublier and Casallas [7] have reported that merge tools in revision control systems often fail. They point out that merging modules is not a perfect mechanism. Inconsistencies may arise from a merge; the probability of problematic merges rapidly increases with the number of changes performed in both copies. Therefore ....

Estublier, J., Casallas, R., The Adele configuration manager. In Tichy, W., F., (ed.), Configuration Management. Trends in Software. John Wiley & Sons, 1994.

....tools and systems. The early days of SCM were characterized by dedicated SCM tools like SCCS [43] or RCS [55] revision and change control) CPP, the C preprocessor [23] variant control) or MAKE [17] manufacture) These days, a new generation has emerged, represented by SCM systems like ADELE [15], EPOS [19] or CLEARCASE [31] These systems provide and integrate support for all SCM aspects through federated SCM system architectures [8] as illustrated in figure 1: a primitive layer provides basic versioning and access capabilities, a protocol layer realizes SCM tasks and procedures, and ....

....are not supported. This restriction would severely constrain SCM identification and selection schemes. There is an alternative candidate for a SCM foundation that does not suffer from these restrictions. Boolean operators from first order logic are used in several SCM selection schemes [39, 15, 19, 58, 33]; first order terms may also be used for identification purposes, using deduction techniques such as boolean unification [34] to match identification and selection terms. The problem with first order logic is that it is far too general; it lacks the central property of being attributeoriented. ....

[Article contains additional citation context not shown here]

Estublier, J., and Casallas, R. The Adele configuration manager. In Configuration Management,W.F.Tichy, 34

....interconnection language derived from Intercol [15] This made it difficult to model non design objects, and it forced the user to adopt the predefined language for programming in the large. For example, even a simple textual document was required to have an interface and a body. In Adele II [5], there is a predefined system model that the user may or may not use. In addition, the user may define any desired system model for organizing software objects. Thesis 4 Unavoidable redundancy in system descriptions: Under the constraints of bottom up integration, there is no hope to unify ....

J. Estublier and R. Casallas. The Adele configuration manager. In W. F. Tichy, editor, Configuration Management, volume 2 of Trends in Software, pages 99--134. John Wiley & Sons, New York, 1994.

.... control facilities, e.g. RCS [47] SCCS [41] Sablime [5] others provide more complete configuration management solutions (e.g. CVS [7] CoED [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] ....

J. Estublier and R. Casallas. The Adele configuration manager. In W. Tichy, editor, Configuration Management,number 2 in Trends in Software, pages 99--134. Wiley, London, Great Britain, 1994.

....Combined, all revisions and variants create a version tree, which is the central entity through which users interact with a first generation CM system. In order to support tracking of compound changes to groups of source files and advanced workspace management, research into system models [9,14,27,37] sparked the inception of the second generation of CM systems. System models and their associated modeling languages provide a way to capture the structure of the software being managed via configurations sets of specific versions of specific source files. To capture the potential evolution of ....

....because the system model inherently operates at the architectural level, and meaningful, because the system model relates changes to each other. Existing CM system models (e.g. ShapeTools [14] and PROTEUS [37] are limited in this regard: with the exception of Adele (through interfaces [9]) and Inscape (through obligations and pre and post conditions [27] these system models do not provide mechanisms beyond grouping, versioning, and selection. The central role of architectural concepts in our system model changes that fact. Specifically, it allows us to leverage explicit ....

[Article contains additional citation context not shown here]

Estublier, J. and Casalles, R., The Adele Configuration Manager, in Configuration Management, W.F. Tichy, Editor, Wiley: London, Great Britain. pp.99-134, 1994.

....and prototypes in OPG may be compared with components and variants in SCM: prototypes may be seen as different variants of their type. In OPG, the prototypes of a type differ in their property values. Similarly, the variants of a component in SCM are often characterized by attributes or features [6, 22]. However, the selection rules work quite differently. In OPG, the rules are localized to the components and check consistency between a component and its enclosing components and subcomponents, e.g. checking that a Lining has the same diameter as its enclosing Hole. In SCM, the rules are usually ....

J. Estublier and R. Casallas. The Adele Configuration Manager. In Tichy (Ed.) Configuration Management, Wiley, 1994.

.... and access rights for the different functions in the project [14] The extent to which these requirements are met systems varies from file based checkin checkout mechanisms as in RCS [28] over virtual file systems as in CLEARCASE [18] or in n DFS [13] to database supported workspaces in ADELE [9]. However, since every SCM system provides means to generate, propagate, and apply changes, every SCM system allows to simulate workspaces even if the workspace is but a developer s private directory or a branch in the version graph. This problem is thus considered solved. With an ....

....decent versioning of file hierarchies, issues like renaming or reorganizing structures are still not handled in a fully satisfying manner. All SCM systems offer methods to select specific configurations; the range goes from tags as in RCS or CVS to elaborated rules as in CLEARCASE [18] or ADELE [9]. The organization of versions (or changes) within an SCM system, the version model, has considerable impact on the way users interact with an SCM system [5] Although it has been shown that all existing versioning models can be unified to applying constrained changes [37] the quest for ....

[Article contains additional citation context not shown here]

ESTUBLIER, J., AND CASALLAS, R. The Adele configuration manager. In Tichy [30], ch. 4, pp. 99--133.

....[NATURE 96] MENTOR [GROSZ 96] the team of J. Souquires [SOUQUIERES 93] who mainly focus on requirements engineering. We can also cite [CURTIS 92] and [GARG 96] which are more oriented toward software development process modelling. Business process modelling is supported by, among others, Adele [ESTUBLIER 94] Process Weaver which allow the designed processes to be followed and is Modeler, ProcessWise, IDEF [MAYER 98] SilverRun or SOCCA [ENGELS 94] which are just descriptive tools. A common point between most of them is the use of a declarative language or a graphical language and the need for an ....

....the way these recordings are performed and reused. POTTS 88] is one of these. C. Potts and G. Bruns explain why and how to record the reasons for design decisions, but they do it through hypertext techniques which are well suited to build human readable documentation, but less for reuse. ESTUBLIER 94] explains how processes can be supported, with the recording of what is actually done and with versioning, but stays at a high level; we know what tool has been used, with what products, when, but we do not know what happened during the use of the tool. In this paper, we describe how we record ....

Jacky Estublier and Rubby Casallas, The Adele Configuration Manager, in Tichy editor, Configuration Management. John Wiley & Sons, 1994.

....in the rule or assertion. This set can then be used to restrict the generation of candidate assignments. 8 Related Work Traditional configuration management (CM) systems provide an alternate platform on which to build an analysis framework similar to the one described in this paper. The Adele [4] CM system in particular embodies some kinds of automatic analysis for interfaces that is one kind of analysis package. Adele introduces the notions of interfaces and realizations of those interfaces. A specific interface may have many revisions, where each revision may have multiple realizations ....

J. Estublier and R. Casallas. The Adele Configuration Manager. In Configuration Management, pages 99--134. Wiley, 1994.

....workspace. A user can then make changes to the artifacts in the workspace. To commit the changes, the configuration is sent back to the central repository. Once there, the modified artifacts are merged with other changes that may have been made concurrently in other user workspaces. Adele Adele [9] has been enhanced for distribution through a tool called Mistral [12] Mistral helps a user manage the replication of an Adele database. Using Mistral, an Adele user at one site assembles a database delta, which compactly represents the changes made to artifacts at that site, and ships the delta ....

J. Estublier and R. Casallas. The Adele Configuration Manager. In W. Tichy, editor, Configuration Management, number 2 in Trends in Software, pages 99--134. Wiley, London, 1994.

....in compiler syntax errors. 11] This data came from an in house merge of the Windows port of ClearCase with their UNIX version [10] The merge involved several thousand files resulting from nine to twelve months of diverging development effort by about 10 people. The Adele Configuration Manager [4] incorporates the notion of workspaces into configuration management to provide support for change management. Within a workspace a lock can be set on a file which causes the transparent creation of a copy (referred to as dynamic versioning) Releasing the lock causes the merging of the dynamic ....

....mergers rapidly increases with the number of changes performed in both copies. Were mergers to be performed only at transaction commit, most of them would not be successfully performed. Frequent mergers, at some well defined points, are needed to maintain two cooperating WSs in synch. [4] Thus Adele requires frequent updating of the changes being made in the other workspaces to keep the various parallel versions more or less in synch. 2.2 Program Analysis The other strand of research is that of Horwitz, Prins and Reps [7] work on integrating noninterfering versions. They ....

Jacky Estublier and Rubby Casallas. The Adele configuration manager. In Walter F. Tichy, editor, Configuration Management. Trends in Software. John Wiley & Sons, 1994.

....purposes can be found in [KH95] In that paper, we introduce project flow graphs as a general and flexible notation for modeling and comparing configuration management systems. With ADELE, Estublier presented a version management system with an intensional mechanism for building configurations [Est94]. The selection scheme is more general because it allows for dynamic dependency schemes and for imposing general predicates on versions labels. However, ADELE only supports one stage of the software life cycle (selecting source code versions) and will not identify objects or executables nor ....

J. Estublier. The adele configuration manager. In Tichy, editor, Configuration management. John Wiley & Sons, New York, 1994.

.... select the most recently formed version , cf. 17] ffl an explicit identification, i.e. a name of the component to be included is given, e.g. in the form of a table, cf. 9] ffl description by attributes, i.e. a version is described implicitly by stating properties which it should fulfil, cf. [4, 8, 5, 19]. The empty description has an obvious disadvantage of being too inaccurate. The explicit description can lead to difficulties in practical situations when the number of components is high and to produce a list of all those which should be included is very error prone. As the most suitable way ....

....1 2 The selection requirements formulate actually a query to a database of software components. To evaluate them, database query processing techniques can also be used, e.g. 1, 16] Frequently used approach to version selection is to use conditions restricting properties of versions, e.g. [18, 4, 8, 5]. The conditions are often represented by a logic expression. For example, an expression (operating system = DOS communication language = Slovak) identifies all such versions which can run under DOS operating system and the communication with the user is in Slovak language. The ADELE system [5] ....

[Article contains additional citation context not shown here]

J. Estublier. The Adele configuration manager. Technical report, L.G.I., Grenoble, 1992.

....hash signature for each artifact set, then re analysis of duplicated sets can be detected and avoided. 8. Related Work Traditional configuration management (CM) systems provide an alternate platform on which to build an analysis framework similar to the one described in this paper. The Adele [3] CM system in particular embodies some kinds of automatic analysis for interfaces that is one kind of analysis package. Adele introduces the notions of interfaces and realizations of those interfaces. A specific interface may have many revisions, where each revision may have multiple realizations ....

J. Estublier and R. Casallas. The adele configuration manager. In Configuration Management, pages 99--134. Wiley, 1994.

....is no tool covering the whole deployment process yet, there are however many domains in computer science related to deployment. Among these technologies are (see Fig. 1) Software Description Formalisms (SDF) 2,3,4] Organization Description Formalisms [5,6] Software Configuration Managers (SCM) [7,8], Package Managers (PM) 9,10] Content Delivery systems and push technology (CD) 11,12,13,14] Installation Tools (IT) 15,16,17,18] Application Management Systems (AMS) 19,20,21,22,23] and Configurable Distributed Systems (CDS) 24,25] Producer Enterprise User SDF SCM PM CD AMS ....

....newsgroups to notify people or other notifications (events) to notify parts of the infrastructure itself (agents) on the consumer side. As far as existing technologies (see Fig. 1)are concerned, most producer deployment activities are covered by Software Configuration Systems such as Adele [7] or Clearcase [8] and Package Managers such as Red Hat s RPM [9] or HP UX s Mkpck command [10] Installation Tools such as InstallFromTheWeb [15] NetDeploy [16] InstallManager [17] and AutoInstall [18] also provide packing facilities. 2.2. Enterprise Deployment Activities described in this ....

J. Estublier and R. Casallas. "The Adele Configuration Manager", Configuration Management, Wiley, 1994, pp.99134.

No context found.

J. Estublier and R. Casallas, "The Adele Configuration Manager," in Configuration Management, W. F. Tichy, Ed. Chicester: John Wiley & Sons, 1994, pp. 99-133.

No context found.

J. Estublier and R. Casallas, "The Adele Configuration Manager," in Configuration Management, W. F. Tichy, Ed. Chicester: John Wiley & Sons, 1994, pp. 99-133.

No context found.

Estublier, J. and Casalles, R., The Adele Configuration Manager, in Configuration Management, W.F. Tichy, Editor, Wiley: London, Great Britain. pp.99-134, 1994.

First 50 documents  Next 50

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