Introduction to Lean Canvas Transformation Models and Metrics in Software Testing

Padmaraj Nidagundi 1  and Leonids Novickis 2
  • 1 IITMinds, India
  • 2 Riga Technical University, Latvia

Abstract

Software plays a key role nowadays in all fields, from simple up to cutting-edge technologies and most of technology devices now work on software. Software development verification and validation have become very important to produce the high quality software according to business stakeholder requirements. Different software development methodologies have given a new dimension for software testing. In traditional waterfall software development software testing has approached the end point and begins with resource planning, a test plan is designed and test criteria are defined for acceptance testing. In this process most of test plan is well documented and it leads towards the time-consuming processes. For the modern software development methodology such as agile where long test processes and documentations are not followed strictly due to small iteration of software development and testing, lean canvas transformation models can be a solution. This paper provides a new dimension to find out the possibilities of adopting the lean transformation models and metrics in the software test plan to simplify the test process for further use of these test metrics on canvas.

If the inline PDF is not rendering correctly, you can download the PDF file here.

  • [1] M. Ide, Y. Amagai, M. Aoyama, Y. Kikushima, “A Lean Design Methodology for Business Models and Its Application to IoT Business Model Development,” in Agile Conference, AGILE, 2015, pp. 107–111. http://dx.doi.org/10.1109/Agile.2015.8

  • [2] R. Korosec, R. Pfarrhofer, “Supporting the Transition to an Agile Test Matrix,” in 2015 IEEE 8th Int. Conf. on Software Testing, Verification and Validation (ICST), 2015, pp. 13–16. http://dx.doi.org/10.1109/ICST.2015.7102632

  • [3] U. Viswanath, “Lean Transformation How Lean Helped to Achieve Quality, Cost and Schedule: Case Study in a Multi Location Product Development Team,” in IEEE 9th Int. Conf. on Global Software Engineering, ICGSE, 2014, pp. 95–99. http://dx.doi.org/10.1109/ICGSE.2014.13

  • [4] A. C. Barus, D. I. P. Hutasoit, J. H. Siringoringo, Y. A. Siahaan, “White box testing tool prototype development,” in 2015 Int. Conf. Electrical Engineering and Informatics, ICEEI, 2015, pp. 417–422. http://dx.doi.org/10.1109/ICEEI.2015.7352537

  • [5] K. M. Mustafa, R. E. Al-Qutaish, M. I. Muhairat, “Classification of Software Testing Tools Based on the Software Testing Methods,” in Second Int. Conf. on Computer and Electrical Engineering, ICCEE '09, 2009, pp. 229–233. http://dx.doi.org/10.1109/ICCEE.2009.9

  • [6] Z. W. Hui, R. Chen, S. Huang, B. Hu, “GUI regression testing based on function-diagram,” in 2010 IEEE Int. Conf. on Intelligent Computing and Intelligent Systems, ICIS, 2010, pp. 559–563. http://dx.doi.org/10.1109/ICICISYS.2010.5658394

  • [7] C. Rankin, “The Software Testing Automation Framework,” IBM Systems J., vol. 41, 2002, pp. 126. http://dx.doi.org/10.1147/sj.411.0126

  • [8] N. P. Singh, R. Mishra, M. K. Debbarma, S. Sachan, “The review: Lifecycle of object-oriented software testing,” in 2011 3rd Int. Conf. Electronics Computer Technology, ICECT, 2011, pp. 52–56. http://dx.doi.org/10.1109/icectech.2011.5941799

  • [9] D. Jeffrey, N. Gupta, “Test Case Prioritization Using Relevant Slices,” in 30th Annu. Int. Computer Software and Applications Conf., COMPSAC'06, 2006, vol. 1, pp. 411–420. http://dx.doi.org/10.1109/COMPSAC.2006.80

  • [10] G. Abu, L. Chacko, J. W. Cangussu, “Software test process control: status and future directions,” in Proc. of the 28th Annu. Int. Computer Software and Applications Conf., COMPSAC, 2004, pp. 160–163. http://dx.doi.org/10.1109/CMPSAC.2004.1342701

  • [11] I. Burnstein, T. Suwanassart, R. Carlson, “Developing a Testing Maturity Model for software test process evaluation and improvement,” in Proc. Int. Test Conf., 1996, pp. 581–589. http://dx.doi.org/10.1109/TEST.1996.557106

  • [12] J. Kasurinen, “Elaborating Software Test Processes and Strategies,” in 2010 Third Int. Conf. on Software Testing, Verification and Validation, 2010, pp. 355–358. http://dx.doi.org/10.1109/ICST.2010.25

  • [13] P. Klindee, N. Prompoon, “Test cases prioritization for software regression testing using analytic hierarchy process,” in 2015 12th Int. Joint Conf. on Computer Science and Software Engineering, JCSSE, 2015, pp. 168–173. http://dx.doi.org/10.1109/jcsse.2015.7219790

  • [14] L. Xue-Mei, G. Guochang, L. Yong-Po W. Ji, “Research and Implementation of Knowledge Management Methods in Software Testing Process,” in 2009 WRI World Congress on Computer Science and Information Engineering, vol. 7, 2009, pp. 739–743. http://dx.doi.org/10.1109/CSIE.2009.360

  • [15] S. Raman, “Lean software development: is it feasible?,” in The AIAA/IEEE/SAE Digital Avionics Systems Conference, 1998, pp. C13/1–C13/8. http://dx.doi.org/10.1109/dasc.1998.741480

  • [16] K. Ghane, “A model and system for applying Lean Six sigma to agile software development using hybrid simulation,” in 2014 IEEE Int. Technology Management Conf., ITMC, 2014, pp. 1–4. http://dx.doi.org/10.1109/itmc.2014.6918594

  • [17] J. Trimble, C. Webster, “From Traditional, to Lean, to Agile Development: Finding the Optimal Software Engineering Cycle,” in 2013 46th Hawaii Int. Conf. System Sciences, HICSS, 2013, pp. 4826–4833. http://dx.doi.org/10.1109/hicss.2013.237

  • [18] C. A. Cois, J. Yankel, A. Connell, “Modern DevOps: Optimizing software development through effective system interactions,” in 2014 IEEE Int. Professional Communication Conf., IPCC, 2014, pp. 1–7. http://dx.doi.org/10.1109/ipcc.2014.7020388

OPEN ACCESS

Journal + Issues

Search