SEI's software product line tenets

Northrop, Linda

doi:10.1109/ms.2002.1020285

Cited by 188 publications

(80 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…a company decides to use, as long as one is chosen. If not, there have been cases where the product line effort languished [28].…”

Section: Process Challengesmentioning

confidence: 99%

See 1 more Smart Citation

Analysis of a Small Company for Software Product Line Adoption — An Industrial Case Study

Nazar¹,

Rakotomahefa²

2016

IJCTE

View full text Add to dashboard Cite

Abstract-While there are many success stories of adoption of software product line (SPL) practices in large companies, there is a need to investigate how well the product line strategy works for small organizations and what issues and challenges they could possibly face. This case study provides a comprehensive detailed analysis of a small company's tendency of adopting Software product line. It also reveals how new trends in software engineering, for example, agile methods interact with product line strategy. We used an ethnographic approach of collecting data by spending some time at a company in China and gathering information through interviews, documents, and studying organizational processes. The collected data was analysed using grounded theory. The findings were evaluated with regard to business, architecture, process and organizational concerns of a company, generally known as BAPO model. In the end, the challenges faced by the company were addressed and potential improvements were suggested to reap the benefits of software product line. The results show that the company is unknowingly using some SPL practices and has a potential to adopt SPL practices fully.Index Terms-Agile development processes, BAPO model, empirical study, grounded theory, software product lines. I. INTRODUCTIONSoftware Product Line Engineering (SPLE) is an idea of building and managing a family of products with shared commonalities, targeting a certain market area and is developed from a common set of core resources. SPLE is therefore beneficial for a company developing a software suite with common or somewhat similar features between the products. To manage this product line, the commonalities are first identified and modularized. This commonality has certain variational points separating different products. There exist possibilities to derive new products from the platform by creating new variabilities. Thus, decreasing production cost, time to market, increased product quality, and exploring new market ventures could be achieved by reusing such variations and commonalities in a proper manner [1]. Usually, managing commonality and variability between different products are conducted using systematic variability management techniques [2]. Such techniques help achieve a number of benefits including defining the sources of variability and the different variants, tracing variability from the model to the code and vice versa, and communicating variability to the different stakeholders [3]. Manuscript received October 14, 2014; revised May 12, 2015. N. Nazar is with School of Software, Dalian University of Technology, China (e-mail: najamnazar@126.com).T. M. J. Rakotomahefa is with the School of Civil Engineering, Dalian University of Technology, China (e-mail: ymamesoj@outlook.com).The SPLE is proactive in nature and often structured to facilitate two separate roles: domain engineering and application engineering [4]. Domain engineering concerns the commonalities in order to build and manage reusable or core assets such as requirement...

show abstract

“…a company decides to use, as long as one is chosen. If not, there have been cases where the product line effort languished [28].…”

Section: Process Challengesmentioning

confidence: 99%

“…a company decides to use, as long as one is chosen. If not, there have been cases where the product line effort languished [28].Operational Processes: We suggest them to organize operational processes first and then move to adopt Agile practices. Such operations cover for day-to-day activities such as support, training, key account management, etc.…”

mentioning

confidence: 99%

Analysis of a Small Company for Software Product Line Adoption — An Industrial Case Study

Nazar¹,

Rakotomahefa²

2016

IJCTE

View full text Add to dashboard Cite

show abstract

“…Nevertheless, using an incremental transition approach with a large legacy code base in a large organization, it is possible to adopt a software product line without a large upfront investment and without disrupting ongoing product schedules [18]. Important issues related to software product line engineering are the definition of scope [19], and the consideration of variability and commonalities [20, 21, and 22].…”

Section: Software Product Line Engineeringmentioning

confidence: 99%

“…Challenges related to technical aspects are wrong or incomplete requirements for the platform and wrong platform architecture [26]. In addition, if there is lack of either in architecture focus or architecture talent, an otherwise promising product line effort can be killed [19]. Software product line adoption affects employees' roles and responsibilities.…”

Section: Software Product Line Adoptionmentioning

confidence: 99%

See 1 more Smart Citation

Software Product Line Adoption – Guidelines from a Case Study

Kuvaja

Similä

Hanhela³

2011

Software Engineering Techniques

View full text Add to dashboard Cite

Abstract. It is possible to proceed with software product line adoption only once without major reinvestments and loss of time and money. In the literature, reported experiences of using the adoption models are not to be found, and especially the suitability of the models has not been reported. The purpose of this research is to compare known adoption models by formulating general evaluation criteria for the selection of an adoption model. Next an adoption model is selected for empirical research based on the context of a multimedia unit of a global telecommunication company. The empirical part consists of a case study analyzing the present state of adoption and producing plans for proceeding with the adoption. The research results can be utilized when selecting an adoption model for an empirical case and adopting a software product line in a software intensive organization.

show abstract

Bibliography

2012

Model‐Driven and Software Product Line Engineering

View full text Add to dashboard Cite

SEI's software product line tenets

Cited by 188 publications

References 5 publications

Analysis of a Small Company for Software Product Line Adoption — An Industrial Case Study

Analysis of a Small Company for Software Product Line Adoption — An Industrial Case Study

Software Product Line Adoption – Guidelines from a Case Study

Bibliography

Contact Info

Product

Resources

About