• Cost
  • More money buys larger development team
  • Too little money means cannot adequately solve problem
  • Too much money means coordination difficulties
• Time
  • More time allows better quality, more features
  • Too little time prevents adequate functionality, quality, feedback for revision
  • Too much time may get in the way of feedback, which can be a major factor for product improvement
• Quality
  • Both developers and customers want to be involved with high quality work
  • Skimping on quality satisfies no one
  • Focusing on quality can give rise to better design and analysis, perhaps even saving time in the long run!
• Scope
  • Choices can be made regarding how much functionality is incorporated into a release of software
  • Too much scope may make quality or time suffer
  • Small scope can allow release quickly, with high quality, and relatively low cost

Quality has two components

• External: what the customer sees
• Internal: what the programmer sees

created May 14, 2003 last revised May 15, 2003

previous   next