Techreport624: Unterschied zwischen den Versionen
K (Added from ontology) |
K (Wikipedia python library) |
||
| (3 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
| + | {{Publikation Erster Autor | ||
| + | |ErsterAutorNachname=Landes | ||
| + | |ErsterAutorVorname=Dieter | ||
| + | }} | ||
{{Publikation Author | {{Publikation Author | ||
|Rank=2 | |Rank=2 | ||
|Author=Rudi Studer | |Author=Rudi Studer | ||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{Techreport | {{Techreport | ||
| Zeile 14: | Zeile 14: | ||
|Institution=University of Karlsruhe, Institute AIFB | |Institution=University of Karlsruhe, Institute AIFB | ||
|Number=319 | |Number=319 | ||
| − | | | + | |Archivierungsnummer=624 |
}} | }} | ||
{{Publikation Details | {{Publikation Details | ||
|Abstract=Non-functional requirements significantly affect and determine the quality of software systems. In this paper it is shown how non-functional requirements are modelled in MIKE, an approach to the development of knowledge-based systems. A semi-formal hypermedia-based model is used to describe the results of the elicitation and interpretation of non-functional requirements and their relationships. Non-functional requirements are the driving force behind the decisions taken in the design phase of MIKE. The impact of non-functional requirements on design decisions and interdependencies between design decisions are explicitly recorded in an additional model in MIKE, thus resulting in a rich documentation of the rationale of design decisions and also providing an important contribution to the traceability of these requirements. | |Abstract=Non-functional requirements significantly affect and determine the quality of software systems. In this paper it is shown how non-functional requirements are modelled in MIKE, an approach to the development of knowledge-based systems. A semi-formal hypermedia-based model is used to describe the results of the elicitation and interpretation of non-functional requirements and their relationships. Non-functional requirements are the driving force behind the decisions taken in the design phase of MIKE. The impact of non-functional requirements on design decisions and interdependencies between design decisions are explicitly recorded in an additional model in MIKE, thus resulting in a rich documentation of the rationale of design decisions and also providing an important contribution to the traceability of these requirements. | ||
|VG Wort-Seiten= | |VG Wort-Seiten= | ||
| − | |Download= | + | |Download=1995_624_Landes_The_Treatment_o_1.ps.gz |
| − | |||
|Projekt= | |Projekt= | ||
| − | |Forschungsgruppe= | + | |Forschungsgruppe=Wissensmanagement |
}} | }} | ||
Aktuelle Version vom 16. Oktober 2009, 17:24 Uhr
Published: 1995
Juni
Nummer: 319
Institution: University of Karlsruhe, Institute AIFB
Erscheinungsort / Ort: 76128 Karlsruhe, Germany
Archivierungsnummer: 624
Kurzfassung
Non-functional requirements significantly affect and determine the quality of software systems. In this paper it is shown how non-functional requirements are modelled in MIKE, an approach to the development of knowledge-based systems. A semi-formal hypermedia-based model is used to describe the results of the elicitation and interpretation of non-functional requirements and their relationships. Non-functional requirements are the driving force behind the decisions taken in the design phase of MIKE. The impact of non-functional requirements on design decisions and interdependencies between design decisions are explicitly recorded in an additional model in MIKE, thus resulting in a rich documentation of the rationale of design decisions and also providing an important contribution to the traceability of these requirements.
Download: Media:1995_624_Landes_The_Treatment_o_1.ps.gz