5 present written documentation 6 state assumptions

This preview shows page 14 - 18 out of 19 pages.

5.Present written documentation6.State assumptions that you made in creating your solutionAssumptions were that every song will fall under one genre. Another assumption was that any theme can be created for an event.
7.Thank the clients for their time“Thank you. Please get home safely.”8.Exit gracefullyLeave.Remember: When you have a very large diagram, it may also help to break it up into smaller diagrams of functionally related entities. You could use the smaller sub-diagrams when presenting to different groups within the customer’s company.Hint: Review Section 11 Lesson 1 for drawing conventions for readability.Step 10 – Making modifications and new requirementsModify your ERD based on the feedback received from the presentation to the DJson Demand Director. Produce a Design Revision Document outlining the changes made since the presentation was given. Include the modified ERD with the Design Revision Document and submit the package to your instructor for review.Think of reports that can be generated from the future system, which includes the modifications you just made. Document how you imagine these reports could be used in the business.For example, the staffing manager could run an “Events Report” that lists the names of the partners who worked on different projects. If it looks like some of the partners are busier and perform better, then, the manager can promote them.IDfirst_nameLast_namePhone_numbersEmail100AntonioPeters555-1891[email protected]45MaryCollins662-227563SarikaPatel383-4572[email protected]19IvanBalazs777-5511[email protected]IddateDescriptionCostClient_idTheme_code1522-Apr800.001001712-MarCocktail hourfollowed by dinner2000.0045TROP2511-MarGarden party400.0045TROP5001-MayBlack-tie affair1200.00SIXTStep 11 – Checking data integrity in the DJ database
refers toExamine the sample data for these tables in the DJs on Demanddatabase.Check for entity, referential, and column integrity. Identify any data integrity violations. Assume that all date columns should have a date format and all cost columns should have a number format.Figure 1 Sample data for DJs on Demand databasePrimary Keyrefers toCLIENTSidfirst_namelast_namephone_numEmail100AntonioPeters555-1891[email protected]45MaryCollins662-2275SarikaPatel383-4572[email protected]19IvanBalazs777-5511[email protected]Primary KeyForeign KeyForeign KeyEVENTSidnamedatedescriptioncostclient_idtheme_ code15Peter’s graduation22-Apr800.00100BB17Collins wedding12-MarCocktail hour followed by dinner2gs45TROP25Collins rehearsal dinnerDay before weddingGarden party400.0045TROP50Eiks Club annual fundraiser01-MayBlack-tie affair1200.0077SIXTPrimary Key THEMEScodedescriptionCARNCarnivalSIXTSixtiesTROPTropical
Step 12 – The PARTNER supertypeTransform the PARTNER supertype in the DJ model, using the supertype or single-table implementation.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture