Application of Feature-Oriented Domain Analysis to the Army Movement Control Domain (Appendices A-I)

Cohen, Sholom; Stanley, Jay L; Peterson, Abigayle; Krut, Robert

doi:10.21236/ada552613

Cited by 13 publications

(15 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the widely used feature-oriented domain analysis method, rules are created to represent the dependencies [7,19]. Composition rules define the semantics existing between features that are not expressed in the feature diagram.…”

Section: Related Workmentioning

confidence: 99%

“…These graphs have nodes that represent the features and different types of edges between the nodes where the edges connect nodes in other parts of the feature hierarchy. The feature-oriented domain analysis (FODA) method [19] and successors of FODA [7] require a tree-like structure of the feature model which may be very difficult to generate, as there are no clear criteria to align the structure to a tree-like form. Moreover, you cannot capture all of the information contained in a (general) graph in a tree, leaving you with the possibility of omitting dependencies or losing control of the model [17].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Ferber

Haag

Savolainen

2002

Software Product Lines

View full text Add to dashboard Cite

Abstract. Reengineering a legacy product line has been addressed very little by current product line research activities. This paper introduces a method to investigate feature dependencies and interactions, which restricts the variants that can be derived from the legacy product line assets. Reorganizing the product line assets with respect to new requirements requires more knowledge than what is easily provided by the classical feature-modeling approaches. Hence, adding all the feature dependencies and interactions into the feature tree results in unreadable and unmanageable feature models that fail to achieve their original goals. We therefore propose two complementary views to represent the feature model. One view shows the hierarchical refinement of features similar to common featuremodeling approaches in a feature tree. The second view describes what kind of dependencies and interactions there are between various features. We show two examples of feature dependencies and interactions in the context of an engine-control software product line, and we demonstrate how our approach helps to define correct product configurations from product line variants.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Ferber

Haag

Savolainen

2002

Software Product Lines

View full text Add to dashboard Cite

show abstract

“…Feature models can be used to represent dependencies across features in a product line and analyze the impact of changes on features. Feature-Oriented Domain Analysis (FODA) [2,4], which uses several models such as context models and architectural models besides feature models, can also facilitate impact analysis. Feature-Oriented Reuse Method (FORM), an extension of FODA, addresses design issues from a marketing perspective [5].…”

Section: Related Researchmentioning

confidence: 99%

Change management patterns in software product lines

Mohan

Ramesh

2006

Commun. ACM

View full text Add to dashboard Cite

S oftware product lines (SPLs) undergo numerous changes to accommodate evolving needs of various market segments [1]. While some changes may apply to specific members, others permeate throughout the product line, often finding their way into the platform. In effectively managing evolution, product line development organizations are often faced with the following questions:• Are there general patterns of changes that are common in product lines? • If so, what change management practices can be used to effectively manage these patterns?We investigate these questions through a case study in a product line development organization (see the sidebar on how we conducted our study), identify three interesting patterns of change management, and suggest effective practices for addressing them.Establishing effective change management practices to prevent uncontrolled evolution of the product platform.

show abstract

“…Contact the vendor of the product to request all available marketing literature. 4. Fill in the name of the product.…”

Section: Assign a Unique Sdf Identifier (See Section 12)mentioning

confidence: 99%

“…Staff Affiliate Account -holders of this account type have a typical Unix account and an AFS account with restrictions in RLF development directories and the living documents directory. 4. Users with Sun4 and AFS -holders of this account type will have an AFS account only, with restrictions in RLF development directories and in the living documents directory.…”

Section: Pae J-1mentioning

confidence: 99%

Library Development Handbook. Central Archive for Reusable Defense Software (CARDS)

Curfman¹,

Lewis²,

Reddy³

1993

View full text Add to dashboard Cite

Application of Feature-Oriented Domain Analysis to the Army Movement Control Domain (Appendices A-I)

Abstract: The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange.

Cited by 13 publications

References 2 publications

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Change management patterns in software product lines

Library Development Handbook. Central Archive for Reusable Defense Software (CARDS)

Contact Info

Product

Resources

About