Terminology



next up previous contents index
Next: 1 Introduction and Overview Up: PhD Thesis Stefan Halama Previous: Abbreviations

Terminology

   

It is the fate of computer science not to suffice with established terminology. Certain technical terms have to be used in this text and are explained when they are introduced. Some other, common terms are presupposed, but used in a special context. Although redundant, it is worthwhile to define these terms here to avoid misinterpretations.

   
Application.
The term application is synonymous to tool and denotes an executable operation which solves a certain category of problems, usually implemented as a distinct program or part (module) of a distinct system of programs (see also Section 2.1).

   

Architecture.
(Architectural Design) The architecture of a software system or component is not simply a snapshot of its static structure, but takes into account all dynamical aspects of system evolution and the relationship between the system and the rest of the world. In this work, the term architectural design is also understood to contain major aspects of problem analysis and functional specification.

Freeman [1] defines Architectural Design algorithmically.
Input: specifications, general context of desired system, knowledge of similar systems
Output: structural description of inside of system (definition of modules and their interfaces)
Operations: discovery of problem structure, identification of major pieces of system, establishment of relationships between parts, abstraction, decomposition

 

Binding.
In the context of the present work, binding denotes the creation process and means of systematic, unidirectional, explicit import of functionality or data, without duplication, from one programming domain into another. Simply speaking, binding(s) make available functions and data that have been implemented in a given programming environment in another programming environment. (Multi-language binding is a more common term for a less general semantics.)

 

Methodology.
According to Kleinfeldt et al. [2], methodology is ``the process, techniques, or approaches employed in the solution of a problem or in doing something: a particular procedure or a set of procedures''. Note that this definition contains a latent recursion. When the technique or procedure for the solution of a given problem is unavailable or unknown a priori, another problem arises, that is to invent (and implement) the required technique or procedure. Once the technique or procedure is available it can be executed to provide the solution for problem . Thus, methodology has essentially two different aspects: the application of methodology and the creation of methodology.

Rigorosity.
Vertical rigorousity: The depth of methodological recursion employed in the solution of the original problem. Horizontal rigorousity: The extent to which a particular, specific problem is generalized before being approached and solved.



next up previous contents index
Next: 1 Introduction and Overview Up: PhD Thesis Stefan Halama Previous: Abbreviations



Martin Stiftinger
Thu Oct 13 13:51:43 MET 1994