M. L. Griss, J. Favaro, M. d'Alessandro, Integrating feature modeling with the RSEB, Proceedings Fifth International Conference on Software Reuse (Cat. No.98TB100203). IEEE Comput. Soc, Los Alamitos, CA, USA, xiii+388 pp. 76-85, 1998.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....into component systems, which are similar to our abstract packages. In certain cases component systems implement the facade design pattern, which corresponds to a facade package in our setting containing just the code to provide an integrated interface to the constituent packages. FeatuRSEB [64] is an extension of RSEB with an explicit domain analysis phase based on FODA [86] The feature model is used as a catalog of feature commonality and variability. Moreover, it acts as configuration roadmap providing an understanding of what can be combined, selected, and customized in a system. ....

M. Griss, J. Favaro, and M. d' Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International Conference on Software Reuse, pages 76--85. IEEE Computer Society Press, 1998.

....specification should not be biased by implementation. Since features are an interpretation of the requirements, there is a need to map implementation independent requirements to implementation aware features. Feature Modeling. Our extended feature graph is based on the work presented in [9]. The main difference, aside from graphical differences, between our notation and theirs is the external feature and the addition of binding time. In [10] the feature graph notation is used as an important asset in a method for implementing software product lines. Combined with our management ....

....a central architecture that can be evolved and specialized into concrete products. The differences between those products can be discussed in terms of features. Consequently, a software product line must support variability for those features that tend to differ from product to product. In [9] the following categorization of features is suggested: Mandatory Features. Thesearethefeaturesthatidentify a product. e.g. the ability type in a message and send it to the mail server is essential for an email client application. Optional Features. These are features that, when enabled, add ....

[Article contains additional citation context not shown here]

M. L. Griss, J. Favaro, M. d'Alessandro, "Integrating feature modeling with the RSEB", Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203). IEEE Comput. Soc, Los Alamitos, CA, USA, 1998, xiii+388 pp. p.76-85.

....or end user point of view. Features describe the context of domain applications, the needed operations and their attributes and representation variations. Methods using feature analysis are FODA (feature oriented domain analysis) 15] FORM (feature oriented reuse method) 14] and FeatuRSEB [9]. FORM is an super set of FODA, which makes the FODA approach plausible for implementation and design. # Legacy system analysis. The analysis of the source code of legacy systems to find common functionality. The independent code clusters found can be grouped together in a new component. These ....

....Only a selection of Customers may rent certain Videos This features are selected because they illustrate the various problems encountered when composing them. In figure 3.3 a feature graph is presented showing the dependencies of these features. 27 Feature graphs are used to indicate variability [9]. The final system should always contain the features Renting and Returning , to have at least some functionality. The other features are more optional. The goal is to give code fragments for each of the features without knowing beforehand what features and how many will be included in the final ....

Martin L. Griss, J. Favaro, and M. d'Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International Conference on Software Reuse, pages 76--85, Vancouver, BC, Canada, 1998. http://citeseer.nj.nec.com/griss98integrating.html

....we present a method for managing variability in large systems, such as SPLs. The remainder of the paper is structured as follows. In Section 2, we relate the notion of variability to feature changes. Based on this analysis, we present a notation based on the feature model notation presented by [Griss et al. 1998] in Section 3. This notation makes it possible to express variability in terms of features. Then, in Section 4, we present our conceptual framework of terminology. In Section 5, we present three recurring patterns of variability. After that, in Section 8, we present our method for identifying and ....

....set of related features (optional, mandatory or even external) An example of a variant feature for the email client might be the editor used for typing in messages. Some email clients offer the feature of having a user configurable editor. The last three categories of features are also listed in [Griss et al. 1998]. The reason we added the category of external features is that we need to be able to reason about the context in which a system operates. 2.2 Feature Interaction Features are not independent entities [Bosch 2000] If they were, there would be no good reason to bundle them into a product. When ....

[Article contains additional citation context not shown here]

M. L. Griss, J. Favaro, M. d'Alessandro, "Integrating feature modeling with the RSEB", Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203). IEEE Comput. Soc, Los Alamitos, CA, USA, 1998, xiii+388 pp. p.7685.

....must also be considered. Features can stand as: mutually exclusive variants, mutually required features, features, whose optional number can be chosen. A feature, which has de ned such variability relationships for its subfeatures, is denoted as a variation point [21] or variation [11]. Feature diagrams are the key part of the feature modelling in methods such as MBSE [21] or generative programming [5] UML is employed for example in Reuse Driven Software Engineering Business (RSEB) 15, 11] Variability points are considered in the use case view and the component view in ....

