System Analysis Model & Design

profileced1999
Systems_Analysis_and_Redesign_Project_Phase_2_Grading_Rubric.docx

Project Phase 2 Grading Rubric

Criteria

Levels of Achievement

Content 70%

Advanced 90-100%

Proficient 70-89%

Developing 1-69%

Not present

Introduction and conclusion

10 points

The introduction is succinct and embodies the project’s primary

objectives and outcomes. The

introduction constructs the purpose of the system. A compelling and

justifiable conclusion is developed that supports the key outcomes.

More than 5 scholarly sources and 500 words combined.

8 to 9 points

The introduction and conclusion are succinct and embody most of the project’s primary objectives and

outcomes, and/or the introduction

constructs an unclear purpose of the system. Justified conclusion

developed. Minimum of 5 scholarly sources and 500 words.

1 to 7 points

The introduction and/or conclusion are generalized and embody some of the project’s primary objectives and

outcomes and/or has less than the

minimum of 5 scholarly sources and 500 words and/or is not defensible.

0 points

Substantially unmet or not present

Literature review and systems design methods

46 to 50 points

Systems analysis and design literature review and

methodology is accurate,

feasible, and addresses the key deliverables of the project

including a highly innovative,

available, scalable, and secure information systems cloud

solution. Literature results and

methods are properly contrasted

and are specific and relevant to the problem. They detail the

standards used and how these will benchmark the systems.

Over 2,000 words and 15 unique scholarly journal articles

that justify the methodology, its reliability, and its validity in

comparing and contrasting the information systems.

42 to 45 points

Systems analysis and design literature review and

methodology is mostly accurate,

feasible, and addresses the key deliverables of the project

including a highly innovative,

available, scalable, and secure information systems cloud

solution and/or literature results and methods are contrasted and somewhat specific and relevant to the problem and/or detail

some standards used and how these will benchmark the

systems and/or minimum of

2,000 words and 15 unique scholarly journal articles that justify the methodology, its

reliability, and its validity in

comparing and contrasting the information systems.

1 to 41 points

Systems analysis and design literature review and methodology

is not always accurate, feasible, and/or is missing the key

deliverables of the project

including a highly innovative,

available, scalable, and secure

information systems cloud solution and/or literature results and

methods are not contrasted and/or not specific and/or relevant to the problem and/or benchmarking is

inadequate and/or less than 2,000 words and 15 unique scholarly

journal articles that justify the

methodology, its reliability, and its validity in comparing and

contrasting the information systems.

0 points

Substantially unmet or not present and/or quotes more than 5% of the writing

Systems analysis and design

74 to 80 points

Use case diagrams (2), written use cases / use case descriptions

(2), activity diagrams (2), and sequence diagrams (2) are more

thorough and detailed than the textbook examples, follow

appropriate and advanced UML techniques, and meet

comparative industry best practices and standards.

Diagrams show an extensive knowledge of the system being designed. Minimum of 5

success scenarios and 10

extensions exist in each use case along with proper subflows and alternatives.

Minimum of 10 activities exist with accurate associated

decisions, swim lanes, guards, parallel activities, and proper object-oriented strategies to

address distributed computing.

Minimum of 5 objects exist in each sequence diagram with

accurate associated lifelines, execution occurrences,

messages, frames, guards,

functions, loops, and proper object-oriented strategies to address distributed computing.

67 to 73 points

Use case diagrams (2), written use cases / use case descriptions

(2), activity diagrams (2), and/or sequence diagrams (2) are as detailed as the textbook

examples, follow appropriate

and advanced UML techniques,

and meet comparative industry

best practices and standards and/or diagrams show

knowledge of the system being

designed. Most minimums are met including 5 success

scenarios and 10 extensions in

each use case along with proper

sub-flows and alternatives and/or

10 activities exist with accurate associated decisions, swim lanes, guards, parallel activities, and

proper object-oriented strategies

to address distributed computing and/or the minimum of 5 objects exist in each sequence diagram

with mostly accurate associated

lifelines, execution occurrences, messages, frames, guards,

functions, loops, and proper object-oriented strategies to address distributed computing.

1 to 66 points

Use case diagrams (2), written use cases / use case descriptions (2), activity diagrams (2), and/or

sequence diagrams (2) are not as

detailed as the textbook examples and/or do not follow appropriate UML techniques and/or do not meet comparative industry best practices and standards and/or

diagrams fail to show knowledge of the system being designed

and/or minimums are not met

including 5 success scenarios and

10 extensions in each use case along with proper sub-flows and alternatives and/or 10 activities exist with accurate associated

decisions, swim lanes, guards, parallel activities, and proper object-oriented strategies to

address distributed computing

and/or the minimum of 5 objects does not exist in each sequence

diagram with associated lifelines, execution occurrences, messages,

frames, guards, functions, loops, and proper object-oriented

strategies to address distributed computing.

0 points

Substantially unmet or not present or proper screenshots do not exist for each diagram

Structure 30%

Advanced 90-100%

Proficient 70-89%

Developing 1-69%

Not present

APA, Grammar, and Spelling

18 to 20 points

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

17 points

Paper contains fewer than 5 errors in grammar or spelling that distract

the reader from the content and/or some errors (3-7) noted in the

interpretation or execution of proper

APA format and/or inadequate

1 to 16 points

Paper contains fewer than 10 errors in grammar or spelling that distract the reader from the content and/or

numerous errors (7+) noted in the

interpretation or execution of proper

APA format and/or inadequate

0 points

Paper contains more than 10 errors in grammar or spelling that distract the reader from

the content and/or numerous errors (10+) noted in the interpretation or execution of

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.

organization, headings, and flow of the main concepts exist and/or

notable absences in required APA formatting elements such as: Title page, running head, font type and

size (Times New Roman 12 point), and line spacing.

organization, headings, and flow of

the main concepts exist and/or notable absences in required APA formatting elements such as: Title page, running head, font type and size (Times New Roman 12 point), and line spacing.

proper APA format and/or

inadequate organization,

headings, and flow of the main concepts exist.

Overall Requirements

37 to 40 points

Over 2,500 words and 8 diagrams exist of original student authorship that shows excellent mastery and

knowledge of systems analysis and design. Over 15 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.

34 to 36 points

Minimum of 2,500 words and 8 diagrams exist of original student

authorship that shows mastery and

knowledge of systems analysis and design. 15 unique scholarly peer

reviewed journal articles from wellrespected IT journals exist that

relate to and sufficiently support an operational systems analysis and design.

1 to 33 points

Less than 2,500 words and 8 diagrams exist of original student authorship

that shows mastery and knowledge of systems analysis and design and/or

there are less than 15 unique scholarly peer reviewed journal articles from

well-respected IT journals that relate to and sufficiently support an operational systems analysis and design.

0 points

Substantially unmet or not present or proper screenshots do not exist for each diagram

Total Points