Management Information Systems

University of Louisville-Panama June 2002 Syllabus


Contents

[Instructor | Text | Overview of Course | Grades ]
[Outline and Course Schedule | Participation ]
[Course Policy | Group Work on Homework | Late Homework |
Late Projects | Class Preparation]


Instructor

Name: Dirk Baldwin
Email: baldwin@uwp.edu
WWW: http://www.uwp.edu/academic/mis/baldwin

Blackboard site: http://blackboard15.imt.uwm.edu You will need a user id and password for this site. The site will contain a discussion board, class notes, and other information. I will supply the user ids and passwords.

Texts

Overview of Course

Information Systems (ISs) are fundamental to any organization. Managers must be able to use ISs, identify potential IS projects, manage aspects of an IS, and participate in IS development. This course has two primary topic areas. First, the course exposes students to IS applications. Through labs, homework and projects, the student will be able to use and build systems with a variety of information system tools, including the Internet and database packages. Second, the course focuses on strategies and techniques for information systems use, development and management. Topics include information system types, e-commerce, development methodologies, implementation techniques, strategic IS planning, process improvement, and IS quality control. Students will learn many of these concepts through the process of proposing, planning, and possibly developing a small application (e.g.,  a Web site). The modes of instruction for the second topic area include lecture, readings, class discussion, class presentations and cases.

Objectives

Upon completion of this course, the student should:

  1. Be able to use computer technology in decision making.
  2. Understand the impact of information systems on an organization's performance.
  3. Demonstrate an understanding of the MIS functional area and its integration with other areas.
  4. Demonstrate an understanding of various IS applications.
  5. Be able to propose and justify a particular information system application for an organization.
  6. Be able to develop a long term information system plan.
  7. Be able to develop and implement an information system project plan.
  8. Demonstrate effective written communication on a business problem or issue.

Assessment

A project, homework, cases, and class participation are used to help teach and assess concepts related to the course objectives. 

Project

The project requires students to propose an application, discuss the strategic benefit of the application, develop a project plan, document the features of the application, develop a small prototype, and propose an implementation plan. Several factors are used to evaluate the project, including the benefits of the potential application (as it relates to objectives of the organization), the quality of the design, the quality of the justification, and the completeness of the implementation plan. These factors are directly related to objectives 2-8 above. The projects can be done in groups. I will try to allow some time in class to complete these activities.

Homework

The course also requires the completion of homework assignments. Many of these assignments require the use of computer technology to solve a business problem (objective 1). The computer related assignments lead the student through the process of gathering data, storing data, using the information for decision making, and presenting the information (this homework is labeled computer homework). All students must turn in the computer homework. The other homework is managerial in nature and will help with class discussion. All students must complete HW 4. Students should turn in at least one homework from homeworks 1, 2 and 5.

Cases

Cases require the analysis of a business situations. The cases review key concepts in the class.  Students must turn in a paper for the Red Bell and Submarino cases.

Class participation

The class participation grade is based upon your participation in class discussions, presentations, group work, and communication through e-mail or bulletin boards.

Grading Policy

Grades are assigned as follows: 92-100% A, 90-91% A-, 87-89% B+, 82-86% B, 80-81% B-, 77-79% C+, 72-76% C, 70-72% C-, 60-69% D, less than 60% F. Final grades are based on the following percentages: Project 35%, Case 1 20%, Case 2 20%, Homework 15%, Class Participation 10%.

Outline and Course Schedule

The following outline and schedule may be changed at the discretion of the instructor.

Date

Reading

HW

Subject

 
June 17

 

      Introduction and Overview of Course
      Course Administration: WWW notes, Blackboard
Chapter 1    The Role and Importance of IS
The Vasa Capsizes HW 1 Characteristics of Success vs. Failure of IS
Chapter 2   Business Models and Aligning IS with an Organization
     Classifying IS (e.g., DSS, TPS, MIS)
    Technology Lab
 
June 19 Chapter 3 HW 2 Selecting IS for strategic impact
    Developing the System Request
Chapter 13   Information Technology Economics
    Technology Lab
 
June 20 Chapter 8   IT Planning
    Business Process Improvement and Reengineering
    Process Modeling
    Technology Lab
 
June 22 Chapter 14   Development Methodologies
Managing Public IS Case   Web Site Planning
    Web Site Development
    Project Management Techniques and Tools
  Computer HW 3 Technology Lab
Chapters 4 and 5   E-Commerce
    Web Development Exercise
  Project HW 4 IT Application Proposals (Presentations)
 
June 24 Red Bell Case Case 1 IT Development for Small Business
    E-Commerce Continued
    Technology Lab
 
June 26 Chapter 6   Supply Chain Management
    Enterprise Resource Planning (ERP)
Chapter 7   Transaction Processing and Customer Relationship Management
  HW 5 Technology Forecasting/Workplace Trends
 
June 27 Submarinos Case 2 International E-Commerce and Global IT
Skim Chapter 9   Knowledge Management
Skim Chapter 10   Decision Support
    Technology Lab
 
June 29 Chapter 11   Data Management
Technology Guide 3 Computer HW 6 Databases and Modeling
Skim Chapter 15   Managing information resources and Security
Skim Chapter 16   Impacts on individuals and society
  Project Due Technology Lab

Class Participation

The class participation grade is subjective. The class participation grade is influenced by attendance, speaking in class, discussions outside of class, discussions through e-mail or news groups, and group evaluations.

Course Policy

Group Work on Homework Assignments

Unless homework is explicitly identified as group homework, students must complete their own homework. Copying homework is not allowed. If help is needed, the student is encouraged to ask the professor or someone from the student's homework group. Homework groups will be formed at the beginning of the semester. Note there is a fine line between "help" and completing homework for a student. Students should be careful not to cross this line.

Late Homework

Homework must be turned in at the beginning of class. There is a 10% per day penalty for late homework.

Late Projects

Late Projects will be accepted only when the instructor, prior to the project due date, has approved the request to change the time. Approval will be given for illness, sickness or death in the family etc.

Class Preparation

Read materials before class. A portion of your final grade is based on class participation.


Last modified: June 10, 2002
Dirk Baldwin, MIS, UW-Parkside, dirk.baldwin@uwp.edu