Systems Analysis and DesignMIS 425/CIS 625 Spring 2003 Syllabus |
[Instructor | Text | Prerequisites | Overview of Course | Grades |Outline and Course Schedule | Homework | Project | Group Eval. | Course Policy | Group Work on Homework | Late Homework |Makeup Exams | Class Preparation | Students with Disabilities ]
|
|
|
|
|
|
MIS 328
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 dictionaries, entity-relationship models, use cases, class diagrams, state diagrams, sequence diagrams and other models used by the Unified Modeling Language (UML).
Homework, exams, and a project will be used to assess the achievement of the above objectives. In particular, students will work in teams to specify the requirements and design of an information system for a real organization. The students will be graded on the quality of their project management plan, quality of their requirements specification, quality of the group's design specification, the implementation of their project management plan, and effective oral and written communication. Feedback from team members will be used to judge team effectiveness. The project is used to assess each of the objectives above. In addition, exam and homework scores will be used to assess the student's understanding of the concepts relevant to objectives 1-4. Graduate students must include a partially developed IT strategic plan as a component of their project..
Grades are assigned as follows: 93-100% A, 90-92% A-, 87-89% B+, 83-86% B, 80-82% B-, 77-79% C+, 73-76% C, 70-72% C-, 60-69% D, less than 60% F. Final grades are based on the following percentages: Midterm 25%, Final 25%, Project 30%, Homework 15%, Class Participation 5%.
The following outline and schedule may be changed at the discretion of the instructor.
Date |
Reading |
HW |
Subject |
| Jan. 22 | Syllabus; Introduction to Analysis and Design | ||
| Jan. 27 | Roles of Information Systems in Organizations | ||
| Jan. 29 | The Vasa Capsizes | HW 1 | Success and Failure Factors |
| Feb. 3 | HW 2 | General Types of Information Systems | |
| Feb. 5 | CIO Resolutions for 2003 | IT Projects and Business Value | |
| Feb. 10 | Chpt. 1-2 | IT Strategic Planning | |
| Feb. 13 | IS Development Processes | ||
| Feb. 17 | Chpt. 3 | HW 3 | Project Management (see simple
Gantt chart program) Risk Management |
Date |
Reading |
HW |
Subject |
| Feb. 19 | Chpt.4 | System Analysis Overview Business Process Improvement Gathering Information |
|
| Feb. 24 | Chpt. 5 | Analysis Work Plan | |
| Feb. 26 | Chpt. 6 | Use Case Models, Use Case Template | |
| Mar. 3 | HW 4 | Use Case Models, Use Case Diagram | |
| Mar. 5 | HW 5 | Activity Diagrams, DFD basics | |
| Mar. 10 | Review | ||
| Mar. 12 | Midterm (Take home part) | ||
| Mar. 24 | Chpt. 7 | Structural Models (Class Diagrams) | |
| Mar. 26 | Structural Models (Class Diagrams), Data Dictionary | ||
| Mar. 31 | Decision Tables, Trees, CRUD | ||
| Apr. 2 | Dream House Case (just read) | HW6 | Finishing the Requirements Spec. and preparing the system proposal. |
Date |
Reading |
HW |
Subject |
| Apr. 7 | Chpt. 9 | Presentations | Introduction to Systems Design Presenting and Evaluating Design Alternatives (including purchasing) Design Objects |
| Apr. 9 | Chpt. 8 | Behavioral Modeling (Sequence Diagram) | |
| Apr. 14 | Behavioral Modeling (Collaboration Diagram) | ||
| Apr. 16 | Behavioral Modeling (Statechart) , Package Diagrams | ||
| Apr. 21 | Chpt. 10 | System Architecture Design (Network model, hardware
& software specification, security) Deployment and Component Diagrams |
|
| Apr. 23 | Chpt. 11-12 | User Interface Design | |
| Apr. 28 | Chpt. 13 | HW 7 | Data Storage Design and Object Persistence |
| Apr. 30 | Chpt. 14 | Class and Method Design (Techniques: Structured English, Decision Trees, Decision Tables) | |
| May 5 | Cohesion & Coupling | ||
| May 7 | Project Due | Review |
Final: Monday, May 12 3:30-5:30 PM Final Posted
The homework will include 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 occasion, 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.
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 should follow the UML object-oriented paradigm, but could also include, ER models, data flow diagrams, data dictionary and method descriptions. 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 and, optionally, 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. Periodically during the semester, your project will be orally presented to the class.
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.
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 class. Note there is a fine line between "help" and completing homework for a student. Students should be careful not to cross this line.
Homework must be turned in at the beginning of class. There is a 10% per day penalty for late homework.
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.
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.
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.