UMUC Europe
SearchSearch Contact UsMyUMUC Site MapWebTycho  
  M. Logo
UMUC European Division-Term v/99-00

UMUC European Division-Term III/00-01
 
 

INSS 540 INFORMATION SYSTEMS ANALYSIS & DESIGN 
COURSE OUTLINE

 

Class Times: 9:00 - 16:00 27/01 - 10/03                          Class Location: Geilenkrichen, DE
Lecturer: Joyce M. Rowe, Ph.D.                                    Office Hours:  1/2 hr. after class;
Phone: TBA                                                                               by appointment 
e-mail: jrowe@faculty.ed.umuc.edu                              Course Credit: 3 semester hours

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

TEXTBOOK: Systems Analysis and Design in a Changing World by Satzinger, Jackson, and Burd, 1st Edition, Course Technology, 2000.

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, often in class, sometimes out of class..  These cases 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: initial study and investigation, project management, DFDs, ERDs, cause-and-effect diagrams,  state transition diagrams, and implementation.  Projects will be graded 80% content, 20% presentation.  Presentation must be at a business level and should include some form of graphic display, preferably Power Point.  A System Manual will be due to the Lecturer, in which all of the documentation of the study, the models, etc., will be included along with the presentation materials.

Subject Research and Class Participation---Each student will select one topic from a list of current Systems Analysis and Design topics (tentative list at bottom of syllabus).   The student  will make a 10- to 15-minute class presentation,  turn in a 2- to 3-page summary along with a page of resources used,  (use the APA format for this bibliography, as provided on the UofM Library website), and   provide each class member a 1-page handout.  Students will be graded on the quality of their presentations and summations along with their classroom discussion.  By the end of the class every student should have an elementary understanding of these topics; this material will be eligible for testing on 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 familiarize 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, both mornings and afternoons of weekend classes. 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 to be missed must be taken before the date the test is to be given in class.  On the date of research presentations or project presentations, each person must be in attendance for the first presentation.  Otherwise, the presentation will be deemed late and a 10% reduction will be made for all presentations given that the student missed.

*  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.

TENTATIVE SCHEDULE 
  Topics Discussed Activities
Class 1 Jan. 27 9:00-noon Introductions; The Systems Analyst; GST; Information Systems Building Blocks; Information Systems Development;  Mintzberg's grid Read Chapters 1-3, Append. A and C before class; Lecture/discussions of Chapter 1; Group discussions; Key Terms; Review Questions; Thinking Critically; Exercises; Case Study
Class 2  Jan 27 1:00-4:00 Chapter 1:  World of Modern Systems Analyst;  Chapter 2:  Analyst as Project Manager; Business Structures and Information Systems Use; Systems Software; Systems Development Lecture/discussions on Chapters1 and Append C; Research topic assigned; Group exercises; Assignment: On-line news site for class discussion; Look up site for EE1; "Demand for IT Workers  Far Exceeds Supply" WSJ, 4/10/00; "The Working Life--Labor Gains" WSJ, 11/29/00
Class 3 Jan 28  9:00-noon Chapter 2 Continued; Systems Analysis; Process Modeling; Fact-Finding and Information Gathering Lecture/discussion on Chapter 2 and Append A; Terms; Questions; Thinking Critically; EE1; Case; Team Assignments;  Discussion on IS Ethics

Class 4

 Jan 28

 1:00-4:00

