Professional Documents
Culture Documents
PresentationGuidelines
Thefollowingshouldbeavailableatleastonedaypriortoyourpresentation.
1. ERDofyourdatabasethisisyourfinalversionofyourDB.Youonlyneedtoincludethename
ofeachentity/tableandkeys(PK,FK).
2. Tabledescriptionsprovidetechnicaldocumentationonalltablesincludingcolumnnames,
columndatatypes,andreferentialintegrity(RI)statements.RefertotheProjectRequirements
documentonhowtoformatyourtabledescriptions.
3. Listofstoredproceduresandviewsprovideasimplelistofallstoredproceduresandviewsin
yourdatabase.
4. Workingdatabaseaworkingversionofyourdatabasethatisabletobeaccessedifneeded.
Thedatabaseshouldbeclosetobeingcomplete.Inaddition,itemsfoundinyour
review/attackmustbefixed.
5. HW3Part2Responsearesponsetowhatwasfoundinyoursystemsreview.Addressthe
issuesthattheattackinggroupfoundalongwithhowyoufixedthem.Ifnecessary,youmay
rebutwhatwasfound.
Theaboveareessentiallythemajorpiecesofthetechnicaldocument.Ifyouchoose,youmayprovidea
copyofthetechnicaldocument.
APowerPointslidedeck/fileisNOTneeded.ThepresentationwillbeaonehourtechnicalQ&Aofyour
project.Theevaluatorscanandwillaskabouttherevisedstructureofyourdatabase,objectscreated,
performance,andsecurity.Theywillalsoaskaboutwhatwasidentifiedinyourreview(HW3Part2).
Eachgroupmembershouldknowthedatabaseinsideandout.Thereshouldbemorethanoneperson
thatanswersquestionsthepanelwillquizeachgroupmember.
Theremaybeitemsthatshouldbeaddressedduringthepresentationandshouldbeaddressedinyour
finaldocumentation.
Pleasecontacttheinstructorforanyadditionalclarification.