• DocumentCode
    378525
  • Title

    Design rationale for software maintenance

  • Author

    Burge, Janet E. ; Brown, David C.

  • Author_Institution
    Dept. of Comput. Sci., Worcester Polytech. Inst., MA, USA
  • fYear
    2001
  • fDate
    26-29 Nov. 2001
  • Firstpage
    433
  • Abstract
    For a number of years, members of the artificial intelligence (AI) in design community have studied design rationale (DR), the reasons behind decisions made while designing. A record of what decisions were made, and why, is especially valuable for software maintenance. One reason for this is that the software lifecycle is a long one. Large projects may take years to complete and spend even more time out in the field being used (and maintained). The combination of a long lifecycle and the typically high personnel turnover in the software industry increases the probability that the original designer is unlikely to be available for consultation when problems arise. J. Lee´s survey (1997) presents an excellent overview of DR research. There has also been work specific to software design, such as Boehm´s WinWin (1994).
  • Keywords
    artificial intelligence; software maintenance; artificial intelligence; design community; design rationale; software industry; software lifecycle; software maintenance; Artificial intelligence; Collaborative software; Computer industry; Computer science; Documentation; Personnel; Process design; Prototypes; Software design; Software maintenance;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Automated Software Engineering, 2001. (ASE 2001). Proceedings. 16th Annual International Conference on
  • ISSN
    1938-4300
  • Print_ISBN
    0-7695-1426-X
  • Type

    conf

  • DOI
    10.1109/ASE.2001.989846
  • Filename
    989846