loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
20th Conference on Software Engineering Education & Training (CSEET'07)
Dublin, Ireland
July 03-July 05
ISBN: 0-7695-2893-7
ASCII Text
x 
 
David Parnas, "Resolving Dilemmas in Software Engineering Education," Software Engineering Education and Training, Conference on, pp. xix, 20th Conference on Software Engineering Education & Training (CSEET'07), 2007.
 
 
BibTex
x
 
@article{ 10.1109/CSEET.2007.43,
author = {David Parnas},
title = {Resolving Dilemmas in Software Engineering Education},
journal ={Software Engineering Education and Training, Conference on},
volume = {0},
year = {2007},
issn = {1093-0175},
pages = {xix},
doi = {http://doi.ieeecomputersociety.org/10.1109/CSEET.2007.43},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Software Engineering Education and Training, Conference on
TI - Resolving Dilemmas in Software Engineering Education
SN - 1093-0175
SP
EP
A1 - David Parnas,
PY - 2007
KW - null
VL - 0
JA - Software Engineering Education and Training, Conference on
ER -
 
David Parnas, University of Limerick, Ireland
Anyone developing a Software Engineering curriculum is faced with several dilemmas:

Should it emphasize fundamental principles or current technology?

Should it teach about a wide variety of approaches or how to use a few important methods?

When discussing how the software industry does things, should we teach that this is what to do or what not to do?

How should we balance ?Core Engineering? vs. ?Software Engineering?

This talk will discuss one set of answers to these questions and outline a curriculum that implements them.

Citation:
David Parnas, "Resolving Dilemmas in Software Engineering Education," cseet, pp.xix, 20th Conference on Software Engineering Education & Training (CSEET'07), 2007
Usage of this product signifies your acceptance of the Terms of Use.