Cmgt 555

pic Course Syllabus College of training frames & Technology CMGT/555 mutant 10 2/19/2013 4/1/2013 Systems psychoanalysis and growing Copyright 2010, 2009, 2008, 2006, 2005 by University of capital of Arizona. All rights reserved. Course Description This course provides a background in summary and propose techniques for task governance and activity learning. Although the Systems teaching smell Cycle (SDLC) is fundamental to the course, different methodologies and tools atomic number 18 examined from a managerial perspective. PoliciesFaculty and scholars/learners go out be held responsible for understanding and adhering to all policies contained deep down the following two memorandums 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 atomic number 18 subject to change. Be sure to read the policies at the beginning of ea ch level. Policies may be slightly different depending on the modality in which you attend class. If you ease up 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 musical arrangements analysis and design (4th ed. ). Prentice Hall. Software Microsoft Visio (Recommended) Supplemental Re get-gos factor K. (2010). mental home to Software Life Cycle Models. Element K. (2010). The Fundamentals of Requirements Elicitation (Inquestra) (Part 1 of 8). Element K. (2010). ascertain a communicates Objectives (Inquestra) (Part 2 of 8). Element K. (2010). Defining Project orbital cavity (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). instrumenting 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 flow is. Supply & Demand Chain Executive, 9(1), 22. Brache, A. P. (2008, January). Nine variables affect conversion within todays 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 softwares 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 phylogenesis techniques. Faulkner Information proces ss. Greiner, L. (2010). ASP. net architecture. Faulkner Information Services. Grenier, L. (2010). Java-based exertion ontogenesis technology. Faulkner Information Services. Grenier, L. (2009). Outsourcing the Enterprise development project. Faulkner Information Services. Hugos, M. H. (2008, January 7). call on IT to do the impossible. Computerworld, 42(2), 21. Nicolaisen, N. (2010).Choosing mobile ph wholeness operating systems. Faulkner Information Services. Nicolaisen, N. (2010). develop mobile applications. Faulkner Information Services. Nicolaisen, N. (2010). Open source development platforms. Faulkner Information Services. Woodward, K. (2010). Project management externalisening and scheduling. Faulkner Information Services. Woodward, K. (2009). Project management software trade trends. Faulkner Information Services. Woodward, K. (2010). Setting project goals and measuring slaying. Faulkner Information Services. Woodward, K. (2010). Service orient architecture. Faulkner I nformation Services. All electronic materials are available on the student website. workweek One Systems Development (2/19 2/25) Details due Points Objectives ready the systems development life cycle. Examine systems development methodologies. Course education take in the course description and objectives. Ensure you have access to the indispensable and recommended software Microsoft Visio (Recommended) Review the acquire Team Toolkit. Readings Read Ch. 1, Systems, Roles, and Development Methodologies, of Systems compendium and Design. Read Appendix B, Agile Methodologies, of Essentials of Systems compend and Design. Read this weeks Electronic moderate Readings. date record in class preaching. 2/25 2 reciprocation Questions Respond to weekly discussion questions. 2/21 2 encyclopaedism Team Instructions Complete the erudition Team Charter. The Learning Team will complete Service necessitate SR-rm-004, decomp ose HR System. Create an 816 rascal authorship of the project that includes the requested business requirements definition for the development of an HR system.Also fabricate 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 conjugation of the business requirements in terms of specific processes or business development needs The execution approach for the project Week Two Systems Analysis (2/26 3/4) Details payable Points Objectives Explain scope and feasibility. Define systems analysis and systems requirements. Readings Read Ch. 3, Project Management, of Systems Analysis and Desig n. 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 weeks Electronic Reserve Readings. Participation Participate in class discussion. 3/4 2 raillery Questions Respond to weekly discussion questions. 2/28 2 Learning Team Instructions set down work on Service require SR-rm-004, Analyze HR System. 3/4 2 correct a 24 page Executive Summary of the project. Individual Select a system for development that would benefit your workplace. mark a 23 page plan 3/4 10 Systems Development Paper for determining the feasibility of the systems development. Week Three Systems Design (3/5 3/11) Details Due Points Objectives Define design specifications. Explain human computer interaction. Readings Read Ch. 7, locomote Into Design, of Systems Analysis & Design. Read Ch. 8, Architecture Design, of Systems Analysis & Design. Read Ch. 8, Designing the military personnel Interface, of Essentials of Systems Analysis and Design. Read this weeks Electronic Reserve Readings. Participation Participate in class discussion. 3/11 2 sermon 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 24 page identification of the business requirements of the service request. Individual Prepare a 23 page plan for gathering requirements. Build on the systems development selected3/11 10 Requirements Paper in Week Two. Begin gathering the requirements for the project.State any assumptions you make. State the difficulties of gathering the requirements. Week quadruple 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, Mov ing Into Implementation, of Systems Analysis & Design. Read Ch. 16, Quality Assurance and Implementation, of Systems Analysis and Design. Read this weeks 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 24 page section of the report that will use process flow charts, procedures, and/or policy statements to articulate the business requirements in terms of specific process or business development needs. Individual Prepare a 35 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 computer hardware and software requirements. Performance Specify expected response time and/or throughput requirements. Usability Describe the human-comput er interface, documentation, any new procedures, etc. Reliability Define requirements for system dependability, such as up-time, error detection, etc. Security Identify drug user access requirements and conditions under which access may be granted. Week quintette 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 weeks 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 24 page section of the report that will identify the implementation approach for the project. The implementation approach should identify software testing and readiness activities as well as the training consideration. Include, als o, 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 Week Two. The define 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 availableness Reliability Maintenance Disaster recovery Other Training / credential Installation issues Cost Other Administra tive Information Who may throw How to apply Confidentiality References How to get clarification Proposal format Submission enrolment Decision schedule Selection criteria Other Week Six Development Standards (3/26 4/1) Details Due Points Objectives Examine development standards. oblige systems analysis. Readings Read this weeks 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 hold the 816 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. found on Hugos 2008 article, what is the relationship between IT infrastruc ture 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 comparing Ajax with ASP. NET? Week Two Discussion Questions Based on Goulds (2008) article, what is the main attraction for rotate source ERP? Based on the Grenier (2011) article, what do you commemorate is the largest benefit and the largest drawback for using mobile devises in the workplace? assure extensibility, integration, manageability, security, etc. Week Three Discussion Questions Based on Braches 2008 article, what are the three bearings a business process is considered an intro 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 Chisckowskis (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(a) 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 agreed 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 opening move 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 United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective companies. lend oneself of these marks is not intended to imply endorsement, sponsorship, or affiliation. Edited in accordance with University of Phoenix editorial standards and practices.