Systems Analysis and Project Management (MIS 6308)

Spring 2006

Course Information:
Class: Spring 2006 (T 4:00 – 6:45 p.m.)
Instructors Dr. Hyeun-Suk Rhee
Office: 3.410 School of Management
Phone: 972-883-4459
Office Hours: Tuesday 6:45 – 7:30, Wednesday 1:00 – 2:30 p.m.
or by appointment
E-mail: suerhee@utdallas.edu

Text:
• “Systems Analysis and Design with UML Version 2.0: An Object-Oriented
Approach" by Dennis, Wixom, and Tegarden, Second Edition, John Wiley &
Sons, 2005.
• Class note and Handouts

Course Objectives:
• Provide an understanding of the systems development life cycle with
emphasis on the analysis and design phases.
• Familiarize students with the tools and processes used system developers to
analyze, design and construct computer-based system.
• Provide a practical experience in analyzing and designing a computer-based
system.

Course Contents and Preparation:

This course will consist of lectures, readings, presentations, examinations, and a
group project.

Evaluation:
Students will be evaluated on the basis of
1. Exam 1 (No Make-Up Exam is allowed.) 20%
2. Exam 2 (No Make-Up Exam is allowed.) 30%
3. Project 45%
• Business Analysis and User requirement (Report #1) 8%
• Systems Analysis (Report #2) 15%
• Systems Design (Report #3) 15%
• Peer Evaluations 7%
(Presentations for the corresponding report will be included in the grading as well.)
4. Class Participation and Attendance 5%

Total 100%

1
 Tentative Schedule
Week # Date Topics Assignments
1 1/10 Course Introduction Ch 1
Overview of Systems Analysis and Design
2 1/17 Project Initiation Ch 3, 4
Project Management
3 1/24 Feasibility Analysis Handouts

4 1/31 Modeling Systems Requirement Ch 5

Systems Development Methodology
5 2/7 Presentation #1 Handouts
Traditional Development Approach
6 2/14 Traditional Development Approach Handouts
Demo on Case Tool Case
7 2/21 Exam 1
Project Walkthrough
8 2/28 Object Oriented Development Approach Ch 2, 6
Functional Modeling
9 3/7 Spring Break
10 3/14 Presentation #2

11 3/21 Structure Modeling Ch 7

Case
12 3/28 Behavioral Modeling Ch 8
Case
13 4/4 Issues on System Design Ch 9, 12, 14, 15
Implementation, and Management
14 4/11 Exam 2
Project Walkthrough
15 4/18 Presentation #3
Information Technology Control

2
 Project Milestones and Requirements

A. Suitable project for the course

Any transaction processing system that aims at automating or at reengineering the

day-to-day activities of an organization is suitable for the course project. Projects earlier
years include automated cash registrar for a small store, inventory tracking system for a
manufacturing outfits, membership and billing system for a health club, inventory and
billing system for a video store, automated course schedule for a school, and parking
permit system for a university.

One option is to develop a system for a specific organization. Good sources of

such project have been student’s place of employment, small business owned by friends
or relatives, and university offices. I have also known students in earlier years who have
called local business to find out if they have suitable projects.

Another options to develop a general-purpose system aimed at a very specific

type of users. For example, a team in an earlier semester developed a record keeping
system for apartment rental offices. They interviewed several managers of local
apartment complexes and compiled their requirements. General purpose of doctor and
lawyers’ offices, heath clubs, videl rental offices etc. would fall under this category.

Have a brainstorming seccion with your group members. Once your team has
narrowed your options to a few possible projects, please discuss it with me. You need to
get started on your projects as earlier as possible.

B. Group specifications and dividing up the work

Each group will consist of group members (the number to be determined on the
first day of class) with one group leader. The leader is responsible for fair allocation of
tasks as well as its completion. Team members should note that the project itself is a
learning activity and that one individual should not perform the same task over and over
again (for example, one person does the writing of all reports.) It is often impractical to
have all members of the group put in equal amount of effort in all parts of the project.
However, I do require that all of you put in approximately equal effort for the project,
when taken as a whole. During the semester, you will get to evaluate your other group
members’ performance.

Any dissension, arguments about equity etc. are to be settled within the group. If
I am brought in to arbitrate, the group as a whole will be penalized with extra penalties
imposed on the group leader. However, if a group member shows a significant
unwillingness to work for he group project, I should be informed.

3
C. How do I grade

All reports and presentations will be judged on a competitive basis. Contents,

organization, creativity, overall presentability, applications of concepts discussed in class
as well as feedback from organization representatives (if applicable) will be used to grade.

Note that late work irrespective of the cause will be penalized at the rate of 2
points per day. Each group member will evaluate the others within the group as well as
provide a self-evaluation at the end of the semester. Team leaders will get or loose credit
based on whether the project proceeds on target, providing specific information within the
reports as indicated below, for making sure that task assignments emphasize learning
requirements and ensuring the quality of reports.

Evaluation basis for the project: 45%

• Business Analysis and User requirement (Report #1) 8%
• Systems Analysis (Report #2) 15%
• Systems Design (Report #3) 15%
• Peer Evaluations 7%
(Presentations for the corresponding report will be included in the grading as well.)

Project Documentation:
Each report should have the following in minimum:
• A cover page with team members and title
• Table of contents with page number
• Each submission should have appropriate narrative discussion pertaining to the
system as well as the documentation that is general at each phase.
• Team leader should provide an appendix, indicating the tasks assigned and performed
within each phase by team members.
• Appendix should also include a copy of the log, which indicates the dates that a site is
visited, and group meetings, duration, place, and the purpose of the visit (meeting).
• Each report should be neatly typed and bounded.
• Each report should be handled both to me as well as the company representative (if
applicable) you are working with. Please maintain a copy of all submission.
• Some suggestions about contents to be included in each report will be discussed
during the class hour.
• More specific guidelines will be given in class.