1989
DOI: 10.1049/sej.1989.0028
|View full text |Cite
|
Sign up to set email alerts
|

Experiences with group projects in software engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

1993
1993
1999
1999

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(1 citation statement)
references
References 1 publication
0
1
0
Order By: Relevance
“…(Bruegge, 1992, Jacquot et al, 1990, and McMillan & Rajaprabhakaran, 1999, also take this view.) It should be of a nature that ensures that a high-flier cannot complete the project himself (King, 1989), yet there is a danger that, if the problem is too large, the students will abandon software engineering techniques and hack the program together to complete the project (McMillan & Rajaprabhakaran, 1999). • The group should be sufficiently large to ensure that it has to be managed, and have sufficient people to provide an adequate skill base.…”
Section: Rationale For Introducing a Large-scale Group Projectmentioning
confidence: 99%
“…(Bruegge, 1992, Jacquot et al, 1990, and McMillan & Rajaprabhakaran, 1999, also take this view.) It should be of a nature that ensures that a high-flier cannot complete the project himself (King, 1989), yet there is a danger that, if the problem is too large, the students will abandon software engineering techniques and hack the program together to complete the project (McMillan & Rajaprabhakaran, 1999). • The group should be sufficiently large to ensure that it has to be managed, and have sufficient people to provide an adequate skill base.…”
Section: Rationale For Introducing a Large-scale Group Projectmentioning
confidence: 99%