Abstract
The system developer typically co-ordinates expert system development teams and ensures goals and objectives are met in a timely fashion. A spiral model of expert system software development procedures incorporating Quality Assurance principles for determining documentation requirements is advocated to aid the system developer in his co-ordination role. Efficient use of documentation and inter-team consultation can ensure Quality Control and Quality Assurance by exposing each stage of the development to reasoned criticism.
© 1994 Association for Materials Protection and Performance (AMPP). All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise) without the prior written permission of AMPP. Positions and opinions advanced in this work are those of the author(s) and not necessarily those of AMPP. Responsibility for the content of the work lies solely with the author(s).
1994
Association for Materials Protection and Performance (AMPP)
You do not currently have access to this content.