scholarly journals A Case Study in Software Product Lines - The Case of the Mobile Game Domain

2008 ◽  
Author(s):  
Leandro Marques Nascimento ◽  
Eduardo Santana de Almeida ◽  
Silvio Romero de Lemos Meira
Keyword(s):  
Software Product Lines ◽  
Product Lines ◽  
Mobile Game ◽  
Software Product

Risk management in software product lines: An industrial case study

2012 ◽  
Author(s):  
Luanna Lopes Lobato ◽  
Paulo Anselmo da Mota Silveira Neto ◽  
Ivan do Carmo Machado ◽  
Eduardo Santana de Alemida ◽  
Silvio Romero de Lemos Meira
Keyword(s):  
Risk Management ◽  
Software Product Lines ◽  
Product Lines ◽  
Industrial Case Study ◽  
Software Product

A Case Study in Software Product: Lines An Educational Experience

2008 ◽  
Author(s):  
Liana Barachisio Lisboa ◽  
Leandro Marques Nascimento ◽  
Eduardo Santana de Almeida ◽  
Silvio Romero de Lemos Meira
Keyword(s):  
Educational Experience ◽  
Software Product Lines ◽  
Product Lines ◽  
Software Product

SYSTEMATIC FUNCTIONAL DECOMPOSITION IN A PRODUCT LINE USING ASPECT-ORIENTED SOFTWARE DEVELOPMENT: A CASE STUDY

2007 ◽  
Vol 17 (01) ◽  
pp. 33-55 ◽  
Author(s):  
TEGEGNE MAREW ◽  
JUNGYOON KIM ◽  
DOO HWAN BAE
Keyword(s):  
Software Development ◽  
Configuration Management ◽  
Software Product Lines ◽  
Product Line ◽  
User Requirements ◽  
Product Lines ◽  
Functional Decomposition ◽  
Software Product ◽  
Feature Based

Systematic configuration management is important for successful software product lines. We can use aspect-oriented software development to decompose software product lines based on features that can ease configuration management. In this paper, we present a military maintenance product line that employs such strategy. In particular, we applied a specific approach, feature based modeling (FBM), in the construction of the system. We have extended FBM to address properties specific to product line. We will discuss the advantages of FBM when applied to product lines. Such gains include the functional decomposition of the system along user requirements (features) as aspects. Moreover, those features exhibit unidirectional dependency (i.e. among any two features, at most one depend on another) that enables developers to analyze the effect of any modification they may make on any feature. In addition, any variations can be captured as aspects which can also be incorporated easily into the core asset if such variation is deemed to be important enough to be included in the product line for further evolution.

Sign in / Sign up

Export Citation Format

Share Document