UMUC Europe
SearchSearch Contact UsMyUMUC Site MapWebTycho  
    Syllabi | Generic |
UMUC-Europe Syllabus

Common Syllabus for IFSM461

Course Title:

Systems Analysis and Design

Course Materials:

Satzinger, J. W., Jackson, R. L., & Burd, S. D. (2009). Systems analysis and design in a changing world (5th ed.). Boston: Course Technology.

Course Description:

IFSM 461 Systems Analysis and Design (3) Prerequisite: IFSM 300. A study of the methods used in analyzing needs for information and in specifying requirements for an application system. Implementation of the operational system, integration of computer technology, and aspects of organizational behavior in the design support system are examined. Topics include the concept of the system life cycle, the iterative nature of the processes of analysis and design, and the methodology for developing a logical specification and physical design for an operational system. Students may receive credit for only one of the following courses: IFSM 436, IFSM 460, or IFSM 461.

Course Goals/Objectives:

After completing this course, the student should be able to:

  • Demonstrate an understanding of the classical systems development life cycle and give a overview of several alternative development approaches (competence in information technology)
  • Prepare a requirement analysis report after conducting an initial investigation (competence in information technology, information literacy, effective writing)
  • Demonstrate skills required for information gathering, analysis, and synthesis leading to requirements definition and functional specifications documents (competence in information technology, information literacy)
  • Produce an in-depth analysis of the use of structured tools and techniques using traditional systems flow-charting methodologies (competence in information technology, information literacy, effective writing)
  • Identify and provide examples of various criteria for evaluation and refinement of alternatives for decision-making (competence in information technology, information literacy, effective writing)
  • Provide rationale for structured methodologies, such as CASE tools and prototyping, during the systems development phase (competence in information technology, information literacy, effective writing)
  • Identify and provide examples of the concepts and techniques used in developing a physical design for an operational system (including data modeling, process modeling, and network modeling) (competence in information technology)
  • Identify and discuss the implementation of the operational systems, integration of computer technology, analysis and design of systems, applicability of the capability maturity model, and extensions to enterprise-wide analysis (competence in information technology)
  • Prepare business case studies, proposals, and cost estimates (competence in information technology, information literacy, effective writing)
  • Demonstrate effective briefing techniques (competence in information technology, effective writing)

Course Introduction:

Systems analysis and design is a key part of information technology in which information systems are created as effective solutions to unique problems.  Based on customer requirements in business processes, a system of hardware, software, data processes, and people is designed and implemented.

Students will learn about significant systems development techniques, methodologies, and tools.  Within the framework of the classic system development life cycle (SDLC), students will:

a) Study methods for evaluating a systems requst so that a feasibility study can be completed that will result in a prelimnary investigation report.
b) Study methods for perfoming requirements modeling of the business process and how data modeling and process modeling will support the requirements.  The final outcome will be development of a requirements analysis report.
c) Investigate communications tools, feasibility tools, and cost-analysis tools and learn about structured development technologies, such as CASE tools and prototyping.
d) Study data design and resulting data relationships.  Students will learn how to establish the architecture of an application, develop an application based on its architecture, and design a specifications report.
e.) Address how the writing, testing, and documenting of software are used as fundamentals of the new system.  Students will learn how to prepare a system evaluation report as an evaluation of system operations and the costs and benefits obtained.

Grading Information and Criteria:

Grades for this course will be based on a 1000-point scale, as indicated below:
Mid Term exam:                        250 points
Research Project - written document:  200 points
Project Presentation - in class, with the use of tools such as Power Point:                  150 points
Final exam:                           300 points
Quizzes:                              100 points

And will be assigned as follows:
A 900 to 1000
B 800 to 899
C 700 to 799
D 600 to 699
F Less than 600

Other Information:

Homework/Project - homework is expected to be turned in on time.
If a student is unable to submit the homework on time due to work related circumstances or circumstances out of the student's control, then it is the student's responsibility to make an agreeable written arrangement with the instructor prior to the corresponding deadline.
Grades on homework/projects submitted after the due date will be reduced by according to the table below. Appropriate documentation will be required.
1-7 days late     - 10%
7-14 days late    - 20%
Over 14 days late - 40%

Project Descriptions:

Project I
Students are required to develop a Course Glossary of " at least" 100 terms.
The purpose of the assignment is to have students monitor their learning. The terms included in the glossary should be terms new to them and defined/explained in their own words. For the more experienced students they can use familiar terms but explained in more depth.

Project II
A group project which asks the students to work on one of the textbook cases.
Students are asked to either use the OO aproach or the traditional approach. They are also asked to develop a case summary describing the issues their group addressed as they analyzed and developed the case.

Academic Policies:

Cases of plagiarism are handled consistent with current UMUC guidelines.
See the UMUC policies at the following URL:
http://www.umuc.edu/policy/

Course Schedule:

Session Topic Reading Assignment

Session 1
The Job of Systems Analyst - Ch. 1

Session 2
The Systems Development Life Cycle - Ch. 2

Session 3
The responsibilities of a project manager - Ch. 3
Approaches to System Development - Appendix A

Session 4
Investigating System Requirements - Ch. 4

Session 5
Modeling System Requirements - Ch. 5
Appendix C

Session 6
Modeling System Requirements - Ch. 6
Appendix B

Session 7
The Object-Oriented Approach to Requirements - Ch.7 (p.216-236)
Review for Mid-Term

Session 8
Midterm Exam
(material covered up through the end of class 6 )

Session 9
Environments, Alternatives, and Decisions - Ch. 8

Session 10
Moving to design - Ch. 9

Session 11
More on design & Human Computer Interaction - Ch. 9, Ch. 12

Session 12
Designing Databases - Ch.10

Session 13
Case study presentations

Session 14
Case study presentations

Session 15
Review for final exam
Course Evaluation

Session 16
Final Exam - Comprehensive
Accreditation | Contact Us | Catalogs | Worldwide Locations | Press Room | Nondiscrimination |  ©2008