|
The Proceedings of the Information Systems Education Conference 2002: §321b
Home
Papers/Indices
prev (§321a)
Next (§321c)
| | Paper (refereed) Information Systems Curriculum
| | Recommended Citation: Hanchey, D. Lessons Learned in Teaching a Software Projects Course. In The Proceedings of the Information Systems Education Conference 2002, v 19 (San Antonio): §321b. ISSN: 1542-7382.
|
| ![CDpic]("../../art/2009cdS.jpg") |
Lessons Learned in Teaching a Software Projects Course
Refereed
| | Dale Hanchey [a1] [a2]
Computer Science Department
Oklahoma Baptist University [u1] [u2]
Shawnee, Oklahoma, USA [c1] [c2]
|
Today, almost all computer job ads include an experience requirement. The phrase "2 to 5 years experience" is typical. Why is this? Well, employers want more than employees who know how to do the work. Employers want people who can be given a task and who can handle it with little or no supervision. In other words, they want employees who know what to do. New college graduates may know the theory and possess the right skills, but will they know what to do when assigned a typically unstructured problem. A software project course can help students "put it all together". This paper outlines how a software projects course has been done at one university and summarizes lessons learned from sixteen years of experience in teaching that course.
Keywords: projects course, software development, systems analysis and design, systems development life cycle
Read this refereed paper in Adobe Portable Document (PDF) format. (117 K bytes)
Preview this refereed paper in Plain Text (TXT) format. (15 K bytes)
View the photo/graphic Hanchey.Dale.jpg with this presentation. (18 K bytes)
Comments and corrections to
webmaster@isedj.org
