Your manager has tasked you with developing a proposed approach for implementing an ERP system in your organization. The proposed approach will be submitted in three milestones:Milestone 2 - System Diagram and Information System Personnel ConsiderationsReview the requirements for this Portfolio Project in Module 8, then proceed with Milestone 2.For this milestone, you are required to submit a system diagram of the ERP system. The design should contain the databases, software application areas, and the business user groups which will use their respective software applications. ERP software applications normally are categorized by business function, e.g. Human Resources, Accounting and Finance, Supply Chain Management, and Sales and Marketing (which includes Customer Relationship Management). Your deliverable should also contain a discussion of the rationale behind inclusion of each of the components in your system diagram.The second part of this assignment is an analysis of considerations for information systems personnel regarding the implementation of this new system. Examples of considerations are staffing levels and training. Ensure you provide justifications for why these considerations are important.Your Milestone 2 deliverable should be at least 4-5 pages (excluding the title and reference pages) and written according to the CSU Global Writing Center (Links to an external site.). The paper should be supported by at least one credible reference not including the textbook. Review the Milestone Rubric below for specific grading criteria.

Assignment 2: The Presentation Due Week 10 and worth 200 points Congratulations. Your project has been staffed and you are about to meet with the team for the first time. Initial impressions are important and you’ll need visuals for your presentation. Create a slide show (in PowerPoint or similar software) in which you address the following, in this order: Goals: What the project hopes to accomplish. Critical Success Factors: Identify at least 4 different stakeholders; for each, list at least 2 things that the stakeholder requires in order to deem the project successful. Acquisition strategy: Should the system be built in-house, created by a contractor, purchased off- the-shelf and customized, or leased as a service? Explain your rationale. Resources: For in-house development, what people/skills are required and what development lifecycle do you recommend? Otherwise, identify 3 candidate organizations that can deliver the system. System functions: In a table format, summarize the types of users for the system; the business reason(s) each would use the system; the ways that the system supports each of these needs; and how this support differs from the current system. Connectivity: Provide a diagram that shows how the system will connect to the other information systems and what data flows among them. Security: List the most serious cybersecurity threats and vulnerabilities of the new system. Suggest strategies to address them. Mobility: Identify the system’s capabilities for mobile use. Include a title and summary slide. Use one slide for each of the 8 points above. Include speaker notes or audio narration that explains each slide more fully. Grading for this assignment will be based on answer quality, logic / organization of the paper, and language and writing skills, using the following rubric. Points: 200 Assignment 2: The Presentation Criteria Unacceptable Below 70% F Fair 70-79% C Proficient 80-89% B Exemplary 90-100% A 1. Goals: What the project hopes to accomplish. Weight: 10% (20 points) Did not communicate what the project hopes to accomplish Did not list project goals Communicated what the project hopes to accomplish Did not list project goals Communicated what the project hopes to accomplish Listed the project goals Communicated importance of project reaching its goals Connected project goals to the organizational strategy 2. Critical Success Did not identify 4 Identified 4 Identified 4 Identified and © 2017 Strayer University. All Rights Reserved. This document contains Strayer University Confidential and Proprietary information and may not be copied, further distributed, or otherwise disclosed in whole or in part, without the expressed written permission of Strayer University. CIS 500 Page 1 of 4 CIS 500 – Information Systems for Decision-Making Factors: Identify at least 4 different stakeholders; for each, list at least 2 things that stakeholder requires in order to deem the project successful. Weight: 10% (20 points) stakeholders Listed things to make project successful, but did not connect each stakeholder stakeholders Listed less than 2 things each stakeholder would require to deem project successful stakeholders Listed 2 things that each stakeholder would require to deem the project successful justified the selection of 4 stakeholders Explained why each stakeholder would be most interested in 2 things to deem project successful 3. Acquisition strategy: Should the system be built in-house, created by a contractor, purchased off-the-shelf and customized, or leased as a service? Explain the rationale for your choice. Weight: 10% (20 points) Did not compare acquisition strategies Did not determine the best strategy for the proposed information system Inadequately explained the rationale for choosing the acquisition strategy Reasonable comparison of acquisition strategies Determined best acquisition strategy for the proposed information system Somewhat explained the rationale for choosing the acquisition strategy Compared various acquisition strategies Determined which acquisition strategy would be the best for the proposed system Provided rationale for choosing a specific acquisition strategy Analyzed various acquisition strategies, or presented an acquisition strategy that was not previously mentioned Explained why other acquisition strategies would potentially not work Discussed cost considerations 4. Resources: For in- house development, what people/skills are required and what development lifecycle do you recommend? Otherwise, identify 3 candidate organizations that can deliver the system. Weight: 10% (20 points) Inadequately determined resources needed for the acquisition strategy Limited recommendation for development lifecycle for in- house development, or three external organizations that can deliver the system Inadequate justification Determined resources needed for the acquisition strategy, but did not justify reasoning Recommended a project development lifecycle for in- house development, or three external organizations that can deliver the system, but did not justify why they were chosen Determined and justified resources needed for chosen acquisition strategy Recommended a project development lifecycle for in- house development, or three external organizations that can deliver the system. Presented resources not previously considered Included risk identification and mitigation procedures Proposed a combination of resources and strategy to organize stakeholder efforts toward project completion 5. System functions: In a table format, summarize the types of users for the system; the business Failed to put in table format In table format: Summarized some In table format: Summarized the In table format: Analyzed user © 2017 Strayer University. All Rights Reserved. This document contains Strayer University Confidential and Proprietary information and may not be copied, further distributed, or otherwise disclosed in whole or in part, without the expressed written permission of Strayer University. CIS 500 Page 2 of 4 CIS 500 – Information Systems for Decision-Making reason(s) each would use the system; the ways that the system supports each of these needs; and how this support differs from the current system. Weight: 10% (20 points) Inadequate summary of users for the system Limited explanation of why users would use the system Inadequate description of how system supports users Inadequate comparison of the proposed system to the old system of the types of users for the system Somewhat explained business reasons for system use Somewhat described how the system supports users Reasonable comparison of the proposed system to the old information system types of users for the information system Explained business reasons why each user type would use the system Described how the system supports the needs of each user type Determined how this support differs from the current information system experience and user design considerations Explained design changes that took place between the old and new system Provided rationale for the user types identified Discussed how to reach out to user types to test the system 6. Connectivity: Provide a diagram that shows the other information systems this one will connect to, and what data flows among them. Weight: 10% (20 points) Failed to put in diagram format Inadequate diagram showing your system, hard to follow, incomplete Inadequate or hard to follow the data that would flow among systems, incomplete In a diagram: Showed other information systems that your system would connect to, but hard to follow Demonstrated what data would flow among systems, but hard to follow In a diagram: Showed other existing information systems that your proposed system would connect to Demonstrated what data would flow between your and other information systems. In a diagram: Showed how you selected existing systems that your system would connect to Explained how diagram would be updated and maintained based on changes in the marketplace 7. Security: List the most serious cybersecurity threats and vulnerabilities of the new system. Suggest strategies to address them. Weight: 10% (20 points) Inadequate list of cybersecurity threats Inadequate strategies to address each threat Reasonable list of cybersecurity threats, failed to show why they are most serious Identified strategies to address each threat Listed the most serious cybersecurity threats to your new system Proposed strategies to address each threat Proposed how your new system would integrate with Shadow IT, if at all Demonstrated strategies for current users to avoid threats 8. Mobility: Identify the system’s capabilities for mobile use. Weight: 10% Failed to identify your system’s capabilities for mobile use, incomplete Identified your system’s capabilities for mobile use, but not comprehensive Identified your system’s capabilities for mobile use Proposed situations in which mobile use would happen and situations where its limitations © 2017 Strayer University. All Rights Reserved. This document contains Strayer University Confidential and Proprietary information and may not be copied, further distributed, or otherwise disclosed in whole or in part, without the expressed written permission of Strayer University. CIS 500 Page 3 of 4 CIS 500 – Information Systems for Decision-Making (20 points) 9. Speaker / Audio Notes: Include speaker notes or audio narration that explains each slide more fully. Weight: 10% (20 points) Inadequate speaker notes or audio narration, too much or too little information on each slide provided Somewhat detailed speaker notes or audio narration explaining each slide more fully Included speaker notes or audio narration explaining each slide more fully Speaker notes or audio narration succinct and direct, persuasive presentation Discussed cost considerations, and risk identification & mitigation 10. Clarity, persuasion, proper communication, writing mechanics, and formatting requirements. Weight: 10% (20 points) Unclear structure, not persuasive, major grammatical errors Somewhat clear structure, limited persuasion, grammatical errors, language too simple or too wordy Clear structure, persuasive writing, minor or no grammatical errors, length and format within requirements, plain language No grammatical errors, plain language, organized by topic, references business needs, connects to technical specs, persuasive