COURSE SYLLABUS
MIS 300 – SYSTEMS ANALYSIS
Instructor
Dr.
Jeff Harper
Professor
of MIS and Program Coordinator
School
of Business, Room 805
Voice:
(812)237-2279 FAX:
(812)237-8133
E-mail:
JeffHarper@indstate.edu Web: http://misnt.indstate.edu/harper
Office Hours: Tues. & Thurs.2:00 – 3:30 p.m., other times by appointment.
Course Description
An overview of the systems development process. Includes: tools/techniques for describing processes, data flows, data structures, file designs, input/output designs, program specifications, and prototyping for business systems. Discovery, problem-solving, and communications skills as employed by the business systems analyst are also covered.
Course Sequencing
This is a required course for all MIS majors and minors in the School of Business. It is also required by, or an elective in, other majors. The course will normally be taken in the first or second semester of the junior year. A student must have at least junior status to enroll in the course.
Upon successful completion of the
course, the students will be able to:
1.
Describe
in detail the steps of the systems development life cycle.
2.
Plan
a project using PERT/CPM, Gantt charts, and project management software.
3.
Identify
the real problem for a project and define its scope.
4.
Evaluate
the preliminary feasibility of a project.
5.
Use
observation, interviewing, and questionnaires to gather information concerning
project user requirements.
6.
Conduct
a preliminary feasibility study for a project.
7.
Write
a preliminary investigation report that thoroughly documents the results of
efforts to determine if a project should be pursued and clearly specifies
recommendations for future action.
8.
Explain
the different system modeling methodologies and when they should be used.
9.
Use
data flow diagrams and data dictionaries to model user information
requirements.
10.
Write
a primitive process description using such methods as structured English,
decision tables, and decision trees.
11.
Use
a CASE tool to create a basic system model through data flow diagrams and
entity-relationship diagrams (E-R/Ds).
12.
Describe
the role of prototyping and other approaches to obtaining software.
13.
Design
input and output screens and reports.
MIS 300, Dr.
Harper
Measurement of
Attainment of Course Objectives
Scores on examinations and quizzes, student projects, and case analyses measure attainment of course educational objectives by the student. Peer evaluations, included in the student project grade, are used to assess individual contribution to group projects.
Course Content
1. Introduction to the Systems
Development Life Cycle 5-10%
2. Management of Projects 5-10%
3. The Preliminary Investigation Phase 5-10%
The Systems Analysis Phase:
4. Determining Requirements: Gathering
Data 5-10%
5. Process Modeling with Data Flow Diagrams
10-20%
6. The Data Dictionary 5-10%
7. Data Modeling 5-10%
8. Other Approaches to Analysis 0-10%
Alternative Methods of Obtaining
Software
9. Systems Prototyping 5-10%
10. System/Software Purchasing 5-10%
Systems Design:
11. Input/Output Design 5-10%
13. Development of Program
Specifications 5-10%
14. Database Design 5-10%
Perspectives Coverage
·
Ethical
and global issues – Ethical issues are raised in the discussion of
relationships with clients and the need to be realistic and honest in making
system delivery promises. Global issues are not explicitly covered, although
discussion of systems development issues in international organizations raises
global considerations.
·
The
influences of political, social, legal and regulatory, environmental and
technological issues are not explicitly covered, with the exception of issues
related to Management of Technology.
·
The
effects of demographic diversity on organizations are covered in the sections
dealing with determining user requirements.
Communications
Coverage
·
Written
communication activities include documentation of the research project and
analyses of case studies, as well as required written responses to discussion
questions on exams.
·
Oral
communication activities include required participation in class discussions
and oral presentation of the results of the analysis project.
·
Computer
communications activities include research via on-line resources and
correspondence with the instructor and student peers via electronic mail.
·
Library
usage is required, as library resources are an essential source of data and
information for the project.
·
Computer
usage is required, as on-line resources are an essential source of data and
information for the project and CASE software is also used in the project.
Also, the use of electronic mail for outside-of-class communications and
presentation software for the presentation of the project results is
encouraged.
MIS 300, Dr.
Harper
·
Appropriate
instructional technology, such as overheads, software slide shows, videotapes,
and Internet sites will be employed during class lectures and discussion.
·
Lifelong
learning skills will be enhanced through the use of organizational, critical
thinking, and research skills for student projects.
·
Workplace
knowledge and skills will be enhanced through setting priorities, organizing
work, and using time wisely. Case studies will provide an improved
understanding of real-world problems and techniques used in problem solving.
·
Integration
of technology will be accomplished through several of the items from
Communications Coverage and Instructional Resources, above.
·
Development
of values and ethics will be addressed as described above.
·
Business
community connections will be established during the project through interviews
with representatives of organizations for which an IS solution to a problem is
identified.
Textbook
Shelly,
G. B., Cashman, T. J., and Rosenblatt, H. J. Systems Analysis and Design, 6th Ed., Course Technology,
Cambridge, MA, 2006.
Students with
Disabilities: The
instructor pledges to honor all reasonable requests to accommodate any student
with a physical disability.
Academic Dishonesty: Any acts of academic dishonesty (see Undergraduate
Catalog) will result in swift and decisive penalty, solely at Dr. Harper’s
discretion and subject to University policy.
If you cheat, plagiarize, or otherwise misrepresent your work, your
academic career and standing as a student at Indiana State University will
surely be in most serious jeopardy!
Grade
Percentage:
A = 90 -100%
B+ = 87 – 89.99%
B = 80 – 86.99%
C+ = 77 – 79.99%
C = 70 – 76.99%
D+ = 67 – 69.99%
D = 60 – 66.99%
F = less than 60%
MIS 300, Dr.
Harper
Tentative Master Schedule
The tentative master schedule is
shown below. The instructor will make further clarification of the schedule
verbally. The instructor reserves the right to modify the schedule, through
written or oral notification, as is necessary to meet the objectives of the
course. Attendance of all class sessions is required. If you are not able to attend a class
session, notify the instructor in advance.
Any student with more than two absences may receive an F, at the instructor's
discretion.
MIS 300 – Spring 2006
|
DATE |
TOPIC(S) |
|
WK1 |
Introduction MIS and Systems Analysis |
|
WK2 |
Chapter 1 (1.1-1.13 &1.22-1.28) |
|
WK3 |
Chapter 1 (1.16-1.20 & Case Study 1.30) |
|
WK4 |
Test
#1, Chapter 2 (2.3-2.15 & 2.17-2.23) |
|
WK5 |
Case
Study 2.35, SATK I (TK3-10) |
|
WK6 |
Test
#2, Chapter 3 (3.3-3.17) |
|
WK7 |
Chapter
3 (3.21-3.24 & SATK II [TK12-TK26]) |
|
WK8 |
Case
Study 3.38, Chapter 4 (4.1-4.16) |
|
WK9 |
Chapter
4 (4.1-4.16 continued & 4.23-4.31) |
|
WK10 |
Case
Study 4.49, Test #3 |
|
WK11 |
SATK
III (TK33-44), Chapter 5 (5.1-5.17) |
|
WK12 |
Chapter
5 (5.18-5.29) |
|
WK13 |
Case
5.32 |
|
WK14 |
Group
Presentations |
|
WK15 |
Final
Examination, Instructor Evaluation |