Talk:New Curriculum Structure and Content
From IS Curriculum
This page is for discussion regarding the proposed IS Curriculum Structure and Content.
Contents |
[edit] Please feel free to propose new Elective Topics
Here's an excellent place for proposing new elective topics or commenting on existing ones. --Heikki Topi
[edit] Have we identified the correct core topics?
The core topics presented here are the task force's proposal? Please feel free to debate them here. --Heikki Topi
[edit] ===================================
MIS/IS students have to compete for their first jobs with engineering and computer science graduates. More often than not, the first jobs for MIS/IS graduates are related to systems design and programming. Thus, IS students should know programming and should be competent in programming although we do not expect them to be involved in heavy programming for their entire career (probably only the first 1-3 years). If we do not equip them well to compete for the first jobs, they may not get a job (or an IT-related job) and they may tell their peers and friends not to enroll in the MIS program.
I am not proposing that the IS curriculum should mirror those of engineering or computer science. Personally, I know of some IS students who dislike computer and programming. Yet, they are in the IS program and their aim is to become Chief Information Officer (CIO). Some even publicly said that their ideal first job is a CIO! Somehow, the MIS/IS program is giving them the wrong perception and expectation. This is not only the case for students. Some non-IS faculty even tell computer science students that if they do not like programming, they should join the MIS/IS program!
[edit] =====================================
I am somewhat amazed that security is not seen as a professional requirement of all IT people. Clearly, it is not just the job of the Security Specialist or Manager, but with better trained IT people throughout the field, we might have less of a security problem. Sharon Tabor, Boise State.
[edit] Towards a better structure
When I look at the core topics in this first draft of a IS model curriculum, the main focus is on systems (development) issues. None of the topics Data & Information, SA&D, IT-infra, PM and AD takes in account the different use of IT in society and modern companies. In my view the starting point of a modern IS curriculum should be how people use information and communication in their day-to-day life. The curriculum should represent the threefold Business <-> Information/ communication<-> I&C technology. It means that issues like sensemaking, knowledge creation and decision making should be core issues in the curriculum. In the first draft, issues like this can only be discussed in the topic Foundation and role of IS. In my view we should change the focus towards the use of ICT in organizations. This should be discussed in business terms and not in technology terms. This should be a core topic. This business issues should be the basis of our reasoning. After that the question what this means for information and communication requirements should be discussed. The question how these requirements are implemented in technology is a third (and in my view less important) level in the discussion. This approach means that we make a difference between IS - en IT management. Companies do make this change in focus quite rapidly. The number of companies building their own information systems is declining very fast. ERP and other commercial of the shelf (COTS) systems are of growing importance in the field. These changes in focus in companies and society is not represented in the first draft.
[edit] =================================
When I looked at the structure, we may be giving the wrong impression that some IS-related jobs required little expertise and training. For example, when one looks at "G=ERP Specialist", the chart is saying that one only needs to know "Foundations and Role of IS" and "Enterprise System". There is no need to know Systems Analysis and Design, Enterprise Architecture, Project Management, etc. One key strength and uniqueness of the MIS program is Systems Analysis and Design. That should be one of the core courses that is required for all IS students. For example, an "H = Information Auditing and Compliance Specialist" needs to be able to read and understand DFDs, ERDs, UML diagrams, etc. A "K = IT Consultant" needs to be able to analyze and design systems.
