Development Process?

[monkeytunes]

As someone who's worked with Access since 95, but only started developing in earnest a year or three ago, I often find myself spending an inordinate amount of time going back and fixing silly mistakes - correcting naming conventions, correcting forms built on tables instead of queries, forgetting which object is a backup and which is in-progress - things like that. As I get better, I'm developing intuitive protocols and methods to get things in order, but I just got handed an urgent project, and I want to make sure I get this one right the first time; there won't be time to go back and correct cut-corners or screw ups. Anybody have checklists or processes they can share that help them get things right the first time around? (I can't be the only one who hasn't committed everything to memory yet!)

 

[KenHigg]

1. Walk the process.
2. Identify Entities
3. Identify Attributes
4. Do a logical data model
5. Normalize
6. Do mock up forms
7. Walk through forms with end users
8. Do the db
9. Test
10. Deploy
11. Support

 

[Matt Brown]

As kennHigg says follow the Database Life Cycle and you wont go far wrong:

I normally follow:

1.Requirements Analysis (Define spec from users and producers of data).
2.Logical design (ER modelling and Normalisation).
3.Physical design
4.Data Distribution
5.Database implementation and upgrading/updating

 

[KenHigg]

Good read