Cmgt 555

Topics: Systems Development Life Cycle, Requirements analysis, Project management Pages: 17 (2068 words) Published: March 24, 2013
|[pic] |Course Syllabus | | |College of Information Systems & Technology | | |CMGT/555 Version 10 | | |2/19/2013 - 4/1/2013 | | |Systems Analysis and Development |

Copyright © 2010, 2009, 2008, 2006, 2005 by University of Phoenix. All rights reserved.

Course Description

This course provides a background in analysis and design techniques for business system and application development. Although the Systems Development Life Cycle (SDLC) is fundamental to the course, other methodologies and tools are examined from a managerial perspective.


Faculty and students/learners will be held responsible for understanding and adhering to all policies contained within the following two documents:

• University policies: You must be logged into the student website to view this document. • Instructor policies: This document is posted in the Course Materials forum.

University policies are subject to change. Be sure to read the policies at the beginning of each class. Policies may be slightly different depending on the modality in which you attend class. If you have recently changed modalities, read the policies governing your current class modality.

Course Materials

Dennis, A., Wixom, B. H., & Roth, R. M. (2009). Systems analysis and design (4th ed.). John Wiley & Sons, Inc.

Kendall, K. E., & Kendall, J. E. (2011). Systems analysis and design (8th ed.). Prentice Hall.

Valacich, J. S., George, J. F., & Hoffer, J. A. (2009). Essentials of systems analysis and design (4th ed.). Prentice Hall.


Microsoft Visio® (Recommended)

Supplemental Resources

Element K. (2010). Introduction to Software Life Cycle Models.

Element K. (2010). The Fundamentals of Requirements Elicitation (Inquestra) (Part 1 of 8).

Element K. (2010). Determining a Project's Objectives (Inquestra) (Part 2 of 8).

Element K. (2010). Defining Project Scope (Inquestra) (Part 3 of 8).

Element K. (2010). Describing Business Process (Inquestra) (Part 4 of 8).

Element K. (2010). Determining Information Requirements (Inquestra) (Part 5 of 8).

Element K. (2010). Describing Functional Business Requirements (Inquestra) (Part 6 of 8). Element K. (2010). Documenting Requirements Meetings (Inquestra) (Part 7 of 8).

Element K. (2010). Eliciting Data Warehouse Requirements (Inquestra) (Part 8 of 8).

Article References

Bather, M. (2007/2008, December/January). Put your data where your work is. Supply & Demand Chain Executive, 9(1), 22.

Brache, A. P. (2008, January). Nine variables affect innovation within today's Enterprise Model. Tooling & Production, 74(1), 16.

Chisckowski, E. (2008, November). Built-in security. Baseline, (90), 36-38.

Gotterbarn, D., & Miller, K. (2010). Unmasking your software’s ethical risks. IEEE Software, 27(1), 12.

Gould, L. S. (2008, January). On-demand ERP is here. Automotive Design & Production, 120(1), 46-48.

Grenier, L. (2010). AJAX web development techniques. Faulkner Information Services.

Greiner, L. (2010). architecture. Faulkner Information Services.

Grenier, L. (2010). Java-based application development technology. Faulkner Information Services.

Grenier, L. (2009). Outsourcing the Enterprise development project. Faulkner Information Services.

Hugos, M. H. (2008, January 7). Calling on IT to do the impossible. Computerworld, 42(2), 21.

Nicolaisen, N. (2010)....
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • 555 Paper
  • CMGT 555 Week 5 DQs Essay
  • ACC 555 Essay
  • CMGT 555 Week 2 Team Project Plan Essay
  • CMGT 555 Week 5 Individual Paper
  • CMGT Project Budget Paper
  • Week Four CMGT 400 Essay
  • CMGT 400 Entire Course Essay

Become a StudyMode Member

Sign Up - It's Free