HCSD unit development process: Step-wise process improvement

  • David Emery
  • Jas Madhur
Software Development Methods
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1088)


Hughes Canada has been involved with the development of the Canadian Automated Air Traffic Control System (CAATS) software since 1993. The program, originally estimated to be over a million lines of Ada code, has evolved from prototyping concepts and requirements to producing operational software. This paper describes the evolution of the procedures for software development. We explain the reasons behind the changes made to the unit development process, and show our movement from ad-hoc through qualitative to quantitative process enhancement, consistent with our transition from prototyping to production.


Software Process Software Management Ada 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Kal Toth and Jas Madhur. “Establishing and Maintaining an Infrastructure for a Quality System.” In Proceedings of the 1995 National Council of Systems Engineering (NCOSE) Symposium, St. Louis, Missouri.Google Scholar
  2. [2]
    Trevor Paine, Kal Toth and Philippe Kruchten, “Modernizing ATC Through Modern Software Methods.” Proceedings of the 1993 Conference of the Air Traffic Control Association, Nashville, Tennessee.Google Scholar
  3. [3]
    Watts Humphrey, Terry Snyder and Ron Willis, “Software Process Improvement at Hughes Aircraft,” IEEE Software, vol 8, no 7, pgs 11–23, July_1991.Google Scholar
  4. [4]
    Philippe Kruchten, “The 4+1 View Model of Architecture.” IEEE Software, v 12, no 6, pages 42–50 November 1995.Google Scholar
  5. [5]
    Barry W. Boehm, “The Spiral Model of Software Development and Enhancement.” Proceedings of the International Workshop on The Software process and Software Environments. Coto de Caza, CA March 1985.Google Scholar
  6. [6]
    Watts Humphrey. Managing the Software Process. New York, Addison Wesley, 1989.Google Scholar
  7. [7]
    U.S. Department of Defense. Military Standard 2167A: Defense System Software Development. Washington, DC, February 29, 1988.Google Scholar
  8. [8]
    U.S. Department of the Air Force, Rome Air Development Center. Specification of Software Quality Attributes. RADC-TR-85-37, Rome, NY February 1985.Google Scholar
  9. [9]
    RCTA, Inc. Software Considerations in Airborne Systems and Equipment Certification. DO-178B, RCTA, Inc, Washington, DC, December 1992.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1996

Authors and Affiliations

  • David Emery
    • 1
  • Jas Madhur
    • 2
  1. 1.Systems DivisionHughes Aircraft of CanadaRichmondCanada
  2. 2.MacDonald Dettwiler and AssociatesRichmondCanada

Personalised recommendations