140 likes | 320 Views
IS 2009. Presentation to the ACM Education Council September 25, 2009 Heikki Topi, Bentley University. Joint ACM/AIS Task Force. Kate Kaiser Jay Nunamaker Janice Sipior Heikki Topi (co-chair) Joe Valacich (co-chair) GJ de Vreede Ryan Wright. Brief History.
E N D
IS 2009 Presentation to the ACM Education Council September 25, 2009 Heikki Topi, Bentley University
Joint ACM/AIS Task Force • Kate Kaiser • Jay Nunamaker • Janice Sipior • Heikki Topi (co-chair) • Joe Valacich (co-chair) • GJ de Vreede • Ryan Wright
Brief History • Task force started its work in early 2007 • Right from the beginning, a strong focus on making this a broad community-based effort • IS curriculum wiki • A large number of presentations and intermediate publications in 2007 and 2008 • A major reorientation in 2008 because of newly architected outcome expectations • Comprehensive public draft in May 2009 – comment period until July 2009 • Edited version distributed to Ed Council on September 11, 2009
Four Major Characteristics • Explicit attempt to support and reach programs beyond North American schools of management and business • Domains beyond business; IS as one of the first “computing + X” disciplines • Comprehensive re-evaluation of outcome expectations (and, consequently, curriculum content) • High-level IS capabilities • Three categories of knowledge and skills: IS specific, foundational, and domain specific • Separation of the core from electives • Significantly higher level of flexibility • Prior curriculum had none
High-Level IS Capabilities • Improving organizational processes • Exploiting opportunities created by technology innovations • Understanding and addressing information requirements • Designing and managing enterprise architecture • Identifying and evaluating solution and sourcing alternatives • Securing data and infrastructure • Understanding, managing and controlling IT risks
IS Specific Knowledge and Skills • Identifying and designing opportunities for IT-enabled organizational improvement • Analyzing trade-offs • Designing and implementing information systems solutions • Managing ongoing information technology operations
Foundational Knowledge and Skills • Leadership and collaboration • Communication • Negotiation • Analytical and critical thinking, including creativity and ethical analysis • Mathematical foundations
Domain Fundamentals • General models of a domain • Key specializations within a domain • Evaluation of performance within a domain.
Core vs. Career Track Electives • Previously, a 10 course core • Now, a seven course/topic core and a structure that allows the introduction of a large number of career-track electives • Core • Foundations of Information Systems (intro) • Data and Information Management • Enterprise Architecture • IS Project Management • IT Infrastructure • Systems Analysis & Design • IS Strategy, Management, and Acquisition (capstone) • Simplified prerequisite structure for the core
Observations Regarding the Core • Systems Analysis & Design and Data & Information still the identifying elements • No programming or application development in the core • Most programs will still be including it; this recognizes that it is not a required element • From IT Hardware and Systems software + Networks and Telecommunications to Enterprise Architecture + IT Infrastructure • We are raising the level of abstraction and pushing the field into a territory that is not fully familiar • Removal of a personal productivity tool course • Flatter prerequisite structure
Examples of Career Tracks • Application Developer • Business Analyst • Business Process Analyst • Database Administrator • Database Analyst • ERP Specialist • IT Architect • IT Asset Manager • IT Consultant • IT Project Manager • IT Security and Risk Manager
Where From Here • Achieving ACM Ed Board and AIS Council approval by the end of the year • Making the final report broadly available • Continuing to develop the broad, community-based approach for ongoing curriculum development • Establishing a task force to review the Master’s curriculum (MSIS 2006)?
Thank you! • For questions and comments, please contact Heikki Topi (htopi@bentley.edu) or Joe Valacich (jsv@wsu.edu)