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

 

INSS 540 INFORMATION SYSTEMS ANALYSIS & DESIGN 
COURSE OUTLINE

Class Times: Conference Course                                    Class Location: Aviano, Italy

Lecturer: Joyce M. Rowe, Ph.D.                                 Office Hours:  1 hr. before class; 
Phone: +33-911-3043                                                call anytime
e-mail: jrowe@faculty.ed.umuc.edu                              Course Credit: 3 semester hours 

 

TEXTBOOK: Systems Analysis & Design in a Changing World, by Satzinger, Jackson, Burd, Course Technology, 2002

Special Reading Assignments:  As required

 

 

 

 

GRADING CRITERIA:

 

Individual cases; assignments; participation

10 points

Analysis and Design Project

25 points

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

20 points

MidTerm

 

Final

25 points

 

20 points

 

 

GRADING SCALE:

 

 

90-100 points = A

80-89 points = B

70-79 points = C

Below 70 = 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 select one on-line IS news source to monitor and report on each weekend.  Such sources include 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 4- to 5-page report along with a page of resources used,  (use the APA format), and   provide each class member a 1-page handout.  Students will be graded on the quality of their presentations and papers along with their classroom discussion.  Students are expected to discuss 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

 Oct 28

Introductions; The Systems Analyst; GST; Information Systems Building Blocks; Information Systems Development;  Mintzberg's grid

Read Chapter 1, Appx. C before class; look up www site for current job needs in IS;  Lecture on Chapter 1; Review Questions; Thinking Critically; Exercises; Case Study; Assignment: Read Chapter 2,  Appx C; On-line news site

Class 2

 Oct 30

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 Chap 2 and Appx C; Research topic assigned; Group exercises; Assignment: On-line news site for class discussion; Read Chap 3., Appx A 

Class 3

Nov 4

Chapter 3; Approaches to Systems Development; SDLC; Modeling  Systems Analysis; Process Modeling; Fact-Finding and Information Gathering

Lecture/discuss Chap 3,  Appx A; Terms; Questions; EE1; Case; Team Assignments;  Discussion on IS Ethics; Research Topic selected;  On-line news  Assignment: Read Chap. 4

Class 4

Nov 6

Continue  Approaches to Systems Development; SDLC; Modeling; Begin Chapter 4 Investigating System Requirements 

Lecture/discuss Chap 4;Terms; Questions; Thinking Critically; News site assignments;  On-line news site;  Assignment: Appx B

Class 5

Nov 11

Chapter 4: Appx B; Video

Lecture/discuss Chap 4; Appx B; Terms; Questions; Thinking; Case; in-class modeling exercises; Assignment: Read Chap 5

Class 6 Nov 13

Chapter 5:  Modeling System Requirements:  Events and Things 

Lecture and discuss Chap 5; Team Topics submitted; Terms; Questions; Thinking; On-line news site; Assignment: Read Chap 6

Class 7
Nov 18

Chapter 6:  The Traditional Approach

Lecture/discuss Chap 6; Terms; Questions, Thinking; Case; Assignment: Read Chapter 8

Class 8

Nov 20

Chapter 8:  Environments, Alternatives and Decisions; Chapter 9:  Moving to Design

Lecture/discussion on Chapters 8and 9; Terms; Questions; Thinking; On-line news site Assignment Study for Mid-Term Exam

Class 9
Nov 25

Mid-Term Exam

Assignment: Read Chapters 7, 10

Class 10

Nov 27

Chapter 7:  The Object-Oriented Approach to Requirements; Chapter 10:  Designing Databases 

Team projects reviewed; Lecture/discussions on Chap 7, 10; Terms; Questions; Thinking;  On-line news site; Assignment: Read Chapters 11, 12

Class 11

Dec 2

Chapter 11:  Designing Inputs, Outputs, and Controls; Chapter 12:  Human-Computer Interaction; Research Papers Presented

Lecture/ discussion on Chaps 11, 12; Terms; Questions, Thinking; Research Papers Presented; Assignment: Read Chapters 13-15;

Class 12

Dec 4

Chapter 13:  Rapid Application Development and Component Based Development; Append. D

Lecture/discussion on Chap 13;  Terms; Ques.;  Thinking; Case; Appendix D;  On-line news site; Work on  Projects

Class 13 Dec 9

Chapter 15:  Making the System Operational 

Lecture/discussion on Chap 15; Terms; Questions; Thinking; Study for Final Exam 

Class 14 Dec 11

Final Exam

Complete projects for  presentations

Class 15 Dec 16

Chapter 14: Packaged Software and ERP; Summary of class concepts, Projects Presented

Lecture/discussion of Chap15; Terms; Questions; Thinking; Case; Projects presented and discussed

Class 16
Dec 18

Projects presented

Complete project presentations

 


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.        Purchasing vs. In-house development

6.        Human Interface to Computerized Systems

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

8.        Reduction of time lag between system request and system installation in the e-environment and its effect

9.        Factors Influencing Growth/Reduction of MIS Department

10.     Competitive Advantages/disadvantages with e-business and its relationship to the IS jobs and responsibilities

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

12.     Relationship Between Communication of IS personnel and Management 

13.     Integrating Structured OO Approaches In IS 

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

15.     Measurement and Prediction of Verification ; Software metrics – measures of productivity and quality in IS

16.     Strategies for Organizing the MIS Function 

 

 

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