Systems Analysis and Design

MIS 425 Spring 98 Syllabus

Instructor

Name: Dirk Baldwin
Office: 355 Molinaro
Phone: 595-2449
e-mail: baldwin@uwp.edu
Office Hours: 2-4 PM M; 10-11 AM W, 8-9 AM F

Texts

Whitten, J. L. & Bentley, L. D.Systems Analysis and Design Methods, Irwin, 1998.
System Architect Tutorial

The objective of this course is to study current strategies and techniques of systems analysis and design. The student will learn how to use the techniques to analyze and model information system requirements, propose an information systems solution and build an information system that meets an organization's needs. The course covers managerial, behavioral, and technical components of the system's analysis and design process. Managerial and behavioral topics include system development methods (e.g., life cycle, prototyping, spiral model), systems theory, strategic planning, business process reengineering, project management, and information gathering techniques. Technical topics include data flow diagrams, data dictionaries, entity-relationship models, transform descriptions, state transition diagrams, and object-oriented modeling. Microsoft Access is used to build prototype systems.

Objectives

The student will determine the most appropriate systems development method to use in various scenarios.
The student will determine and document a project management plan for information system development cases. This plan will include components that address the schedule, process, and quality of the project.
The student will use systems analysis models to document the information system requirements of a real organization.
The student will use system design models to propose an information system design for a real organization.
The student will build a prototype system using Microsoft Access.

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: Midterm 20%, Final 25%, Project 30%, Homework 15%, Group Evaluations 5%, Class Participation 5%.

Outline and Course Schedule

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

Developing Quality Information Systems

Date	Reading	HW	Subject
Jan. 20	Chpt. 1-2		Information Systems in Organizations Success and Failure Factors Intro. to Analysis and Design
Jan. 27	Chpt. 3, Module A The Vasa Capsizes	HW 1	IT Strategic Planning Business Process Reengineering IS Development Processes

Systems Analysis

Date	Reading	HW	Subject
Feb. 3	Chpt.4-5, Module C	HW 2	Selecting IS Projects SA Overview. Systems Theory Intro. to Data Modeling
Feb. 10	Chpt. 6	HW 3	Data Modeling Continued Process Oriented Models (e.g. Data Flow Diagrams (DFDs))
Feb. 17	Module B, E	HW 4	Data Flow Diagrams
Feb. 24	Module D	HW 5	JAD Systems Dictionary: Data Dictionary, Process Specifications
Mar. 3	Chpt. 7	HW 6	Network Modeling & Review
Mar. 10	Midterm Exam
Mar. 24	Chpt. 8		Object Modeling

Systems Design

Date	Reading	HW	Subject
Mar. 31	Chpt. 9-10	HW 7	Intro. to Systems Design Preparing and Presenting the System Proposal Quality Assurance
Apr. 7	Chpt. 11-14		Input, Output and Data Design
Apr. 14	Chpt. 15	HW 8	Structured Software Design Structure Charts Cohesion & Coupling
Apr. 21	Chpt. 16	HW 9	Object-Oriented Design
Apr. 28	Chpt. 17		Systems Implementation & Review
May 5	Chpt. 18	Project Due	Systems Support & Review

Final: Tuesday, May 12, 5:45-7:45 PM

Homework

The homework will cover Microsoft Access, SA Models, SD Models, and other aspects of the development process. Many of the homework assignments build from past homework assignments. Some homework will require the use of a CASE tool. A student or group of students will, on occassion, present their homework results to the rest of the class. Student's will be told in advance when they are to present their homework assignment.

Project

The project is a major part of your grade. The project must be done in groups of two to four people. The project involves the analysis and design of an information system for a real organization. You are responsible for locating this organization. The projects should include the following: A title page, table of contents, general description of the organization, description of the company's current and potential information system problems, and description of the purpose and scope of the study. Next, your project should document the organization's information system requirements using text, models of the current system and models of the future system. The models can include object-oriented models, ER models, data flow diagrams, state transition models, a data dictionary and process description. After the requirements are specified, the project should propose future systems that addresses at least part of the company's information system requirements. The proposed future systems can include an investigation of purchased software packages. At least one alternative should be documented using object-oriented models, structure charts, dialog diagrams, and/or a system prototype. A cost/benefit analysis should be performed for each alternative. Finally, the project should include documentation relevant for project management. This documentation includes a history of past work, a work log, project management models (e.g., schedules), and evaluations of the project team and its members. The projects typically range from 40 to 150 pages in length.

Group Evaluations

Students will participate in project groups. Students will have an opportunity to evaluate the group and recognize outstanding members of the group. This feedback will be used to determine the group evaluation grade.

Course Policy

Group Work on Homework Assignments

Unless homework is explicitely 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 class. 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.

Makeup Exams

Makeup exams will be given only when the instructor, prior to the exam, has approved the request to change the exam time. Approval will be given for illness, sickness or death in the family etc.

Class Preparation and Participation

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

The class participation grade is completely at the instructor's discretion. Students can improve class participation grades through attendance, speaking in class, talking with the instructor individually and showing effort toward understanding the course material.

Students With Disabilities

Any student who, because of a disabling condition, may require some special arrangements in order to meet course requirements should contact the instructor as soon as possible to make necessary accommodations. Students should present appropriate verification from Disability Services, Wyllie Hall D175.