Requirement Engineering and Software Product Line Scoping Paradigm

Authors: Ahmed Mateen, Zhu Qingsheng, Faisal Shahzad

Abstract:

Requirement Engineering (RE) is a part being created for programming structure during the software development lifecycle. Software product line development is a new topic area within the domain of software engineering. It also plays important role in decision making and it is ultimately helpful in rising business environment for productive programming headway. Decisions are central to engineering processes and they hold them together. It is argued that better decisions will lead to better engineering. To achieve better decisions requires that they are understood in detail. In order to address the issues, companies are moving towards Software Product Line Engineering (SPLE) which helps in providing large varieties of products with minimum development effort and cost. This paper proposed a new framework for software product line and compared with other models. The results can help to understand the needs in SPL testing, by identifying points that still require additional investigation. In our future scenario, we will combine this model in a controlled environment with industrial SPL projects which will be the new horizon for SPL process management testing strategies.

Keywords: Requirements engineering, software product lines, scoping, process structure, domain specific language.

Digital Object Identifier (DOI): doi.org/10.5281/zenodo.1316830

References:

[1] Y. Alsultanny, and A. M. Wohaishi “Requirements of Software Quality Assurance Model. Second International Conference on Environmental and Computer Science” 2009 pp. 23.
[2] J. Bayer, O. Flege, P. Knauber, R. Laqua, D. Muthig, K. Schmid, T. Wide, and J. M. DeBaud, methodology to develop software product lines, in: Proceedings of the 5th ACM SIGSOFT Symposium on Software Reusability, 2011 pp. 122–131.
[3] J. Bosch, and P. M. Bosch-Sijtsema “Introducing agile customer-centered development in a legacy software product line”. Software: Practice and Experience, 2011 41(8), 871–882.
[4] J. Erickson, and K. Siau. “Theoretical and Practical complexity of modeling methods,” in ACM Communications, vol. 50, 2007 pp. 46-51.
[5] T. Gorschek, A. Gomes., A. Pettersson, and R. Torkar, Introduction of a process maturity model for marketdriven product management and requirements engineering. Journal of Software: Evolution and Process, 2012 24(1), 83–113.
[6] I. Inayat, L. Moraes, M. Daneva, and Salim, S. S. “A Reflection on Agile Requirements Engineering”: Solutions Brought and Challenges Posed. Scientific Workshop Proceedings of the XP2015, Trondheim, 2015p. 6.
[7] S. Lim, and A. Finkelstein Stake Rare: Using Social Networks and Collaborative Filtering for Large-Scale Requirements Elicitation. IEEE Transactions on Software Engineering, 2012 38(3), 707–735.
[8] I García, Pacheco C, Mendoza E, Calvo‐Manzano JA, Cuevas G, San Feliu T. Managing the software process with a software process improvement tool in a small enterprise. Journal of Software: Evolution and Process. 2012 24(5): 481-91.
[9] L. Antovski and F. Imeri. “Review of Software Reuse Processes” International Journal of Computer Science Issues 2013 volume 10, 6(2), 83-88.
[10] B. B. Morales, S. Crespo and Clifton C. “Reuse of Use Cases Diagrams: An Approach based on Ontologies and Semantic Web Technologies” International Journal of Computer Science Issues 2012 volume 9, 1(2),24-29.
[11] K. Wnuk, D. Callele, E.-A. Karlsson, and B. Regnell, Controlling Lost Opportunity Costs in Agile Development–The Basic Lost Opportunity Estimation Model for Requirements Scoping, in Software Business, Springer, 2012 pp. 255–260.
[12] http://www.biglever.com, The Software Product Line (SPL) Lifecycle Framework: Overview of the framework', 2017. (Online). Available: http://www.biglever.com/newsletters/SPL_Lifecycle_Part_2.html. (Accessed: 13- Dec- 2017).
[13] http://www.methodsandtools.com, Software Product Line Engineering with Feature Models’ 2017. (Online). http://www.methodsandtools.com/archive/archive.php?id=49. (Accessed: 13- Dec- 2017).
[14] Yang, J. Hu, Y. Q. Wang, G. Ruhe, and H. Wang ―Value-based portfolio scoping: an industrial case study, ‖ in Proceedings of the Third International Workshop on Product LinE Approaches in Software Engineering, 2012 pp. 45–48.
[15] K. Pohl, The three dimensions of requirements engineering. In Seminal Contributions to Information Systems Engineering 2013 pp. 63–80.
[16] Linden, F. van der, J. Bosch, E. Kamsties, K. Kansala and H. Obbink, Software product family evaluation, in: Proceedings of the 3rd International Conference on Software Product Lines 2014 pp. 110–129.
[17] M. Khurum, N. Uppalapati, and R. C. Veeramachaneni,.―”Software requirements triage and selection: state-of-the-art and state-of-practice”, ‖ in Software Engineering Conference (APSEC), 2012 19th Asia-Pacific, vol. 1, 2012 pp. 416–421.
[18] F. S. N, Danuza. A requirements engineering process for software product lines, Universidade Federalde Pernambuco Centrode Informática 2009.
[19] D. F. S. Neiva, A requirements engineering process for software product lines, MSc Dissertation, Page 51 august 2009.