Topic: Building Better Software - Subtopic: Modeling
A good data model, done right the first time, can save you time and money. We have all seen the charts on the increasing cost of finding a mistake/bug/error late in a software development cycle. Would you like to reduce, or even eliminate, your risk of finding one of those errors late in the game? Of course you would! Who wouldn't? Nobody plans to miss a requirement or make a bad design decision (well, nobody sane, anyway). No modeler worth his or her salt wants to leave a model incomplete or incorrect. So what can you do to minimize the risk?
In this talk, get a best-practice approach to developing your data models that Kent has been using for over 15 years. It is a simple, repeatable process for reviewing your models. It is one that even a nonmodeler could follow. Kent will share his checklist of what to look for and what to ask the modeler (or yourself) to make sure you get the best possible model. As a bonus, Kent will share how he uses SQL Developer Data Modeler to collect the information and report it.
Jun 25, 2014, Session 12, 9:45 am - 10:45 am
Topic: Building Better Software - Subtopic: Agile
This presentation will explore one of the major bottlenecks in database application development: the movement of data from production databases to development though QA, UAT, and test including building and managing development and QA environments. You will export what the impact is, how to solve these bottlenecks, and metrics to track to validate the solution.