Rationale-based software engineering

Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. This information becomes increasingly criticalas software development becomes more distributed and encompasses the corporate knowledge both used and refined during the development process. The capture of rationale helps to ensure that decisions are well thought out and justifiedand the use of rationale can help avoid the mistakes of the past during both the development of the current system and when software products (architectureand design, as well as code) are reused in future systems. INDICE: Part 1: Introduction.- 1) What is rationale and why does it matter- 2) What makes software different - 3) Rationale and software engineering - 4) Learning from rationale research in other fields - 5) Decision-making in software engineering.- Part 2: Uses for rationale.- 6) Presentation of rationale- 7) Evaluation - 8) Support for collaboration - 9) Change analysis.- Part 3:Rationale and software engineering.- 10) Rationale and the software life-cycle - 11) Rationale and requirements engineering - 12) Rationale and software design - 13) Rationale and software verifcation, validation, and test - 14) Rationale and software maintenance - 15) Rationale and software reuse.- Part 4: Frameworks for rationale-based software engineering.- 16) A conceptual framework- 17) An architectural framework - 18) Rationale-based software engineering: summary and prospect.- Bibliography, Glossary, Index.

• ISBN: 978-3-540-77582-9
• Editorial: Springer
• Encuadernacion: Cartoné
• Páginas: 320
• Fecha Publicación: 01/04/2008
• Nº Volúmenes: 1
• Idioma: Inglés