BazEkon - Biblioteka Główna Uniwersytetu Ekonomicznego w Krakowie

BazEkon home page

Meny główne

Král Jaroslav (Masarykova Univerzita, Brno, Czech Republic), Žemlička Michal (Charles University in Prague)
Experience with Real-Life Students' Projects
Annals of Computer Science and Information Systems, 2014, vol. 2, s. 827 - 833, bibliogr. 19 poz.
Słowa kluczowe
Programowanie komputerów, Proces projektowania
Computer programming, Design process
Student software projects are often focused on training coding skills and on model-driven software system design. The projects rarely develop skills needed for the proper formulation of system visions and requirements specifications. To solve this issue the projects must deal with real-life software projects issues. The projects should solve main commercial aspects of real-life - they must include looking for project topics in practice and there should be possible to communicate and collaborate with future project users. Successful projects should be rewarded (optimally paid) by the users like other commercial products. We discuss here the quite successful experience with a "prototype" implementation of the concept.(original abstract)
Pełny tekst
  1. "Chaos manifesto 2013: Thing big, act small," 2013, [Online:]; accessed 2014-02-28. [Online]. Available:
  2. "Chaos: A recipe for success," 1999, [Online:]; accessed 2014-02-28.
  3. Armour P., "The reorg cycle," Communications of the ACM, vol. 46, pp. 19-22, Feb. 2003, DOI: 10.1145/606272.606288.
  4. Beck K., Extreme Programming Explained: Embrace Change. Boston: Addison Wesley, 1999.
  5. Boehm B. W., "Software engineering economics," 1981.
  6. Brown W. J., Malveau R. C., McCormick H. W. S., III, and T. J. Mowbray, AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis. New York: John Wiley & Sons, 1998.
  7. Calleam Consulting, "Why projects fail," 2014, [Online:]; accessed 2014-02-28. [Online]. Available:
  8. Cohn M., Succeeding With Agile: Software Development Using Scrum. Addison-Wesley Professional, 2009.
  9. Ebert C., "Software product management," Software, IEEE, vol. 31, no. 3, pp. 21-24, May 2014, DOI: 10.1109/MS.2014.72.
  10. Erl T., Service-Oriented Architecture: Concepts, Technology, and Design. Prentice Hall PTR, 2005.
  11. Král J. and Žemlicka M., "Implementation of business processes in service-oriented systems," in 2005 IEEE International Conference on Services Computing (SCC 2005), vol. 2. IEEE Computer Society, 2005, pp. 115-122, DOI: 10.1109/SCC.2005.58.
  12. Levinson M., "Recession causes rising IT project failure rates," CIO Magazine, Jun. 2009. [Online]. Available:
  13. MacKenzie C. M., Laskey K., McCabe F., Brown P. F., and Metz R., "Reference model for service-oriented architecture 1.0, OASIS standard, 12 October 2006," 2006. [Online]. Available:
  14. Martin J., An Information Systems Manifesto. Englewood Cliffs, New Jersey: Prentice-Hall, Inc., 1984.
  15. Open Group, "Open Group standard SOA reference architecture," Nov. 2011. [Online]. Available:
  16. Royce W. W., "Managing the development of large software systems," in IEEE WESCON Proceedings. Institute of Electrical and Electronics Engineers, Aug. 1970, pp. 328-338.
  17. Sommerville I., Software Engineering, 9th ed. Pearson Education, Apr. 2010.
  18. Standish Group, "The chaos report," 1994, [Online:]; accessed 2014-02-28.
  19. Weinberg G. M., The Psychology of Computer Programming. New York: Van Nostrand, 1971.
Cytowane przez
Udostępnij na Facebooku Udostępnij na Twitterze Udostępnij na Google+ Udostępnij na Pinterest Udostępnij na LinkedIn Wyślij znajomemu