• DocumentCode
    1127912
  • Title

    Top-down vs. bottom-up process improvement

  • Author

    Thomas, Martyn ; McGarry, Fred

  • Author_Institution
    Praxis,Touche Ross, Bath
  • Volume
    11
  • Issue
    4
  • fYear
    1994
  • fDate
    7/1/1994 12:00:00 AM
  • Firstpage
    12
  • Lastpage
    13
  • Abstract
    There are two approaches to process improvement. The top-down approach compares an organization´s process with some generally accepted standard process. Process improvement is then the elimination of differences between an existing process and a standard one. The assumption is that, once the process is changed the generated products will be improved-or at least the risk of generating new software will he reduced. The bottom-up approach assumes that process change must be driven by an organization´s goals, characteristics, product attributes, and experiences. Change is defined by a local domain instead of a universal set of accepted practices. For example, an organization whose primary goal is improving time to market may take a significantly different approach to process change than one whose primary goal is to produce defect-free software
  • Keywords
    project management; software quality; accepted practices; bottom-up approach; bottom-up process improvement; defect-free software; generally accepted standard process; local domain; new software; organization goals; process change; product attributes; top-down approach; Capability maturity model; Computer industry; Design engineering; Design optimization; Management training; Process planning; Programming; Risk analysis; Risk management; Software engineering;
  • fLanguage
    English
  • Journal_Title
    Software, IEEE
  • Publisher
    ieee
  • ISSN
    0740-7459
  • Type

    jour

  • DOI
    10.1109/52.300121
  • Filename
    300121