The earlier you discover the problems, the less time is wasted and the fewer things are affected. Wait a minute! There are better ways to do this! You may want to say, “But I don't have time to figure all these things out, I've got to get this done! The deadlines are tight on this project!” Before you do, take a moment to consider how much quicker it is to fix a problem early in the process, rather than later. Developers talk to the client for a few minutes, get a general idea of what the client needs, and then sit down at the computer and start to code… Blueprints? Who needs them? Heck, you know what you are doing and you've been inside a lot of houses right? This notion, of course, seems absurd, but that's exactly the way most software applications are built today. You get the materials delivered and you grab the first 2x4 and start building the house. So, the first thing you do is go to the lumberyard and purchase various materials - lumber, windows, doors, drywall, roofing and cement blocks. You're not sure exactly what you want to build, but you know you want a “nice” house, a “big” house, and you know that you have a budget of $200,000. So, how can developers avoid these errors and create a solid design for their software? This article will describe various methods for gathering software requirements and writing Use Cases - the first two steps in the software development process. This is huge! Finding problems while they are just in the planning stages is MUCH easier to deal with than finding them after the code has been written. Studies indicate that between 40% and 60% of all defects found in software projects can be traced back to errors made while gathering requirements.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |