LEADER 02075oam  2200457zu 450 
001 9910139108603321
005 20241212215857.0
010   $a9781424470532
010   $a1424470536
035   $a(CKB)2560000000009679
035   $a(SSID)ssj0000452020
035   $a(PQKBManifestationID)12157740
035   $a(PQKBTitleCode)TC0000452020
035   $a(PQKBWorkID)10468473
035   $a(PQKB)11414914
035   $a(NjHacI)992560000000009679
035   $a(EXLCZ)992560000000009679
100   $a20160829d2010      uy 
101 0 $aeng
135   $aur|||||||||||
181   $ctxt
182   $cc
183   $acr
200 10$a2010 IEEE 23rd Conference on Software Engineering Education and Training
210 31$a[Place of publication not identified]$cIEEE$d2010
215   $a1 online resource
300   $aBibliographic Level Mode of Issuance: Monograph
311 08$a9780769540542 
311 08$a0769540546 
311 08$a9781424470525 
311 08$a1424470528 
330   $aMost computer science (CS) and software engineering (SE) curricula include some form of SE project with the aim of lowering the gap between CS and SE education and real-world demands in industry. In this paper we briefly discuss and explain our findings of software engineering projects taught at LiU in Sweden. These courses use what we call the "tail" approach, where student projects are performed at the end of a degree program. We then argue that there are several problems with this approach and sketch an idea where SE projects are an integrated part of a curriculum. Furthermore, pros and cons of this idea, which we call the SE project "backbone" approach, are discussed and analyzed.
606   $aSoftware engineering$xStudy and teaching (Higher)$vCongresses
615  0$aSoftware engineering$xStudy and teaching (Higher)
676   $a001.642
702   $aieee
801  0$bPQKB
906   $aPROCEEDING
912   $a9910139108603321
996   $a2010 IEEE 23rd Conference on Software Engineering Education and Training$92384720
997   $aUNINA