COMS 380  SYSTEMS ANALYSIS AND DESIGN

Spring Semester 2003-04

Professor Rebecca Bates

Office WH 243   Phone 389-5587   Email bates@mnsu.edu

Office Hours T, W 2-5, R 10-12, F 10-12 (by appointment)

T, W 2-4 will be held in WH 119

Course Goal

This course introduces students to topics, trends, software, and terminology associated with the analysis, design and implementation of information systems. 

Course Objectives

Participants will study the methodologies associated with structured analysis and design of information systems and be assigned the tasks of analyzing, designing and implementing a prototypic system.  After successfully completing this course, participants will be able to:

1.  Apply fundamental structured analysis and design methodologies to assess the requirements of an existing system and determine the requirements of a revised system.

a.                    Determine the requirements of the proposed systems including input, output, processes and their related volume, size, timing and frequency.

b.             Identify the system’s users and their degree and type of system usage.

c.             Identify the necessary management reporting and decision support components.

d.             Identify the data components and data relationships of the proposed system.

e.                    Determine the current and future hardware and application software requirements.

f.                     Assess the proposed system’s technical, operational, and economic feasibility.

g.                   Create a timeline for the completion of the project.

2.  Document the data flow through the proposed information system.

a.             Decompose the information system using context and system diagrams to depict the overall structure of the system.

b.             Prepare balanced data flow diagrams (DFD) and describe their component.

c.             Create Use Case Reports and a data dictionary to store descriptions of the entities, data flows, processes, and data stores.

3.  Develop an in-depth data model (DM) that supports the proposed system.

a.             Use an Entity Relation Diagram (ERD) to model file structures.

b.             Enhance the data model through Use Case Reports.

c.             Normalize the data model to support/complement data modeling.

d.             Store metadata in a repository.

4.  Implement the DFD, DM and sample prototype using MS Access.

a.             Convert the data model developed above into a MS Access relational database.

b.             Define all elements and field conditions.

c.             Populated the tables with meaningful sample data.

d.             Map the data stores to the data model.

e.             Implement the DFD using a design tool.

f.              Map the primitive processes to MS Access functions and queries.

g.             Develop a data dictionary.

h.             Implement a graphical user interface (GUI) and sample reports in MS Access.

Course Structure

Course Meetings

T 9-9:50 TR N241, W 9-9:50 WH 119, RF 9-9:50 WH286

Course Website

The course website is a resource that should be checked often.  Announcements, solutions, assignments, errata and useful links will all be put on the website.  They may or may not be announced in class so you should check the website regularly.  http://bates.cs.mnsu.edu/coms380

Course Sessions

Sessions will consist of lectures, discussions, cooperative group work and demonstrations.  As a member of the class, you are responsible for all materials discussed and assignments given during class sessions whether you are present or not.  Some class sessions may be set aside for groups to present informal progress reports.

Attendance

While it is not the role of the instructor to determine whether students are in class, it is the obligation of the instructor to facilitate the learning of each group and its members.  Since this course incorporates a project that requires a great deal of cooperative team work, it is imperative that **ALL MEMBERS** of a team be in class each day.  To emphasize the significance of this issue, please read and heed the following attendance policy.  All students will be afforded four class periods (approximately four hours) during the semester for absences due to unexpected events.  Use these wisely or better yet not at all!  For each additional absence, the course participant will have 10 points deducted from her/his total course points.

If a participant believes s/he will require more than the allowed absences, discuss the issue with your instructor during the first week of class.

Semester Project

Throughout the semester, class participants will work in teams on a project.  The project involves the analysis, design, and prototypic implementation of an information system.

The project will be decomposed into three phases to ensure that it is completed in a timely manner.  Each phase will correspond to lecture and lab sessions.  At the completion of each phase, all materials developed by the team will be submitted to the instructor.  Materials will be submitted in a three ring binder with dividers marking each phase.

