Final Rubric for Grading on DMBS 1

Application: 60 pts

Criteria Outstanding
60 pts
Adequate
40 pts
Not Adequate
20 pts Rating
Database Design and Logically designed database that Exhibited a partial implementation of the Exhibited minimal understanding the
Architecture corresponds to the back-end structure of design and manipulation. database design and manipulation
the application. Some minor inaccuracy when explaining Inaccurate design explanation in regard to
Completely and accurately explained design usage and purpose design usage and purpose
design usage and purpose.
Table Creation Created all of the tables defined in project Created most of the tables defined in Partially created some of the tables
requirements project requirements defined in project requirements
Named tables appropriately in regard to Table name was a little unclear in regard Table name did not correlate to its data
their data elements to its data elements elements
Normalization, Relations and Correctly interpreted all the Business Correctly Interpreted most Business Rules Incorrectly Interpreted the Business
Cardinalities Rules and created all necessary relations and created most of the necessary Rules, few relations were created and few
with clear indication to the cardinalities relations with some indication to indications to Cardinalities and Normal
and observing the three normalizations cardinalities and observing at least two forms. Tables are not broken down to
forms. Primary and Foreign Key fields are normal forms. Broken down tables to its represent a specific entity.
correctly referenced in each related table normal form that fully represents the key
in each individual table.
Keys and Entities Correctly choose all primary and foreign Correctly choose most of the primary and Incorrectly choose most of the primary
keys respecting the naming convention foreign keys respecting the naming and foreign Keys, and somehow
convention respected the naming convention
Implementation/Records/ Accurately entered data elements into Entered data elements into tables with Irrelevant data values that is not
Data Quality tables. Data values are consistent. minimal keypunch errors. Populated necessary to perform database
Completely populated tables with correct tables with majority of data elements operations. Populated tables with
data elements reflecting the ERD design outlined in the ERD design minimal data elements defined in project
the ERD design
Reports and Queries Created all of the reports needed for the Created some of the reports needed for Created minimal reports needed for the
as defined in project requirements and the company as defined in project company as defined in project
can perform on-demand queries. requirements requirements. Report names does not
Report name is indicative of data it will Report name partially correlates to the indicate what data will be returned
return data it will return
Total
Final Rubric for Grading on DMBS 1 and OOP
Documentation and Presentation: 60 pts

Criteria Outstanding
40 pts
Adequate
25 pts
Not Adequate
10 pts Rating
Documentation Completely described the entire Fairly supplies the document with The document is filled with unrelated
specifications of the application. necessary information about the information that does not support to the
application entire application
Group Presentation The presentation goes well beyond the Meets requirements as laid out in the The presentation suffers from serious or
requirements as laid out in the assigned assignment specifications. un-ignorable flaws or difficulties
project.
Individual Presentation
Member 1:
Member 2:

Total
Final Rubric for Grading on OOP

Criteria Outstanding
60 pts
Good
40 pts
Fair
20 pts Rating
Program Consistent structure : white space, New class: no frills Separate class (in Doesn't compile or run some codes.
locations of declarations, nothing separate file, for instance Account.Java).
overdone
Classes Reasonably clear, relatively independent Some clumsy division of labour. Hard to Still only one class.Or other classes exist,
classes. Main class small, simple, provides justifiy why certain behaviours are being but don't work.
just enough set-up, easy to read and carried out by the classes they are.
understand.
Functionality All JSwing components perform their Minor bugs, few undone fixes, some Majority of the application components
assigned functionalities as well as the features that needs revision. does not perform its expected output.
connection of front-end to back-end
systems
Class Definition: Behaviours Methods make sense. Includes Uses set/get methods as necessary. New Class does very little; most functions
constructor that initializes carefully. remain in one main (driver) class;

Debugging Aids Reasonable use of DEBUG flags or Some evidence of built-in debugging aids; No evidence of debugging aids
(tracing)/comments reasonable alternative, program tracing a few output statements in key locations.
and other debugging aids;
"in function X"; "got to here"
General Design Clear justification given for how and why Provides good logical separation of tasks Tasks that should belong to the Numeral
variables and functions are organized the and attributes between the classes that class are still part of main class.
way they are. Looks professional have been defined.
Total