Chapter 3:  Approaches to Systems Development; SDLC; Modeling  Lecture/discussion on Chapter 3;Terms; Questions; Thinking Critically; News site assignments;  Assignment: Read Chapters 4-8; Append B; On-line news site for 2 weeks; Research Topic selected
Class 5 Feb 10
9:00-noon
Chapter 4:  Investigating System Requirements  Lecture/discussion on Chapters 4; Append B; Terms; Questions; Thinking; Case; in-class modeling exercises;  News sites presentations
Class 6 Feb. 10 1:00-4:00 Chapter 5:  Modeling System Requirements:  Events and Things  Lecture and discussion on Chapter 5 and Append B; Team Topics submitted; Terms; Questions; Thinking; Case  
Class 7
Feb 11
9:00-noon
Chapter 6:  The Traditional Approach; Chapter 7    Lecture/discussion of Chapter 6; Terms; Questions, Thinking; Case   
Class 8 Feb. 11 1:00-4:00 Chapter 7:  The Object-Oriented Approach to Requirements; Chapter 8:  Environments, Alternatives and Decisions Lecture/discussion on Chapter 7; Terms; Questions; Thinking; Case; Assignment: Read Chapters 9-12; prepare presentations of research and news sites; study for midterm exam 
Class 9
Feb. 24
9am-noon
 Midterm Exam  News site presentations and discussion; Midterm Examination
Class 10 Feb. 24 1:00-4:00 Chapter 9:  Moving to Design; Chapter 10:  Designing Databases  Team projects reviewed; Lecture/discussions on Chapters 9 and 10; Terms; Questions; Thinking; Case
Class 11 Feb. 25 9am-noon Chapter 11:  Designing Inputs, Outputs, and Controls Research Papers Presented; Lecture/ discussion on Chapter 11; Terms; Questions, Thinking; Case
Class 12 Feb. 25 1:00-4:00 Chapter 12:  Human-Computer Interaction Lecture/discussion on Chapter 12;  Terms; Ques.;  Thinking; Case; Appendix D Assignment: Read Chapters 13-15; Complete  Projects
Class 13 Mar 10 9:00-noon Chapter 13:  Rapid Application Development and Component Based Development; Append. D; Chapter 14: Packaged Software and ERP News Sites discussed: Lecture/discussion on Chapters 13 and 14; Terms; Questions; Thinking; Case   
Class 14 Mar 10
1:00-4:00
Projects Presented  Projects presented and discussed
Class 15 Mar 11
9:00-noon
Chapter 15:  Making the System Operational  Lecture/discussion of Chapters15; Terms; Questions; Thinking; Case  
Class 16
Mar 11 1-4
Summary of class concepts Final on Chapters 1-15, Appendix
  PRELIMINARY LIST OF RESEARCH TOPICS

1.        Correlation of personal characteristics of top executives and integration and growth of  IS in organizations I

2.        Communication Skills and Personality Traits of the Systems Analyst/Project Leader and the Success of Computer Systems

3.         Information Systems and its Influence on Organizational Culture and vice versa

4.        Participative Systems Analysis, Design and Implementation

5.        Structured Systems Analysis, Design and Implementation

6.        Software Metrics and Productivity Measurements

7.        Human Interface to Computerized Systems

8.        Discussion of various views of developing Strategic  Information Systems

9.        Productivity Tools:  Past, Present, Future for the Systems Analyst

10.     Time lapse between system request and system installation in the e-environment

11.     Factors Influencing Growth/Reduction of MIS Department

12.     Competitive Advantages/disadvantages with e-business and its relationship to the IS analyst and programmer

13.     How business uses IS in today's environments (suggested starting place:  Mintzberg's business/IS grid)

14.     User-Centered Systems Design and Participation in systems design; Relationship Between User Participation and User Satisfaction

15.     Relationship Between Communication of IS personnel and Management  

16.     Integrating Structured OO Approaches In IS  

17.     Information Management in Global Enterprise (Peppard had article in 1999)

18.     Measurement and Prediction of Verification ; Software metrics - measures of productivity and quality in IS

19.      What is meant by the Structured Approach; compare to OO approach

20.     Strategies for Organizing the MIS Function  

21.     Science and Art of Debugging; Comparison of Measurement techniques and Defects in software

22.     Managing IS Development in today's organization 

Return to: Graduate Programs Syllabi

Accreditation | Contact Us | Catalogs | Worldwide Locations | Press Room | Nondiscrimination |  ©2009