The Adoption of Agile Software Methodology with Team Software Process (TSPI) Practices in the Software Engineering Undergraduate Course
DOI:
https://doi.org/10.33736/jita.613.2017Abstract
In computer science, software engineering courses expose the undergraduate students to both the technical and methodological aspects of software development. The traditional software development methods and techniques represent a huge proportion of the courses and hence contribute an essential part of software engineering students’ development process. This plan-driven development is dependent on a set of predefined phases and ongoing documentation which found to be problematic; such as time-consuming, slipped requirements and complicated processes. The main aim of this paper is to study and review the adoption of Agile Software Methodology and Team Software Process (TSPi) practices in the undergraduate course focus on software development. The framework and course plan will be designed to apply and observe the implementation. Furthermore, this study will help to gather the teams’ viewpoint regarding the importance of Agile and TSPi practices in handling small projects with real clients.
References
Abdulwahab, L., Abdalla, A. A., Galadanci, B. S., Algudah, M., & Murtala, M. (2015). Agile Methods for Software Engineering Students Project : A Proposed Hybrid Methodology. In Proceedings of The Third International Conference on Digital Enterprise and Information Systems (pp. 63-69). Shenzhen, China.
Cannon, R., Hilburn, T. B., & Diaz-Herrera, J. (2002). Teaching a Software Project Course Using the Team Software Process. Proceedings of the 33rd SIGCSE Technical Symposium on Computer Science Education, (March), 369-370.
https://doi.org/10.1145/563340.563486
Chick, T. A., Cannon, R., McHale, J., Nichols, W., Pomeroy-Huff, M., Welch, J., & Willett, A. (2009). Team Software Process (TSP) Coach Mentoring Program Guidebook. Sei.Cmu.Edu, (August).
https://doi.org/10.21236/ADA512361
Com, V. (2015). 9th Anual State of Agile Survey.
Deemer, P., Benefield, G., Larman, C., & Vodde, B. (2012). A Lightweight Guide to the Theory and Practice of Scrum Version 2.0. InfoQ.
Despa, M. (2014). Comparative study on software development methodologies. Database Systems Journal, 5(3), 37-56. Retrieved from http://dbjournal.ro/archive/17/17_4.pdf
Fowler, M., & Highsmith, J. (2001). The agile manifesto. Software Development, 9(August), 28-35.
Humphrey, W. S. (2000). Introduction to the Team Software Process. Reading, Massachusetts.: Addison Wesley.
https://doi.org/10.21236/ADA386941
Kruchten, P. (2003). The Rational Unified Process An Introduction (3rd ed.). Addison-Wesley Professional.
Larman, C. (2002). Applying UML and Patterns - An Introduction to OO Analysis and Design and the Unified Process, 736.
Mahni, V. (2015). Scrum in software engineering courses: An outline of the literature. Global Journal of Engineering Education, 17(2), 77-83.
Moniruzzaman, A. B. M., & Hossain, D. S. A. (2013). Comparative Study on Agile software development methodologies. arXiv Preprint arXiv:1307.3356.
Over, J. W. (2000). Instructor 's Guide for Introduction to the Team Software Process. Retrieved from
http://www.uml.org.cn/softwareprocess/pdf/tspi.pdf
PricewaterhouseCoopers. (2014). Adopting an Agile methodology: Requirements - gathering and delivery.
Qureshi, M. R. J., Alshamat, S. A., & Sabir, F. (2014). Significance of The Teamwork in Agile Software Engineering. Sci.Int.(Lahore), 26(1), 117-120.
Reichlmayr, T. (2003). The Agile Approach In An Undergraduate Software Engineering Course Project. ASEE/IEEE Frontiers in Education.
https://doi.org/10.1109/FIE.2003.1265946
Stewart, J. R., & Agah, A. (2012). Teaching a software engineering course on developing video games : a Unified Process versus Extreme Programming, 10(1), 6-12.
Sureshchandra, K., & Shrinivasavadhani, J. (2008). Moving from waterfall to agile. In Proceedings - Agile 2008 Conference (pp. 97-101).
https://doi.org/10.1109/Agile.2008.49
Werner, L., Arcamone, D., & Ross, B. (2012). Using Scrum In A Quarter-Length Undergraduate Software Engineering Course. In Consortium for Computing Sciences in Colleges (pp. 140-150).
Zorzo, S. D., De Ponte, L., & Lucrédio, D. (2013). Using scrum to teach software engineering: A case study. Proceedings - Frontiers in Education Conference, FIE, 455-461.
Downloads
Published
How to Cite
Issue
Section
License
Copyright Transfer Statement for Journal
1) In signing this statement, the author(s) grant UNIMAS Publisher an exclusive license to publish their original research papers. The author(s) also grant UNIMAS Publisher permission to reproduce, recreate, translate, extract or summarize, and to distribute and display in any forms, formats, and media. The author(s) can reuse their papers in their future printed work without first requiring permission from UNIMAS Publisher, provided that the author(s) acknowledge and reference publication in the Journal.
2) For open access articles, the author(s) agree that their articles published under UNIMAS Publisher are distributed under the terms of the CC-BY-NC-SA (Creative Commons Attribution-Non Commercial-Share Alike 4.0 International License) which permits unrestricted use, distribution, and reproduction in any medium, for non-commercial purposes, provided the original work of the author(s) is properly cited.
3) For subscription articles, the author(s) agree that UNIMAS Publisher holds copyright, or an exclusive license to publish. Readers or users may view, download, print, and copy the content, for academic purposes, subject to the following conditions of use: (a) any reuse of materials is subject to permission from UNIMAS Publisher; (b) archived materials may only be used for academic research; (c) archived materials may not be used for commercial purposes, which include but not limited to monetary compensation by means of sale, resale, license, transfer of copyright, loan, etc.; and (d) archived materials may not be re-published in any part, either in print or online.
4) The author(s) is/are responsible to ensure his or her or their submitted work is original and does not infringe any existing copyright, trademark, patent, statutory right, or propriety right of others. Corresponding author(s) has (have) obtained permission from all co-authors prior to submission to the journal. Upon submission of the manuscript, the author(s) agree that no similar work has been or will be submitted or published elsewhere in any language. If submitted manuscript includes materials from others, the authors have obtained the permission from the copyright owners.
5) In signing this statement, the author(s) declare(s) that the researches in which they have conducted are in compliance with the current laws of the respective country and UNIMAS Journal Publication Ethics Policy. Any experimentation or research involving human or the use of animal samples must obtain approval from Human or Animal Ethics Committee in their respective institutions. The author(s) agree and understand that UNIMAS Publisher is not responsible for any compensational claims or failure caused by the author(s) in fulfilling the above-mentioned requirements. The author(s) must accept the responsibility for releasing their materials upon request by Chief Editor or UNIMAS Publisher.
6) The author(s) should have participated sufficiently in the work and ensured the appropriateness of the content of the article. The author(s) should also agree that he or she has no commercial attachments (e.g. patent or license arrangement, equity interest, consultancies, etc.) that might pose any conflict of interest with the submitted manuscript. The author(s) also agree to make any relevant materials and data available upon request by the editor or UNIMAS Publisher.
