Industrialization software Engineering using CMMI Luc Quadflieg Atos Origin - Global System Integration

Transcription

1 Industrialization software Engineering using CMMI Luc Quadflieg Atos Origin - Global System Integration Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish symbol itself are registered trademarks of Atos Origin SA Atos Origin. Private for the client. This report or any part of it, may not be copied, circulated, quoted without prior written approval from Atos Origin or the client.

2 The agenda»! Define the objectives»! Tools selection»! Identify the delivery process»! International organization goes for standardisation: common development lifecycle»! Structure the global process»! Synergies between process and tools»! Deploy the solution in the projects»! Maintain and improve the solution»! The tool on the top: CMMI process framework 2 Custom presentation- or document control name

3 Define the objectives Project objectives Vision Deliverables Expected Impact! Atos Origin will apply principles of reuse, economies of scale and standardization of processes and tools to improve the cost base of delivery and to address the market with competitive and innovative solutions! A common and shared set of global processes and tools on an integrated delivery platform together with the training and offerings to promote internally and externally! Cost savings through productivity improvement and reduced project slippage; more competitive offerings 3 Custom presentation- or document control name

4 Define the objectives 7 main areas of improvements From To 1 Testing factory Non-harmonized testing distributed across team and geographies Harmonized tools and processes, with transversal units showing best practice 2 Business requirement Non-standard, ad-hoc description of business requirements Standard process and repository of projects effort; leads to better commercial estimates; simpler design; lower testing effort 3 S.W. production line Non-standard production environment Standardized development environment called Dev. forges with automation 4 Project management Non-systematic project management leading to costly accidents Single tool enforcing project management best practices Strong risk management 5 Productivity management Un-homogenous tracking of productivity across units and geographies Standard tools and operational KPIs, enabling productivity tracking 6 Application Mining tool in AM Non-utilization of tool to map applications Use of application cartography to ease bugfinding and get more accurate commercial estimates of AM-contract 7 Configuration management Non-utilization of standard tool Use a standard set of tools to enable exchange of sources between sites in an FO/BO operating model 4 Custom presentation- or document control name

5 Tools selection The challenges»! Tools to selected for:»! Requirement management»! Testing»! Configuration management»! Process control»! Some where already selected»! Project management: Artemis 7! already selected before the program starts»! Application mining: CAST! no competition»! Challenges»! Involve all countries in the decision, some of the tools in competition was already used by some countries.»! Price and licence mechanism»! Ability off the tools to match the process requirements»! Ability of tools to integrate together 5 Custom presentation- or document control name

6 Tools Selection approach»! Propose process cases to the vendor»! Vendors deploy mock-up of the process case in the tools»! Vendors presents the mock-up»! Atos Origin evaluate and select the adequate tools 6 Custom presentation- or document control name Example: apply a change in an application Tools Actor Involved Phase RM CM TM Developers / Configuration Managers SW Implementation X The Customer changes the Requirement Customer Change requirement X X X The RM tools must be able to notify changes and to stop the development Analysts / Designers Requirement Managers / Test Engineers Developers / Configuration Managers Analysis / Design Freeze X X X Review analysis and design X Requirement tool update element on the CM and TM repository and restart development SW Implementation Test Engineers Execution Test Configuration Managers Configuration Managers Delivery Close X X X The CM tool must be able to notify the closure on the RM and TM repositories X X X

7 The tools selected 7 Custom presentation- or document control name

8 Identify the Delivery processes»! The challenge:»! Define delivery processes to run in all countries for all technologies all AO software development businesses»! Always think that tools will support the process»! Incorporate cross border way of working with offshore, nearshore and closeshore organizations. 8 Custom presentation- or document control name

9 Defined process map P1: Contract initiation P8: Contract renewal P9: Contract termination Contract startup:!! P2: Matchmaking! P3: Transition for AM!! P4: Project startup Global Sourcing Center management!! P5: Capacity planning!! P6: Resource management!! P7: Time tracking CE1: Project Management CE2: Application Management CE3: Business requirements Handling CE4: Software Engineering Main Build CE5: Testing Factory CE6: Installation Services S1: Configuration Management S2: Process & Quality (CMMI) S3: Performance & Productivity S4: Global Tooling S5: Estimates S6: Application Mining S7: Risk Management 9 Custom presentation- or document control name

10 International organization goes for standardisation: common development lifecycle 10 Custom presentation- or document control name

11 Common lifecycle with common deliverables Business architecture Requirement development Software architecture Requirement assessment + Detailed technical specification Detailed technical design Construction + Unit Test Integration System Test User acceptance Prepare production + Deployment Production Support 11 Custom presentation- or document control name

12 Structure the process: Main page build with Livelink 12 Custom presentation- or document control name

13 Structure the process assets 13 Custom presentation- or document control name

14 Build views of the process 14 Custom presentation- or document control name

15 Synergies between process and tools 15 Custom presentation- or document control name

16 Integrate process and tools together Nessie Finance and People Projects-Personal Data Projects-Organization-Personal Data-Effort- Artemis Project Management Tasks Update-Change Requests USD Service Management Tickets Change Requests Resources-Tasks Update Configuration management Workflow Management Process Control IBM Clearcase and Clearquest Business architecture Requirement development Software architecture Requirement assessment + Detailed technical specification Detailed technical design Construction + Unit Test Integration System Test User acceptance Prepare production + Deployment Production Support Process Integration Results-Defects Business Requirements IBM Req.Pro Caliber Requirements Technology dependent environment. Source Code Test Factory HP Quality Center Requirements 16 Custom presentation- or document control name

17 Integrate Project management and process control 17 Custom presentation- or document control name

18 Deploy the solution in the projects 18 Custom presentation- or document control name

19 Maintain and Improve the solution 19 Custom presentation- or document control name

20 Roles and responsibilities for process improvements 20 Custom presentation- or document control name

21 The tools on the top: CMMI 21 Custom presentation- or document control name

22 CMMI and the future of the GDP Demand Countries Front Offices France NL Atos Origin Enterprise CMMI Supply Countries Back Offices India UK Germany Spain USA Set-up Font Office Back office Morocco Armenia South-America Belgium 22 Custom presentation- or document control name