Thinking in OO - Analysis and Design

                        Step 1) understand the Appl purpose
                                  find the Users
                                  find their needs
                                  User groups:
                                   1) the people typing in the Appl
                                   2) is Tech support (security, DBA, etc)
                                   3) "off-stage" (legal)

                               Analysis and Design
                               Analysis answers the question "What does this Appl do?"
                               Design answers the question "How are we going to do that?"

                         2) break the appl into "parts" (How many classes do we create?)
                             which parts handle the Business Rules? (Entity classes)
                             which parts handle the SQL? (Action classes)
                             which parts talk to the User? (Web classes)

                         3) Define the Entity Classes (Set of Data, think DB Record)
                              the sets of data
                              their names
                              each field in the set
                                name
                                initial value
                                the business rules for
                                  min value
                                  max value
                                  any constraints

                         4) Define the Action Classes
                              list the routines (functions/methods/actions)
                               each class should have (implement)
                               this is an Interface (a list of methods)
                              write and test each routine (method)

                         5) Define the User interaction (Web pages)
                              write and test each Web Page