A Comparison of Software Product Line Traceability Approaches from End-to-End Traceability Perspectives

2014 ◽  
Vol 24 (04) ◽  
pp. 677-714 ◽  
Author(s):  
Jingyu Kim ◽  
Sungwon Kang ◽  
Jihyun Lee
Keyword(s):  
Software Development ◽  
Software Product Line ◽  
Development Project ◽  
Product Line ◽  
Future Research ◽  
Research Directions ◽  
Software Development Project ◽  
Software Traceability ◽  
Software Product ◽  
End To End

Software traceability is the ability to provide trace information on requirements, design, and implementation of a system. It helps stakeholders understand the many associations of software artifacts created during a software development project. End-to-end traceability refers to linkage of all artifacts in the entire lifecycle of a software development project. Its goal is to provide stakeholders of the software development with trace information in order to analyze impacts due to changes in a software system. Compared to that of a single product, the end-to-end traceability of software product line is more complicated because Software Product Line Development (SPLD) requires two separate but intimately related phases of domain engineering and application engineering. Various SPLD traceability approaches have been proposed in the past. However, thus far no research work on SPLD traceability has focused on SPLD end-to-end traceability. This paper defines SPLD end-to-end traceability and evaluates the existing SPLD traceability approaches from SPLD end-to-end traceability perspectives. We surveyed studies on SPLD traceability methods, traceability mechanisms used in major SPLD approaches, and software traceability survey papers. We compared the existing SPLD traceability approaches based on Systematic Literature Review (SLR). Through the survey, we found that none of the SPLD traceability studies fully supports SPLD end-to-end traceability, and there are unexplored research areas of SPLD end-to-end traceability in the existing SPLD traceability studies. The contribution of this paper is that it presents future research directions that give research guidelines for each unexplored research area in SPLD end-to-end traceability. Finally, based on the research directions, this paper suggests future research opportunities for SPLD end-to-end traceability.

scholarly journals El Modelo del Análisis de Precios Unitarios Industrial adaptado a un Proyecto de Desarrollo de Software para un Producto de Informática / The Industrial analysis model of unitary prices adapted to a Software Development Project for a Software Product

2016 ◽  
Vol 4 (8) ◽  
pp. 86
Author(s):  
Cirilo Vega Magaña ◽  
Ivan Steve Vega Herrera
Keyword(s):  
Software Development ◽  
Development Project ◽  
Analysis Model ◽  
Software Development Project ◽  
Software Product

En el presente trabajo se analiza la factibilidad de realizar el cálculo y estimación de costo de un proyecto de personalización de un producto de software empleando técnicas de costeo del Análisis de Precios Unitarios utilizados en Ingeniería Industrial. Se contemplan los ajustes que se tendrían que hacer para poder utilizar el modelo de Análisis de Precios Unitarios, buscando las equivalencias de los conceptos usados en Ingeniería Industrial: maquinaria y equipo, materiales, mano de obra, jornada, etcétera, y aplicados a la ingeniería de software específicamente en proyectos de desarrollo y mantenimiento de software. Mediante un modelo simplificado obtenido a partir del análisis se verifica la viabilidad de usar el modelo de costeo comparándolo con cifras obtenidas a partir de las estimaciones generales que se hacen en informática en el mercado mexicano.

scholarly journals ROI Estimation in a Scrum Project: A case study

10.29007/nqq6 ◽  
2019 ◽  
Author(s):  
Rita Cortés ◽  
Fulvio Lizano
Keyword(s):  
Software Development ◽  
Return On Investment ◽  
Investment Decisions ◽  
Development Project ◽  
Project Managers ◽  
Future Research ◽  
Software Project ◽  
Software Development Project ◽  
Financial Metrics

Financial metrics are necessary to inform decisions about the beginning or continuity of a software development project to justify investments. This research discuses initial ROI (Return on Investment) estimates in a software project using Scrum and how to analyze variations in the initial calculations to make return on investment decisions during partial deliveries of the product. The case study included a survey, a review of documentation, two focus group sessions, and an exercise involving application of the proposed technique. Twenty-four professionals participated, of which 4 were Scrum trainers (17%), 4 were officials of the company where the estimation technique was applied (17%), and 16 were project managers of domestic and foreign software development companies (66%), all of whom had experience in project management. This study provides elements to be considered in future research on ROI calculation in projects using Scrum, and can be used as a guide to estimate and review financial metrics during the execution of an actual project.

scholarly journals TESTING PROCESS OVERVIEW EXPLORATION FOR A SOFTWARE PRODUCT IN A LARGE SOFTWARE DEVELOPMENT PROJECT

2013 ◽  
pp. 100-105
Author(s):  
SRIHARSHA G ◽  
NARESH E
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Test Case ◽  
Test Cases ◽  
Software Development Project ◽  
Root Cause ◽  
Software Product ◽  
Large Software ◽  
Manual Test

