Complete and Integrated Lifecycle Management

Challenges 1

Background Current Environment – Status Quo Waterfall – Phased approach  Each development phase is a distinctive work package in SDLC Manually driven process  Hand-off from phase to phase with no traceability  Little use of automated tools  People driven Proposed Environment Implement automated tools and process to support a software delivery optimization model  Pilot project to test the new tools and process

Challenges Inability of teams to effectively communicate Key person syndrome Missed deadlines Increased costs due to rework Inconsistent estimates Difficultly in maintaining and supporting development efforts Inability to effectively manage resources Difficulty in the outsourcing of tasks Lack of system documentation

Impact of these Issues on Business Inability to assume additional revenue generating work Reduced profitability Non-compliant development processes, i.e. Bill 198 and SOX

Solution 2

Pilot Objectives – Success Criteria Repository for all system documentation Automated Review and Approval process for system development Traceability of system documentation to source code Methodology which is compliant with Bill 198 and SOX Detailed system documentation of source code Efficiency gains of 30% from existing procedures

Solution CaliberRM  Business requirements are written and tracked within the tool  CaliberRM is also used as a repository for design, testing (Unit testing and Functional) and business requirements Together Control Center  It is used by system analysts and architects to design solutions and reverse engineer existing code base  Tool helps to generate system documentation with detailed information Scenario Tester  It is used as a test automation tool and test case repository to execute and capture the testing for functional and regression test cases

Solution Details Figure 1

Solution Details – Business Stage Business Analysts are no longer required to create functional specifications using static Word template as CaliberRM replaces the Word templates CaliberRM creates functional requirements document in current corporate format, so clients are not unaffected The tracking of changes throughout the business phase is no longer a manual procedure as CaliberRM tracks the changes and forward them to individuals for sign-off The review cycle is automated with the introduction of CaliberRM and is expanded to include Designers, Development and QA CaliberRM is the central repository for project and Core documentation. This provides the team with instant notification of changes from internal source/team so that appropriate action can be taken from design changes to test coverage Business Analysts have feedback from the Ambiguity reviews in Caliber RM prior to being issued to the clients. As the Core application rules are available online, new requirements/rules can be easily assessed by the Business Analyst to confirm that nothing has been omitted

Solution Details – Design Stage Technical Specifications are created using Together Control Center replacing MS Word to adapt an industry standard representation (UML- Unified Modeling Language) of the underlying source code The design documentation is linked back to CaliberRM allowing for seamless flow of requirements into design with full traceability and ability to perform impact analysis Reverse-engineering of the source code, can be adjusted and augmented accordingly to allow the development team to create, modify and review the source code effectively Together generates system documentation with detailed information

Solution Details – Coding Stage Individual programmers begin construction with a complete list of business requirements, designs, and code/programs (technical specifications) Developers will have the mechanism through CaliberRMs’ discussions and active notification to communicate questions and inconsistencies back to Designers and Business Analysts – thus allowing them to more efficiently reduce ambiguity in their coding effort and keep documentation current

Solution Details – Testing Stage Quality Assurance Analysts are no longer required to create testing specifications using the Word or excel templates. CaliberRM replaces the Word/Excel templates. Quality Analyst review requirements, design unit test plans to create testing scenarios. The scenarios are validated by the business analyst or stake holders to ensure adequate testing coverage prior to the test execution stage. Test scenarios approved are entered into the testing tool for automation prior to code delivery to QA CaliberRM coordinates document storage, reviews cycles, change requests, impact analyses and has built in traceability and visibility of the development methodology

Benefits 3

Pilot Results Improved quality Reduced dependency on key people - Key Person Syndrome 100% testing coverage Provides the ability to off shore code – Increased capacity Efficiency Gains: Estimated 45% efficiency gain on existing development procedures.  Development tools automating manual tasks  Fewer defects  Less investigation time  Accurate and updated system documentation  Increased impact analysis capabilities – reliable estimates  Improved team communication  Decrease in training  Traceability and sign-off on system development Audit Readiness: Application and development procedures meet future banking requirements (5900 audit and Sarbanes-Oxley).  Traceability – requirements traced to source code and test cases  Traceability – test results traced to source code and requirements

Pilot Results (Continued) Pilot Project - Efficiency Gains Current Development Life Cycle New Tools and Automated Development Life Cycle Software Delivery Model Days Requirements Gathering Design Coding Testing Rework

Pilot Results (Continued) TaskCurrent Development Life Cycle New Tools and New Development Life Cycle Savings Requirements Gathering 26 days18 days31% Design11 days8 days27% Coding11 days7 days36% Testing12 days3 days75% Rework6 days0 days100% Total66 days42 days45%

Q & A