2005
DOI: 10.1145/1047124.1047513
|View full text |Cite
|
Sign up to set email alerts
|

Intra-curriculum software engineering education

Abstract: We have been funded by the National Science Foundation to investigate the feasibility of distributing large software engineering projects across the academic curriculum (DUE 0127439). This paper reports on the pedagogical aspects of the intra-curriculum methodology we have developed including motivation, goals, instructor responsibilities, and variations of the approach. The paper also reports on three applications of the methodology including lessons learned.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
6
0

Year Published

2008
2008
2017
2017

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 6 publications
0
6
0
Order By: Relevance
“…The sophomore students work closely with the senior project teams to produce realistic schedules and estimates for cost/effort for the senior teams to use (instead of toy examples); sophomores review the design models created by the senior team against those produced by the previous yearG teams (providing them with an external, objective review of the design); and sophomores use the code developed by the seniors for reverse engineering exercises (instead of randomly selected code). In other work, (Fenwick 2005) reports on three variations in organizing a project across classes: projects that span the capstone project course and a lower level data structure course; an upper level specialized elective course (HCI); and both the data structure and a junior level (database) course. After trying all three variations, the authors present four lessons learned.…”
Section: Related Workmentioning
confidence: 99%
“…The sophomore students work closely with the senior project teams to produce realistic schedules and estimates for cost/effort for the senior teams to use (instead of toy examples); sophomores review the design models created by the senior team against those produced by the previous yearG teams (providing them with an external, objective review of the design); and sophomores use the code developed by the seniors for reverse engineering exercises (instead of randomly selected code). In other work, (Fenwick 2005) reports on three variations in organizing a project across classes: projects that span the capstone project course and a lower level data structure course; an upper level specialized elective course (HCI); and both the data structure and a junior level (database) course. After trying all three variations, the authors present four lessons learned.…”
Section: Related Workmentioning
confidence: 99%
“…With these observations, instead of looking externally outside the university, many educators search internally for opportunities for collaboration, and design classes with less logistically demanding projects. In the case of Software Engineering (SE) classes, video games [9], or even other CS classes [10], have been used as "real-world contexts" for teaching the involved concepts. A natural continuation of this "internal approach for real-world project" is to explore the possibilities of integrating projects from non-CS classes into an SE class.…”
Section: Introductionmentioning
confidence: 99%
“…It has been noted that there are many potential benefits for such projects coming from within the institution [10,7]. There has been approaches that integrate SE with other CS classes.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…For example, Fenwick et al [6] study the feasibility of distributing large software engineering projects across the academic curriculum, Tvedt et al [12] propose that students from different courses collaborate by taking different roles in a simulated software factory, and Walker and Slotterbeck [13] explore the teaching of large scale teamwork in a small college environment by using multi-semester, multi-course projects that require students to work together in teams. The objectives of Fenwick et al's, Tvedt et al's, and Walker and Slotterbeck's work are broad and related to bringing an entire curriculum closer to real-world software engineering practices whereas the objectives of the work reported in this paper are focused on knowledge and skills particular to software project management.…”
Section: Related Workmentioning
confidence: 99%