6 Principles to Guid Systems Development
1. The system is for the end-user. Get the end-user involved throughout systems development.
2. Establish phases and tasks to better manage systems development projects.
3. Systems development tasks are not strictly sequential. They can overlap. Also, you
Principle 1
1. The system is for the end-user. Get the end-user involved throughout
Principle 2
2. Establish phases and tasks to better manage systems development projects.
Principle 3
3. Systems development tasks are not strictly sequential. They can overlap. Also, you may need to backtrack to correct mistakes.
Principle 4
4. Systems are capital investments. They should be economically justified as such.
Principle 5
5. Establish checkpoints to reevaluate feasibility, and don't be afraid to cancel infeasible projects despite sunk costs.
Principle 6
6. Documentation should be the natural, working by-product of systems development. Don't post-document phases or tasks.