CS 320 Milestone Two Guidelines and Rubric
CS 320 Milestone Two Guidelines and Rubric
Overview: In this milestone, you have the opportunity to practice and receive feedback on the summary section of your final project. The following prompt is a
more specific list of the same essential questions that you will need to address in your final submission but with added details and supporting information to
assist you in successfully meeting the requirements.
Prompt: Describe your experience developing and writing JUnit tests for each of the three features by addressing each of the following questions: How many JUnit tests did you create for each of the features (i.e., Doctor Information Feature, Medical Records Feature, and Allergy Find Feature) and
why? In other words, what was your level of testing for each of the features? Explain your reasoning based on the best practices you have learned in the
course. How did you organize your tests for each of the features? For example, did you group any of your tests into test suites for any of the features? Why or
why not? Explain your reasoning based on the best practices you have learned in the course. Did you address all the software requirements? Describe how you met each of the requirements from the test plan (listed below).
○ Doctor Information Feature Requirement: The system shall allow the user to log in and add a doctor to the list of doctors. Doctors’ names do
not have to be unique, but doctors’ IDs should be unique.
○ Medical Records Feature Requirement: The system shall allow the user to add a medical record to a patient.
i. Add a patient.
ii. Add a medical record with treatments, medications, and allergies.
o When you create a medical record, it is necessary to create a patient history, which will contain 1 to many treatments, 1 to many
medications, and 1 to many allergies. Medications cannot be assigned to a patient history unless there has been a treatment
first.
○ Allergy Find Feature Requirement: The system shall allow the user to search for allergies and print all patients with allergies. How did you ensure that your code was technically sound and efficient? Include screenshots of your code demonstrating that it is the following:
○ Syntactically accurate (style and syntax)
○ Logical (how well your program satisfies the requirements of the assignment)
○ Concise (how thoroughly you have tested your own code)
○ Modular (how you organized your tests) Defend the effectiveness of your tests by answering the following final questions:
○ Did you find at least five errors? How many did you find in total?
○ What were the errors?
Rubric
Guidelines for Submission: Milestone Two should be 2 pages in length with double spacing and 12-point Times New Roman font. Any citations should be in APA
format.
Critical Elements Proficient (100%) Needs Improvement (70%) Not Evident (0%) Value
Level of Testing Defends the level of testing for each of the
features using specific examples of testing
best practices discussed in the course
Defends the level of testing, but fails to fully
or appropriately explain the level using
specific examples of testing best practices
discussed in the course
Does not defend the level of testing for each
of the features
13
Organizational
Approach
Defends the organization of tests for each of
the features using specific examples of
testing best practices discussed in the course
Defends the organization of tests, but fails to
fully or appropriately explain the level using
specific examples of testing best practices
discussed in the course
Does not defend the organization of tests for
each of the features
13
Alignment to Doctor
Information Feature
Requirement
Defends the alignment of the testing
approach to the feature requirement with
specific examples
Defends the alignment of the testing
approach to the feature requirement, but
fails to fully or logically explain using specific
examples
Does not defend the alignment of the testing
approach to the feature requirement
7
Alignment to
Medical Records
Feature
Requirement
Defends the alignment of the testing
approach to the feature requirement with
specific examples
Defends the alignment of the testing
approach to the feature requirement, but
fails to fully or logically explain using specific
examples
Does not defend the alignment of the testing
approach to the feature requirement
7
Alignment to Allergy
Finder Feature
Requirement
Defends the alignment of the testing
approach to the feature requirement with
specific examples
Defends the alignment of the testing
approach to the feature requirement, but
fails to fully or logically explain using specific
examples
Does not defend the alignment of the testing
approach to the feature requirement
7
Syntactically
Accurate Code
Defends the accuracy of the code with
specific evidence and appropriate
screenshots
Discusses the accuracy of the code, but fails
to fully or logically defend with specific
evidence and appropriate screenshots
Does not discuss the accuracy of the code 7
Logical Code Defends the functional logic of the code with
specific evidence and appropriate
screenshots
Discusses the functional logic of the code,
but fails to fully or logically defend with
specific evidence and appropriate
screenshots
Does not discuss the functional logic of the
code
7
Concise Code Defends the conciseness of the code with
specific evidence and appropriate
screenshots
Discusses the conciseness of the code, but
fails to fully or logically defend with specific
evidence and appropriate screenshots
Does not discuss the conciseness of the code 7
Modular Code Defends the modularity of the code with
specific evidence and appropriate
screenshots
Discusses the modularity of the code, but
fails to fully or logically defend with specific
evidence and appropriate screenshots
Does not discuss the modularity of the code 7
Effective Tests Defends the effectiveness of the tests by
citing at least five identified errors and
describing the nature of each
Defends the effectiveness of the tests, but
fails to cite at least five identified errors and
describe the nature of each
Does not defend the effectiveness of the
tests
20
Articulation of
Response
Submission has no major errors related to
citations, grammar, spelling, syntax, or
organization
Submission has major errors related to
citations, grammar, spelling, syntax, or
organization that negatively impact
readability and articulation of main ideas
Submission has critical errors related to
citations, grammar, spelling, syntax, or
organization that prevent understanding of
ideas
5
Total 100%