knowledgemoduledesignanddevelopmentfor.docVIP

Knowledge Module Design and Development for Autonomous Intelligent Agents (PATROL Agents) by Dietmar J. Hildebrand brandy@acm.org version 1.2 rationale: The product documentation of Patrol explains programming interfaces (APIs), Patrol Script Language (PSL), Agent Configuration, and all usage and programming details, but fails to explain why and how you would use the provided features, when you design and develop a Knowledge Module (KM). This paper tries to close the gap and give hints and recommendations to KM designers based on experience collected with the members of the European Knowledge Module Factory and the PATROL Developer Network. However, the targeted audience includes managers , who need to justify the choice of using the Autonomous Intelligent Agent Technology of Patrol as a development platform from a business perspective. Introduction This paper assumes, that you are familiar with the features of the product as documented in manuals or as consequence of attending training classes. It also assumes that you are familiar with the architecture and rationales as presented in the papers Application Management using Autonomous Intelligent Agents and A Red Thread for Teaching PATROL to a Technical Audience by the same author. This paper is only a suggestion. If you can comfortably reuse design and development methodologies, which you are familiar with or which have a success record in your enterprise, feel free to apply them as far as possible to the process of designing and developing KMs. Deviating from the BMC manuals the term KM will be used to mean a group of Class definition (,which are each called a KM in the narrow sense of the Agents perspective), which are collected in a KM-List (*.kml file). The term business process is used to mean any kind of business related process such as production process, chemical process, QA process,, as well as the overall business process of the enterprise. PHASE 0 Justifying the use of Patrol technology