In the course I.N.1.1.7.4 - Advanced Seminars in Software Reuse at CIN was achieved a research about current status on Software Product Lines (SPL) Scope, phase of SPL planning, related with the identification of the costs and viability of the product line. For one that is not familiar with the theme this text can be interesting.
The research consisted of a systematic review whose objective was to review the software product lines approaches to identify, compare and summarize evidence about the Scope Definition Techniques. The research questions investigated in this review were related with the identification of the activities, scope types, stakeholders, strengths, drawbacks, and the use of metrics for scoping definition.
With the analysis we identify that metrics definition is the problematic aspect of the approaches, where only the papers of Klaus Schmid, Isabel Jhon and Shin Young Park cite metrics for scoping in its studies. Schmid utilize techniques of business objectives operationalization based in GQM, Jhon define characterization metrics and Park uses metrics of cost to analyze economical value for the core assets.
After of the analysis a idea was questioned, what the viability of relate scope techniques for SPL with agiles development methodologies? and what scope techniques are most appropriate with agiles methodologies?
Subscribe to:
Post Comments (Atom)
10 comments:
Hi, Marcela!
The metrics that you identified in these papers will help in your investigation?
If not, do you have already imagine the idea of creating new metrics?
I thnik that is the way..
Marcela, just for clarifying some ideas... 1) in your study do you consider PL scoping a part of RE or
not?! 2) Could you identify, by performing a Systematic Review, what are the most important gaps to be solved regarding to this research topic, in both academic and industrial point of view!?
Thank u so much!
Hi Marcela,
Just a reminder for you to consider the PLEvo Scoping method in your systematic review. This method is from Karina Vilella (Fraunhofer - IESE) and it concerns scoping activities to help you identify possible changes in the future and prepare for them right from the beginning of the Product line.
Marcela, you said that metrics is a crucial problem is scope deifnition, so when you try to know the scope techniques for SPL with agiles development methodologies, you are also considering the metrics for these tecnhiques? In your review, any approach describe scope in the agile methodoligies context?
Marcela, I think that scope definition is a very difficult task. I believe that only domain experts have the right knowledge to define it. Am I right? What are the roles involved in scoping definition? and Who gives the final word during scoping decisions?
Braga, the metrics ientifieds in the study can yes help, but I imagine the creation of new metrics which complement those that exist
Ivan, in my opinion Scoping is a phase and not a part of RE, but some authors consider of this form. Some gaps were identifieds a is the metrics definition, which few studies have, other is the factor of the approaches do not consider scope optimization, among other.
Thiago, I know the method, but the work was not selected because is fosused in evolution and this is not our focus.
Hernan, the study of the agiles methodologies will be made, therefore the metrics defined in SPl were not analised in the new context. And none of the approaches analysed describe scope in the agile methodoligies context
Flávio in only a of the study identified "A Practical Guide to Product Line Scoping" are defined roles, this are: scoping expert, domain expert and product line manager.
Post a Comment