.... relationships for its subfeatures, is denoted as a variation point [21] or variation [11] Feature diagrams are the key part of the feature modelling in methods such as MBSE [21] or generative programming [5] UML is employed for example in Reuse Driven Software Engineering Business (RSEB) [15, 11]. Variability points are considered in the use case view and the component view in [15] The variability modelling in the conceptual view is discussed in [11] In this work the extension for features, their attributes and variation points is de ned. The attributes can be suppressed in the model. ....

[Article contains additional citation context not shown here]

Martin L. Griss, John Favaro, and Massimo d' Alessandro. Integrating feature modeling with the rseb. In P. Devanbu and J. Poulin, editors, Proc. of 5th International Conference on Software Reuse, pages 76-85, Victoria, Canada, June 1998. IEEE Computer Society Press.

....However, there is no complete domain model, but several independent sets of parameters are used to describe the conditions. Although this might enhance the reusability, this restricts the description of cross component dependencies. Several other approaches use feature models for domain modeling [9, 13]. However, most of them do not use an explicit feature modeling tool which effectively limits the size of the models. In [21] a tool is described which operates on a feature model and is able to generate java class skeletons from feature models. The transformation process in CONSUL, which ....

M. L. Griss, J. Favaro, and M. d'Alessandro. Integrating Feature Modeling with the RSEB. In Proc. of the 5th International Conference on Software Reuse, pages 76--85, Victoria, Canada, June 1998.

....packages. In certain cases component systems implement the facade design pattern, which corresponds to a facade package in our setting containing just the code to provide an integrated interface to the constituent packages. FeatuRSEB is an extension of RSEB with an explicit domain analysis phase [12] based on FODA [16] The feature model is used as a catalog of feature commonality and variability. Moreover, it acts as configuration roadmap providing an understanding of what can be combined, selected, and customized in a system. Generative programming aims at automating the mapping from ....

M. Griss, J. Favaro, and M. d' Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International Conference on Software Reuse, pages 76--85. IEEE Computer Society, 1998.

....packages. In certain cases component systems implement the facade design pattern, which corresponds to a facade package in our setting containing just the code to provide an integrated interface to the constituent packages. FeatuRSEB is an extension of RSEB with an explicit domain analysis phase [12] based on FODA [16] The feature model is used as a catalog of feature commonality and variability. Moreover, it acts as configuration roadmap providing an understanding of what can be combined, selected, and customized in a system. Generative programming aims at automating the mapping from ....

M. Griss, J. Favaro, and M. d. Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International Conference on Software Reuse, pages 76--85. IEEE Computer Society, 1998.

.... Specialization Hierarchy (GSH) which supports the ISA relationship linking subtypes to their supertype. Feature Object dependencies. A feature represents one or more domain requirements, and this feature analysis becomes an important aspect of domain analysis [Cohen98, Dionisi98, Griss98, Kang90] This view relates the end user s perspective of the application domain, namely the features supported by the application domain, to the object types within the domain model. Also defined are required prerequisite features and any mutually exclusive features. This view is particularly ....

M. Griss, J. Favaro, M. D'Alessandro, "Integrating Feature Modeling with the RSEB", Proceedings of IEEE ICSR5, Victoria, June 1998.

....are based on UML, with variation points added to define variable parts and to connect them to model elements. However, the combination of variants and their configuration within a product line architecture is not supported in RSEB. The extension of RSEB with feature modeling is called FeatuRSEB [7]. Here a product line architecture view was added. Use cases are classified and grouped into mandatory and optional features. Even if adopted to object technology, FeatuRSEB has still most of the limitations of FODA. The traceability of requirements and features is needed to keep the ....

M. Griss, J. Favaro, M. d'Allesandro, Integrating Feature Modeling with RSEB. Hewlett-Packard Comp., 1998.

....by constructing domain specific feature categories, and the relations between the categories. The categories we have presented are not based on particular features, but rather on possible steps of evolution. In that sense, FODA is orthogonal to our work. Related to FODA is FeatureRSEB [Griss et al. 98] which extends the use case modeling of RSEB [Jacobson et al. 97] with the feature model of FODA. The Billing Gateway has been studied in earlier publications by our research group. The papers most closely related to our subject are [Mattsson Bosch 99a] and [Mattsson Bosch 99b] In ....

Griss, M.L., Favaro, J., d'Alessandro, M., "Integrating feature modeling with the RSEB", Proceedings of the Fifth International Conference on Software Reuse, IEEE Computer Society, Los Alamitos, CA, USA, p.7685. , 1998.

