G. Schreiber, B. J. Wielinga, R. de Hoog, H. Akkermanns, and W. Van de Velde. Commonkads: A comprehensive methodology for kbs development. IEEE Expert, 9(6):28-- 37, 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....on the patients themselves. The paper is structured in the following manner. Section 2 analyses the treatment administration task in the medical domain of ICCUs. The remainder of the article concentrates on modelling in the knowledge level [15] of this task following the CommonKADS methodology [20]. Section 3 describes the domain knowledge, using the object modelling technique (OMT) 19] Section 4 deals with our adaptation of the PCM method for modelling the treatment administration task, and the task tree and problem resolution methods that the application of this method gives rise to. ....

....Discussion In this paper, we have presented a model of expertise for the therapy administration task in unprotocolised clinical domains. This task has been undertaken as a design task. The model of expertise has been developed using the basic modelling components of the CommonKADS methodology [20]. However, we have not reused any functional structure proposed for the design task in the CommonKADS library (such as MR2 [4] due to the complexity of the clinical domain, rather we have selected the propose critique modify method [7] This method has been adapted to the clinical domain, ....

Schreiber G, Wielinga B, Hoog R, Akkermans H, Val de Velde W. CommonKADS: A comprehensive Methodology for KBS development. IEEE Expert 1994;9(6):28 -- 37.

....compare different methods. The methods in the library [25] were obtained by describing planning methods available in the AI planning literature which characterizes our library as system derived as opposed to domain derived libraries [27] These components adopt a division in two layers CommonKADS [15]. In the domain layer, a set of typical knowledge roles characterizes the main types of domain knowledge used in planning methods. They also help in understanding the way knowledge is structured by providing an index to the domain models used to play these roles. In the task layer, a task method ....

....world which is only consulted during planning, but not manipulated. However, from a KA perspective, we must consider how this same knowledge is used by the planner itself in defining its dynamically changing model of the world. Thus, we identify two roles for domain knowledge: static and dynamic [15]. Static knowledge roles in planning Figure 1 shows the hierarchical organization of static knowledge roles for planning [1] The leaves of the hierarchy of static roles are associated with the types of domain knowledge (domain models) that can play these roles. The plan model role defines what ....

A. Th. Schreiber, B. J. Wielinga, R. de Hoog, J. M Akkermans, and W. Van de Velde. CommonKADS: A comprehensive methodology for KBS development. IEEE Expert, 9(6): 28-37, December 1994.

....goal of MaSE is to lead the designer from the initial system specification to the implemented agent system. Domain restrictions of MaSE are similar to those of Gaia s, but in addition it requires that agent interactions are one to one and not multicast MAS CommonKADS [9] is extends CommonKADS [21] for multi agent systems. It starts with a conceptualization phas e that is an informal phase for collecting the user requirements. This methodology defines the models for the analysis and design of the system, which includes the following models: agent, task, expertise, coordination, ....

Schreiber, A., Wielinga, B. J., Akkermans , J. M., and Van de Velde W.: CommonKADS: A comprehensive methodology for KBS development. Deliverabel DM1.2a KADSII /M1RR/UvA/70/1.1, University of Amsterdam, Netherlands Energy Research Foundation ECN and Free University of Brusels, (1994) .

....on a knowledge intensive task. The central model is the knowledge model. The use of CommonKADS in this case study is limited to this model. A synopsis of the main constructs in a knowledge model can be found in Table. 1. Most constructs are well known from previous CommonKADS publications, e.g. [12]. A relatively recent addition is the notion of rule type in the domain knowledge. A rule type is used to model a set of rules that share a similar structure. For example, in the assessment application we distinguish three rule types: 1) abstraction rules that are used to abstract case values ....

A. Th. Schreiber, B. J. Wielinga, R. de Hoog, J. M. Akkermans, and W. Van de Velde. CommonKADS: A comprehensive methodology for KBS development. IEEE Expert, 9(6):28--37, December 1994.

....to ensure complete acquisition of knowledge of each type, easier to maintain the knowledge, and easier to re use individual models if another application should be developed. The basis for this approach was the CommonKADS methodology for modelling organisational and expert knowledge. CommonKADS [ Schreiber et al. 1994; Breuker van de Velde, 1994 ] is a collection of structured methods for building knowledge based systems, analogous to structured methods for software engineering; as such, it provides an enabling technology for the analysis of acquired knowledge and the design of knowledge based systems. It ....

Schreiber, G.; Wielinga, B.; de Hoog, R.; Akkermans, H.; and van de Velde, W. 1994. CommonKADS: A Comprehensive Methodology for KBS Development. IEEE Expert 28--37.

