From KISS to Implementation: A Study of Problems, Solutions and Open Issues

Andrea Valente; Patrick van Bommel

From KISS to Implementation: A Study of Problems, Solutions and Open Issues

Radboud University Nijmegen

Publikation: Kapitel i bog/rapport/konference-proceeding › Bidrag til rapport › Forskning

Abstract

A main idea in this paper is that KFD is a formal language, so we can forget about C++ or other implementation languages, and consider KFD as a very high level programming language. KFD is readable, normally small and closer to informal specification than any other languages, but it's not ambiguous and quite easy to parse, in order to produce code for the system. This means that KFD is really a portable language and that we can improve, optimize, implementation technique in future without involving the KFD programmers, or existing KFD definition of a system. When we create a complete KISS formal description of a system, we are definitely writing a program.

Originalsprog	Engelsk
Titel	Technical Note CSI N9505 : University of Nijmegen (NL)
Antal sider	55
Publikationsdato	nov. 1995
Status	Udgivet - nov. 1995

Bibliografisk note

Dept. of Information Systems, Faculty of Mathematics and Computing Science, University of Nijmegen, Toernooiveld,
NL-6525 ED Nijmegen, The Netherlands

Citationsformater

@inbook{fbe72f69c36f4e91962dd6c7cc0c0b2b,

title = "From KISS to Implementation: A Study of Problems, Solutions and Open Issues",

abstract = "A main idea in this paper is that KFD is a formal language, so we can forget about C++ or other implementation languages, and consider KFD as a very high level programming language. KFD is readable, normally small and closer to informal specification than any other languages, but it's not ambiguous and quite easy to parse, in order to produce code for the system. This means that KFD is really a portable language and that we can improve, optimize, implementation technique in future without involving the KFD programmers, or existing KFD definition of a system. When we create a complete KISS formal description of a system, we are definitely writing a program.",

author = "Andrea Valente and {van Bommel}, Patrick",

note = "Dept. of Information Systems, Faculty of Mathematics and Computing Science, University of Nijmegen, Toernooiveld, NL-6525 ED Nijmegen, The Netherlands",

year = "1995",

month = nov,

language = "English",

booktitle = "Technical Note CSI N9505",

}

TY - GEN

T1 - From KISS to Implementation: A Study of Problems, Solutions and Open Issues

AU - Valente, Andrea

AU - van Bommel, Patrick

N1 - Dept. of Information Systems, Faculty of Mathematics and Computing Science, University of Nijmegen, Toernooiveld, NL-6525 ED Nijmegen, The Netherlands

PY - 1995/11

Y1 - 1995/11

N2 - A main idea in this paper is that KFD is a formal language, so we can forget about C++ or other implementation languages, and consider KFD as a very high level programming language. KFD is readable, normally small and closer to informal specification than any other languages, but it's not ambiguous and quite easy to parse, in order to produce code for the system. This means that KFD is really a portable language and that we can improve, optimize, implementation technique in future without involving the KFD programmers, or existing KFD definition of a system. When we create a complete KISS formal description of a system, we are definitely writing a program.

AB - A main idea in this paper is that KFD is a formal language, so we can forget about C++ or other implementation languages, and consider KFD as a very high level programming language. KFD is readable, normally small and closer to informal specification than any other languages, but it's not ambiguous and quite easy to parse, in order to produce code for the system. This means that KFD is really a portable language and that we can improve, optimize, implementation technique in future without involving the KFD programmers, or existing KFD definition of a system. When we create a complete KISS formal description of a system, we are definitely writing a program.

M3 - Report chapter

BT - Technical Note CSI N9505

ER -