Fraktal SAS Programming: Unterschied zwischen den Versionen
K |
K |
||
| Zeile 6: | Zeile 6: | ||
'''The pages provided here are intended to serve as guidelines for ''Beginners in SAS Based Reporting from Database Tables.''' | '''The pages provided here are intended to serve as guidelines for ''Beginners in SAS Based Reporting from Database Tables.''' | ||
| − | '''Why ''Fraktal''?''' [http://www.myvideo.ch/watch/8064214 Try this movie on measurement of coast lines by using Fractals (German audio)] | + | '''Why ''"Fraktal"''?''' [http://www.myvideo.ch/watch/8064214 Try this movie on measurement of coast lines by using Fractals (German audio)] |
'''We are using the term ''"Fraktal"'' with a ''"k"'' here to emphasize, that the programming concept introduced is derived from ''Fractal Geometry'' in Mathematics but not identical to it.''' | '''We are using the term ''"Fraktal"'' with a ''"k"'' here to emphasize, that the programming concept introduced is derived from ''Fractal Geometry'' in Mathematics but not identical to it.''' | ||
| − | #[[Preface (from Fraktal SAS Programming)|'''Preface:''' Learn about appropriate positioning of the '''"SAS System"''' from '''"SAS Institute" | + | #[[Preface (from Fraktal SAS Programming)|'''Preface:''' Learn about appropriate positioning of the '''"SAS System"''' from '''"SAS Institute"'''.]] |
| − | #[[Coding (from Fraktal SAS Programming)|'''Coding:''' Read important considerations on front-end '''program structure''' and back-end '''runtime behaviour | + | #[[Coding (from Fraktal SAS Programming)|'''Coding:''' Read important considerations on front-end '''program structure''' and back-end '''runtime behaviour'''.]] |
| − | #[[Macro (from Fraktal SAS Programming)|'''Macro:''' Find out how every aspect from your workflow definition can easily be implemented.''']] | + | #[[Macro (from Fraktal SAS Programming)|'''Macro:''' Find out how every single aspect from your '''workflow definition''' can easily be '''reflected and implemented'''.]] |
| + | |||
| + | |||
| + | '''''Fraktal SAS Programming''''' is considered to be ''"fractal"'' because the program archtitecture is suggested to use minimized i.e. smallest scale modules to comprise the implementation from. Unlike fractal curves segments, e.g. used in coast line measurement, the module size meets a lower limit introduced by [[Coding (from Fraktal SAS Programming)|syntactic properties]]. Nevertheless, the module size possible will range between a few lines and very few screen pages. Overall size of a module will very rarely reach 100 lines of code. This includes declares, communication and documentation as well as logic like loops and branches. | ||
| + | |||
| + | '''To make these guidelines compatible with the subject they present, the structure is likewise modularized to a maximum: It is comprised from half-page text slides, making single lessons, that are easy to be learned one by one.''' | ||
Version vom 5. März 2014, 14:55 Uhr
Welcome to the Introduction to Fraktal SAS Programming.
The pages provided here are intended to serve as guidelines for Beginners in SAS Based Reporting from Database Tables.
Why "Fraktal"? Try this movie on measurement of coast lines by using Fractals (German audio)
We are using the term "Fraktal" with a "k" here to emphasize, that the programming concept introduced is derived from Fractal Geometry in Mathematics but not identical to it.
- Preface: Learn about appropriate positioning of the "SAS System" from "SAS Institute".
- Coding: Read important considerations on front-end program structure and back-end runtime behaviour.
- Macro: Find out how every single aspect from your workflow definition can easily be reflected and implemented.
Fraktal SAS Programming is considered to be "fractal" because the program archtitecture is suggested to use minimized i.e. smallest scale modules to comprise the implementation from. Unlike fractal curves segments, e.g. used in coast line measurement, the module size meets a lower limit introduced by syntactic properties. Nevertheless, the module size possible will range between a few lines and very few screen pages. Overall size of a module will very rarely reach 100 lines of code. This includes declares, communication and documentation as well as logic like loops and branches.
To make these guidelines compatible with the subject they present, the structure is likewise modularized to a maximum: It is comprised from half-page text slides, making single lessons, that are easy to be learned one by one.
