Software Process simulation

Software Process simulation modelling: Like any simulation, software process simulation (SPS) is the numerical evaluation of a mathematical model that imitates the behavior of the software development process being modeled. SPS has the ability to model the dynamic nature of software development and handle the uncertainty and randomness inherent in it.[1]

Uses of software process simulation

Following main purposes have been proposed for SPS:[2]

How to do software process simulation

Software process simulation starts with identifying a question that we want to answer. The question could be, for example, related to assessment of an alternative, incorporating a new practice in the software development process. Introducing such changes in the actual development process will be expensive and if the consequences of change are not positive the implications can be dire for the organization. Thus, through the use of simulation we attempt to get an initial assessment of such changes on the model instead of an active development project. Based on this problem description an appropriate scope of the process is chosen. A simulation approach is chosen to model the development process. Such a model is then calibrated using empirical data and then used to conduct simulation based investigations. A detailed description of each step in general can be found in Balci's work,[5] and in particular for software process simulation a comprehensive overview can be found in Ali et al.[6]

Examples of using software process simulation for practical issues in industrial settings

Key venues

Software process simulation has been an active research area for many decades some of the key venues include the International Conference on Software and Systems Process[9] and its predecessor Workshop on Software Process Simulation Modeling (ProSim) from 1998-2004.[10]

References

  1. Ali, NB; Petersen, K; Wohlin, C. "A Systematic Literature Review on the Industrial Use of Software Process Simulation". Journal of Systems and Software. 97: 65–85. doi:10.1016/j.jss.2014.06.059.
  2. Kellner, Marc I; Madachy, Raymond J; Raffo, David M. "Software process simulation modeling: Why? What? How?". Journal of Systems and Software. 46 (2–3): 91–105. doi:10.1016/s0164-1212(99)00003-5.
  3. "Use of simulation for software process education: a case study" (PDF).
  4. von Wangenheim, C.G.; Shull, F. "To Game or Not to Game?". IEEE Software. 26: 92–94. doi:10.1109/MS.2009.54.
  5. Osman Balci (2012), "A Life Cycle for Modeling and Simulation," Simulation: Transactions of the Society for Modeling and Simulation International 88, 7, 870–883.
  6. Ali, N.B.; Petersen, K., "A Consolidated Process for Software Process Simulation: State of the Art and Industry Experience," Software Engineering and Advanced Applications (SEAA), 2012 38th EUROMICRO Conference on , vol., no., pp.327,336, 5-8 Sept. 2012 doi: 10.1109/SEAA.2012.69 http://www.bth.se/fou/forskinfo.nsf/0/7e2b9e104c9956cec1257acf006a1282/$file/Consolidated%20process.pdf
  7. Ali, NB; Petersen, K; de França, BBN. "Evaluation of simulation-assisted value stream mapping for software product development: Two industrial cases". Information and Software Technology. 68: 45–61. doi:10.1016/j.infsof.2015.08.005.
  8. Garousi, Vahid; Pfahl, Dietmar (2015). "When to automate software testing? A decision‐support approach based on process simulation". Journal of Software: Evolution and Process.
  9. http://www.icsp-conferences.org/icssp2015/
  10. http://www.verlag.fraunhofer.de/bookshop/artikel.jsp?v=220684
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.