Parallel Software Engineering Student Projects
Juha Taina, Kimmo Simola
Abstract
Juha Taina, Kimmo Simola
Abstract
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 students form a team. Each team has an assigned customer who needs a software product. Next to traditional one-team projects, we have parallel team projects where several 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 projects, the resulting software has been unique enough for various comparisons. In this paper, we summarize our experiences with parallel teams and draw conclusions of their advantages and disadvantages.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
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 students form a team. Each team has an assigned customer who needs a software product. Next to traditional one-team projects, we have parallel team projects where several 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 projects, the resulting software has been unique enough for various comparisons. In this paper, we summarize our experiences with parallel teams and draw conclusions of their advantages and disadvantages.
Key concepts: Team software process, Scope (computer science), Software engineering, Software project management, Personal software process, Software development, Engineering management, Social software engineering