Open Access
Parallel Software Engineering Student Projects
Juha Taina,Kimmo Simola +1 more
- 01 Jan 2007
TL;DR: This paper summarizes the experiences with parallel teams of a one-semester software engineering project, and draws conclusions of their advantages and disadvantages.
read more
Abstract: Software engineering education requires a practical course where students can learn processes and practices in a controlled environment. Since software development is usually done in teams, such a course should be a team work course. Due to this, we have a one-semester software engineering project where five to seven st udents form a team. Each team has an assigned customer who needs a software product. Next to traditional one-t eam projects, we have parallel team projects where seve ral teams have the same customer and problem scope. The teams work separately and optimally they do not have any cooperation. Each team has its own product to develop from equal specifications. As a result, the customer gets several products from the same original specification. After three years of parallel projec ts, the resulting software has been unique enough for vario us comparisons. In this paper, we summarize our experiences with parallel teams and draw conclusions of their advantages and disadvantages.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Improving the quality of software engineering education: Benefits and disadvantages of working processes
Kimmo Simola,Marko Ikonen +1 more
- 01 Jan 2008
TL;DR: It was evident that teamwork leads to good planning, probably because all information needs to be communicated to other members, and those students who were eager to report their high work experience, were less capable of developing their personal work process.
1
References
Large team projects in software engineering courses
David Coppit,Jennifer M. Haddox-Schatz +1 more
- 23 Feb 2005
TL;DR: This paper presents an approach to teaching a one-semester software engineering course in which approximately 30 students work together to construct a moderately sized (22 KLOC) software system, without incurring significant managerial overhead for the instructor.
57
Learning software engineering with group work
M.I. Alfonso,F. Mora +1 more
- 20 Mar 2003
TL;DR: This paper describes the experience of teaching a software engineering course based on the use of group work to teaching and practise theoretical concepts to develop a complete software project and underline the importance of documenting software projects effectively.
14
Distributed Cross-Cultural Student Software Project: A Case Study
A. Inkeri Verkamo,J. Taina,Y. Bogoyavlenskiy,Dmitry Korzun,T. Tuohiniemi +4 more
- 18 Apr 2005
TL;DR: In a pilot project of two universities in Finland and in Russia a cross-cultural student team gathered experience by developing a common software product in a distributed project.
13
•Journal Article
A software engineering project that looks like the real world
Andrew Pletch,Aram Agajanian +1 more
TL;DR: This paper describes a Software Engineering class project where real world, production environment concerns and issues are brought to the fore and concerns relating to teachable classroom topics, while present, do not dominate.
5
Hints for Reviewing Empirical Work in Software Engineering
TL;DR: These hints are meant to help with judging empirical work and reduce some of the angst associated with accepting empirical papers.