Txpros JAD Session Summary

JAD Summaries – TSD Standards

1.3.3 Version 0.3April 7, 2008

FINAL Version

TxPROS JAD Summary

TSD Standards

January 9, 2008
CampHubbard, Bldg. 5 GSD Meeting Room

PURPOSE: The purpose of the TSD Standards JAD session was to jointly discuss all applicable TSD standards for the project and any concerns related to security, infrastructure and database design.

PARTICIPANTS:

DISCUSSION TOPICS:

• Discuss JAD purpose and give project status to date.
• Understand and agree on architectural standards that must be met to satisfy TSD and TFT requirements.
• Understand the technical architectural approach that PSDC is proposing and obtain consensus of direction.
• Understand the modeling requirements that need to be met by the project and obtain consensus on approach to accomplish.
• Agree on the database approach, structure, usage and support direction for the project.
• Understand and agree on the approach to integrate with TxDOT infrastructure and resource limits.
• Understand Web development standards that need to be met by the project.
• Understand any security issues that need to be addressed by the project and the approach to accomplish.
• Identify any additional TSD concerns not already identified.

CONSENSUS ITEMS:

1. The following TSD standards have been added as requirements to the TxPROS project:

1.1.The TxPROS system will use an Oracle database, and 10-g release II is recommended.

1.2.TxDOT will provide GIS data to TxPROS in shape files.

1.3.For security reason, there will be a “check-back” feature. When a user logs in, a system

greeting will tell them their last login date and time.

RELATED ITEMS, YET TO BE RESOLVED:

Within the next six months, TxPROS will want to test and collect performance metrics. TxDOT will have to obtain hardware for this.

TxPROS will need to get Oracle comparison information of the relationship between the AIX CPU that TxDOT is using vs. the Intel CPU that ProMiles would use so that they can extrapolate the CPU requirements that ProMiles has identified as TxPROS requirements.

TxPROS will need to determine the number of saved routes there can be in a customer’s and in a permit officer’s account.

TxPROS will need to identify retention requirements.

Once the session management module has been designed, TSD will need to review for security purposes.

It will need to be determined how to allow contractors to access the Restriction Management application for entry of Restrictions if necessary.

ITEMS IDENTIFIED FOR FUTURE SESSIONS OR PARKING LOT:

There were no items identified for future sessions or parking lot.

LESSONS LEARNED:

Gathering different departments together that perform a piece of a large process, helps all to understand the entire process and also helps identify ways the current system works well in addition to ways it does not.

DETAILED JAD MEETING NOTES:

Please see detailed JAD meeting notes for further information.

1