| Popis: |
Selecting the "right" software methodology may save you a fortune in the long run. Consider these figures: Several studies indicate that maintenance consumes 67% of the software life cycle: the remaining 33% is development. Once a software system becomes operational. It may be used for five to 20 years (some IBM 1401 programs are still around).Consider the result if a methodology helps you save at least 10% in total life-cycle costs. This savings may result in different ways. For example, depending on the methodology, you may spend more on the front-end development cycle (in the design stage) and save 20% on the subsequent maintenance, including repairs and enhancements.Keep an open mind when choosing a methodology. Be willing to learn and discover no matter what your position---president or programmer. Remember that a highly promoted or well-known methodology is not necessarily the best.Professionals should learn more than one methodology, since one may not be suitable for every application. To save on training costs and to standardize, organizations may select one major methodology and use another when an application demands. When possible, methodologies may be judiciously combined. Large companies may have methodology specialists, while small companies might use outside consultants specializing in the appropriate methodology.Most methodologies can be divided into two major groups: functional and data-structured. With the first type, data flow analyses (for instance. |
