![]() |
ASE2 CARD CATALOG ENTRY |
Instructions:
A central theme of these Guidelines is how to turn an adverse situation into a success - how to turn a challenge into a victory. The most important ingredient in achieving these goals, the most crucial resource in producing a quality product, is the people selected to do the job. The skills, talent, experience, creative abilities, or lack thereof, of the team are the determinants of success of failure in the software world. These Guidelines cover the gamut of software life cycle management activities, from pre- programmed strategic planning to post-deployment software support. They lay out the ground work of what makes up a computer-dominated system and progress to the details of what must be performed to successfully manage a large, complex software development. They also condense and assimilate into one document the range of guidance now being used for the acquisition and management of software intensive systems AF-wide. These Guidelines should be read by all levels of managers involved in the development and acquisition of major computer dominated systems within the Air Force. Program Executive Officers (PEO's), Designated Acquisition Commanders (DAC's), program managers, software maintainers, engineers, action officers, and technical personnel will all benefit from the guidance provided herein.
January 1996 George Klipper, STSC Initial Release to the PAL
Released to the PAL by the Software Technology Support Center, Hill Air Force Base. Authorization was received via electronic mail from George A. Klipper, Information Manager/BBS, Software Technology Support Center, klipperg@stsc.hill.af.mil.
This documentation is provided "AS IS" and without any expressed or implied warranties whatsoever. No warranties as to performance, merchantability, or fitness for a particular purpose exist. The user must assume the entire risk and liability of using this document. In no event shall any person or organization of people be held responsible for any direct, indirect, consequential or inconsequential damages or lost profits.
Powered by the Generic Web-Based Reuse Library (GWRL)