39717843

|[pic] |Course Syllabus | | |College of Information Systems , Technology | | |CMGT/555 Variation 10 | | |2/19/2013 , 4/1/2013 | | |Systems Research and Development | Copyright © 2010, 2009, 2008, 2006, june 2006 by College or university of Phoenix. All rights reserved. Study course Description This program provides a qualifications in examination and design techniques for organization system and application creation.

Although the Systems Development Lifestyle Cycle (SDLC) is primary to the training course, other methodologies and equipment are examined from a managerial perspective. Policies

Teachers and students/learners will be held accountable for understanding and adhering to all procedures contained inside the following two documents: • University policies: You must become logged in the student site to view this document. • Instructor procedures: This document is posted in the Course Supplies forum. College or university policies happen to be subject to transform. Be sure to browse the policies at the beginning of each class. Policies might be slightly different with respect to the modality in which you attend course. If you have recently changed strategies, read the policies governing your existing class technique. Course Supplies Dennis, A., Wixom, W. H., , Roth, Ur. M. (2009). Systems evaluation and design and style (4th male impotence. ). Ruben Wiley , Sons, Incorporation. Kendall, T. E., , Kendall, T.

E. (2011). Systems examination and design (8th impotence. ). Prentice Hall. Valacich, J. S., George, M. F., , Hoffer, M. A. (2009). Essentials of systems analysis and style (4th education. ). Prentice Hall. Software program Microsoft Visio® (Recommended) Extra Resources Aspect K. (2010). Introduction to Application Life Routine Models. Component K. (2010). The Fundamentals of Requirements Elicitation (Inquestra) (Part 1 of 8). Component K. (2010). Determining a Project’s Targets (Inquestra) (Part 2 of 8). Component K. (2010). Defining Project Scope (Inquestra) (Part 3 of 8). Element E. (2010). Describing Business Method (Inquestra) (Part 4 of 8). Aspect K. (2010).

Determining Info Requirements (Inquestra) (Part 5 of 8). Element E. (2010). Talking about Functional Business Requirements (Inquestra) (Part six of 8). Element E. (2010). Documenting Requirements Gatherings (Inquestra) (Part 7 of 8). Element K. (2010). Eliciting Data Warehouse Requirements (Inquestra) (Part 8 of 8). Document References Bather, M. (2007/2008, December/January). Place your data where your work is usually. Supply , Demand String Executive, 9(1), 22. Brache, A. S. (2008, January). Nine factors affect advancement within this Enterprise Version. Tooling , Production, 74(1), 16. Chisckowski, E. (2008, November). Integrated security. Baseline, (90), 36-38. Gotterbarn, D. , Callier, K. (2010). Unmasking your software’s moral risks. IEEE Software, 27(1), 12. Gould, L. T. (2008, January). On-demand ERP is here. Automobile Design , Production, 120(1), 46-48. Grenier, L. (2010). AJAX web design techniques. Faulkner Information Solutions. Greiner, L. (2010). OR NET. net structure. Faulkner Data Services. Grenier, L. (2010). Java-based program development technology. Faulkner Data Services. Grenier, L. (2009). Outsourcing the Enterprise expansion project. Faulkner Information Solutions. Hugos, M. H. (2008, January 7). Calling on IT to do the impossible. Computerworld, 42(2), twenty one. Nicolaisen, In. (2010).

Selecting mobile phone systems. Faulkner Information Services. Nicolaisen, N. (2010). Developing mobile applications. Faulkner Information Companies. Nicolaisen, And. (2010). Open source development platforms. Faulkner Data Services. Woodward, K. (2010). Project managing planning and scheduling. Faulkner Information Solutions. Woodward, E. (2009). Task management software marketplace trends. Faulkner Information Providers. Woodward, E. (2010). Environment project desired goals and testing performance. Faulkner Information Providers. Woodward, K. (2010). Services oriented structures. Faulkner Info Services. All electronic components are available on the student internet site. Week One particular: Systems Creation (2/19 – 2/25) | | |Details |Due |Points | |Objectives |Define the systems advancement life routine. | | | | |Examine systems development strategies. | | | |Course Preparation |Read the study course description and objectives. | | | | |Ensure you have usage of the required and recommended software: | | | | | | | | | Microsoft Visio (Recommended) | | | | | | | | | |Review the Learning Staff Toolkit. | | | |Readings |Read Ch. you, “Systems, Jobs, and Creation Methodologies, ” of Devices Analysis and Design. | | | | |Read Appendix M, “Agile Strategies, ” of Essentials of Systems Analysis and Design. | | | | |Read this kind of week’s Electronic digital Reserve Readings. | | | |Participation |Participate in the lecture discussion. 2/25 |2 | |Discussion Inquiries |Respond to weekly dialogue questions. |2/21 |2 | |Learning Group Instructions |Complete the Learning Staff Charter. | | | | | | | | | |The Learning Team will certainly complete Service Request SR-rm-004, Analyze HUMAN RESOURCES System. Make an 8–16 | | | | |page statement of the task that includes the requested business requirements definition for | | | | |the development of an HR system.

