Abstract :
Many software engineers believe a detailed solution should be created and meticulously verified as solving the problem before any code is written. On the other hand, a few of us believe that we have not solved the problem until we deliver the software and prove it works. This difference in when we believe the problem is solved causes us to view the requirements document differently. The author believes requirements should describe the problem, not the solution, because the problem is not solved until we have got the code running.
Keywords :
program verification; software development management; software engineering; critical requirements; project management; requirements planning; software development; software engineering; software requirements; Costs; Educational institutions; Information analysis; Information security; Lean production; Prototypes; Reliability engineering; Robustness; Software quality; Software systems;
