Stage-oe-small.jpg

Techreport665: Unterschied zwischen den Versionen

Aus Aifbportal
Wechseln zu:Navigation, Suche
K (Added from ontology)
 
K (Added from ontology)
Zeile 1: Zeile 1:
 +
{{Publikation Author
 +
|Rank=1
 +
|Author=Dieter Landes
 +
}}
 
{{Publikation Author
 
{{Publikation Author
 
|Rank=2
 
|Rank=2
 
|Author=Rudi Studer
 
|Author=Rudi Studer
}}
 
{{Publikation Author
 
|Rank=1
 
|Author=Dieter Landes
 
 
}}
 
}}
 
{{Techreport
 
{{Techreport
Zeile 19: Zeile 19:
 
|Abstract=Not only knowledge acquisition, but also the principled transition from knowledge acquisition to implementation is an important question in knowledge engineering. This paper focuses on this transition and characterises the design phase of the MIKE approach to model-based incremental development of knowledge-based systems. The role of non-functional requirements in the development process is discussed and it is argued that for reasons of transparency, the description of the design should not just contain the description of the artefact, but should additionally include a record of the design decisions and their motivation, i.e. their relationship to the requirements posed. DesignKARL is outlined as the formalism for describing the artefact as well as design decisions and their rationale in MIKE.
 
|Abstract=Not only knowledge acquisition, but also the principled transition from knowledge acquisition to implementation is an important question in knowledge engineering. This paper focuses on this transition and characterises the design phase of the MIKE approach to model-based incremental development of knowledge-based systems. The role of non-functional requirements in the development process is discussed and it is argued that for reasons of transparency, the description of the design should not just contain the description of the artefact, but should additionally include a record of the design decisions and their motivation, i.e. their relationship to the requirements posed. DesignKARL is outlined as the formalism for describing the artefact as well as design decisions and their rationale in MIKE.
 
|VG Wort-Seiten=
 
|VG Wort-Seiten=
|Download=1994_665_Landes_The Design Proc_1.gz
+
|Download=1994_665_Landes_The_Design_Proc_1.ps.gz
|Forschungsgebiet=
 
 
|Projekt=
 
|Projekt=
 
|Forschungsgruppe=
 
|Forschungsgruppe=
 
}}
 
}}

Version vom 15. August 2009, 16:22 Uhr


The Design Process in MIKE




Published: 1994 Dezember
Nummer: 285
Institution: University of Karlsruhe, Institute AIFB
Erscheinungsort / Ort: 76128 Karlsruhe, Germany
Archivierungsnummer:665

BibTeX



Kurzfassung
Not only knowledge acquisition, but also the principled transition from knowledge acquisition to implementation is an important question in knowledge engineering. This paper focuses on this transition and characterises the design phase of the MIKE approach to model-based incremental development of knowledge-based systems. The role of non-functional requirements in the development process is discussed and it is argued that for reasons of transparency, the description of the design should not just contain the description of the artefact, but should additionally include a record of the design decisions and their motivation, i.e. their relationship to the requirements posed. DesignKARL is outlined as the formalism for describing the artefact as well as design decisions and their rationale in MIKE.

Download: Media:1994_665_Landes_The_Design_Proc_1.ps.gz



Forschungsgebiet