Also build a Microsoft PowerPoint® presentation in the | | | | |project. The report and presentation are due in Week Half a dozen. | | | | | | | | | |The report will need to contain: | | | | | | | | | |An business summary that eveals areas of the organization to be increased, identifies the | | | | |purpose in the project, and lists the stakeholders linked to the project | | | | | | | | | |An identification of the organization requirements of the service request | | | | | | | | | |An articulation from the business requirements in terms of certain processes or perhaps business | | | | |development needs | | | | | | | | | |The implementation approach for the job | | | Week Two: Systems Analysis (2/26 – 3/4) | | |Details |Due |Points | |Objectives | | | | | |Explain scope and feasibility. | | | | |Define devices analysis and systems requirements. | | | |Readings |Read Ch. 3, “Project Management, ” of Devices Analysis and Design. | | | | |Read Ch. your five, “Determining Program Requirements, ” of Basics of Systems Analysis and Design. | | | | |Read Ch., “Structuring System Requirements: Process Building, ” of Essentials of Systems | | | | |Analysis and Style. | | | | |Read this week’s Electronic digital Reserve Blood pressure measurements. | | | |Participation |Participate in the lecture discussion. |3/4 |2 | |Discussion Inquiries |Respond to weekly discussion questions. |2/28 |2 | |Learning Staff Instructions |Begin work on Service Request SR-rm-004, Analyze HR System. |3/4 |2 | | |Prepare a 2–4 page Executive Summary from the project. | | |Individual |Select something for development that would profit your place of work. Prepare a 2–3 page strategy |3/4 |10 | |Systems Development Daily news |for identifying the feasibility of the devices development. | | | |Week 3: Systems Style (3/5 – 3/11) | | |Details |Due |Points | |Objectives | | | | | |Define design specifications. | | | |Explain human computer interaction. | | | |Readings |Read Ch. six, “Moving In Design, ” of Devices Analysis , Design. | | | | |Read Ch. almost eight, “Architecture Design, ” of Systems Analysis , Design. | | | | |Read Ch. 8, “Designing the Human Program, ” of Essentials of Systems Examination and Style. | | | | |Read this kind of week’s Electronic digital Reserve Psychic readings. | | | |Participation |Participate in class discussion. 3/11 |2 | |Discussion Queries |Respond to weekly discussion questions. |3/7 |2 | |Learning Crew Instructions |Continue work on Services Request SR-rm-004. |3/11 |2 | | |Prepare a 2–4 site identification in the business requirements of the assistance request. | | | |Individual |Prepare a 2–3 page plan for gathering requirements. Build on the systems development selected|3/11 |10 | |Requirements Paper |in Week Two. Begin gathering the requirements to get the task.

