Cmgt 555

|[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. PoliciesFaculty 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. Pol icies 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. Software 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). ASP. net architectu re. 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).Choosing mobile phone operating systems. Faulkner Information Services. Nicolaisen, N. (2010). Developing mobile applications. Faulkner Information Services. Nicolaisen, N. (2010). Open source development platforms. Faulkner Information Services. Woodward, K. (2010). Project management planning and scheduling. Faulkner Information Services. Woodward, K. (2009). Project management software market trends. Faulkner Information Services. Woodward, K. (2010). Setting project goals and measuring performance. Faulkner Information Services. Woodward, K. (2010). Service oriented architecture. Faulkner Information Services. All electronic materials ar e available on the student website. Week One: Systems Development (2/19 – 2/25) | | |Details |Due |Points | |Objectives |Define the systems development life cycle. | | | | |Examine systems development methodologies. | | | |Course Preparation |Read the course description and objectives. | | | | |Ensure you have access to the required and recommended software: | | | | | | | | | Microsoft Visio (Recommended) | | | | | | | | | |Review the Learning Team Toolkit. | | | |Readings |Read Ch. 1, â€Å"Systems, Roles, and Development Methodologies,† of Systems Analysis and Design. | | | | |Read Appendix B, â€Å"Agile Methodologies,† of Essentials of Systems Analysis and Design. | | | | |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class discussion. 2/25 |2 | |Discussion Questions |Respond to weekly discussion questions. |2/21 |2 | |Learning Team Instructions |Complete the Learning Team Charter. | | | | | | | | | |The Learning T eam will complete Service Request SR-rm-004, Analyze HR System. Create an 8–16 | | | | |page report of the project that includes the requested business requirements definition for | | | | |the development of an HR system.Also create a Microsoft PowerPoint ® presentation of the | | | | |project. The report and presentation are due in Week Six. | | | | | | | | | |The report should contain: | | | | | | | | | |An executive summary that eveals the areas of the business to be improved, identifies the | | | | |purpose of the project, and lists the stakeholders associated with the project | | | | | | | | | |An identification of the business requirements of the service request | | | | | | | | | |An articulation of the business requirements in terms of specific processes or business | | | | |development needs | | | | | | | | | |The implementation approach for the project | | | Week Two: Systems Analysis (2/26 – 3/4) | | |Details |Due |Points | |Objectives | | | | | |Explain sc ope and feasibility. | | | | |Define systems analysis and systems requirements. | | | |Readings |Read Ch. 3, â€Å"Project Management,† of Systems Analysis and Design. | | | | |Read Ch. 5, â€Å"Determining System Requirements,† of Essentials of Systems Analysis and Design. | | | | |Read Ch. , â€Å"Structuring System Requirements: Process Modeling,† of Essentials of Systems | | | | |Analysis and Design. | | | | |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class discussion. |3/4 |2 | |Discussion Questions |Respond to weekly discussion questions. |2/28 |2 | |Learning Team Instructions |Begin work on Service Request SR-rm-004, Analyze HR System. |3/4 |2 | | |Prepare a 2–4 page Executive Summary of the project. | | |Individual |Select a system for development that would benefit your workplace. Prepare a 2–3 page plan |3/4 |10 | |Systems Development Paper |for determining the feasibility of the systems deve lopment. | | | |Week Three: Systems Design (3/5 – 3/11) | | |Details |Due |Points | |Objectives | | | | | |Define design specifications. | | | |Explain human computer interaction. | | | |Readings |Read Ch. 7, â€Å"Moving Into Design,† of Systems Analysis & Design. | | | | |Read Ch. 8, â€Å"Architecture Design,† of Systems Analysis & Design. | | | | |Read Ch. 8, â€Å"Designing the Human Interface,† of Essentials of Systems Analysis and Design. | | | | |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class discussion. 3/11 |2 | |Discussion Questions |Respond to weekly discussion questions. |3/7 |2 | |Learning Team Instructions |Continue work on Service Request SR-rm-004. |3/11 |2 | | |Prepare a 2–4 page identification of the business requirements of the service request. | | | |Individual |Prepare a 2–3 page plan for gathering requirements. Build on the systems development selected|3/11 |10 | |Requir ements Paper |in Week Two. Begin gathering the requirements for the project.State any assumptions you | | | | |make. State the difficulties of gathering the requirements. | | | |Week Four: Systems Development and Implementation (3/12 – 3/18) | | |Details |Due |Points | |Objectives | | | | | |Analyze development. | | | | |Analyze implementation. | | | |Identify methods of information system security. | | | |Readings |Read Ch. 12, â€Å"Moving Into Implementation,† of Systems Analysis & Design. | | | | |Read Ch. 16, â€Å"Quality Assurance and Implementation,† of Systems Analysis and Design. | | | | |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class discussion. |3/18 |2 | |Discussion Questions |Respond to weekly discussion questions. 3/14 |2 | |Learning Team Instructions |Continue work on Service Request SR-rm-004. |3/18 |2 | | |Prepare a 2–4 page section of the report that will use process flow charts, procedur es, | | | | |and/or policy statements to articulate the business requirements in terms of specific process| | | | |or business development needs. | | | |Individual |Prepare a 3–5 page requirements document for the systems development selected in Week Two. 3/18 |15 | |Requirements Document |Include the following areas of analysis: | | | | | | | | | |Technical: Describe any proposed hardware and software requirements. | | | | |Performance: Specify expected response time and/or throughput requirements. | | | | |Usability: Describe the human-computer interface, documentation, any new procedures, etc. | | | |Reliability: Define requirements for system dependability, such as up-time, error detection, | | | | |etc. | | | | |Security: Identify user access requirements and conditions under which access may be granted. | | | |Week Five: Maintenance (3/19 – 3/25) | | |Details |Due |Points | |Objectives | | | | | |Identify types of maintenance. | | |Readings |Read Ch. 10, â€Å" Systems Implementation and Operation,† of Essentials of Systems Analysis and | | | | |Design. | | | | |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class discussion. |3/25 |2 | |Discussion Questions |Respond to weekly discussion questions. |3/21 |2 | |Learning Team Instructions |Continue work on Service Request SR-rm-004. 3/25 |2 | | | | | | | |Prepare a 2–4 page section of the report that will identify the implementation approach for | | | | |the project. The implementation approach should identify software testing and installation | | | | |activities as well as the training consideration. Include, also, the identification of the | | | | |training method(s) and the audience to be trained. | | | | | | | | |Begin work on PowerPoint ® presentation of the project. | | | |Individual |Prepare a Request for Proposal (RFP) for the design and implementation of the systems |3/25 |15 | |Request for Proposal |development selected in W eek Two. The outline guides the type of information that should be | | | | |included in a RFP. | | | | | | | | |RFP | | | | | | | | | |Introduction | | | | | | | | | |Description of company, including type of organizational structure | | | | |Business goals | | | | |Project goals | | | | |Scope of project | | | | |Time constraints | | | | |Budget constraints | | | | |Other | | | | | | | | | |Requirements | | | | | | | | | |Technical: | | | | | | | | |Standards | | | | |Existing system | | | | |Hardware | | | | |Operating systems | | | | |Networking | | | | |Application software | | | | |Communications | | | | |Security | | | | |Scalability | | | | |Availability | | | | |Reliability | | | | |Maintenance | | | | |Disaster recovery | | | | |Other | | | | | | | | | |Training /Documentation | | | | |Installation issues | | | |Cost | | | | |Other | | | | |Administrative Information | | | | | | | | | |Who may apply | | | | |How to apply | | | | |Confidentiality | | | | |Refer ences | | | | |How to get clarification | | | | |Proposal format | | | | |Submission schedule | | | | |Decision schedule | | | | |Selection criteria | | | | |Other | | | |Week Six: Development Standards (3/26 – 4/1) | | |Details |Due |Points | |Objectives | | | | | |Examine development standards. | | | | |Apply systems analysis. | | |Readings |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class discussion. | | | |Discussion Questions |Respond to weekly discussion questions. | | | |Learning Team |Complete work on Service Request SR-rm-004. |4/1 |12 | |Report |Finalize and submit the 8–16 page paper summarizing the project proposal. | | | |Learning Team |Finalize and submit the PowerPoint ® presentation of the project. 4/1 |10 | |Presentation | | | | Optional Discussion Questions Week One Discussion Questions †¢ Describe at least one risk inherent in each phase of the SDLC. †¢ Based on Hugos’ 2008 article, what is the relationship between IT infrastructure and new development? Which one comes first, or can they be built in tandem? †¢ Based on the Greiner (2010) article, how has the Ajax development methodology influenced the SDLC for developing Web-based customer facing applications? †¢ Based on the Greiner (2010) article, how has the ASP. NET facility of the Visual Studio. NET methodology influenced the SDLC for developing Web-Based customer-facing applications?How would you compare Ajax with ASP. NET? Week Two Discussion Questions †¢ Based on Gould’s (2008) article, what is the main attraction for open source ERP? †¢ Based on the Grenier (2011) article, what do you think is the largest benefit and the largest drawback for using mobile devises in the workplace? Consider extensibility, integration, manageability, security, etc. Week Three Discussion Questions †¢ Based on Brache’s 2008 article, what are the three ways a business process is conside red an innovation lever? †¢ Based on the Nicolaisen (2010) article, what accounts for the increased reliance on open source development methodologies to develop new application solutions?Do you think proprietary development methodologies are loosing market share? †¢ Based on the Greiner (2010) article, how has Java-based application development technology influenced the growth and acceptance of open source development platforms? Week Four Discussion Questions †¢ According to Chisckowski’s (2008) article, what are some of the advantages of incorporating security measures into the design and implementation of information systems? What obstacles may be encountered? †¢ Based on the Woodward (2010) article, how should unpredictable delays, failures on the part of third parties, and other obstacles accommodated by the traditional SDLC? Week Five Discussion Questions Based on the Woodward (2010) article, why is measuring project performance in a way that is agree d on by all stakeholders essential for securing agreement that the application solution meets business goals? †¢ Based on the Woodward (2009) article, how has measuring project performance been affected by portfolio management systems that view projects across the entire enterprise for securing agreement that the application solution meets business goals? Week Six Discussion Questions †¢ Based on the Woodward (2010) article, how has service oriented architecture (SOA) provided efficiencies in the design, development, implementation, and deployment of applications? Based on the Greiner (2009) article, how has outsourcing the enterprise development provided efficiencies in the design, development, implementation and deployment of applications? Copyright University of Phoenix ® is a registered trademark of Apollo Group, Inc. in the United States and/or other countries. Microsoft ®, Windows ®, and Windows NT ® are registered trademarks of Microsoft Corporation in the U nited States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective companies. Use of these marks is not intended to imply endorsement, sponsorship, or affiliation. Edited in accordance with University of Phoenix ® editorial standards and practices.