Faculty Contact Information:
|
I can be contacted using the e-mail address at the top of this syllabus or via your personal study group within the Web Tycho (WT) classroom. Each student will be assigned a pesonal study group within the WT classroom. This study group has each student and the instructor as members. We can use this group to communicate separately from the rest of the class on issues regarding the course.
|
|
Consultation:
|
I am always available for consultation via e-mail and the WT personal study group.
|
|
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.ed.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. (Formerly INSS 540.) Prerequisites: Undergraduate statistics and quantitative methods, and either INSS 510, INSS 520, INSS 530, INSS 620, INSS 630, 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.
Note: The last date to withdraw from the course is 20 April 2007.
|
|
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 online conferences and discussions
40% - Complete an individual Systems Analysis and Design project
25% - Complete an online open book/notes midterm examination
25% - Complete an online open book/notes final examination
Important note: 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. Additionally, I check each assignment (programs and papers) turned in to see if it has been copied from the Internet or other sources. I consider this to be cheating. Cheating is not acceptable in this course and will result in at least an automatic failure for the assignment. In more severe cases, it may also result in an automatic failure for the course.
|
|
Description of Course Requirements:
Participate in classroom discussions: You are expected to engage in the online conferences. Usually this requires the student to log into the classroom five to six times per week for about a half an hour per session. Each week's conferences will have numerous informational topics as well as one or two mini assignments. In the mini assignments, students will be asked questions on various real-world, textbook, and case-study topics, which they are required to answer to receive participation points.
Additionally, each student will be required to complete a Systems Analysis and Design project. The topic of the design project will be chosen by the instructor. Students will receive the design project topic during the first week of class.
|
|
Course Schedule:
This schedule presents 13 units or modules, with each unit corresponding to a regular three-hour weekday meeting, a half-day on weekends, or a full week of DE.
All chapter references are to the course text.
SESSION 1: Introduction and Course Overview (29 Jan - 3 Feb 07)
- Introductions
- Review of Syllabus
- Clarification of goals, objectives and requirements
- Orientation to the subject
- The World of the Modern Systems Analyst
- Required Skills of the Systems Analyst
- The Analyst as a System Developer
- The Systems Development Life Cycle
- Tools to Support System Development
Satzinger, Jackson & Burd Chapters 1 and 2
SESSION 2: The Analyst as Project Manager (4 - 10 Feb 07)
- Project Management
- Producing the Project Schedule
- Using Microsoft Project 2003 (tutorial)
Satzinger, Jackson & Burd Chapter 3, Appendix A
SESSION 3: Systems Analysis Tasks (11 - 17 Feb 07)
- Beginning the Analysis
- System Requirements
- Gathering the Information
- Validating the Requirements
Satzinger, Jackson & Burd Chapter 4
SESSION 4: Modeling System Requirements (18 - 24 Feb 07)
- Events and System Requirements
- Things and System Requirements
- The Class Diagram
Satzinger, Jackson & Burd Chapter 5
SESSION 5: The Traditional Approach to Requirements (25 Feb - 3 March 07)
- Traditional and Object-Oriented Views of Activities
- Data Flow Diagrams
- DFD Components
- The Object-Oriented Approach to Requirements
- Object-Oriented Requirements
- Inputs and Outputs-The System Sequence Diagram
- The Domain Model Class Diagram
Satzinger, Jackson & Burd Chapter 6, 7
SESSION 6: Alternatives for Environments, Requirements and Implementation (4 - 10 March 07)
- Project Management Perspective
- Scope and Level of Automation
- Contracting with Vendors
- Presenting the Results
Satzinger, Jackson & Burd Chapter 8
SESSION 7: Online Open Book/Notes Midterm Exam (11 - 17 March 07)
SESSION 8: Break (18 - 24 March
SESSION 9: Moving to Design (25 - 31 March 07)
- Understanding the Elements of Design
- Design Phase Activities
- Coordinating the Project
- Application Architecture
Satzinger, Jackson & Burd Chapter 9
SESSION 10: The Traditional Approach to Design (1 - 7 Apr 07)
- The Structured Approach to Application Architecture
- The System Flowchart and the Structure Chart
- Integrating the Design Tasks
Satzinger, Jackson & Burd Chapter 10
SESSION 11: Designing Databases (8 - 14 April 07)
- Databases and Database Management Systems
- Relational Databases
- Object-Oriented Databases
- Distributed Databases
Satzinger, Jackson & Burd Chapter 13
SESSION 12: The User Interface (15 - 21 April 07)
- Understanding the User Interface
- Designing the Interface
- Designing Windows and Browser Forms
- Identifying System Interfaces
- Designing System Inputs, Outputs and Controls
Satzinger, Jackson & Burd Chapters 14, 15
SESSION 13: Online Open Book/Notes Comprehensive Exam (22 - 29 April 07)
- Analysis and Design Project Due by COB 29 April 07.
|
|
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.
Students with disabilities should contact the appropriate support office at UMUC-Europe.
Jan Keller, Director of Student Services
UMUC-Europe, Heidelberg
Phone: +49-6221-378299
Email: edstudent_svc@ed.umuc.edu
Mailing Address: Unit 29216, APO AE 09102 OR Im Bosseldorn 30, D-69126 Heidelberg, Germany
Please refer 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
Code of Civility
Hard copies of the catalog are available at your local Education Center.
|
|
Faculty Bio:
James Helton is a Senior software developer and analyst working for Zeta Associates Incorporated. He has been the software project lead or architect for several medium to large size information systems projects. He is well-versed in multiple programming languages and operating systems and has experience with a multitude of hardware platforms.
He has taught undergraduate computer science and information systems management courses for the University of Maryland since 2001, graduate courses for Bowie State University since 2002, and graduate MSIT courses for UMUC since 2006. He has an undergraduate degree in Computer Information Systems and a Master's degree in M.I.S.
|
|