About this paper

Appears in:
Pages: 3258-3265
Publication year: 2009
ISBN: 978-84-612-7578-6
ISSN: 2340-1079

Conference name: 3rd International Technology, Education and Development Conference
Dates: 9-11 March, 2009
Location: Valencia, Spain

SOFTWARE ENGINEERING LABORATORY

N. Stankovic1, I. Paik2

1Xi'an Jiaotong-Liverpool University (CHINA)
2University of Aizu (JAPAN)
Software engineering (SWE) has rapidly evolved into a dominant industry. Yet, the education has often neglected the importance of managerial and organizational aspects, and failed to incorporate them together with technology into a coherent and relevant laboratory project. Over time much has been written on how to organize the SWE laboratory, with arguments flowing for and against additional complexity.

We believe that SWE is a capstone course in any computer science curriculum. Unfortunately, this may still not be widely recognized. The modern course on SWE requires that the student is familiar with many aspects of computing (e.g., networking, Internet technologies, programming languages, databases, HCI, computer graphics, and project management). Depending on the year of academic study these expectations could be unrealistic, especially if that is a 2nd year course.

The theoretical component of any SWE course should be structured and presented such that the student eventually gets comprehensive understanding of the discipline, with technical and nontechnical topics logically and causally interwoven. The practical component (i.e., the laboratory project) should refrain from unnatural simplifications of roles and work products. The student should experience that, at times, solutions are to be found, not prescribed by the book.

The uneven distribution of knowledge or even lack of it must not become an obstacle to the student. However, we should not scale down the curriculum but incorporate, if and when necessary, additional elements that will allow all students to make a uniform progress. SWE is a complex discipline that primarily aims at answering the question of how to build SW systems. But, it must also be decided what tools to use, learned how to select tools and technologies, and their character and impact must be understood.

This problem is far-reaching, and should be dealt with accordingly. In this paper, we elaborate on our ideas to address these issues.
@InProceedings{STANKOVIC2009SOF,
author = {Stankovic, N. and Paik, I.},
title = {SOFTWARE ENGINEERING LABORATORY},
series = {3rd International Technology, Education and Development Conference},
booktitle = {INTED2009 Proceedings},
isbn = {978-84-612-7578-6},
issn = {2340-1079},
publisher = {IATED},
location = {Valencia, Spain},
month = {9-11 March, 2009},
year = {2009},
pages = {3258-3265}}
TY - CONF
AU - N. Stankovic AU - I. Paik
TI - SOFTWARE ENGINEERING LABORATORY
SN - 978-84-612-7578-6/2340-1079
PY - 2009
Y1 - 9-11 March, 2009
CI - Valencia, Spain
JO - 3rd International Technology, Education and Development Conference
JA - INTED2009 Proceedings
SP - 3258
EP - 3265
ER -
N. Stankovic, I. Paik (2009) SOFTWARE ENGINEERING LABORATORY, INTED2009 Proceedings, pp. 3258-3265.
User:
Pass: