Description / paper instructions
Please find the instruction an the memo attached. The professor is
very strict please use the memo template and fill in info please.
Please let me know if you have any question. The task is based on week
upcoming week 10 assignments. I will attach it here as well. I need
just the list of task. I will week 9 and week 10 with the same writer.
I need the work as soon as possible. Just one page of task. Thanks
CIS 500 – Information Systems for Decision-Making
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:
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 | |||||||
Unacceptable | Fair | Proficient | Exemplary | |||||
Criteria | Below 70% F | 70-79% C | 80-89% B | 90-100% A | ||||
1. Goals: What the | Did not | Communicated | Communicated | Communicated | ||||
project hopes to | communicate what | what the project | what the project | importance of | ||||
accomplish. | the project hopes to | hopes to | hopes to | project reaching its | ||||
accomplish | accomplish | accomplish | goals | |||||
Weight: 10% | ||||||||
(20 points) | Did not list project | Did not list project | Listed the project | Connected project | ||||
goals | goals | goals | goals to the | |||||
organizational | ||||||||
strategy | ||||||||
2. Critical Success | Did not identify 4 | Identified 4 | Identified 4 | Identified and |
CIS 500 – Information Systems for Decision-Making
Factors: Identify at least | stakeholders | stakeholders | stakeholders | justified the | |
4 different stakeholders; | selection of 4 | ||||
for each, list at least 2 | Listed things to | Listed less than 2 | Listed 2 things that | stakeholders | |
things that stakeholder | |||||
make project | things each | each stakeholder | |||
requires in order to deem | |||||
successful, but did | stakeholder would | would require to | Explained why each | ||
the project successful. | |||||
not connect each | require to deem | deem the project | stakeholder would | ||
stakeholder | project successful | successful | be most interested | ||
Weight: 10% | in 2 things to deem | ||||
(20 points) | project successful | ||||
3. Acquisition strategy: | Did not compare | Reasonable | Compared various | Analyzed various | |
Should the system be | acquisition | comparison of | acquisition | acquisition | |
built in-house, created by | strategies | acquisition | strategies | strategies, or | |
a contractor, purchased | strategies | presented an | |||
off-the-shelf and | Did not determine | Determined which | acquisition strategy | ||
customized, or leased as | that was not | ||||
the best strategy for | Determined best | acquisition strategy | |||
a service? Explain the | previously | ||||
the proposed | acquisition strategy | would be the best | |||
rationale for your choice. | mentioned | ||||
information system | for the proposed | for the proposed | |||
information system | system | ||||
Weight: 10% | Explained why | ||||
(20 points) | Inadequately | Somewhat | Provided rationale | other acquisition | |
strategies would | |||||
explained the | for choosing a | ||||
explained the | potentially not work | ||||
rationale for | specific acquisition | ||||
rationale for | |||||
choosing the | strategy | ||||
choosing the | |||||
acquisition strategy | Discussed cost | ||||
acquisition strategy | |||||
considerations | |||||
4. Resources: For in- | Inadequately | Determined | Determined and | Presented | |
house development, | determined | resources needed | justified resources | resources not | |
what people/skills are | resources needed | for the acquisition | needed for chosen | previously | |
required and what | for the acquisition | strategy, but did not | acquisition strategy | considered | |
development lifecycle do | strategy | justify reasoning | |||
you recommend? | Recommended a | Included risk | |||
Otherwise, identify 3 | |||||
Limited | Recommended a | project | identification and | ||
candidate organizations | |||||
recommendation for | project | development | mitigation | ||
that can deliver the | |||||
development | development | lifecycle for in- | procedures | ||
system. | |||||
lifecycle for in- | lifecycle for in- | house | |||
house | house | development, or | Proposed a | ||
Weight: 10% | development, or | development, or | three external | ||
combination of | |||||
(20 points) | three external | three external | organizations that | ||
resources and | |||||
organizations that | organizations that | can deliver the | |||
strategy to organize | |||||
can deliver the | can deliver the | system. | |||
stakeholder efforts | |||||
system | system, but did not | ||||
toward project | |||||
justify why they | |||||
completion | |||||
were chosen | |||||
Inadequate | |||||
justification | |||||
5. System functions: In a | Failed to put in | In table format: | In table format: | In table format: | |
table format, summarize | table format | ||||
the types of users for the | Summarized some | Summarized the | Analyzed user | ||
system; the business | |||||
CIS 500 – Information Systems for Decision-Making
reason(s) each would | Inadequate | of the types of | types of users for | experience and | |
use the system; the ways | summary of users | users for the | the information | user design | |
that the system supports | for the system | system | system | considerations | |
each of these needs; and | |||||
how this support differs | Limited explanation | Somewhat | Explained business | Explained design | |
from the current system. | |||||
of why users would | explained business | reasons why each | changes that took | ||
use the system | reasons for system | user type would use | place between the | ||
Weight: 10% | use | the system | old and new system | ||
(20 points) | Inadequate | ||||
description of how | Somewhat | Described how the | Provided rationale | ||
system supports | described how the | system supports the | for the user types | ||
users | system supports | needs of each user | identified | ||
users | type | ||||
Inadequate | Discussed how to | ||||
comparison of the | Reasonable | Determined how | reach out to user | ||
proposed system to | comparison of the | this support differs | types to test the | ||
the old system | proposed system to | from the current | system | ||
the old information | information system | ||||
system | |||||
6. Connectivity: Provide a | Failed to put in | In a diagram: | In a diagram: | In a diagram: | |
diagram that shows the | diagram format | ||||
other information | Showed other | Showed other | Showed how you | ||
systems this one will | |||||
Inadequate diagram | information systems | existing information | selected existing | ||
connect to, and what | |||||
showing your | that your system | systems that your | systems that your | ||
data flows among them. | |||||
system, hard to | would connect to, | proposed system | system would | ||
follow, incomplete | but hard to follow | would connect to | connect to | ||
Weight: 10% | |||||
(20 points) | Inadequate or hard | Demonstrated what | Demonstrated what | Explained how | |
to follow the data | data would flow | data would flow | diagram would be | ||
that would flow | among systems, but | between your and | updated and | ||
among systems, | hard to follow | other information | maintained based | ||
incomplete | systems. | on changes in the | |||
marketplace | |||||
7. Security: List the most | Inadequate list of | Reasonable list of | Listed the most | Proposed how your | |
serious cybersecurity | cybersecurity | cybersecurity | serious | new system would | |
threats and vulnerabilities | threats | threats, failed to | cybersecurity | integrate with | |
of the new system. | show why they are | threats to your new | Shadow IT, if at all | ||
Suggest strategies to | Inadequate | most serious | system | ||
address them. | |||||
strategies to | Demonstrated | ||||
address each threat | Identified strategies | Proposed strategies | strategies for | ||
Weight: 10% | to address each | to address each | current users to | ||
(20 points) | threat | threat | avoid threats | ||
8. Mobility: Identify the | Failed to identify | Identified your | Identified your | Proposed situations | |
system’s capabilities for | your system’s | system’s | system’s | in which mobile use | |
mobile use. | capabilities for | capabilities for | capabilities for | would happen and | |
mobile use, | mobile use, but not | mobile use | situations where its | ||
Weight: 10% | incomplete | comprehensive | 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 – Information Systems for Decision-Making
(20 points) | ||||
9. Speaker / Audio | Inadequate speaker | Somewhat detailed | Included speaker | Speaker notes or |
Notes: Include speaker | notes or audio | speaker notes or | notes or audio | audio narration |
notes or audio narration | narration, too much | audio narration | narration explaining | succinct and direct, |
that explains each slide | or too little | explaining each | each slide more | persuasive |
more fully. | information on each | slide more fully | fully | presentation |
slide provided | ||||
Discussed cost | ||||
Weight: 10% | considerations, and | |||
risk identification & | ||||
(20 points) | ||||
mitigation | ||||
10. Clarity, persuasion, | Unclear structure, | Somewhat clear | Clear structure, | No grammatical |
proper communication, | not persuasive, | structure, limited | persuasive writing, | errors, plain |
writing mechanics, and | major grammatical | persuasion, | minor or no | language, |
formatting requirements. | errors | grammatical errors, | grammatical errors, | organized by topic, |
language too simple | length and format | references business | ||
Weight: 10% | or too wordy | within requirements, | needs, connects to | |
plain language | technical specs, | |||
(20 points) | ||||
persuasive | ||||
Week 8 Status Report
Due Week 8 and worth 50 points
In Week 10, you will provide a detailed project presentation for your new information system project. Because of its importance to the organization, your presentation must be thoughtful and visually appealing.
To help you stay on track for this three-week effort, the executives have assigned you a project manager. For each week leading up to the presentation, you are expected to turn in a short (less than one page) status report. It must address just 4 things:
Please write up your responses as a series of bullet points in memo form. There is no need for a cover page.