130 likes | 280 Views
ITS Software A TxDOT Statewide Perspective Charlie Farnham ITS Configuration Manager ITS America June 6, 2007. Agenda. TxDOT ITS Background In-House vs Outsource Software Procurement Statewide Development Contract Implementation Approach Creation of Statewide Architecture
E N D
ITS SoftwareA TxDOT Statewide PerspectiveCharlie FarnhamITS Configuration ManagerITS AmericaJune 6, 2007
Agenda • TxDOT ITS Background • In-House vs Outsource • Software Procurement • Statewide Development Contract • Implementation Approach • Creation of Statewide Architecture • Configuration Management • Software Maturity • Quality Measurements • Lessons Learned
TxDOT ITS Background • Makeup • 25 Independent Districts • 1 ITS Support Office • TMCs • 4 Initial TMCs • 2 New TMCs • Statewide Solution Needed • ATMS • Modular Subsystems • Develop or Purchase
In-House vs Outsource • In-House • Small Development Staff • Staff needed to support deployment • Limited Experience with latest ITS concepts • Limited Experience with documentation • Software Owned by TxDOT • Outsource • Larger Staff • Experience with latest ITS concepts • Experience with Documentation • Ownership depends on Procurement Process
Software Procurement • RFP for a “Work for Hire” Contract • Under Guidance of the Division • In Support of Districts and Divisions • Develop Software in Support of ITS • Provide ITS Software Support • Embrace National Standards • Embrace TxDOT Standards • Follow TxDOT’s System Engineering Model
Statewide Development Contract • Multi-Year “Work for Hire” Contract • Executed and Managed by Division • Project Manager • Configuration Manager • Unify goals of Division and Districts • Can be utilized by each of the 25 TxDOT districts • Can be utilized by other Division of TxDOT (i.e., Maintenance) • Initial Guidance from Working Group • Information Exchange thru ITS Technical Committee
Implementation Approach • Similar to System Engineering V-diagram • Develop Concept of Operations • Develop System Requirements • Develop High Level /Detailed Design • Develop code and unit test • Integration testing • Perform Limited Field Testing • Modify Design and Code • Perform Acceptance Testing • Release software
Creation of Statewide Architecture • Initial Concept was Individual Subsystem base on District needs • Created an Architecture with well defined interfaces • Allows custom development as well as third party software to be integrated
Configuration Management • For Deployed Systems • Issues reported to Division Office • Division analyses issue • Division sends issue to developers for evaluation • Developer evaluates and provides recommended solution • Division authorizes work thru Change Request • Developer performs work and delivers release
Software Maturity • Individual subsystems • Deployed in multiple districts for multiple years • Primary requests are for enhancements • Ability to deploy various configurations of subsystems
Quality Measurements • Track number of issues reported • Enhancements • Bugs • Software Acceptance Testing at Division • Acceptance of software by Districts • Reviews by Division Staff
Lessons Learned • Setup Contract where you own software • Develop Software Architecture up front • Get Buy-in from In-House Developers • Build Once and Deploy Many Times • Keep Districts Informed of Status of Development • “If you build it they will come” • Documentation Pays!
Contact Information Charlie Farnham ITS Configuration Manager Traffic Operation Division Texas Department of Transportation CFARNHAM@dot.state.tx.us (512) 506-5115