Hi Everyone.
I'd appreciate your thoughts and pointers about how to design, track development and achieve customer acceptance of a database (Access being the preferred route).
I would have a workflow of:
1. Discuss what the customer wants - this gets you Quality expectations, Acceptance criteria and major requirements.
2. Break the major requirements into smaller requirements which can be prioritised and estimated.
3. Create a plan for the tasks (design db, design style, build tables, queries, forms, test, and no doubt change)
4. Cope with change (oh, by the way, can you just...) (I don't like it ....)
What I'm interested in is techniques and/or tools to manage / track the above. Most of the books I've read about Access go into the techniques of how to use Access but don't mention the User / Business reasons for having a database in the first place. Any hints, tips, websites, books, forums, ideas welcomed.
Many thanks
Ray
Posted by: rayfrew@gmail.com
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (1) |
Tidak ada komentar:
Posting Komentar