Fraktal SAS Programming: Unterschied zwischen den Versionen
K |
K |
||
Zeile 16: | Zeile 16: | ||
##[[Explicit Coding (from Fraktal SAS Programming)|Explicit Coding]] | ##[[Explicit Coding (from Fraktal SAS Programming)|Explicit Coding]] | ||
#[[Macro (from Fraktal SAS Programming)|'''Macro:''' Find out how every single aspect from your '''workflow definition''' can easily be '''reflected and implemented'''.]] | #[[Macro (from Fraktal SAS Programming)|'''Macro:''' Find out how every single aspect from your '''workflow definition''' can easily be '''reflected and implemented'''.]] | ||
− | + | ##[[Straightforward Coding (from Fraktal SAS Programming)|Straightforward Coding]] | |
+ | ##[[Generalized Approach (from Fraktal SAS Programming)|Generalized Approach]] | ||
+ | ##[[Advanced Coding (from Fraktal SAS Programming)|Advanced Coding]] | ||
+ | ##[[Symbol Tables (from Fraktal SAS Programming)|Symbol Tables]] | ||
+ | ##[[Parameter Scope (from Fraktal SAS Programming)|Parameter Scope]] | ||
+ | ##[[Extending Control (from Fraktal SAS Programming)|Extending Control]] | ||
+ | ###[[Apply Logic (from Fraktal SAS Programming)|Apply Logic]] | ||
+ | ###[[Process Metadata (from Fraktal SAS Programming)|Process Metadata]] | ||
+ | ####[[What is Metadata? (from Fraktal SAS Programming)|What is Metadata?]] | ||
+ | ####[[Process Metadata: List (from Fraktal SAS Programming)|Process Metadata: List]] | ||
+ | ####[[Process Metadata: Numbered (from Fraktal SAS Programming)|Process Metadata: Numbered]] | ||
+ | ####[[Process Metadata: Direct (from Fraktal SAS Programming)|Process Metadata: Direct]] | ||
+ | ###[[Workflow Documentation (from Fraktal SAS Programming)|Workflow Documentation]] | ||
+ | ###[[Realtime Information (from Fraktal SAS Programming)|Realtime Information]] | ||
'''''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. | '''''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 tiny lessons that are easily taken one by one.''' | '''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 tiny lessons that are easily taken one by one.''' |
Version vom 14. Mai 2014, 13:09 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 tiny lessons that are easily taken one by one.