SYSTEMS ANALYSIS AND REDESIGN PROJECT
Systems Analysis and Redesign Project Phase 1 Grading Rubric
|
|
Criteria |
|
|
|
Levels of Achievement |
|
|
|
|
Content 70% |
|
|
Advanced 90-100% |
|
|
|
|
|
|
|
|
18 to 20 points |
|
|
|
|
|
|
|
|
The introduction is succinct and |
|
|
|
|
|
|
|
|
embodies the project’s primary |
|
|
|
|
|
|
|
|
objectives and outcomes. The |
|
|
|
|
|
Introduction and |
|
|
introduction constructs the purpose |
|
|
|
|
|
conclusion |
|
|
of the system. A compelling and |
|
|
|
|
|
|
|
|
justifiable conclusion is developed |
|
|
|
|
|
|
|
|
that supports the key outcomes. |
|
|
|
|
|
|
|
|
More than 5 scholarly sources and |
|
|
|
|
|
|
|
|
500 words combined. |
|
|
|
|
|
|
|
|
18 to 20 points |
|
|
|
|
|
|
|
|
Problem statement is feasible |
|
|
|
|
|
|
|
|
and addresses the key |
|
|
|
|
|
|
|
|
deliverables of the project |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
including a highly innovative, |
|
|
|
|
|
|
|
|
available, scalable, and secure |
|
|
|
|
|
Problem statement |
|
|
information systems solution |
|
|
|
|
|
|
|
|
that can be implemented in the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cloud or a distributed |
|
|
|
|
|
|
|
|
environment. Over 500 words |
|
|
|
|
|
|
|
|
and 5 unique and relevant |
|
|
|
|
|
|
|
|
scholarly journal articles that |
|
|
|
|
|
|
|
|
justify the problem and need for |
|
|
|
|
|
|
|
|
a solution. |
|
|
|
|
|
|
|
|
92 to 100 points |
|
|
|
|
|
|
|
|
Feasibility study and project |
|
|
|
|
|
|
|
|
plan are more detailed and |
|
|
|
|
|
|
|
|
higher quality than the textbook |
|
|
|
|
|
|
|
|
examples in each of the core |
|
|
|
|
|
Feasibility study and |
|
|
objectives including at a |
|
|
|
|
|
|
|
|
minimum the SDLC cycle, |
|
|
|
|
|
project plan |
|
|
|
|
|
|
|
|
|
|
|
updating the old information |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
system to the new cloud-based |
|
|
|
|
|
|
|
|
system, a comprehensive / |
|
|
|
|
|
|
|
|
detailed project charter, scope, |
|
|
|
|
|
|
|
|
alternatives, schedule, tasks, |
|
|
|
|
|
|
|
|
resource estimations, work |
|
|
|
|
|
|
break down structure, financial |
|
|
|
||||||||
|
|
|
budget, cost, and benefit |
|
|
|
||||||||
|
|
|
analysis. Plan is over 2,000 |
|
|
|
||||||||
|
|
|
words with over 10 relevant |
|
|
|
||||||||
|
|
|
supporting scholarly sources |
|
|
|
||||||||
|
|
|
justifying the methods, |
|
|
|
||||||||
|
|
|
standards, estimations, and |
|
|
|
||||||||
|
|
|
costs. |
|
|
|
||||||||
|
Structure 30% |
|
Advanced 90-100% |
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|||||||
|
APA, Grammar, and |
|
18 to 20 points |
|
|
|||||||||
|
Spelling |
|
Properly formatted APA paper |
|
|
|||||||||
|
|
|
with table of contents and |
|
|
|||||||||
|
|
|
references pages. Correct spelling |
|
|
|||||||||
|
|
|
and grammar used. Contains fewer |
|
|
|||||||||
|
|
|
than 2 errors in grammar or |
|
|
|||||||||
|
|
|
spelling that distract the reader |
|
|
|||||||||
|
|
|
from the content and/or minimal |
|
|
|||||||||
|
|
|
errors (1-2) noted in the |
|
|
|||||||||
|
|
|
interpretation or execution of |
|
|
|||||||||
|
|
|
proper APA format. Excellent |
|
|
|||||||||
|
|
|
organization, headings, and flow of |
|
|
|
||||||||
|
|
|
the main concepts exist. |
|
|
|
||||||||
|
|
|
|
|
|
|
|
|||||||
|
Overall Requirements |
|
37 to 40 points |
|
|
|||||||||
|
|
|
Over 2,000 words exist of original |
|
|
|||||||||
|
|
|
student authorship that shows |
|
|
|||||||||
|
|
|
excellent mastery and knowledge |
|
|
|||||||||
|
|
|
of systems analysis and design. |
|
|
|
||||||||
|
|
|
Over 10 unique scholarly peer |
|
|
|
||||||||
|
|
|
reviewed journal articles from |
|
|
|
||||||||
|
|
|
well-respected IT journals exist |
|
|
|
||||||||
|
|
|
that directly relate to and |
|
|
|
||||||||
|
|
|
sufficiently support an operational |
|
|
|
||||||||
|
|
|
systems analysis and design. |
|
|
|
||||||||
|
Total Points |
|
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Systems Analysis and Redesign Project Phase 1 Grading Rubric
Criteria
Levels of Achievement
Content 70%
Advanced 90
-
100%
18 to 20 points
The
introduction is succinct and
embodies the project’s primary
objectives and outcomes. The
Introduction and
introduction constructs the purpose
conclusion
of the
system. A compelling and
justifiable conclusion is developed
that supports the key outcomes.
More than 5 scholarly sources and
500 words combined.
18 to 20 points
Problem statement is feasible
and addresses the key
deliverables of the project
including a highly innovative,
available, scalable, and secure
Problem statement
information systems solution
that can be implemented in the
cloud or a distributed
environment. Over 500 words
and 5 unique and relevant
scholarly journal articles that
justify the problem and need for
a
solution.
92 to 100 points
Feasibility study and project
plan are
more detailed and
higher quality than the textbook
examples in each of
the core
Feasibility study and
objectives including at a
minimum the SDLC cycle,
project plan
updating the old information
system to the new cloud
-
based
system, a comprehensive /
detailed project charter, scope,
alternatives, schedule, tasks,
resource estimations, work
Systems Analysis and Redesign Project Phase 1 Grading Rubric
Criteria
Levels of Achievement
Content 70% Advanced 90-100%
18 to 20 points
The introduction is succinct and
embodies the project’s primary
objectives and outcomes. The
Introduction and introduction constructs the purpose
conclusion of the system. A compelling and
justifiable conclusion is developed
that supports the key outcomes.
More than 5 scholarly sources and
500 words combined.
18 to 20 points
Problem statement is feasible
and addresses the key
deliverables of the project
including a highly innovative,
available, scalable, and secure
Problem statement
information systems solution
that can be implemented in the
cloud or a distributed
environment. Over 500 words
and 5 unique and relevant
scholarly journal articles that
justify the problem and need for
a solution.
92 to 100 points
Feasibility study and project
plan are more detailed and
higher quality than the textbook
examples in each of the core
Feasibility study and
objectives including at a
minimum the SDLC cycle,
project plan
updating the old information
system to the new cloud-based
system, a comprehensive /
detailed project charter, scope,
alternatives, schedule, tasks,
resource estimations, work