|
The Proceedings of the Information Systems Education Conference 2005: §2542
Home
Papers/Indices
prev (§2535)
Next (§2543)
| | Fri, Oct 7, 2:30 - 2:55, Senate A Paper (refereed)
| | Recommended Citation: Harkins, R J. Using the Software Development Life Cycle as a Curriculum Design Tool in the Development of a "Companion Course" for Beginning Programmers. In The Proceedings of the Information Systems Education Conference 2005, v 22 (Columbus OH): §2542. ISSN: 1542-7382. (A later version appears in Information Systems Education Journal 4(96). ISSN: 1545-679X.)
|
Recipient of Meritorious Paper Award
|
| ![CDpic]("../../art/2009cdS.jpg") |
Using the Software Development Life Cycle as a Curriculum Design Tool in the Development of a "Companion Course" for Beginning Programmers
The software development lifecycle method has been used widely by software engineers to produce reliable, efficient, and user-friendly software. The lifecycle process solves problems utilizing technology in six distinct steps…Problem Specification, Problem Analysis, Solution Design, Solution Implementation (coding), Solution Testing, and Solution Maintenance. Computer science educators, likewise, have used the lifecycle methodology to promote logical, efficient problem solving, and disciplined programming behaviors in their students. This same six step lifecycle process can be used effectively in solving curricular problems encountered by computer science departments. Specifically, this paper will detail how the lifecycle method was used in solving the problem of helping frustrated, anxious, and unsuccessful students in the early weeks of a first course in computer programming by developing a short, targeted, programming concepts "companion course" for these students. The ensuing content and pedagogical details of this "companion course" will also be reported.
Keywords: CS0, pre-programming, concepts-first curriculum, course development models
Read this refereed paper in Adobe Portable Document (PDF) format. (7 pages, 301 K bytes)
Preview this refereed paper in Plain Text (TXT) format. (24 K bytes)
Comments and corrections to
webmaster@isedj.org
