1. TPS/Source ™ Source Control and Release Management System

2. Source Control & Release Management Software  Provides a single repository for source code  Supports multiple releases and variants  Supports multiple platform installations  Provides standard checkout/checkin control  Provides impact analysis functionality

3. Source Control & Release Management Software (cont)  Provides a comprehensive audit trail  Provides full backout capability  Controls user access

4. TPS/Source  Provides a single repository for source code –Version Control separated from Release Management –Library is pre-defined with initial releases and groups –Fully expandable to support all applications –Multiple libraries can be linked together  Supports standard checkin/checkout control –Checkout function configurable –Controls checkin –Provides information on current checkout activity –Provides version control/update

5. TPS/Source  Supports multiple releases and variants –Releases/Levels are predefined –Releases can be defined as full or incremental –Supports standard development cycle support  Supports multiple platform installations –Provides functionality for applications requiring variants for CISC/RISC/PA-RISC –Supports software delivery to multiple platforms

6. TPS/Source  Provides impact analysis –Full XREF file provides ‘who uses’ information –‘build -check_only’ provides dependency data  Provides comprehensive audit trail –Daily log file records all commands/activity –Version control provides source audit ability

7. TPS/Source  Provides full backout capability –Reverse checkin capability –Cancel checkout –Reverse installations –Access to prior versions of source/application  Controls user access –Access controlled by user or group –Access authorized to library levels

8. TPS/Source Related Functions  TPS/Make –Provides for ‘top down’ compile/bind  TPS/Scan –Multi-use directory search utility –Configurable selection criteria –Capability to automatically create macros  TPS/Build –Provides for external functionality using library structures