The need for technical management to be defined for the acquisition, specification, design, production, and maintenance tasks of a large and complex system is essential to promote standardization and efficiency. It necessitates the formation of Integrated Product and Process Teams in the acquisition phases as well as within the successive system life cycle phases of definition, design, development, production, modification, and maintenance phases.

The contents of this book are as far as possible in compliance with the principles and concepts of published national and international standards, however, for terminology, the terms used will be based on those defined by ISO/IEC 15288/12207, MIL-STD-498, MIL-STD-961D, MIL-STD-499B and the associated guidebook documents. In addition, the processes will be defined to be compliant with CMU/SEI "Capability Maturity Model for software" and other subsequent process models when applicable.

Technical Management is based on the techniques or tasks collectively known as "Systems Engineering Management", "Configuration Management", "Data Management", Test and Evaluation", and "Risk Management" which have evolved as a response to the Technical Management crisis.

The documents main emphasis is to define the system life cycle, the design process, technical tasks, and specialist activities to be performed.

Technical Management; a pragmatic approach, may be utilized in various ways by the target audience. The document may be used as a means of defining the activities for a specific project by ‘tailoring’ or as text to serve as a guideline for a program manager or engineer. It can also be used as a text book for higher level undergraduate or graduate courses in systems and general engineering.

Synopsis
Technical Management of large and complex systems has been known by different titles in various countries and companies such as Quality Management, Program(me) Management, Engineering Management, Quality System, Project Management and other titles. The need for technical management to be defined for the acquisition, specification, design, production, and maintenance tasks of a large and complex system is essential to promote standardization and efficiency. It necessitates the formation of Integrated Product and Process Teams in the acquisition phases as well as within the successive system life cycle phases of definition, design, development, production, modification, and maintenance phases. The contents of this book are as far as possible in compliance with the principles and concepts of published national and international standards, however, for terminology, the terms used will be based on those defined by ISO/IEC 15288/12207, MIL-STD-498, MIL-STD-961D, MIL-STD-499B and the associated guidebook documents. In addition, the processes will be defined to be compliant with CMU/SEI "Capability Maturity Model for software" and other subsequent process models when applicable. Technical Management is based on the techniques or tasks collectively known as "Systems Engineering Management", "Configuration Management", "Data Management", Test and Evaluation", and "Risk Management" which have evolved as a response to the Technical Management crisis. The documents main emphasis is to define the system life cycle, the design process, technical tasks, and specialist activities to be performed. Technical Management; a pragmatic approach, may be utilized in various ways by the target audience. The document may be used as a means of defining the activities for a specific project by 'tailoring' or as text to serve as a guideline for a program manager or engineer. It can also be used as a text book for higher level undergraduate or graduate courses in systems and general engineering. It is intended that this book is used in conjunction with the "MANAGING STANDARDS" WWW page (URL http://www.airtime.co.uk/users/wysywig/wysywig.htm) and its allegiance pages.