Use Case Packet Code
Code is submitted in the environment you plan to develop the software.
It should be placed in the assignment drop box as an executable or a
hyperlink.
CODE A
Each member must submit a method for me to view your specific use
cases. Although all members do not have screens associated with their
use cases, they must have a method for me to execute their code. In this
submission, you include the mechanism and/or procedures that I will
use to grade this code. It has to be flexible as I use many different
machines all do run windows and I can get on UNIX main campus also.
Nothing has to work here we are just checking out the environment.
There should be some output that lets me know I am in the program.
“You have arrived” The code is NOT placed in the assignment. It may
be placed there later.
CODE B
Something should work here. A screen should display, a file created, a
record read, something that is viewable. If you have no screens then
print out something to make me aware of what you have coded. “You
have arrived” will not suffice. This code is NOT placed in the
assignment, it will be placed there later.
CODE C
Here we have two assignments:
1. Some real code working code for some part of your assignment
presented as an executable.
2. Linkage to the main routine (or linkage from another use
case) so you can run it from another use case via a selection or
automatic call.
CODE D
All data is converted, coded, specified in XML if needed and ready for
use. Continue working on your use case code if you have no data to
convert, code or specify.
CODE E
All classes on the Extended Class Diagram for your UCP should be
coded with attributes, methods and method signatures. Some of the
code should be working. The user should be able to operate your use
case in some manner to assure code is executing.
CODE F
One class that has many methods that return a value should be selected
and you should write a unit test for that class according to the
specifications in your lectures.
CODE G
What should be turned in –
Your source CODE for your portions of the project
An executable for the entire project
What will be graded
Your source CODE for your portions of the project
What will be evaluated with feedback
The executable for the entire project
Your grade will be for your source code.
But an evaluation of your executable will allow you to be given one
more opportunity to correct any serious mistakes before the final
project grade is submitted.
FINAL PROJECT
This is all code integrated together….note this is a team effort to make
sure all code integrates….
Grading Criteria
USE CASE CODE
1. Lateness of deliverable:
1 day late 20 points
2 days late 35 points
3 days late 45 points
After 3 days late a zero grade is recorded.
2. Correctness (70 points total):
a. Evidence of dead or starving states
b. Incorrect or missing output
c. Missing use case execution code
d. Missing inclusion of needed instances
e. Executable code included
i. Use case code should not be an executable statement
ii. OTHER than to call methods in other classes
iii. It should not assign variables or modify such other than variables
that are class instances
3. Format (30 points total):
a. Indention not consistent
b. Variable names not according to attribute description
c. Data types of variables not according to attribute description
Use Case Code
Class Definition
Known attributes
Statements to make instances of other classes and call methods in other classes