M.L. Griss, Implementing Product-Line Features with Component Reuse. Proceedings of the 6th International Conference on Software Reuse (ICSR), Springer LNCS 1844, june 2000 Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Evolving Legacy System Features into Fine-Grained - Alok Mehta American (2002) (1 citation) (Correct)
....be implemented within function(s) In this paper we are concerned only with the first two relationships. When a single feature implementation is contained within many functions then the critical viewpoint regarding evolution is the solution domain because the feature cross cuts the software [9]. Such code is often highly coupled and deeply embedded within the legacy system. When many related features are implemented by a single function then understanding the problem domain is critical for successful evolution. When a feature is implemented by a single function, evolution can be ....
....related technology is the cSuds [1] tool that can identify program feature in a C program. Our innovative contribution is showing how to construct a reusable fine grained component from the feature. The SEI FODA feature model ties business models together by structuring and relating feature sets [9]. FODA framework explores how this structured information can be leveraged across the software development effort. Griss [9] extended the FODA methodology to create an explicit feature model of functionality to facilitate reuse driven software engineering. We agree with Griss that a feature model ....
[Article contains additional citation context not shown here]
M. Griss, "Implementing Product-Line Features with Component Reuse", Proceedings, 6 Conference on Software Reuse, Springer-Verlag, Vienna, Austria, June 2000.
On the Notion of Variability in Software Product Lines - van Gurp, Bosch (2001) (14 citations) (Correct)
....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 method, the feature graph notation may be an important contribution to building software product lines. Also related is the FODA method discussed in [14] In ....
....paper, three distinct granularities of reuse are identified (component, class and algorithm) that correspond to our architecture design, detailed design and implementation levels. Feature interaction. Feature interaction can be modeled in a feature graph as dependencies between different features [10]. Since features can be seen as incremental units of development [8] dependencies make it impossible to link all features to a single component or class. As a consequence, source code of large systems such as software product lines tends to be tangled. Features that are associated with several ....
[Article contains additional citation context not shown here]
M. L. Griss, "Implementing Product line Features with Component Reuse", to appear in Proceedings of 6th International Conference on Software Reuse,Vienna,Aus- tria, June 2000.
Managing Variability in Software Product Lines - van Gurp, Bosch, Svahnberg (Correct)
....of incrementation as systems evolve . During each incremental evolution step of the system, features are added. Because of feature interaction, other, already implemented features may be affected by the changes. As a consequence, some features cannot be considered independently of the system. In [Griss 2000], the feature interaction problem is characterized as follows: The problem is that individual features do not typically trace directly to an individual component or cluster of components this means, as a product is defined by selecting a group of features, a care 4 fully coordinated and ....
....on the technological aspects of software reuse, the novelty of the SPL approach is that it takes a holistic approach by addressing business, organization, process and technology simultaneously. In this section we introduce the concepts of SPLs and variability in more detail. Related work (e.g. [Griss 2000]) suggests that modelling variability in SPLs is essential for building a flexible architecture. Yet, the concept of variability is generally not defined in great detail. We aim to address this by providing a conceptual framework for reasoning about variability. 4.1 Variability Variability is ....
[Article contains additional citation context not shown here]
M. L. Griss, "Implementing Product line Features with Component Reuse", to appear in Proceedings of 6th International Conference on Software Reuse, Vienna, Austria, June 2000.
A Taxonomy of Variability Realization Techniques - Svahnberg, Van Gurp, Bosch (2001) (2 citations) (Correct)
....of a system, it can also be represented as procedures during the development process, making use of various tools outside of the actual system being built. Although the use of variability techniques is increasing, research, both by others (for example, Jacobson et al. 1997] Jazayeri et al. 2000][Griss 2000][Clements Northrop 2002] and by ourselves [van Gurp et al. 2001] Bosch et al. 2002] Jaring Bosch 2002] shows that several problems exist. A major source for these problems is that software architects typically lack a good overview of the variability techniques available as well as the pros ....
....features cannot be considered independently. Adding or removing a feature to a system has an impact on other features. In [Gibson 1997] feature interaction is defined as a characteristic of a system whose complete behavior does not satisfy the separate specifications of all its features . In [Griss 2000], the feature interaction problem is characterized as follows: The problem is that individual features do not typically trace directly to an individual component or cluster of components this means, as a product is defined by selecting a group of features, a carefully coordinated and ....
[Article contains additional citation context not shown here]
M.L. Griss, "Implementing Product Line Features with Component Reuse", in Proceedings of 6th International Conference on Software Reuse, 2000.
Implementing Product-Line Features by Composing Component Aspects - Griss (2000) (14 citations) Self-citation (Griss) (Correct)
....one product can be rapidly propagated to other members of the product line. Implementing Product Line Features By Composing Aspects 3 Many researchers are working on these technologies from multiple perspectives, leading to a somewhat confusing and overlapping terminology. In a companion paper (Griss, 2000a) we carefully define many of the terms used in this paper, and propose steps towards unification. A product line is a set of products that share a common set of requirements, but also exhibit significant variability in requirements. A feature is a product characteristic that users and ....
....For example, Bosch, 1999) shows how a particular large scale productline for a communications product is built not by composing black box components, but by assembling customized subsystems, each based on a framework which evolves slowly. Similarly, the HP Laboratories component framework (Griss, 2000a) for medical and financial applications generates a customized C or Java framework for each distinct class of component. Components are then completed and specialized by subclassing or adding other code. The framework is characterized by a cluster of features, and the added code and selections ....
[Article contains additional citation context not shown here]
Griss, M. L. (2000a), Implementing Product-Line Features with Component Reuse, in Proceedings of 6th International Conference on Software Reuse, Springer-Verlag, Vienna, Austria, June.
Feature-Based Product Derivation: Composing Features - Jansen, Smedinga, van Gurp.. (Correct)
No context found.
M.L. Griss, Implementing Product-Line Features with Component Reuse. Proceedings of the 6th International Conference on Software Reuse (ICSR), Springer LNCS 1844, june 2000
Towards a Method for the Development of Aspect-Oriented.. - Kulesza, Garcia, Lucena (2004) (Correct)
No context found.
M. Griss. "Implementing Product-Line Features With Component Reuse". Proceedings of the International Conference on Software Reuse, Vienna, Austria, June 2000.
Automated Requirements-based Generation of Test.. - Nebut, Pickin, Le .. (2003) (Correct)
No context found.
M. Griss. Implementing product-line features with component reuse. In Springer-Verlag, editor, Proc. of the 6th international conference of Software Reuse, pages 137--152, 2000.
On the Notion of Variability in Software Product Lines - Svahnberg, van Gurp, Bosch (Correct)
No context found.
M. L. Griss, "Implementing Product line Features with Component Reuse", to appear in Proceedings of 6th International Conference on Software Reuse, Vienna, Austria, June 2000
Evolving Legacy System Features using Regression Test Cases.. - Mehta, Heineman (Correct)
No context found.
Martin Griss, Implementing Product-Line Features with Component Reuse, Proceedings, 6th International Conference on Software Reuse, Springer-Verlag, Vienna, Austria, Jun. 2000.
Evolving Legacy Systems by Locating System Features using.. - Mehta, Heineman (Correct)
No context found.
Martin Griss, Implementing Product-Line Features with Component Reuse, Proceedings of 6th International Conference on Software Reuse, SpringerVerlag, Vienna, Austria, June 2000.
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