phyllis

6/9/2016 https://blackboard.strayer.edu/bbcswebdav/institution/CIS/429/1128/Week3­1128/Week 3 Assignment 2 Grading Rubric.html

https://blackboard.strayer.edu/bbcswebdav/institution/CIS/429/1128/Week3­1128/Week%203%20Assignment%202%20Grading%20Rubric.html 1/2

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: 100 Assignment 2: Business Requirements

Criteria   Unacceptable Below 60% F

Meets Minimum

Expectations 60­69% D

  Fair

70­79% C

  Proficient 80­89% B

  Exemplary 90­100% A

1. Analyze the purpose of requirements gathering and justify its role in any development process. Weight: 10%

Did not submit or incompletely analyzed the purpose of requirements gathering. Did not submit or incompletely justified its role in any development process.

Insufficiently analyzed the purpose of requirements gathering. Insufficiently justified its role in any development process.

Partially analyzed the purpose of requirements gathering. Partially justified its role in any development process.

Satisfactorily analyzed the purpose of requirements gathering. Satisfactorily justified its role in any development process.

Thoroughly analyzed the purpose of requirements gathering. Thoroughly justified its role in any development process.

2. Explain three (3) differences between building an operational system and a data warehouse. Weight: 10%

Did not submit or incompletely explained three differences between building an operational system and a data warehouse.

Insufficiently explained three differences between building an operational system and a data warehouse.

Partially explained three differences between building an operational system and a data warehouse.

Satisfactorily explained three differences between building an operational system and a data warehouse.

Thoroughly explained three differences between building an operational system and a data warehouse.

3. Explain the significance of information package diagrams. Weight: 5%

Did not submit or incompletely explained the significance of information package diagrams.

Insufficiently explained the significance of information package diagrams.

Partially explained the significance of information package diagrams.

Satisfactorily explained the significance of information package diagrams.

Thoroughly explained the significance of information package diagrams.

4a. Assess the importance of JAD to database warehouse development based on user involvement. Weight: 10%

Did not submit or incompletely assessed the importance of JAD to database warehouse development based on user involvement.

Insufficiently assessed the importance of JAD to database warehouse development based on user involvement.

Partially assessed the importance of JAD to database warehouse development based on user involvement.

Satisfactorily assessed the importance of JAD to database warehouse development based on user involvement.

Thoroughly assessed the importance of JAD to database warehouse development based on user involvement.

4b. Assess the importance of JAD to database warehouse development based on requirements gathering. Weight: 10%

Did not submit or incompletely assessed the importance of JAD to database warehouse development based on requirements gathering.

Insufficiently assessed the importance of JAD to database warehouse development based on requirements gathering.

Partially assessed the importance of JAD to database warehouse development based on requirements gathering.

Satisfactorily assessed the importance of JAD to database warehouse development based on requirements gathering.

Thoroughly assessed the importance of JAD to database warehouse development based on requirements gathering.

4c. Assess the importance of JAD to database warehouse development

Did not submit or incompletely assessed the importance of JAD to database

Insufficiently assessed the importance of JAD to database warehouse

Partially assessed the importance of JAD to database

Satisfactorily assessed the importance of JAD to database

Thoroughly assessed the importance of JAD to database

6/9/2016 https://blackboard.strayer.edu/bbcswebdav/institution/CIS/429/1128/Week3­1128/Week 3 Assignment 2 Grading Rubric.html

https://blackboard.strayer.edu/bbcswebdav/institution/CIS/429/1128/Week3­1128/Week%203%20Assignment%202%20Grading%20Rubric.html 2/2

based on the development process. Weight: 10%

warehouse development based on the development process.

development based on the development process.

warehouse development based on the development process.

warehouse development based on the development process.

warehouse development based on the development process.

5a. Compare and contrast JAD to the Waterfall methodology, which is commonly used in software development projects. Include user involvement. Weight: 10%

Did not submit or incompletely compared and contrasted JAD to the Waterfall methodology. Did not submit or incompletely included user involvement.

Insufficiently compared and contrasted JAD to the Waterfall methodology. Insufficiently included user involvement.

Partially compared and contrasted JAD to the Waterfall methodology. Partially included user involvement.

Satisfactorily compared and contrasted JAD to the Waterfall methodology. Satisfactorily included user involvement.

Thoroughly compared and contrasted JAD to the Waterfall methodology. Thoroughly included user involvement.

5b. Compare and contrast JAD to the Waterfall methodology, which is commonly used in software development projects. Include requirements gathering. Weight: 10%

Did not submit or incompletely compared and contrasted JAD to the Waterfall methodology. Did not submit or incompletely included requirements gathering.

Insufficiently compared and contrasted JAD to the Waterfall methodology. Insufficiently included requirements gathering.

Partially compared and contrasted JAD to the Waterfall methodology. Partially included requirements gathering.

Satisfactorily compared and contrasted JAD to the Waterfall methodology. Satisfactorily included requirements gathering.

Thoroughly compared and contrasted JAD to the Waterfall methodology. Thoroughly included requirements gathering.

5c. Compare and contrast JAD to the Waterfall methodology, which is commonly used in software development projects. Include the development process. Weight: 10%

Did not submit or incompletely compared and contrasted JAD to the Waterfall methodology. Did not submit or incompletely included the development process.

Insufficiently compared and contrasted JAD to the Waterfall methodology. Insufficiently included the development process.

Partially compared and contrasted JAD to the Waterfall methodology. Partially included the development process.

Satisfactorily compared and contrasted JAD to the Waterfall methodology. Satisfactorily included the development process.

Thoroughly compared and contrasted JAD to the Waterfall methodology. Thoroughly included the development process.

6. 3 references Weight: 5%

No references provided

Does not meet the required number of references; all references poor quality choices.

Does not meet the required number of references; some references poor quality choices.

Meets number of required references; all references high quality choices.

Exceeds number of required references; all references high quality choices.

7. Clarity, writing mechanics, and formatting requirements Weight: 10%

More than 8 errors present

7­8 errors present

5­6 errors present

3­4 errors present

0­2 errors present