
Maryland in Europe - Graduate
Programs
Bowie State University, M.S. in Management Information
Systems
INSS 540 -- INFORMATION MANAGEMENT ANALYSIS & DESIGN
| Education Center, Naples, Italy | 27 August to 17 October, 2002 |
| 2002-2003/Term I | Tuesdays and Thursdays |
| Lecturer: Ed Deaton | 18:00 to 21:00 |
| <~ back |
| Description | Objectives | Text | Grading | Office Hours | Schedule |
Credit
3 semester hours of credit
Prerequisites: Either INSS 510, INSS 520, INSS
530 or permission of the instructor.
Course Description
This course provides an in-depth look at two principle phases of the information systems development life cycle: analysis of system requirements, and system design. We will consider various approaches to the gathering and analysis of system requirements, and we will see how a good specification of user requirements contributes to an effective system design. We will study both the structured and the object-oriented methodologies.The course will cover CASE (computer-assisted software engineering) as applied to systems analysis, design and task estimating. Current trends will be a part of this course, including business process reengineering, client-server architectures, networks, and the UML (Unified Modeling Language). There will be an overview of other phases of the entire development life cycle, to gain a better understanding of the role of requirements specifications and design in the success of information systems.
Objectives
Students who successfully complete this course should then be able to understand:- How to look at an existing information system, define requirements for changes, and evaluate alternative solutions.
- How requirements are combined with technology to create a system design.
- How to document and communicate system requirements and designs to users.
- The terms and concepts currently accepted in systems analysis and design.
- How to apply the concepts and principles of systems analysis and design to given problems.
Text
Systems Analysis and Design in a Changing Worldby John W. Satzinger, Robert B. Jackson and Stephen D. Burd.
Course Technology Inc., 2nd edition, 2002.
ISBN 0-619-06309-2
Course Evaluation
Grades for this course will be based on:| Individual Homework Assignments | 20% | |
| Term Project | 25% | |
| Midterm Examination | 25 | |
| Final Examination | 30 |
Computation of Final Grades for INSS 540
| A | 90 to 100 | |
| B | 80 to 89 | |
| C | 70 to 79 | |
| F | below 70 |
Office Hours and Communication
Students may request individual discussions before or after class, and by appointment. Messages may be left for me in the University of Maryland office, or by e-mail (phone numbers to be announced at beginning of term). My e-mail address is edeaton@faculty.ed.umuc.eduAlso, we will use the Web Board during the term, where information and copies of assignments can be posted, discussions carried on and help provided.. The details will be announced at the beginning of the term.
Policies
Class attendance is expected. Students are responsible for all material covered during lectures and discussions, as well as assigned textbook readings. In order to have lively and effective classroom discussions, students should read assignments and case studies and think about them before class.On such matters as exceptional grades, academic dishonesty, interpersonal behavior and attendance, the policies expressed in the current Graduate Catalog of the University of Maryland in Europe will apply to this course.
Instructor: Edmund I. Deaton
Dr. Deaton received his Ph.D. in Mathematics from the University of Texas. He has been teaching and doing research in Computer Science since 1980. After many years at San Diego State University he retired in 1992. He was a visiting professor at Hope College, Holland, Michigan during 1993-1995. He spent two years at Oklahoma State University from 1980 to 1982 as a visiting professor and visited there again in 1992. He worked as a management consultant with a Southern California consulting firm for several years in the 1980's. He specialized in database design for governmental entities. He has been with the University of Maryland, European Division since 1995. He teaches in the graduate MIS program and also teaches undergraduate computer science courses. His academic specialty is data base design. His primary hobbies are hiking and Alpine climbing. Although based in Heidelberg, he calls Rota, Spain home and hopes to be assigned there for some time each year. E-mail: edeaton@faculty.ed.umuc.edu; Address and phone to be provided.
Project
There will be a term project where students can acquire the experience of using software engineering methods to organize information for problem-solving and to create useable designs. Because teamwork is a standard part of the professional software environment, at least some part of the projects will be conducted in teams. During the first week of the course, guidelines for project content will be handed out, and we will decide how to organize the projects in a way which allows for constructive student cooperation and at the same time encourages and recognizes individual student work.Course Standards
Exams will cover both text and lectures. They will consist mostly of short answer essay questions, and technical problems in systems analysis and design. Each exam will include an essay question of the type found in the MIS Graduate program comprehensive exams.Students will be graded primarily on their written work. Good presentation skills are also important, however, and will help contribute to the grade. In both written assignments and verbal contributions, students are encouraged to follow the maxim, "Content before form".
Written assignments:
Black ink on white A4 or 8.5x11 paper, in a standard typewriter face such as Courier, or 11- or 12-point Times New Roman. Line spacing double-spaced or 1.5.No color or graphics, except for (1) charts or maps generated by the student to convey substantive information; or (2) as an artifact of the subject being studied, in support of a point discovered or being argued by the student.
Where there has been research, please use the APA format for citations. Details will be provided..
Tentative Course Schedule
| Week | Topics and Activities | Preparatory Reading |
|---|---|---|
| 1 August 27, 29 | Course Introduction The Systems Analyst's World The Systems Analyst as Project Manager |
1, 2, Appendix A |
| 2 September 3, 5 | Methodologies Gathering Requirements Information Modeling System Requirements Cost-Benefit Analysis Project teams selected |
3, 4, 5 Appendix B |
| 3 September 10, 12 | The Traditional (Structured) Approach The Object-Oriented Approach Project topics selected |
6, 7 |
| 4 September 17, 19 | Environments, Alternatives, Decisions Review Midterm Examination |
8, Appendix C |
| 5 September 24, 26 | Design Preliminaries Database Design Projects: all deliverable elements identified |
9, 10 |
| 6 October 1, 3 | Designing I/O & Controls Human-Computer Interaction Project drafts |
11, 12 |
| 7 October 8, 10 | Development: RAD, Components, Packages The Operational System |
13, 14, 15 |
| 8 October 15, 17 | Review Project Presentations Projects due Final Examination |
| <~ back |
| Top | Description | Objectives | Text | Office Hours | Grading |