|
|
Access
Database Programming
Using Best Practices & Agile Modeling
In
our Access Database Software development we use 'Best
Practice Protocols' to insure the highest user satisfaction along
with lowest code maintenance
- Help define / refine client's
vision - Golden Rule 1!
- Conduct interviews
- Key: stakeholders
& users
- Hold informal development
meetings bi-weekly
- Gather initial requirements
- Collect reports, documents,
etc.
- Focus on initial up-stream
system design - Golden Rule
2!
- List risks & inform
client
- Set up change control process
- Define style guide (fonts,
colors, etc)
- Analyze interactivity nees:
functions, math, adjacent systems
- Study competitive products
- Include competitive
requirements
- Turn accepted requirements
into contract specs - Golden
Rule 3!
- Supply initial cost / time
estimates
- Hi-Low range cost breakdown
- Long-short time breakdown
- Create mock-up user prototype
from requirements
- Test prototype with
key users/stakeholders
- Revise prototype
- Revise prototype
- Stakeholders sign
off on design docs -
Golden Rule 4!
- Begin documentation - help
file creation (if specs require)
- Revisit time / cost estimates
- Begin full development
& programming
- Set naming conventions
for objects
- Set Up milestones schedules
- Set up change request
process
- Control feature
creep - Golden Rule
5!
- Plan for short / long term
componet reuse of...
- Code, personnel, documentation,
etc..
- Focus on quality assurance
process
- Perform daily builds
- Broken builds fixed
before any new code - Golden
Rule 6!
- Perform weekly code
reviews
- Integrate milestone stages
& debug completely before next stage
- Minimize / control external
outsourcing
- Help client address long
term needs & risks - Golden
Rule 7!
- Address code maintenance
& future changes
- Address backup strategy
- Address security strategy
- Address computer risk
(resolution, performance)
- Address network risk
- Address archive strategy
|