Software testing is a process where you have the stated requirements, pre-requisite software that is to be installed and the configuration of the machine that need to be done as per the test data for the test case and for a specific platform which when verified works perfectly. This paper describes about Manual test case process overview in the testing life cycle for a large software development project and how you track the effort for the same. A Tester need to know about the fundamentals of testing concepts. Documentation of the testing concepts and the process overview of the testing life cycle for a software product need to be done initially so that a new tester when recruited can understand the basic flow as to how it is carried out in real time in an organization practically. Initially a tester need to execute the manual test case for few platforms and some tougher manual test cases need to be learnt from the tester who is having some experience. The tougher manual test cases need to be identified initially from the experienced tester who will be giving a session for the execution of such test cases. So when the foundation for a new tester is powerful the plan assigned for the execution of test cases is met. The effort tracking for the testing can be captured for a tester and should be matched with planned effort for the execution of test cases. Measurement of the testing effort plays a very important role as to how comfortable a new tester is and further root cause analysis is done if required when the new tester does not meet the planned effort.

scholarly journals Embedding Quality into Software Product Line Variability Artifacts

2021 ◽  
Vol 12 (3) ◽  
pp. 11-25
Author(s):  
Mworia Daniel ◽  
Nderu Lawrence ◽  
Kimwele Michael
Keyword(s):  
Data Storage ◽  
Analytical Description ◽  
Software Product Line ◽  
Poor Quality ◽  
Development Project ◽  
Product Line ◽  
Functional Requirements ◽  
Functional Quality ◽  
Software Product ◽  
Variability Management

The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

Software Product Lines to Faster Achieving Productivity

2010 ◽  
pp. 121-127
Author(s):  
Sathya Ganeshan ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Asset Management ◽  
Software Product Lines ◽  
Software Product Line ◽  
Product Line ◽  
Product Lines ◽  
Software Product ◽  
Everyday Reality

Software Product Lines have been in the scene of software development since the 1970s. Throughout this time, it has changed from a hot topic that was discussed in universities and seminar halls as future goal of companies, to an everyday reality. There are many crucial aspects that decide the success of a software product line. One among them is the identification, development and maintenance of core assets. This chapter aims at providing a brief introduction to this area of software product lines and ways to improve productivity through efficient core asset management.

scholarly journals A SURVEY ON SOFTWARE PRODUCT-LINE TESTING

2021 ◽  
Vol 9 (01) ◽  
pp. 90-96
Author(s):  
Ayat Yehia Hassan ◽  
Keyword(s):  
System Development ◽  
Evaluation Research ◽  
Software Product Line ◽  
Product Line ◽  
Future Research ◽  
Software Systems ◽  
Development Costs ◽  
Software Product ◽  
Development Processes ◽  
Efficient Software

SPL (Software Product Line) is known as a set of software systems that share a mutual set of features. It is a powerful concept to achieve more efficient software system development. One of the necessary steps in software development processes is Testing. It consumes typically more than 50% of the whole development costs. Testing SPLs is challenging due to the exponential number of products in the number of features. Several approaches have been proposed to reduce the number of products to be tested. However, the testing aspect of SPL is still underdeveloped. This study aims at surveying the latest research on SPL testing to identify useful approaches and needs for future research. seven papers are classified concerning the following: the used Approach, the algorithms, and the type of testing that the research focuses on. The survey found that more validation and evaluation research is required to produce a more robust foundation for SPL testing. Finally, directions for future software product line testing recommendations.

Hybrid Model using Firefly and BBO for Feature Selection in Software Product Line

2020 ◽  
Vol 13 ◽  
Author(s):  
Hitesh Yadav ◽  
Rita Chhikara ◽  
Charan Kumari
Keyword(s):  
Hybrid Model ◽  
High Performance ◽  
Software Product Line ◽  
Product Line ◽  
Feature Model ◽  
Software Systems ◽  
Feature Sets ◽  
Research Article ◽  
Software Product ◽  
Multiple Variants

Background: Software Product Line is the group of multiple software systems which share the similar set of features with multiple variants. Feature model is used to capture and organize features used in different multiple organization. Objective: The objective of this research article is to obtain an optimized subset of features which are capable of providing high performance. Methods: In order to achieve the desired objective, two methods have been proposed. a) An improved objective function which is used to compute the contribution of each feature with weight based methodology. b) A hybrid model is employed to optimize the Software Product Line problem. Results: Feature sets varying in size from 100 to 1000 have been used to compute the performance of the Software Product Line. Conclusion: The results shows that proposed hybrid model outperforms the state of art metaheuristic algorithms.

Sign in / Sign up

Export Citation Format

Share Document