State any kind of assumptions you | | | | |make. Condition the difficulties of gathering the requirements. | | | |Week Four: Devices Development and Implementation (3/12 – 3/18) | | |Details |Due |Points | |Objectives | | | | | |Analyze advancement. | | | | |Analyze implementation. | | | |Identify methods of info system reliability. | | | |Readings |Read Ch. 12, “Moving Into Implementation, ” of Systems Evaluation , Design. | | | | |Read Ch. 16, “Quality Assurance and Implementation, ” of Systems Analysis and Design. | | | | |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class debate. |3/18 |2 | |Discussion Questions |Respond to each week discussion inquiries. 3/14 |2 | |Learning Team Guidance |Continue focus on Service Request SR-rm-004. |3/18 |2 | | |Prepare a 2–4 page part of the report that will work with process movement charts, types of procedures, | | | | |and/or plan statements to articulate the business requirements regarding specific process| | | | |or business expansion needs. | | | |Individual |Prepare a 3–5 page requirements document pertaining to the systems development selected in Week Two. 3/18 |15 | |Requirements Doc |Include the following areas of examination: | | | | | | | | | |Technical: Describe any kind of proposed software and hardware requirements. | | | | |Performance: Specify predicted response period and/or throughput requirements. | | | | |Usability: Describe the human-computer software, documentation, any new methods, etc . | | | |Reliability: Determine requirements to get system dependability, such as up-time, error detection, | | | | |etc. | | | | |Security: Identify user access requirements and circumstances under which will access might be granted. | | | |Week Five: Maintenance (3/19 – 3/25) | | |Details |Due |Points | |Objectives | | | | | |Identify types of repair. | | |Readings |Read Ch. 10, “Systems Setup and Procedure, ” of Essentials of Systems Research and | | | | |Design. | | | | |Read this week’s Electronic digital Reserve Readings. | | | |Participation |Participate in class discussion. |3/25 |2 | |Discussion Queries |Respond to weekly discussion questions. |3/21 |2 | |Learning Team Instructions |Continue work on Support Request SR-rm-004. 3/25 |2 | | | | | | | |Prepare a 2–4 page section of the record that will discover the rendering approach intended for | | | | |the task. The execution approach should identify software testing and installation | | | | |activities as well as the teaching consideration. Incorporate, also, the identification with the | | | | |training method(s) and the market to be qualified. | | | | | | | | |Begin focus on PowerPoint® presentation of the task. | | | |Individual |Prepare a Request for Pitch (RFP) for the design and execution of the systems |3/25 |15 | |Request for Pitch |development picked in Week Two. The outline tutorials the type of information that should be | | | | |included in a RFP. | | | | | | | | |RFP | | | | | | | | | |Introduction | | | | | | | | | |Description of company, including type of company structure | | | | |Business goals | | | | |Project goals | | | | |Scope of task | | | | |Time limitations | | | | |Budget limitations | | | | |Other | | | | | | | | | |Requirements | | | | | | | | | |Technical: | | | | | | | | |Standards | | | | |Existing program | | | | |Hardware | | | | |Operating systems | | | | |Networking | | | | |Application application | | | | |Communications | | | | |Security | | | | |Scalability | | | | |Availability | | | | |Reliability | | | | |Maintenance | | | | |Disaster recovery | | | | |Other | | | | | | | | | |Training /Documentation | | | | |Installation issues | | | |Cost | | | | |Other | | | | |Administrative Information | | | | | | | | | |Who may apply | | | | |How to apply | | | | |Confidentiality | | | | |References | | | | |How to get clarification | | | | |Proposal format | | | | |Submission schedule | | | | |Decision schedule | | | | |Selection criteria | | | | |Other | | | |Week Six: Advancement Standards (3/26 – 4/1) | | |Details |Due |Points | |Objectives | | | | | |Examine expansion standards. | | | | |Apply systems evaluation. | | |Readings |Read this week’s Electronic Reserve Readings. | | | |Participation |Participate in class conversation. | | | |Discussion Questions |Respond to each week discussion concerns. | | | |Learning Team |Complete work on Assistance Request SR-rm-004. |4/1 |12 | |Report |Finalize and submit the 8–16 webpage paper summarizing the task proposal. | | | |Learning Group |Finalize and submit the PowerPoint® business presentation of the task. 4/1 |10 | |Presentation | | | | Optional Discussion Questions Week One Conversation Questions • Describe at least a single risk inherent in every phase with the SDLC. • Based on Hugos’ 2008 article, what is the relationship between THIS infrastructure and new creation? Which one comes first, or will they be constructed in tandem? • Based on the Greiner (2010) article, just how has the Ajax development methodology influenced the SDLC intended for developing Web-affiliated customer facing applications? • Based on the Greiner (2010) article, just how has the ASP. NET facility of the Image Studio. NET methodology affected the SDLC for expanding Web-Based customer-facing applications?

How would you evaluate Ajax with ASP. NET? Week Two Discussion Inquiries • Depending on Gould’s (2008) article, what is the main attraction for free ERP? • Based on the Grenier (2011) article, so what do you think may be the largest profit and the major drawback intended for using portable devises at work? Consider extensibility, integration, management, security, and so forth Week 3 Discussion Questions • Based upon Brache’s 08 article, exactly what the three ways a business procedure is considered a great innovation lever? • Depending on the Nicolaisen (2010) article, what makes up about the increased reliance upon open source expansion methodologies to formulate new software solutions?

Do you consider proprietary expansion methodologies happen to be loosing market share? • Based on the Greiner (2010) document, how features Java-based app development technology influenced the expansion and acceptance of free development programs? Week 4 Discussion Concerns • Relating to Chisckowski’s (2008) article, what are a number of the advantages of incorporating security procedures into the design and execution of information systems? What hurdles may be experienced? • Depending on the Woodward (2010) document, how should certainly unpredictable gaps, failures for third parties, and other obstacles accommodated by the classic SDLC? Week Five Discussion Questions Based on the Woodward (2010) content, why is measuring project overall performance in a way that is agreed on by all stakeholders essential for protecting agreement the application solution meets business goals? • Based on the Woodward (2009) article, how has calculating project functionality been impacted by portfolio supervision systems that view jobs across the whole enterprise pertaining to securing agreement that the application solution complies with business desired goals? Week Six Discussion Inquiries • Based on the Woodward (2010) document, how provides service oriented architecture (SOA) provided efficiencies in the style, development, setup, and deployment of applications? Based on the Greiner (2009) article, how has outsourcing techniques the venture development supplied efficiencies inside the design, creation, implementation and deployment of applications? Copyright University of Phoenix® is actually a registered brand of Apollo Group, Inc. in the United States and other countries. Microsoft®, Windows®, and Windows NT® are registered art logos of Microsoft company Corporation in the usa and/or various other countries. Other company and product names are logos or registered trademarks of their respective firms. Use of these kinds of marks can be not intended to imply validation, sponsorship, or affiliation. Edited in accordance with School of Phoenix® editorial standards and procedures.