Paradigm for Computer Technology Program Development Peter Ping Liu, Ph D, PE, CQE, OCP and CSIT Eastern Illinois University School of Technology Charleston, IL 61920

Program/Curriculum Development Do you want to do it alone?

Of course, we need to involve everyone.

Reality #1 People with doctoral degrees have a lot of ideas, and are capable of offering many directions, like a star fish.

Reality # 2 Committee members like to have debate to show who is the smartest. But, they are pretty flexible, very open-minded. They change their ideas every 2 weeks.

Result We are on the same page again, again, again, and again, …. A committee is where we debate and argue fearlessly, and finally decide to take no action.

Any Suggestions? I am ready to shut up if you have any better ideas than mine.

My Suggestions Relax Use Paradigm to build consensus

Method One: Technological Approach

Typical Technological Architecture: Microsoft (.Net)

Typical Technological Architecture: SUN Microsystems (Java)

Basic Layers of Technology Database Network Database Presentation

Curriculum on Computer Technology with Management Component (MS Program) Network Database Presentation Management of Computer Technology

Method Two: Application- Centered Approach

Enterprise System Architecture Based Upon: Turban, McLean and Wetherbe, c2002 Applications: CAD/CAM, Image/Data Processing, Automation, PLC, Operations, Quality, Materials, Resources, CRM, B2B, B2C … Hardware Software Network Data Database

A Computer Technology Undergraduate Program: Hardware Software/Language Database Network Data (policy) Applicationsssssssssss.