Scientific and Technical Journal


ISSN Print 2221-3937
ISSN Online 2221-3805

The conducted studies of the influence of information in the software requirements specification (SRS) on the success of the software project implementation and the analysis of failures of interaction between the components of the software systems have shown that factors of the quality and success of modern software systems are less dependent on the coding, but essentially depend on the formation and formulation of requirements and on the software architecture design. Under such circumstances, it is actual and very important to analyze the SRS, to "cut" software projects with incomplete (with insufficient information) specification. The research of the emergent properties as a consequence of insufficiency of information in the SRS showed that the emergent properties are such properties of the software system, which appear randomly and manifest in the process of functioning of the software in the interaction of subsystems through interfaces and in the presence of certain data and external influences. Emergent properties of software are part of its knowledge gap. Nowadays, the emergence and manifestation of emergent properties are random and unpredictable both for software developers and for software users. But exactly the reduction of the number of the emergent properties of the software will provide the increase of its quality and success of implementation. The analysis of the approaches to detecting the emergent properties has shown the lack of the effective practical approach to identifying the software's emergent properties and the need to develop methods and technologies for detecting, evaluating and predicting the software's emergent properties. Therefore, the prospect for further research of the author is the development of the methods and technologies for detecting, evaluating and predicting the software's emergent properties, which will be based on the consideration of the subject domain information during the software life cycle.

  1. Dorofee, A., Woody, C., Alberts, C., Creel,          R. and Ellison, R. J. (2011), “A Systemic approach for assessing software supply-chain risk”, Proceedings of The 44-th Hawaii International Conference on System Sciences, January 04-07, 2011, Honolulu (USA), 2011, pp. 1–8.
  2. Ghadge, A., Dani, S., Chester, M. and Kalawsky R. (2013), “A systems approach for modelling supply chain risks”, Supply Chain Management: An International Journal, Vol. 18 (5), pp. 523–538.
  3. Pomorova, O. and Hovorushchenko, T. (2015), “The way to detection of software emergent properties”, Proceedings of The 8-th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems, September 24-26, 2015, Vol. 2, Warsaw, pp. 779–784.
  4. Hastie, S.and Wojewoda S. (2015), “Standish Group 2015 Chaos Report – Q&A with Jennifer Lynch”, available at:
  5. Speed&Function (2017), “A Look at 25 Years of Software Projects. What Can We Learn?”, available at:
  6. Maedche, A., Botzenhardt, A., and Neer, L. (2012), Software for people: fundamentals, trends and best practices (Management for professionals), Springer-Verlag Berlin Heidelberg, Berlin.
  7. Futrell, R. T., Shafer, D. F., Shafer, L. I. (2002), Quality Software Project Management, Prentice Hall, Hoboken (USA).
  8. Sommerville, I. (2015), Software Engineering, Pearson, London.
  9. Vendrov, A. M. (2006), Designing the Software for Economic Information Systems: Tutorial [Proektirovanie programmnogo obespecheniya ekonomicheskih informatsionnih sistem], Finance and Statistics, Moscow.
  10. McConnell, S. (2013), Code complete, Microsoft Press, Redmond.
  11. Jones, C. and Bonsignour, O. (2012), The economics of software quality, Pearson Education, Boston.
  12. ISO/IEC/IEEE 29148:2011, Systems and software engineering. Life cycle processes. Requirements engineering.
  13. Levenson, N. G. (2012), Engineering a safer world: systems thinking applied to safety, MIT Press, Massachusets.
  14. Levenson, N. G. (2001), “Systemic factors in software-related spacecraft accidents”, Proceedings of AIAA Space 2001 Conference and Exposition, August 28-30, 2001. Albuquerque (USA), pp. 1–11.
  15. Levenson, N. (2009), “Software challenges in achieving space safety”, Journal of the British Interplanetary Society, Vol. 62, pp. 265–272.
  16. Ishimatsu, T., Levenson, N. G., Thomas, J. P., Fleming, C. H., Katahira, M., Miyamoto, Yu., Ujiie, R., Nakao, H. and Hoshino, N. (2014), “Hazard analysis of complex spacecraft using systems-theoretic process analysis”, Journal of Spacecraft and Rockets, Vol. 51 No. 2, pp. 509–522.
  17. Hovorushchenko, T. (2015), “The software emergent properties and them reflection in the non-functional requirements and quality models”, Proceedings of 10-th International Conference on Computer Science and Information Technologies, September 14-17, 2015, Lviv (Ukraine), pp. 146–153.
  18. Munch, J. and Schmid, K. (2013), Perspectives on the future of software engineering, Springer-Verlag Berlin Heidelberg, Berlin.
  19. Diaz, V. G., Lovelle, J. M. and Garcia-Bustelo B. C. (2015), Handbook of research on innovations in systems and software engineering, IGI Global,Hershey (USA).
  20. Maier, R. (2013), Knowledge management systems. Information and communication technologies for knowledge management, Springer Science & Business Media, Berlin.
  21. Patterson, Jr. F. G. (2004), “Life cycles for system acquisition”, Encyclopedia of Life Support Systems, Systems Engineering and Management for Sustainable Development, pp. 82–110.
  22. Popov, V. P and Kraynuchenko, I. V. (2003), Global Evolutionism and Synergy of the Noosphere [Globalnyi evolutsionism i sinergetika noosfery], Publishing House APMS NCSCHS, Rostov-na-Donu (Russia).
  23. Hubler, A. (2016), “System under large stress: prediction and management of catastrophic failures”, Complexity, Vol. 21, Issue 3, pp. 9–12.
  24. Lutsenko, E. V. (2008), “Existence, non-existence and change as the emergent properties of systems” [Sushchestvovanie, nesushchestvovanie i izmenenie kak emerdjentnye svoistva sistem], Quantum magic, Vol. 5, Issue 1, pp. 1215–1239.
  25. Fisher, D. A. (2006), “An emergent perspective on interoperation in systems of systems”, TECHNICAL REPORT CMU/SEI-2006-TR-003, 67 p.
  26. ISO/IEC TR 19759:2015, Software Engineering. Guide to the software engineering body of knowledge (SWEBOK).
  27. Kaisler, S. and Madey, G. (2009), “Complex adaptive systems: emergence and self-organization”, available at:
  28. Marsh, G. E. (2009), “The demystification of emergent behavior”, available at:
  29. Johnson, Ch. W. (2006), “What are emergent properties and how do they affect the engineering of complex systems?” Complexity in Design and Engineering, Vol. 91, Issue 12, pp. 1475–1481.
  30. Hsu, J. C. and Butterfield, M. (2007), “Modeling emergent behavior for systems-of-systems”, Proceedings of INCOSE International Symposium, June 24-28, 2007, Vol. 17, Issue 1. San Diego (USA), pp. 1811–1821.
  31. Allison, I. and Merali, Y. (2007), “Software process improvement as emergent change: a structurational analysis”, Journal Information and Software Technology, Vol. 49, Issue 6, pp. 668–681.
  32. Szabo, C. and Teo, Y. M. (2013), “Semantic validation of emergent properties in component-based simulation models”, Ontology, Epistemology, & Teleology for Modelling & Simulation : Philosophical Foundations for Intelligent M&S Applications (edited by Tolk A.), pp. 319–333.
  33. Kashfi, P., Feldt, R., Nilsson, A. and Berntsson Svensson, R. (2014), “Models for integrating UX into software engineering practice: an industrial validation”, Proceedings of The 6th International Working Conference on Human-Centred Software Engineering, September 16-18, 2014, Paderborn (Germany), pp. 259–266.
  34. Mogul, J. C. (2006), “Emergent (mis)behavior vs. complex software systems”, ACM SIGOPS Operating Systems Review, Vol. 40, No. 4, pp. 293–304.
  35. Dyson, G. B. (2012), Darwin among the machines: the evolution of global intelligence, Basic Books, New York.
  36. Rouff, C., Hinchey, M., Truszkowski, W., Vanderbilt, A. and Rash, J. (2004), “Properties of a formal method for prediction of emergent behaviours in swarm-based systems”, Proceedings of The 2-nd International Conference on Software Engineering and Formal Methods, September 28-30, 2004, Beijing (China), pp. 24–33.
  37. Guillerm, R. Demmou, H. and Sadou, N. (2012), “Safety evaluation and management of complex systems: A system engineering approach”, Concurrent Engineering: Research and Applications, Vol. 20 (2), pp. 149–159.
  38. Larsson, M. (2004), Predicting quality attributes in component-based software systems, Västerås.
  39. Pizzi, N. J. (2011), “Mapping software metrics to module complexity: a pattern classification approach”, Journal of Software Engineering and Applications, Vol. 4, pp. 426–432.
  40. Johnson, St. (2002), Essay emergence: the connected lives of ants, brains, cities, and software emergence, Scribner, New York.
  41. Alexander, R. T. and Bieman J. M. (2002), “Challenges of aspect-oriented technology”, Proceedings of Workshop on Software Quality of the 34-th International Conference on Software Engineering, May 25, 2002, Orlando, Florida (USA), pp. 1–3.
  42. Niebuhr, D. Peper, C. and Rausch, A. (2004), “Towards a developement approach for dynamic-integrative systems”, Proceedings of Workshop on Building Software for Pervasive Computing of the 19-th Conference on Object-Oriented Programming Systems, Languages and Applications, October 25, 2004, Vancouver (Canada), pp. 134–139.
  43. Niebuhr, D., Peper, C. and Rausch, A. (2005), “Towards reliable self-integrative IT systems”, Proceedings of The 10-th International Workshop on Component-Oriented Programming, July 25, 2005, Glasgow (Scotland), pp. 98–102.
     44. Vyatkin, V. (2013), “Software engineering in industrial automation: State of the art Review”, IEEE Transactions on Industrial Informatics, Vol. 9, No. 3, pp. 1234–1249
Last download:
14 Feb 2019

[ © KarelWintersky ] [ All articles ] [ All authors ]
[ © Odessa National Polytechnic University, 2014-2018. Any use of information from the site is possible only under the condition that the source link! ]