INSS 540 INFORMATION SYSTEMS ANALYSIS & DESIGN 
COURSE OUTLINE

Class Times: 9:00am - 16:00pm 8/26 - 10/08                 Class Location: Heidelberg
Lecturer: Joyce M. Rowe, Ph.D.                                    Office Hours:  1/2 hr. before and
Phone: TBA                                                                               after class; by appointment 
e-mail: colonandjoyce@yahoo.com                              Course Credit: 3 semester hours

Pre-requisite: Either INSS 510, INSS 520, INSS 530 or permission of the lecturer

TEXTBOOK: Systems Analysis and Design Methods by Whitten and Bentley, 4th Edition, McGraw-Hill, 1998.

HANDOUTS: Will be distributed from time-to-time; you will be responsible for this material

COURSE DESCRIPTION

This course provides an in-depth look at all phases of information systems development.  Requirements acquisition methodologies are reviewed and evaluated with respect to different application areas.  Logical design is reviewed and implementation issues are addressed.  Data-centered as well as process-centered approaches to system design are reviewed.  Particular design methodologies, including structured design, are discussed.  Life cycle as well as heuristic approaches to system development are examined and discussed.  Organizational and behavioral issues with respect to information system development are examined.  An analysis and design project will be required. 

GRADING CRITERIA:

Individual cases; assignments; quizzes

10 points

Analysis and Design Project

25 points

Subject research/presentation(15); participation (5)

20 points

Midterm

20 points

Final

25 points

GRADING SCALE:

90-100 points = A

80-89 points = B

70-79 points = C

Below 69 = FA

ASSIGNMENTS

Individual cases/assignments--Each student will develop various models and complete small case studies.  These assignments are useful in applying the methodologies discussed in class.  Quizzes may be given without notice.  Additionally, each student will be assigned one on-line IS news source to monitor and report on each weekend.  The sources are internet news, ZD Net,   IS News, InfoWorld, Breaking News.

Project--Students will be divided into small teams and will analyze a typical business problem. This problem will be carried through the different phases of the SDLC, including project management, DFDs, ERDs, cause-and-effect diagrams,  state transition diagrams, and implementation.  Projects will be graded 80% content, 20% presentation.

Subject Research and Class Participation---Each student will select one topic from a list of current Systems Analysis and Design topics (tenative list at bottom of syllabus).  Several mandatory readings on that subject  will be required of ALL the students in the class, as listed under Activities of weekly schedule.  The student  will make a 5-minute class presentation,  turn in a 2- to 3-page summary along with a page of resources used,  (use the ADA format for this bibliography), and   provide each class member a one-page handout.  Students will be graded on the quality of their presentations and summations along with  their classroom discussion.  These mandatory outside readings will be tested on the midterm and final exams.  Students also are expected to be able to discuss the concepts in the book and demonstrate their applications  through discussion of real-world problems.  This part of the course will familarize students with the concepts in SA&D and the respected researchers in the field.

Midterm/Final--The midterm and final will consist of short answer essay questions related to the goals listed at the beginning of each chapter and the outside readings and a comprehensive exam question. This portion of the tests (worth 100 points) will be graded exactly like the comprehensives; that is: 75% for content, 25% for English and organization.

COURSE POLICIES/EXPECTATIONS

The following policies apply to this class. These policies are generally reflected in the graduate catalog.

*   ATTENDANCE POLICY: Regular class attendance is expected. If you should miss a meeting, it is your responsibility to obtain information concerning the material covered and upcoming assignments. If there is a quiz or other assignment due on that class period, previous arrangements should be made with the instructor whenever possible. Please note that those students receiving tuition assistance from the Federal Government must not miss three consecutive class meetings without prior approval, or the education Services Officer (ESO) must be notified by the instructor.

*  ACADEMIC HONESTY: Students are expected to do their own work. Cheating on tests, plagiarism on written assignments, or any other form of academic dishonesty will result in a "0" for the assignment. Note that a D or an F usually results in at least 60 or 50 points, where violation of academic honesty results in none. See the European Division Catalog for the UMUC policy on academic dishonesty and plagiarism.

*  ASSIGNMENT/TEST SCHEDULES: Students are expected to hand in all assignments and complete all tests on the days they are due. If a student fails to complete any assignment or test, the resulting grade will be a "0," rather than an "F." Any other assignments will be marked down half a letter grade for each half week the assignment is late. Quizzes cannot be made-up unless the student had an excused absence. Major tests can be made up only if prior arrangements are made with the instructor.

*  CLASS PREPARATION: Students are expected to come to class prepared. This means they should have read the materials assigned for class for that session and have prepared any pertinent assignments. Quizzes may be given.

COURSE OBJECTIVES

The objectives for this course are listed in each chapter. Questions on the midterm and final will be directly related to these goals, even though the topic may not be covered in class.  Students completing class should:

Develop models using  Project Management tools

Identify classes of Information Systems utilized within business structures

Identify, describe and model problems and their underlying causes

Develop data collection methods and initial project studies

Develop feasibility studies with cost/benefit analysis, including Executive Summaries

Develop logical and physical system designs using various modeling methodologies

Producing DFDs, ERDs, state transition diagrams, and HIPOs

Explain evaluation criteria used in designing distributed systems

Explain alternative approaches in acquiring systems, identifying advantages/disadvantages

Develop Program Specification Requirements

Describe the process for developing applications, including development of Program Specification Requirements

Identify CASE modules and adaptation to systems design and development

Identify major theories and concepts in the field

The activities and assignments for this course are designed to help the student know, comprehend, and apply the basic concepts of systems analysis and design.  In addition to the academic objectives, students are expected to improve their skills in the following areas:

1. Critical Thinking: Students should improve their ability to analyze computer user situations and make appropriate suggestions for resolving business problems through computer systems.  The  projects in this class encourage students to think critically about real-world situations.

2. Writing Skills: Students should improve writing skills through development of the Feasibility Study and formal report on the major project and on the mid-term and final.

3. Oral Presentation Skills: Students should improve their presentation skills through their oral reports on the major project, class discussions, and group presentations.

4.  Computer Skills: Students are expected to improve their computer skills by using word processing and project management software.  The use of  Internet and e-mail are also encouraged.