Have a personal or library account? Click to login
Softwareland Chronicles: A Software Development Meta-Process Proposal Cover

Softwareland Chronicles: A Software Development Meta-Process Proposal

Open Access
|May 2016

References

  1. [1] J. Osis and E. Asnina. “Is Modeling a Treatment for the Weakness of Software Engineering?” in Model-Driven Domain Analysis and Software Development: Architectures and Functions. IGI Global, New York, USA, pp. 1–14, 2011. http://dx.doi.org/10.4018/978-1-61692-874-2.ch001
  2. [2] P. Naur and B. Randell, Software engineering: Report of a conference sponsored by the NATO science committee, Scientific Affairs Division, NATO, Garmisch, Germany, November, 1968.
  3. [3] S. McConnell, Rapid Development, Microsoft Press, 1996.
  4. [4] J. Maeda, Las leyes de la simplicidad, Gedisa, 2008.
  5. [5] R. W. Winston, Managing the development of large software systems: IEEE WESCON, July 22–26, 2002, Los Ángeles, USA, 1970.
  6. [6] T. Clancy, “The Extreme Chaos,” Standish Group International Inc., 2012.
  7. [7] R. L. Glass, “The Standish Report: does it really describe a software crisis?” Communications of the ACM, vol. 49, no. 8 pp. 15–15, 2006. http://dx.doi.org/10.1145/1145287.1145301
  8. [8] B. Boehm, “A spiral model of software development and enhancement,” Computer, vol. 21, no. 5, pp. 61–72, 1988. http://dx.doi.org/10.1109/2.59
  9. [9] K. Forsberg and H. Mooz, “The relationship of system engineering to the project cycle,” National Council On System Engineering, vol. 1, no. 1, pp. 57–65, 1981. http://dx.doi.org/10.1002/j.2334-5837.1991.tb01484.x
  10. [10] M. C. Paulk, C. V. Weber, B. Curtis and M. B. Chrissis, The Capability Maturity Model: Guidelines for Improving the Software Process, Addison Wesley, 1994.
  11. [11] P. B. Kruchten, The Rational Unified Process (An Introduction), Addison Wesley, 1999.
  12. [12] U. Donins, J. Osis, A. Slihte, E. Asnina and B. Gulbis. Towards the Refinement of Topological Class Diagram as a Platform Independent Model: ENASE Model-Driven Architecture and Modeling-Driven Software Development, Portugal, pp. 79–88, 2011.10.5220/0003583600790088
  13. [13] J. Osis, E. Asnina and A. Grave, “Computation Independent Representation of the Problem Domain in MDA,” e-Informatica Software Engineering Journal, vol. 2, no. 1, pp. 29–46, 2008.
  14. [14] K. Schwaber, Scrum Development Process: OOPSLA95 Business Object Design and Implementation Workshop, New York, USA. Springer, vol. 6, no. 4, pp. 170–175, 1995.
  15. [15] E. S. Raymond, The Cathedral and the Bazaar, O’Reilly, 199910.5210/fm.v3i2.578
  16. [16] R. L. Glass, “Agile versus traditional: Make love not war,” Cutter IT Journal, vol. 14, no. 2, pp. 12–18, 2001.
  17. [17] M. McCormick, “Technical opinion: Programming extremism,” Communications of the ACM, vol. 44, no. 6, pp. 109–119, 2001. http://dx.doi.org/10.1145/376134.376181
  18. [18] AVOCA-GmbH, “Extreme Programming”, 2012. [Online]. Available: www.avocallc.com/downloads/
  19. [19] H. Saiedian, “Panel: Extreme programming: helpful or harmful?” Proceedings. International Conference on Software Engineering, Washington, USA. IEEE Computer Society, p. 718, 2003. http://dx.doi.org/10.1109/icse.2003.1201258
  20. [20] S. Chatterjee, “The waterfall that won’t go away,” SIGSOFT Software Engineering Notes, vol. 35, no. 1, pp. 9–10, 2010. http://dx.doi.org/10.1145/1668862.1668875
  21. [21] M. Stephens, The Case against Extreme Programming, 2012. [Online]. Available: http://www.softwarereality.com/lifecycle/xp/case_against_xp.jsp
  22. [22] S. R. Rakitin, “Manifesto elicits cynicism,” Computer, vol. 34, pp. 4–7, 2001.
  23. [23] J. Nandhakumar and D. E. Avison, “The fiction of methodological development: a field study of information systems development,” Information Technology & People, vol. 12, pp. 176–191, 1999. http://dx.doi.org/10.1108/09593849910267224
  24. [24] D. Truex, R. Baskerville and J. Travis, “Amethodical systems development: the deferred meaning of systems development methods, Accounting,” Management and Information Technologies, vol. 10, pp. 53–79, 2000. http://dx.doi.org/10.1016/S0959-8022(99)00009-0
  25. [25] W. Hesse, “Dinosaur meets archaeopteryx? or: Is there an alternative for rational unified process?” Software and Systems Modeling, vol. 2, pp. 240–247, 2003. http://dx.doi.org/10.1007/s10270-003-0033-y
  26. [26] D. D. McCracken and M. A. Jackson, “Life cycle concept considered harmful,” SIGSOFT Software Engineering Notes, vol. 7, no. 2, pp. 29–32, 1982. http://dx.doi.org/10.1145/1005937.1005943
  27. [27] C. Andersen, El traje Nuevo del emperador, La galera, 2009.
  28. [28] N. B. Ruparelia, “Software development lifecycle models,” SIGSOFT Software Engineering Notes, vol. 35, no. 3, pp. 8–13, 2010. http://dx.doi.org/10.1145/1764810.1764814
  29. [29] R. Hoda, P. Kruchten, J. Noble and S. Marshall, “Agility in context,” ACM SIGPLAN Notices, vol. 45, no. 10, pp. 74–88, 2010. http://dx.doi.org/10.1145/1932682.1869467
  30. [30] E. A. Abbott, Flatland: A romance of many dimensions, John Wilson and Son, Cambridge, 1885.
  31. [31] L. Wang, “Agility counts in developing small-size software,” IEEE Potentials, vol. 26, no. 6, pp. 16–23, 2007. http://dx.doi.org/10.1109/MPOT.2007.906114
  32. [32] K. Sureshchandra and J. Shrinivasavadhani, “Moving from waterfall to agile,” in Agile Conf., AGILE '08., Toronto, USA, IEEE, 2008, pp. 97–101. http://dx.doi.org/10.1109/agile.2008.49
  33. [33] T. Khne, “Matters of (meta-) modeling,” Software and Systems Modeling, vol. 5, pp. 369–385, 2006. http://dx.doi.org/10.1007/s10270-006-0017-9
  34. [34] R. Zach, “Hilbert’s Program Then and Now”, 2015. [Online]. Available: http://arxiv.org/abs/math/0508572
  35. [35] J. Strick, “Darwinism and the origin of life: The role of H. C. Bastian in the British spontaneous generation debates,” Journal of the History of Biolog, vol. 32, no. 1, pp. 1868–1873, 1999. http://dx.doi.org/10.1023/A:1004460408116
  36. [36] P. Clarke and R. V. O’Connor, “The situational factors that affect the software development process: Towards a comprehensive reference framework,” Information and Software Technology, vol. 54, no. 5, pp. 433–447, 2012. http://dx.doi.org/10.1016/j.infsof.2011.12.003
  37. [37] J. C. Derniame, B. A. Kaba and D. Wastell, Software process: principles, methodology, and technology, Springer-Verlag, 1999.10.1007/BFb0057000
  38. [38] E. Asnina and J. Osis, “Topological Functioning Model as a CIM-Business Model,” in Model-Driven Domain Analysis and Software Development: Architectures and Functions. IGI Global, New York, USA, pp. 40–64, 2011. http://dx.doi.org/10.4018/978-1-61692-874-2.ch003
  39. [39] J. Sanders, “Spice: New directions in software process assessment,” in Proc. of Quality and Productivity in Software Development Conf., University of Iceland, 1970.
  40. [40] M. Suula, T. Makinen and T. Varkoi, “An approach to characterize a software process,” in Int. Conf. on Management of Engineering & Technology, PICMET '09. IEEE, pp. 1003–1109, 2009. http://dx.doi.org/10.1109/picmet.2009.5262007
  41. [41] J. E. Gibson, “Cause and effect analysis: “power tool” for total quality,” Electrical Electronics Insulation Conference and Electrical Manufacturing & Coil Winding Conference, EEIC/ICWA, Chicago, USA, pp. 751–753, 1993. http://dx.doi.org/10.1109/EEIC.1993.631320
  42. [42] E. Asnina and J. Osis, “Computation Independent Models: Bridging Problem and Solution Domains,” in ENASE Model-Driven Architecture and Modeling Theory-Driven Development, Portugal, pp. 23–32, 2010.
  43. [43] F. Woo, R. Mikusauskas, D. Bartlett and R. Law, “A framework for the effective adoption of software development methodologies,” in ACMSE Proc. of the 44th Annual Southeast Regional Conf., New York, USA, ACM, pp. 198–203, 2006. http://dx.doi.org/10.1145/1185448.1185493
  44. [44] E. Germain and P. N. Robillard, “Engineering-based processes and agile methodologies for software development: a comparative case study,” Journal of Systems and Software, vol. 75, no. 1–2, pp. 17–27, 2005. http://dx.doi.org/10.1016/j.jss.2004.02.022
  45. [45] F. Garca, M. Piattini, F. Ruiz, G. Canfora and C. A. Visaggio, “FMESP: Framework for the modeling and evaluation of software processes,” Journal of Systems Architecture, vol. 52, no. 11, pp. 627–639, 2006. http://dx.doi.org/10.1016/j.sysarc.2006.06.007
  46. [46] C. Gonzalez-Perez and B. Henderson-Sellers, “Modelling software development methodologies: A conceptual foundation,” Journal of Systems and Software, vol. 80, no. 11, pp. 1778–1796, 2007. http://dx.doi.org/10.1016/j.jss.2007.02.048
  47. [47] F. Brooks, The Mythical Man – Month, Addison Wesley, 1995.10.1109/MS.1995.10042
  48. [48] S. Dakhli and M. Ben Chouikha, “The knowledge-gap reduction in software engineering,” in Third Int. Conf. on Research Challenges in Information Science, Fez, USA, IEEE, pp. 287–294, 2009. http://dx.doi.org/10.1109/RCIS.2009.5089292
  49. [49] M. Polanyi, The Tacit Dimension, Routledge & Kegan Paul, 1967.
  50. [50] M. Shaw and D. Garlan, Software Architecture, Prentice Hall, 1996.
  51. [51] C. Atkinson and T. Kuhne, “Model-driven development: a metamodeling foundation,” IEEE Software, vol. 20, no. 5, pp. 36–41, 2003. http://dx.doi.org/10.1109/MS.2003.1231149
  52. [52] S. J. Bolaños-Castro, R. Gonzalez-Crespo and V. H. Medina-Garcia, “Antipatterns: A Compendium of Bad Practices in Software Development Processes,” in Int. J. of Interactive Multimedia and Artificial Intelligence, vol. 1, no. 4, pp. 41–46, 2011. http://dx.doi.org/10.9781/ijimai.2011.147
  53. [53] S.J. Bolaños-Castro, R. Gonzalez-Crespo, and V. H. Medina-Garcia, “Patterns of Software Development Process,” Int. J. of Interactive Multimedia and Artificial Intelligence, vol. 1, no. 4, pp. 33–40, 2011. http://dx.doi.org/10.9781/ijimai.2011.146
  54. [54] S. J. Bolaños-Castro, R. Gonzalez-Crespo and V. H. Medina-Garcia, “Patterns of Software Development Process,” IEEE Latin America Transactions, vol. 12, no. 4, pp. 818–824, 2014.10.1109/TLA.2014.6868888
  55. [55] A. Slihte, J. Osis and U. Donins, “Knowledge Integration for Domain Modeling,” in ENASE Model-Driven Architecture and Modeling-Driven Software Development, Portugal, pp. 46–56, 2011.10.5220/0003581200460056
  56. [56] J. Osis and A. Slihte, “Transforming Textual Use Cases to a Computation Independent Model,” in ENASE Model-Driven Architecture and Modeling Theory-Driven Development, Portugal, pp. 33–42, 2010.
  57. [57] J. Osis and U. Donins, “Formalization of the UML Class Diagrams,” Evaluation of Novel Approaches to Software Engineering, Springer-Verlag, Berlin Heidelberg, New York, pp. 180–192, 2010. http://dx.doi.org/10.1007/978-3-642-14819-4_13
DOI: https://doi.org/10.1515/acss-2016-0001 | Journal eISSN: 2255-8691 | Journal ISSN: 2255-8683
Language: English
Page range: 5 - 14
Published on: May 28, 2016
Published by: Riga Technical University
In partnership with: Paradigm Publishing Services
Publication frequency: 1 issue per year

© 2016 Sandro Bolanos, Rubén González Crespo, Jordán Pascual Espada, Vicente García-Díaz, Jānis Osis, published by Riga Technical University
This work is licensed under the Creative Commons Attribution 4.0 License.