OBJECT ARCHITECTURE
Separation of Concerns describes every day SAS analytic
and ETL programs that are coded by SAS programmers. The objective
is create a SAS application where each logical step is excecuted through
a utility that makes it easy to develop and debug. The utility is
necessary because SAS applications are chopped into a series of SAS
programs, each representing one logical step that is designed to perform
a single-function. Each logical step may be as simple a single Proc
SQL that reads a single SAS/Teradata/Oracle table.
- For SAS programmers, the payoff is code that is easy to develop
and debug.
- For Architects and IT Managers, the is the ability to independently
and continuously test each logical step on platforms like Jenkins/Hudson.
- For Business Unit Managers, the payoff is the ability to "layer
in" new features, brand-level adjustments, and GUI's.
Technical material is written for SAS developers with
5+ years experience
DOWNLOAD - 7 PAGES.
This section is only available in the fee-paid download.
Complete access is also available with Certified SAS Object Programmer
training.
Content
- SUCCESS METRICS
- SEPARATION OF CONCERNS
- SEPARATION OF CONCERNS, PART #1, CLASS - THE NEW SAS/MACRO
- SEPARATION OF CONCERNS, PART #2, PROPERTY - THE NEW MACRO VARIABLE
- SEPARATION OF CONCERNS IS DEPENDENT ON INTEGRATION OF CONCERNS
|
|
COPYRIGHT
© 1989 - 2011 Montura, Inc.
All rights reserved. This material may not be published, broadcast, rewritten
or redistributed.
All material on this website is drawn directly from US Patent Repository
Relationship Programming 7,984,422
Call 510-798-8367 to obtain you license for use today.
Violators will be prosecuted and perhaps persecuted with undesirable press
release news as well..
Terms
& Conditions -- Privacy Policy
|