....The second step identifies the relationships between elementary behaviours. Finally, the third step identifies the organizational behaviours of the system representing the way in which agents form themselves into groups. MAS CommonKADS methodology [19] extends the models defined in CommonKADS [38] adding technology from object oriented methodologies and from protocol engineering for describing the agent protocols [36] This methodology starts with a conceptualisation phase from which defines a first description of the system from the user point of view. Then it uses a set of models for ....

A.T. Schreiber, B.J. Wielinga, J.M. Akkermans, W. Van de Velde, CommonKADS: A comprehensive methodology for KBS development, Deliverable DM1.2a KADSII /M1/RR/UvA/70/1.1, University of Amsterdam, 1994.

....Multiple knowledge models are also encouraged to separate conceptually distinct aspects (tasks, problem solving expertise, vocabularies) of the application domain. Knowledge Modelling was used to describe the process of establishing these models. The Knowledge Analysis and Design System (KADS) [139, 140] was a structured methodology developed over a decade promoting this style of development and is now accepted as a standard methodology for the design of knowledge systems in Europe. Both the GALEN and TAMBIS project adopt the principles of multiple models and knowledge level modelling in their ....

....regardless of collaborators geographic locations. In comparison, the trend in individual productivity 3.1. KNOWLEDGE BASE DEVELOPMENT TOOLS 88 concentrates on assisting modellers what to assert into the knowledge base, through systematic methods such as knowledge level descriptions (e.g. KADS [140] and ODE [17] and computer aided knowledge elicitation (e.g. WebGrid [144] Table 3.1 provides a summary of this review under these two areas. All systems address one or some of these issues. In terms of group productivity, sharing of information via annotations is the most basic technique. ....

SCHREIBER,A.T.,WIELINGA,B.,DE HOOG,R.,AKKERMANS,J.,AND VAN DE VELDE, W. CommonKADS: A Comprehensive Methodology for KBS Development. IEEE Expert Systems 9, 6 (1994), 28--37.

....as illustrates its applications to CHECK s diagnosis task. The logic of this structured design process helps to see how certain aspects of maintenance can also be simplified, when maintenance involves revisions of the G underlying a KBS. Like in knowledge modeling approaches such as COMMONKADS [25], we can exploit the link between the KL and the SL microtheories of a task, and require that a revision of the KBS design start with a revision of its underlying KL microtheory. Since in ACE SSM there is a structure preserving mapping between a KL microtheory and its SL counterpart, our proposed ....

Schreiber, G., Wielinga, B., and de Hoog, R., "CommonKADS: A Comprehensive Methodology for KBS Development," IEEE Expert, December, pp. 28-36, 1994.

....performed using off the shelf CASE tools. A problem is that CASE tools and UML provide too many features, that are not needed for ontology design. Thus, these tools are best applied if knowledge engineers and domain experts make ontology changes together. The relative interaction hypothesis [26] states that some kind of dependency exists between the structure of domain knowledge and the types of tasks it is applied to. Therefore, ontology design is anyway typically accomplished in a combination of the domain and engineering points of view and changes in the ontology require changes in ....

....for general industrial use. Our approach is limited by a two assumptions, that may reduce its applicability in some projects. First, the framework is optimized for object oriented languages only, especially those with reflective features. Second, we assume that the relative interaction hypothesis [26] (as discussed in section 5) holds, so that changes of the ontology structure are best made in a collaboration between domain experts and (knowledge) engineers. One reason for this is that current CASE tools are very general and not optimized for knowledge modeling, so that inexperienced domain ....

A. Schreiber, B. Wielinga, R. de Hoog, H. Akkermans, and W. van de Velde. CommonKADS: A Comprehensive Methodology for KBS Development. IEEE Expert, 1994.

....transitions. A task is meant to perform some functionality, usually more complex than what can be performed by a single inference action. We will use a procedural language for defining control over the execution of transitions within tasks. Our style is influenced by the KADS I [37] and CommonKADS [38] projects but it can easily translated into the terminology of most of the other approaches in knowledge engineering (see [39] Our example consists of solving a design problem (of artifacts, but also for example of schedules) The design problem is viewed as a parametric design problem, i.e. the ....

A. T. Schreiber, B. J. Wielinga, H. Akkermans, W. V. D. Velde, and R. de Hoog, "CommonKADS. A comprehensive methodology for KBS development," IEEE Expert, vol. 9, no. 6, pp. 28--37, 1994.

.... in software engineering to separate the activity of manipulating software requirements from the design of software , the actual construction of the system design [4] 20] 25] 26] Principled model based methodologies for knowledge engineering, such as DESIRE (cf. 6] 7] CommonKADS (cf. [27]) or MIKE (cf. 1] the emphasis is on specification of the (conceptual) model of the system being developed and not on specification of required behaviour properties of a system to be developed. A transparent distinction between specification of the structure of a system (or task or problem ....

Schreiber, A.Th., Wielinga, B.J., Akkermans, J.M., Velde, W. van de, and Hoog, R. de (1994). CommonKADS: A comprehensive methodology for KBS development. In: IEEE Expert, 9(6).

....is required in the process of building such systems. The knowledge acquisition process is guided by specific, often extensive, models of the domain. Thus, the process of building decision theoretic networks fits into the methodologies of knowledge engineering proposed in recent years (cf. [14]) These knowledge engineering techniques are supplemented with modelling techniques from decision analysis and statistics. Hence, designing such systems requires drawing upon techniques from various fields. It is, however, not apparent how these techniques must be combined; detailed guidelines ....

Schreiber, AT, Wielinga, B, Hoog, R de, Akkermans, H, Velde, W van der, 1994. CommonKADS: a comprehensive methodology for KBS development. IEEE Expert, 9(6), 28--37.

....behavior of a system in terms of the knowledge that is being applied in carrying out the task. It is a knowledge level way to specify a PSM in an implementation independent way. There merely exists guidelines resulting from the CommonKADS project, on how to operationalize such a model [25]. In contrast, Lama provides a symbol level architecture to implement engines: given a PSM model, a developer translates it into pseudo code, based on Blocks instructions. Since most Blocks components have been designed keeping in mind a model analysis of PSM, it facilitates the operationalization ....

G. Schreiber, B. Wielinga, R. de Hoog, H. Akkermans, and W. Van de Velde, `CommonKADS: A Comprehensive Methodology for KBS Development', IEEE Expert, 9(6), 2837, (1994).

....the cost of reuse, making our reuse library more cost effective. 4. Augmentations to UPML By the mid 1990s, a number of different PSM reuse libraries existed, and thus, there were a number of different specification languages for those PSMs (e.g. KARL, Fensel, Angele Studer 1998, and CML, Schreiber, et al. 1994). The Unified Problem solving Method Development Language (UPML) was proposed as way of summarizing and capturing the experience of these various efforts. UPML was also designed for a specific use by the IBROW 3 project, whose aim is to provide a web based broker for semi automatic retrieval and ....

Schreiber, G., Wielinga, B., de Hoog, R., Akkermans, H., and Van de Velde, W. (1994). CommonKADS: a comprehensive methodology for KBS development. IEEE Expert 9(6): 28-37.

....knowledge based systems successfully. But how should these libraries of problem solving methods be organized This approach to system construction will only work if people (and machines) can easily find components that could be used to address the problem at hand. Approaches such as CommonKADS [Schreiber et al. 1994; Breuker and Van de Velde 1994] use a functional specification of method capabilities. However, the matching of these capabilities with problem goals (e.g. in the CommonKADS Library [Valente et al. 1998] are frequently meant to be done by a human that analyzes a semi formal method description. ....

Schreiber, A. Th., Wielinga, B. J., Akkermans, J. M., Van de Velde, W. and de Hoog, R. CommonKADS: A comprehensive methodology for KBS development. IEEE Expert 9(6), December 1994.

....define domain concepts. We believe that this degree of rigidity is quite justified, given the benefits that result from the availability of domain ontologies and domain models in machine processable form. Other recent methodologies for development of knowledge based systems, such as commonKADS (Schreiber et al. 1994) and GAMES II (van Heijst et al. 1995) have adopted similar views on the role of machine readable domain ontologies in the systemdevelopment process. The language for expressing ontologies in Protg is a framebased representation system in which classes have slots of defined cardinality and data ....

Schreiber, A.T., Wielinga, B., Akkermans, J.M., van de Velde, W., and de Hoog, R. (1994). CommonKADS: A comprehensive methodology for KBS development. IEEE Expert 9:28--37.

....particular knowledge oriented and object oriented approaches. Only recently have methodologies based on purely agent oriented concepts been proposed. The knowledge oriented methodologies proposed for designing agent based systems are extensions of the knowledge engineering methodology CommonKADS [22], to which agent oriented concepts are added. The CoMoMAS methodology [7] extends CommonKADS by adding a social analysis model, identifying social competencies of agents in terms of goals, intentions, and roles; and a co operative analysis model, modeling co operation and conflict resolution ....

G. Schreiber, B.J. Wielinga, R. de Hoog, H. Akkermans, W. Van de Velde: "CommonKADS: A comprehensive methodology for KBS development". In IEEE Expert, Vol. 9, No. 6, pages 28 -- 37, 1994.

....is relative to knowledge engineering. We want to build a knowledge based mediator. Thus, we need techniques to construct all the knowledge bases useful to the mediator. Current knowledge engineering works describe the structure of a knowledge based system (KBS) through highly structured models [Schreiber al. 1994]. The domain models which describe the specific knowledge of a domain are one of the components of such models. Recently, in the knowledge engineering community, research works have been conducted to characterize domain knowledge and to help building domain models by means of ontologies [Gruber, ....

Schreiber A.T., Wielinga B.J., De Hoog R., Akkermans J.M., Van de Velde W., "CommonKads: a comprehensive methodology for KBS development", IEEE Expert, 9(6): 28-37, 1994.

....and as such we will use our analysis for knowledge acquisition and engineering. The library specifies reusable components to configure problem solvers rather than to build them from scratch. These components are represented, based on the knowledge level framework of the CommonKADS methodology (Schreiber et al. 1994). The library is based on three interconnected groups of building blocks. The first group of components is used to specify how domain knowledge is structured by the methods, the second is used to specify how the methods actually solve a planning problem, and the third is used for connecting these ....

Schreiber, A. T., Wielinga, B. J., de Hoog, R., Akkermans, J. M., & Van de Velde, W. (1994). CommonKADS: A comprehensive methodology for KBS development. IEEE Expert, 9(6):28--37.

....and what are possible ways to accomplish it. Goal reformulations also illustrate how method libraries can leverage from domain ontologies and their structure. 5 Related Work Several groups have proposed approaches for representing PSM capabilities. In CommonKADS methodology and related work [Schreiber et al. 1994, Valente et al. 1998] method capabilities are represented in a functional way, i.e. by specifying inputs and outputs, plus the knowledge used in the process (called static knowledge) Part of the semantics was also expressed by relating the method to an element of a typology of methods, ....

Schreiber, A., Wielinga, B., Akkermans. J., Van de Velde, W. and de Hoog, R. "CommonKADS: A comprehensive methodology for KBS development". IEEE Expert, 1994.

....strategies that fundamentally impact the rate of convergence, efficiency, information and communication requirements, and needed agent competencies within market designs. We sketch a general framework for such a problem solving method analysis, whereby advances in knowledge system analysis [12][10] and, in particular, nonlinear optimization and numerical mathematics [1] 3] 6] prove to be helpful. In section 2 we discuss design issues for an automated power load management system and introduce our computational market design. Simulation results are presented in section 3. A framework for ....

....application problem. As the number of successful applications quickly increases, there is a growing need for a common framework for analysis, the more so because the tackled problems as well as the problem solving strategies appear highly diverse. Applicationindependent, knowledge level [9][10][12] characterizations of problems and strategies are needed, in order to gain an improved understanding of, and formulate better guidelines for market oriented problem solving. For computational markets, the following knowledge level aspects of analysis 8 seem particularly useful to us: i) ....

Schreiber, G., B. Wielinga, H. Akkermans, W. Van de Velde, and R. de Hoog, CommonKADS - A Comprehensive Methodology for KBS Development, IEEE Expert 9(6), December 1994, pp. 28-37.

....1997, Barros, L. Nunes de et al. 1997, Valente Lockenhoff, 1993, Chandrasekaran, 1990, Motta Zdrahal, 1996] but they are not accessible for outsiders nor are they compatible (interoperable) There are some proposals for standards for reuse in knowledge engineering [Genesereth Fikes, 1992, Schreiber et al. 1994b] and there are emerging standards in interoperability [Orfali et al. 1996, JavaSoft, 1996] The objective is to investigate whether it is possible to combine and elaborate both technologies to enable scaling up software reuse to a world wide level, using the Internet. 2 Motivation We think ....

Schreiber, A. T., Wielinga, B. J., de Hoog, R., Akkermans, J. M., & Van de Velde, W. (1994b). CommonKADS: A comprehensive methodology for KBS development. IEEE Expert, 9(6):28--37.

No context found.

G. Schreiber, B. J. Wielinga, R. de Hoog, H. Akkermanns, and W. Van de Velde. Commonkads: A comprehensive methodology for kbs development. IEEE Expert, 9(6):28-- 37, 1994.

No context found.

SCHREIBER, A. T., WIELINGA, B. J., DEHOOG, R., AKKERMANS,J.M.&VANDEVELDE, W. (1994a). CommonKADS: A comprehensive methodology for KBS development. IEEE Expert, 9, 28---37.

No context found.

A.Th. Schreiber, B.J. Wielinga, R. de Hoog, H. Akkermans, and W. van de Velde (1994): CommonKADS: A Comprehensive Methodology for KBS Development. In: IEEE Expert, December 1994, 28-37.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC