Home 
Papers
Papers
Migration of a Flexible Reporting System from SAS 6.12 to SAS 9.1.3
Page 8 of 8
7. Project metrics
To illustrate the size of this project the following metrics are presented below:
|
Team size |
5 people |
|
|
|
||
|
Actual project effort excluding validation |
Approx. 100 days |
|
|
Effort by Skill set: |
SAS Knowledge |
40 days |
|
Delphi Knowledge |
30 days |
|
|
Integration Technology Knowledge |
5 days |
|
|
Project Management |
10 days |
|
|
Documentation |
15 days |
|
|
|
||
|
User interface screens: |
FRS |
7 |
|
HDS |
7 |
|
|
Message system |
4 |
|
|
|
||
|
Total number of SAS programs: |
||
|
User interface: |
SAS programs |
31 |
|
SAS macros |
63 |
|
|
Migrated: |
SAS programs |
126 |
|
SAS macros |
15 |
|
8. Lessons Learned
Every project brings new insights; these are some of our experiences:
- Migrating from version 6.12 to version 9.1.3 of SAS thereby skipping version 8 does not present specific additional difficulties.
- Migrating from PC based SAS to server based SAS poses as a main challenge that the users are using the same temporary storage files .
- When communicating via Integration Technologies it is possible to maintain a user specific SAS Work environment during the entire session allowing the use of work -datasets, -macros, -formats, etc.
- Creating a windows based user interface which communicates with SAS is not only very controllable, but is also very fast in comparison to, for example a browser based application.
9. Tips
- We found it useful to create a proof of concept environment to build experience with PC development environments communicating with Integration Technologies.
- Using information datasets to control the content and behaviour of the user interface keeps the intelligence in SAS, making maintenance easier.
- A Windows based user interface allows a broader range of functionality, such as a Multiple Document Interface, allowing the subsystems to run simultaneously in one main window.