2009 22nd Conference on Software Engineering Education and Training 2009
DOI: 10.1109/cseet.2009.42
|View full text |Cite
|
Sign up to set email alerts
|

Designing a Multi-disciplinary Software Engineering Project

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2011
2011
2022
2022

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…The multidisciplinary nature of social software development renders the offering of undergraduate university courses somewhat challenging [34]. As stated in the calls for papers in this HICSS-52 invited track on software engineering education and training, the educational offerings are frequently advanced through the development of reference syllabi on the academic side and practitioner initiatives focused on industry-based trainings on the professional side.…”
Section: Need For a Socialification Coursementioning
confidence: 99%
See 1 more Smart Citation
“…The multidisciplinary nature of social software development renders the offering of undergraduate university courses somewhat challenging [34]. As stated in the calls for papers in this HICSS-52 invited track on software engineering education and training, the educational offerings are frequently advanced through the development of reference syllabi on the academic side and practitioner initiatives focused on industry-based trainings on the professional side.…”
Section: Need For a Socialification Coursementioning
confidence: 99%
“…Designing interdisciplinary courses which include a technical, social, and business component requires specific planning and consideration [34]. For example, both technical and non-technical students may be interested.…”
Section: Current State and Challengesmentioning
confidence: 99%
“…Two papers use psychological approach to obtain requirements from users. The two approaches have been identified as Activity Theory and small group theory respectively [11]- [16] whereby 2 papers have mentioned prototype as the way to get the requirements from their domain [9], [11], [15]- [16]. Regardless of various elicitation techniques, a traditional technique such as interview [5]- [7] is still being implemented in order to gain requirements from user and there is also a participatory approach from expert as well as users [13]- [14] in CSCW development.…”
Section: B Requirements Elicitation Techniquementioning
confidence: 99%