Faculty Contact Information:
Robert S. Christeson
rchristeson@faculty.ed.umuc.edu
christeson@incirlik.net
DSN 676-6608
Comm 90-322-326-6608
Class meetings: 22/23 January 05; 5/6 February 05; 19/20 February 05; 5/6 March 05; 0900-1600 hours.
|
|
Consultation:
prior to and after class meetings
via e-mail (rchristeson@faculty.ed.umuc.edu)
|
|
Required Texts and Readings:
|
Satzinger, J., Jackson, R., and Burd, S. (2004). Systems Analysis and Design in a Changing World (3rd ed.). Boston: Course Technology.
In addition, a case tool will be utilized.
|
|
Supplementary Readings:
|
The standard for papers in the graduate program is the APA style. All participants in this course and all graduate INSS, MGMT, PUAD, and ECON courses should have a copy of the style guide:
American Psychological Association. (2001). Publication Manual of the American Psychological Association, 5th Edition. Washington DC: Author. All graduate students should be prepared to utilize the UMUC online library at http://www.umuc.edu/library/. The library contains a large number of full text academic journals that are free of charge and immediately available. The library homepage also contains a number of links related to improving students' research and writing skills.
|
|
Recommended Journals:
|
Publications of the various professional societies (such as ACM -- the Association for Computing Machinery, the IEEE Computing Society, and the various management professional societies) are strongly recommended. In addition, there are many trade journals (such as eWEEK) that MIS professionals should become familiar with, many of these being published both weekly and on-line.
|
|
Course Description:
|
3 semester hours credit. Prerequisites: Undergraduate statistics and quantitative methods, and either INSS 510, INSS 520, INSS 530, or permission of the Program Director. 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 and object-oriented 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. Students may receive credit for only one of the following courses: INSS 540 or INSS 610.
|
|
Course Goals:
Upon completion of the course, participants should understand and be able to describe/explain:
1. The systems development life cycle (SDLC)
2. The reasons for formal systems analysis and design
3. Ethical, organizational and behavioral issues
4. Non-traditional systems development
|
|
Course Objectives:
At the conclusion of this course the student will be able to:
1. Compare and contrast methods for systems security and controls
2. Describe the processes and phases of IS development, and the deliverables associated with each phase of the SDLC
3. Distinguish methods for requirements acquisition
4. Justify the importance of structured logical analysis
5. Explain the difference between data centered and process centered methodologies
6. Compare and contrast conventional and object-oriented design methodologies
7. Discuss the steps involved in systems prototyping and Rapid Application Development
8. Design plans for systems implementation, operations and maintenance
|
|
Grading Information:
|
Grades for this course will be assigned as follows:
A 90%
B 80 – 89%
C 70 – 79%
F Below 70%
Please note that Bowie State University does not use "D" for graduate students. The grade F(a) is used to designate academic failure. F(n) is used to designate failure for non-completion. Grades of Incomplete or Withdrawal are governed by UMUC-Europe policies. For further details, please refer to the UMUC-Europe Graduate Catalog, available in your local Education Center or online at http://www.ed.umuc.edu/general_info/publications/catalogs.
|
|
Course Requirements:
|
Graduate school at the masters level focuses on helping students obtain the education needed for success as professionals in their chosen fields. Thus, UMUC-Europe Graduate Programs and Bowie State University share the common goals of promoting excellence in academic scholarship through thoughtful inquiry and the skillful application of knowledge and theory for the betterment of society.
In order to maximize your graduate educational experience in general and this course in particular, you are required to:
10% - Participate in classroom discussions
30% - Complete graduate level projects or programming assignments, write graduate level papers or case studies
20% - Orally/visually present prepared material
20% - Mid-Term examination
20% - Final examination
|
|
Description of Course Requirements:
|
Participate in classroom discussions: You are expected to come to class prepared to engage in all discussions in a professional and informed manner. Usually this requires two to three hours for every hour of a face-to-face class.
Complete graduate level projects or programming assignments, write graduate level papers or case studies: You are required to conduct professional-level research, including appropriately citing works of others and avoiding plagiarism. Resubmission of course work from previous classes (whether or not taken at UMUC, UMUC-Europe or BSU), partially or in its entirety, is not acceptable in this course and will result in an automatic failure on the assignment.
Orally/visually present prepared material: You are required to present your results in a professional manner. In a face-to-face course, this typically means an oral presentation accompanied by appropriate visual material.
Complete one or more written examination(s): The examination process in this class will assist you in developing the writing and critical thinking skills necessary for successfully passing the comprehensive exam required of all graduate students. The examination questions used for this course will either be taken directly from past comprehensive exams or written as though to be included on a comprehensive exam.
|
|
Course Schedule:
The class will meet every other weekend: 22/23 January 05; 5/6 February 05; 19/20 February 05; 5/6 March 05; 0900-1600 hours.
Saturday, January 22
Introductions and Team Building Exercise
Review of Syllabus
Clarification of goals, objectives and requirements
Project Topics
Orientation to subject
Part I: The Modern Systems Analyst
Chapter 1: The World of the Systems Analyst
Chapter 2: Approaches to System Development
Appendix A - Principles of Project Management
Sunday, January 23
Chapter 3: The Analyst as Project Manager
Chapter 4: Beginning the Analysis
Chapter 5: Modeling System Requirements
Present Project Choice
Saturday, February 5
Part II: Systems and Analysis Tasks
Chapter 6: Traditional Approach to Requirements
Chapter 7: OO Approach to Requirements
Chapter 8: Evaluating Alternatives
Review for Mid-term
Team Project Planning
Sunday, February 6
Project Updates
Mid-term Examination
Saturday, February 19
Part III: Systems Design Tasks
Chapter 9: Moving to Design
Chapter 10: The Traditional Approach to Design
Sunday, February 20
Chapter 11: OO Approach to Design
Chapter 12: Advanced Topics in OO Design
Chapter 13: Designing Databases
Project Updates
Saturday, March 5
Chapter 14: Designing the User Interface
Chapter 15: Designing System Interfaces, Controls, and Security
Project Presentations
Review for Final Examination
Sunday, March 6
Part IV: Implementation and Support
Chapter 16: Making the System Operational
Chapter 17: Current Trends in System Development
Chapter 18: Packaged Software and ERP
Course evaluations
Final Examination
|
|
Academic Policies:
|
The University has a license agreement with Turnitin.com, a service that helps prevent plagiarism from internet resources. I may be using this service in this class by either requiring students to submit their papers electronically to Turnitin.com or by submitting questionable text on behalf of a student. If you or I submit part or all of your paper, it will be stored by Turnitin.com in their database throughout the term of the University's contract with Turnitin.com. If you object to this temporary storage of your paper, you must let me know no later than two weeks after the start of this class. Please Note: If you object to the storage of your paper on Turnitin.com, I may utilize other services to check your work for plagiarism The official university policy on Plagiarism and Academic Dishonesty can be found at http://www.umuc.edu/policy/aa15025.shtml. Section I.C. states: "Faculty may determine if the resubmission of course work from previous classes (whether or not taken at UMUC), partially or in its entirety, is acceptable when assigning a grade on that piece of course work. Faculty must provide this information in their written syllabi. If the resubmission of course work is deemed to be unacceptable, a charge may not be brought under this Policy and will be handled as indicated in the written syllabi."
Please refer to Description of Course Requirements for specific information on how resubmissions will be treated in this course and to the UMUC-Europe Graduate Catalog for information on the following:
Academic Integrity
Course Load
Exception to Policy
Grade Appeal Process
Make-up Examinations
Nondiscrimination
Students with Disabilities
Hard copies of the catalog are available at your local Education Center.
|
|
Faculty Bio:
|
Rob Christeson is a full-time Communications/Computer Systems Project Manager with the United States Air Force. He received his Bachelors of Science in Computer and Information Science from the University of Maryland, and his Masters of Science in Management and Information Systems from Bowie State University.
|
|