Each group will present a summary of Phase I and III to the entire class and will earn a single grade for their presentation.  A brief description of each phase is attached to this syllabus.  A more detailed outline of each will be distributed during the semester.

In addition to formal assignments, team detailed progress reports are required each week.  The team report shall summarize the work of the team during the week.  Each team member is expected to sign the report if the member is in agreement with the summary.  Failure to submit a report will result in the loss of five points per group member per weekly report.  Copies of these reports should be included in the submitted binder.

Group Membership

While there will be small group work in class, you will be a formal member of a project group.  The formal groups will be decided by the third week of class.  While you will have most of the responsibility to choose your group, the instructor reserves the right to tweak group memberships if needed.  Pick your group wisely.  Talk to a variety of class members.  Determine who has a schedule similar to yours.  Identify students from other classes that have a work ethic similar to yours.  Assess who is prompt and dependable.

At any point in the term, team members may vote to expel a member for non-performance.  The instructor must be informed of this action in writing within 24 hours of the action.  The team and ex-member must split the cost of producing a copy of all work done to that point (team 1/2, ex-member 1/2).  The ex-member will then finish the project individually.

Materials for the Course

These books are available in the bookstore.

Whitten, Jeffery, Bentley, Lonnie & Dittman, Kevin.  (2004).  Systems Analysis and Design Methods. Boston, MA: McGraw Hill.  Required text

Toliver, Pamela R.  (2003).  Microsoft Access 2002, Volume II.  Upper Saddle River, NJ:  Prentice Hall. 

Recommended text

Whitten, Bentley, Dittman URL http://mhhe.com/whitten

Oracle URL http://www.prenhall.com/divisions/bp/app/hoffer/oracle/tutorial

One video tape per group

Additional materials will be made available during the semester.

Important Course Dates

March 8-12                            No classes, Spring Break

April 19                                  Deadline for Dropping Full-Term Classes

May 7, 8-10am                      Final Examination

Evaluation

Point Breakdown (525 total points)

Examinations     300 pts total                                              Project     195 pts total                         Group Work          20 pts total

Examination   I      75 pts                                                     Presentation   I       15 pts                   Phase I group grade   5 pts

Examination  II      75 pts                                                     System analysis                                  Phase II group grade  5 pts

Examination III      75 pts                                                     Presentation II        15 pts                   Phase III group grade 5 pts

Final Exam             75 pts                                                      MS Access implementation              Overall group grade   5 pts

Career Preparation     10 pts total                                    Phase   I report       50 pts  

Resume                  10 pts                                                     Phase  II report       65 pts                                                  

                                                                Phase III report       50 pts

Examinations missed without prior clearance from the instructor are forfeited.  There are no MAKE-UP EXAMS.  No incomplete grades are given except as stated in University policy.

Grading

The percentages shown below will be calculated on the total points accumulated from the examinations, projects, and homework assignments.  If you are taking this course for Pass/No credit, you must obtain at least 72% of the total points to earn a passing grade.  The instructor reserves the right to lower these percentages.

Total points will be used in assigning a course grade.

                92  - 100% of possible points earns an A

                82  -   91% of possible points earns a   B

                72  -   81% of possible points earns a   C

                62  -   71% of possible points earns a   D

Course Requirements

All assignments and tests must be completed before a passing grade will be considered.  You may turn in an assignment after it is due but with the following penalty:

                •  up to 24 hours past due, ten percent off;

                •  up to 48 hours past due, twenty percent off;

                •  over 48 hours past due, not accepted.

Summary of Project Phases

Phase I: System Planning and Analysis

System request

Preliminary investigation and fact finding

System feasibility

Determine and analyze requirements

Evaluate alternatives

Phase II: System Design

System development procedure

Develop context, system and data flow diagrams

Develop data model

Convert to relational model

Normalize tables

Phase III: Implement System

Conversion and implementation of the data model and data flow diagram in MS Access

Populate tables

Implement functions, queries and menus

Tentative Weekly Outline