1 / 11

A CASE-BASED APPROACH TO INTEGRATING AN INFORMATION TECHNOLOGY CURRICULUM

A CASE-BASED APPROACH TO INTEGRATING AN INFORMATION TECHNOLOGY CURRICULUM. Kathleen S. Hartzel William E. Spangler Mordechai Gal-Or Trevor H. Jones. Presentation. Context and Definition of Program Philosophy of definition University context Program drivers Program Courses and Content

cecile
Download Presentation

A CASE-BASED APPROACH TO INTEGRATING AN INFORMATION TECHNOLOGY CURRICULUM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A CASE-BASED APPROACH TO INTEGRATING AN INFORMATION TECHNOLOGY CURRICULUM Kathleen S. Hartzel William E. Spangler Mordechai Gal-Or Trevor H. Jones

  2. Presentation • Context and Definition of Program • Philosophy of definition • University context • Program drivers • Program Courses and Content • Case Addition • Need and rationale • Objective • Approach • Status

  3. Philosophy of Definition • Dilemma of academic – training balance • Cannot be “all things to all people” • Focus on internal strengths and reputation of graduates • Focus on depth not breadth in core • Allow breadth as choice in electives

  4. University Context • Liberal arts university (general core) • Major within School of Business • Heavily tied to business (non-IT) education • Limited credit hours available (18+6) for specific IT courses • Internship credits available

  5. Program drivers • Research and teaching focus of faculty • Parent expectations • Student expectations • Employer expectations • Employment market opportunities

  6. Course Content and Objectives • Not vendor specific • Systems architectures • Database centric - focused on modeling • Systems Analysis and design – focused on SDLC and process modeling • Application development – focused on process logic • Integration of subject components into holistic systems development perspective

  7. IT Program Core Structure

  8. Case - Need and Rationale • Overcome silo approach to content delivery • Provide practical, integrated forum for course content accumulation • Demand students appreciate necessity for integrated knowledge set • Provides a “top down” mechanism for defining lower class content requirements

  9. SystemsIntegration Integrated Case Database SAD App. Dev. Adv. Apps. Case - Objective

  10. Case - Approach • Case context is jointly determined (e.g. order entry sub-system) • Each area defines own scope, parameters to fulfill course objectives • Integration of area content to create single, unified case description • Maintenance of components to allow re-use/modification over consecutive periods

  11. Case - Status • Context defined – sales order entry • Case scope to be refined according to class requirements • Conceptual requirements for each area (class) defined • Working on documenting area scope and deliverables • Planned implementation – Fall 2004

More Related