....in this paper. Application of this approach to other design languages and to the other UML diagrams remain interesting issues for future research. The kinds of requirements whose designs can be described in design subjects are many and varied. They include units of functionality, features [TF 98, GF 98] so called cross cutting requirements, like persistence or distribution, that affect multiple units of functionality, and variants (requirements that identify particular selections in a space of choices, such as of target system or level of capability) Design subjects can also encapsulate ....

M. Griss, J. Favaro, M. d'Allessandro, "Integrating Feature Modeling with the RSEB" In Proc. International Conference on Software Reuse (ICSR) 1998

....identify features, identify variation points and ultimately construct feature diagrams that capture all this information. Tool support mostly provides a blackboard like architecture to accomplish these tasks. Examples of systems are Sherlock Holmes [24, 25] DARE COTS [14] and Feature RSEB [15]. A survey of this kind of systems is given in [25] The emphasis of these tools is on the domain engineering process, and in this sense our work can be seen as complementary to the systems mentioned above. 6.2 Results We have presented results in three areas. First, we have formalized the ....

M. Griss, J. Favaro, and M. d' Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International Conference on Software Reuse, pages 76--85. IEEE Computer Society, 1998.

....features, identify variation points and ultimately construct feature diagrams that capture all this information. Tool support mostly provides a blackboard like architecture to accomplish these tasks. Examples of systems are Sherlock Holmes [SEY 99, SYL00] DARE COTS [FPDF97] and Feature RSEB [GFA98] A comparison of this kind of systems is given in [SYL00] As already mentioned in the introduction, we have no contribution to the process view on domain engineering and our work can be seen as complementary to the systems mentioned above. 6.2 Results We have presented results in three ....

M. Griss, J. Favaro, and M. d' Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International Conference on Software Reuse, pages 76--85. IEEE Computer Society, 1998.

....on different kinds of features is presented. Generative programming is presented as a powerful variability mechanism. A combination of the principles described in [Jacobson97] commonly referred to as the Reuse Driven Software Engineering Business (RSEB) and FODA [Kang90] is described in [Griss98]. They propose refinements to the feature model, and position it as the central view on the architecture of the system. A general introduction to feature engineering is given in [Turner99] The paper discusses the impact on different phases of the life cycle and provides ideas on how these phases ....

M.L. Griss, J. Favaro, M. d'Allessandro, Integrating Feature Modeling with the RSEB, International conference on Software Reuse, Victoria, Canada, June 1998.

No context found.

M. L. Griss, J. Favaro, M. d'Alessandro, Integrating feature modeling with the RSEB, Proceedings Fifth International Conference on Software Reuse (Cat. No.98TB100203). IEEE Comput. Soc, Los Alamitos, CA, USA, xiii+388 pp. 76-85, 1998.

No context found.

Martin L. Griss, John Favaro, and Massimo d'Alessandro. Integrating Feature Modeling with the RSEB. In 5th International Conference on Software Reuse (Proceedings), pages 76--85, 1998.

No context found.

Griss, M. L., J. Favaro and M. d'Alessandro, Integrating Feature Modeling with the RSEB, in: 5th International Conference on Software Reuse (Proceedings) (1998), pp. 76--85.

No context found.

Martin L. Griss, John Favaro, and Massimo d' Alessandro. Integrating feature modeling with the RSEB. In P. Devanbu and J. Poulin, editors, Proc. of 5th International Conference on Software Reuse, pages 76--85, Victoria, Canada, June 1998. IEEE Computer Society Press.

No context found.

M. L. Griss, J. Favaro, and M. d'Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International COnference on Software Reuse, pages 76--85, Victoria, BC, June 1998.

No context found.

M. L. Griss, J. Favaro, and M. d'Alessandro. Integrating feature modeling with the RSEB. In Proceedings of the Fifth International COnference on Software Reuse, pages 76--85, Victoria, BC, June 1998.

No context found.

M. L. Griss, J. Favaro, M. d'Alessandro, "Integrating feature modeling with the RSEB", Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203). IEEE Comput. Soc, Los Alamitos, CA, USA, 1998, xiii+388 pp. p.76-85.

No context found.

Griss, M.; Favaro, J.; d'Allesandro, M.: Integrating Feature Modeling with RSEB. Hewlett-Packard Comp., 1998.

No context found.

M. L. Griss, J. Favaro, and M. d'Alessandro. Integrating feature modeling with the RSEB. In Proceedings Fifth International Conference on Software Reuse, pages 76-85. IEEE Computer Society, 1998.

No context found.

Griss,M., Favaro,J., Alessandro, M., 1998, "Integrating Feature Modeling with the RSEB", in: Proceedings of the Fifth International Conference on Software Reuse, Victoria, Canada, Jun.

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