[UserStory] Assessment tool for CS instructors

[holsappled]

User Story

Essential components

• Title describes the story
• Stakeholder type is identified
• Outcome is described
• Rationale is explicit
• Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a Educator
I want one consolidated report from the quality assessment tools extension
so that a quick grading assessment of student code can be automated

Acceptance Criteria

(Rules or scenarios are acceptable formats.)

• Rule 1 One consolidated report is produced by the extension
• Rule 2 The report identifies problematic code with references to associated line numbers in the source code
• Rule 3 A boolean if the code compiles

Scenario 1

Given A students code submission
when an assignment is due
then the extension automates creating a consolidated report for review

Supporting Information

(Relevant information, context, resources)

A quick quality assessment report of submitted code creates an automated benchmark for an instructor to look at. This could also be used by students to check their code before submission.

Implementing tools from
https://github.com/MetroCS/QualityToolsForBlueJ/blob/master/toolsForIntegration.md

Dependencies

Depends On

(None)

Dependents

(None)

[jody]

Scenario 1 appears to add a new element of when automated behavior is triggered, not included or obvious from the title or user story itself.

The title and the user story need to be rewritten to indicate the timing reflected in Scenario 1. Removing from ToDo until internal consistency achieved.

Requiring the extension to be automatically triggered by an assignment due date and student code submission is desirable but relatively low priority in comparison to getting the primary behavior in place and invoked via manual interaction. Marking as low priority to indicate this for attention further in the future.