You are on page 1of 6

DAD_2 Marking guide

Task 1 and 2 need to be done together

Task 1.

produce a full data model for the client

(2.1, 4.1)

Comment:
Pass standard: Data model to include any of the following: universal relation, derived normalized tables, ERDs, table
design, data dictionary.

Merit standard: Data models considered from both top down & bottom up, are easy to understand, with key and proper
notation.

Distinction: 3rd normal form

Pass+ range 1 to 3

To include the following: universal relation,


derived normalized tables,
ERDs,
table design,
data dictionary

Merit range 1 to 2

Transparent to 3rd party standards (key, clarity)

Distinction Range 1 to 5

all normalized to 3rd normal form


DAD_2 Marking guide

Task 2.

provide annotated notes, considering & justifying your design decision.


(2.2)
Comment:
What data models were possible? Flat file? Hierarchical? Relational? Why did you use your chosen data
model? If you have entities why have you selected them? How did you determine fields, and data types?

Justification chiefly based on a top down approach, with minimal reference to other approaches.

Merit standard: consideration & justification focus on a bottom up view

Distinction standard: consideration & justification for the overall data model paradigm and the detailed bottom up
decisions.

Pass+ 2 marks

top down analysis

Merit 1 mark

bottom up analysis for fields & types

Distinction 3 marks

full model, & both perspectives


 paradigm considered (relational versus flat file)
 entities considered (top down)
 fields considered (bottom up)
DAD_2 Marking guide

Task 3

Implement the data model

(2.1)

comment
A database of 6 tables is produced

merit level: full relation integrity between all tables

Distinction level: The implementation fully matches design with no of reverse engineering.

Pass+ 1 mark

6 table dbms produced matching entities of case study

Merit 1 mark

full relational integrity between all tables (PK/FK)

Distinction 2 marks

implementation matches design- no reverse engineering evident (design evidence will antedate build)
DAD_2 Marking guide

Task 4

enhance the application

(2.3)

comments
The several enhancements provided & justified

Merit standard: more than 2 enhancements have been provided

Distinction standard: A full range of enhancements is evident (more than 5) and these have been fully justified

Pass+ 1 to 3 points

More than 1 enhancement has been made and justified

Merit 1 mark

more than 2 enhancements provided

Distinction 1 to 3 marks

range of enhancements (more than 5) & each justified


DAD_2 Marking guide

Task 5

Impose validation/verification

(4.2)

comment
Validation/verification is employed in several areas

Merit level: both (range) form/VBA and table level (properties) has been considered & implemented

Distinction level: approach to validation is clearly linked to the test plan dummy data strategies

Pass+ 1 to 3 points

validation/verification employed across more than 1 area (eg several tables, several forms)

Merit 1 point

both table level (properties) and form/VBA employed

Distinction 1 to 3 points

range from 1 to 3 points:

validation is clearly linked to the test plan dummy data strategies- direct reference to test plan/dummy data,
DAD_2 Marking guide

Task 6

Implement a testing regime

(4.3)

comment
pass +: test plan & results

Testing at merit level: evidence includes a test plan with sufficient dummy data and results

Testing at Distinction standard: sufficient dummy data to include a range of type- erroneous, extreme- to consider
validation issues fully

Pass+1 to 2 points

test plan provided along with test results;

Merit 1 point

Depth/sufficient dummy data provided in test plan

Distinction 1 to 3 points

utilizes a range of dummy data (erroneous, extreme), point range based on depth of dummy data

You might also like