|
|
|
CIS 3300 - Systems Analysis
Prerequisite Policy:
This course is part of a series of courses to teach the systems
analysts of tomorrow. As such, it requires a good background in computers. A
student must fulfill the course prerequisites as listed in the Catalog
Description, specifically:
CIS 2010 and CSP: 1. As noted in the
General Class Policies below, prerequisites are strictly enforced.
Additionally, it is expected that students will quickly learn how
to
- use email, Internet browsers, WinZip, newsgroups and
- work effectively in groups.
Course Materials:
Course Description and Goals:
Information systems development is a process in which technical, organizational
and human aspects of a system are analyzed and changed in the hope of creating
an improved system. In spite of the advanced technology that surrounds
computer-based information systems, the process of systems analysis and design
is still largely an art. There is a high dependence on the skills of individual
analysts and designers even though there are principles, methods, techniques and
tools to guide and assist in the processes involved. This course will give
students an understanding of the tools and techniques that are available and
will introduce the concepts and theory that underlie the processes. This course
is designed to be useful to those who wish to become systems developers or who
want to be better-informed users of systems. It is a prerequisite to the
follow-on course: CIS 3310 Systems Design.
Objectives:
Upon successful completion of this course the student will be able to:
- define
and document an existing information system;
- analyze
an existing information system and specify the requirements for a replacement
system;
- use a
specific Computer-Aided Software Engineering (CASE) tool to assist in Systems
Analysis;
-
understand alternative approaches to systems development; and
-
understand the purpose, context and commonly expected "deliverables" of
systems analysis.
The CASE Tool:
Rational Rose Enterprise
Edition is available to GSU CIS students via a special agreement with the
software developer, Rational. Students with computers running Windows are
encouraged to take advantage of the software availability that will be described
in class. You will be required to use the software during class. Additionally,
use will be required to complete some assignments. The software is accessible
during class and in the main GSU computer lab, Room LS 109 and the lab in Kell Hall, Room K120.
General
Policy for Assignments and Exams
All
assignments are due at the beginning of the class on the due date. Assignments
turned in late will receive a lower grade.
Deductions will be 5% for late submissions that are turned in on the due
date, and 10% for every calendar day after that. No assignments will be accepted after
the beginning of the class following the assignment due date.
Make-up
exams will not be given. Each exam
will cover the course material to that point.
Any
questions regarding points earned on assignments or examinations must be raised
with the instructor within one week of the assignment’s or examination’s being
first returned to the student. Questions regarding points earned on an
examination will not be entertained until the day after the exam has been
returned to the student.
WebCT
use
The
course relies on WebCT use for the publication of student work, asynchronous
(bulletin board) and synchronous (chat) class discussions, access to class
discussion logs, and testing of performance. For directions for using WebCT, see
Using WebCT.
Special Considerations
The course web and/or WebCT site(s) will be used as a
repository for examples of course paper problems, model solutions, examples of
projects, and further required course material that arises during the class.
Students must arrange for their own access to the World Wide Web (Internet
access is available free in the GSU labs). All student work submitted in
fulfillment of course requirements and any student activity recorded is deemed
to be granted in the public domain (copyright-free) for the purposes of use as
instructional or research material or for examples of student work in future
courses. The course syllabus and schedule provide a general plan for the course.
Deviations may be necessary.
Tentative Schedule of Classes
Session |
Topics & Notes
Content Directory (ppt)
Rational Unified Process (RUP) documentation |
Readings &
Deliverables
See what the Bureau of Labor
statistics has to say about Systems Analysts:
http://www.bls.gov/oco/ocos042.htm
|
|
1 |
Intro to CIS3300, Introduction to Systems Analysis, Methodology |
Larman: 1- 3
(37 if you have time)
Objects by
Design: Review of Larman
Visit WebCT CIS3300
course
Install Rational Rose (demo) |
|
Problem Analysis, Team Formation |
Larman: 37 |
|
2 |
Requirements Analysis 1 & 2,
Rose Install Instructions |
Larman: 4-5;
Install Rose (full: CD or
download
username and password are
required for download. See CIS 3300 WebCT Software and documentation.) |
|
Complete Requirements Analysis
2, Use Cases, Create Rose Use Case |
Larman: 6-8; Requirements Background Material (p.1-14) |
|
3 |
Requirements Elicitation, LAB |
Interview Notes 1, 2, 3, 4
(username & password are in WebCT) |
|
Text & Form Analysis, Group Project Introduction, Case Overview |
|
|
4 |
(No class this day) |
Use Case Assignment Due by midnight via
email (individual) |
|
5 |
Conceptual Modeling, Discovering
Objects,
Conceptual Modeling 2 |
Larman: 10-12 |
|
6 |
(No class this day) |
1st Group Project Assignment Due |
|
7 |
System Sequence Diagrams,
Exam
#1 Review
(sample exam format in WebCT),
LAB |
Larman: 9
|
|
8 |
(No class this day) |
Conceptual Model Assignment Due
by midnight via
email (individual) |
|
9 |
Examination #1, LAB |
|
|
10 |
Contracts, , Collaboration Diagrams,
Research Project Participation |
Larman: 13, System Behavior Model
Larman: 15, Rational Guidelines |
|
11 |
Relating Use Cases, Documenting
“Includes” and “Extends”, Start GRASP Patterns |
Larman: 25
Larman: 16-17
|
|
12 |
Last day to withdraw with possible "W" except for hardship |
1st
Peer Evaluations Due by midnight (please complete this in WebCT) |
|
13 |
(No class this day)
|
Sequence Diagrams, Contracts, Collaboration Diagram
Assignment Due (individual) by
midnight
(email) |
|
14 |
Exam #2
Review, Finish GRASP Patterns,
Group Project Time / Lab |
Finish Larman: 16-17 |
|
15 |
Examination #2, Group Time
|
|
|
16 |
Group Project Interviews, LAB |
|
|
17 |
Coad Analysis Patterns, Class Model Elaboration, Group Project Time
/ Lab |
See
Coad help file within WebCT or pdf version,
Larman: 26-27 |
|
18 |
(No class this day) |
Second
Group Project Assignment Due |
|
19 |
Technical Document Reviews, Project Management, Exam
#3 Review |
|
|
20 |
Examination #3 |
|
|
21 |
UML Group
Assignment Due, Group Peer Evaluations Due |
Last day of class, Return Rose License |
|
Final Exam Schedule
|
Project Presentations |
|
THE COURSE SYLLABUS PROVIDES A GENERAL PLAN FOR THE
COURSE; DEVIATIONS MAY BE NECESSARY. |
|
|
