Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Oct 25 2007, 10:58 AM EDT (current) | RadioFreeTooting | 3 words added |
| Oct 19 2007, 8:20 AM EDT | RadioFreeTooting | 176 words added, 169 words deleted |
Changes
Key: Additions Deletions
Session Title : Designing PL/SQL apps
Facilator : Andrew Clarke
Time : 15.00 (guess)
Date : Wedsday 13th (fingers crossed)
Location : Moscone West 3rd Floor Overlooks
Room TBC
Session Description:
Most Oracle database applications will have a hefty chunk of PL/SQL code. Some packages will be focused on tables. Some packages will be built around business functionality. Some will just be an accretion of unrelated functionality (most of us will have at least one UTILS package rattling around our schemas). All of this code has been subject to designdecisions;if none of your codebase has been formally or informally designed, well that is a decision too.
So, how do you design your PL/SQL programs? Big design up front? With a white board? With Visio? With a CASE tool? Or do you just leap in and start coding? Top down, bottom up, data driven or test driven: there are so many approaches but no clear standard.
This session will be a goldfish bowl. I will facilitate the discussion but I want contributions from everybody in the audience. What tools and methods work for you? What tools would you like but you don't have at the moment? What's your guilty secret?
