White Paper. Code Maintenance Best Practices. 4 Essential Skills for Lean Times

Transcription

1 White Paper Code Maintenance Best Practices 4 Essential Skills for Lean Times

2 Abstract In today s economic environment, every dollar counts. And one of the biggest spends for a company is the development and maintenance of software, where every line of code matters. Code and IP as well as the knowledge behind it, is often an organization s most valuable asset. If companies can capture and harness existing code they can save millions of dollars in time and money and survive in lean times. The key to leveraging existing code is through code and IP discovery. Through code discovery organizations can capitalize on the value of code and IP for both development of new software and maintenance of existing code. By making your code assets and development expertise easily accessible and usable across the organization, companies can identify new ways to maximize these assets. Code discovery streamlines the development of new code and simplifies code maintenance. It is a low cost of ownership approach that solves important problems that are not addressed by Application Lifecycle Management (ALM) or Product Lifecycle Management (PLM) systems. In this paper, we explain four ways an organization can leverage code and IP discovery in order to survive in lean times. These areas are: code reuse, impact analysis, fix sharing, and managing code leverage. Introduction Organizations with 50+ developers and multiple software applications under development and maintenance are vulnerable to development waste. This waste is created when: Significant portions of code are written from scratch, when substantially similar code already exists in the organization and can be readily reused Rogue modifications to standard components cause downstream maintenance headaches Functionally similar code streams must be maintained separately over application lifetimes Difficult lessons learned and vital insights from key developers are not shared or leveraged with other teams or developers Defect and vulnerability fixes are applied on a project by project basis; with little or no collaboration These behaviors result from development practices and ALM / PLM tooling that attempt to optimize the efficiency of individual projects. These development practices and tools limit portfolio level access to valuable code, code changes and metadata that have the potential to bring vital insight and economic leverage into code evolution. Through code discovery, organizations can move beyond siloed projects and increase their visibility and accessibility to code in order to make better decisions. In the following section we discuss the four ways to leverage code discovery. These four areas are grouped in two categories: New Code Development and Code Maintenance. Page 2

3 New Code Development New code development is plagued by redundant coding and complex learning curves. Code discovery is an emerging solution that addresses both of these issues with Code Reuse. AREA 1: Code Reuse The goal with code reuse is to leverage existing ideas, problem solving insight and where appropriate, code itself. The value of code reuse is known to most development organizations, but until now there has been no strong consensus on a single solution approach. Best Practices Code Reuse Identify internal projects that incorporate functionality of interest Locate internal developer(s) with expertise using APIs, components or frameworks of interest Locate pertinent requirements documents and defect issues along with related code Maintain a library of recommended reusable components Browse similar projects completed in the past to understand architectural approaches and code evolution issues Business Value Code Reuse Savings of $40 $75 per line of code i Keep focus on new, unique and strategically relevant development Smaller managed code footprint; greater effectiveness of code quality efforts Existing Solutions Code Reuse Solution Asset Management Challenge / Problem with Solution Editorial / maintenance effort Code currency, accuracy, completeness Tracking and measurement Collaboration tools (wikis, portals) Project Search tools (grep, grok, scm) Information consistency and relevance Code currency, accuracy, completeness Developer behavior (workflow) change Tracking and measurement Good for locating known code, not discovery Error prone, time consuming Limited search scope Code Maintenance Three code maintenance practices lead to significant, ongoing development waste: (i) developers assigned to maintenance are less skilled and experienced than the original developers (ii) developers Page 3

4 assigned to maintenance don t have direct experience with the code they are working on, and (iii) there is usually no visibility into relevant code and code artifacts that would facilitate problem resolution. As a result, development organizations are vulnerable to: Unnecessary code divergence Introducing multiple, different fix streams into to the code base Chronic quality problems in key areas of the code Higher than necessary costs of learning and knowledge transfer Code discovery helps minimize these areas of development waste with the following solutions: impact analysis, fix sharing and managing code leverage. AREA 2: Impact Analysis Maintenance code changes are often made from the narrow context of a particular defect or change request. Planning and implementing code changes without understanding how the code will behave in other situations is a recipe for downstream problems. Understanding the scope of change within a single application is useful, but typically not sufficient. Evaluating the proposed change impact across a portfolio of applications is a required best practice in most organizations. Best Practices Impact Analysis Once a defect is confirmed, assess vulnerability across projects and communicate results Identify other parts of the application that will be affected by the change Identify other applications or services that might be affected by the change Identify other projects where a similar defect or issue was addressed Business Value Impact Analysis Leverage key lessons learned and problems already solved Reduce the defect injection rate Contain code divergence Achieve smaller managed code footprint; greater effectiveness of code quality efforts Existing Solutions Impact Analysis Solution Existing ALM solutions IDE (grep, grok, scm) Challenge / Problem with Solution Works only within the envelope of proprietary tools Analyzes limited set of programming language types Good for locating known, local code only Search scope limited to single project No code discovery from metadata search Does not scale to multi project level Page 4

5 AREA 3: Fix Sharing Once a vulnerability or defect has been remedied, other projects that might benefit from the fix should be notified immediately. Best Practices Fix Sharing Identify other projects that may need the fix Document the fix and unambiguously identify where it should be applied Communicate the fix to individuals who can take remedial action Business Value Fix Sharing Leverage existing solutions Reduce downstream support and development costs Reduce latent defect level Reduce defect aging Contain code divergence Achieve smaller managed code footprint; greater effectiveness of code quality efforts Existing Solutions Fix Sharing Solution Support in existing ALM solutions Broadcast notification ( , etc) Challenge / Problem with Solution Works only within the envelope of proprietary tools Success depends on a highly dependent project organization Not relevant to all > can be easily ignored Reliance on experts doesn t scale Context of problem misunderstood Issue authoring is time consuming, laborious process Page 5

6 AREA 4: Managing Code Leverage This effort involves refactoring and managing component based changes so that code sharing across projects is enhanced. It also involves monitoring of component level and API level changes to ensure that common code across projects does not diverge into forks which lead to separate lifecycle management requirements. Best Practices Code Leverage Monitor extent of code/component/api sharing across code portfolio; coordinate and communicate changes Identify refactoring or SOA candidates by frequency of use analysis across code portfolio Detect and manage rogue edits to common code / components across portfolio Business Value Code Leverage Reduce downstream support and development costs Improve code maintainability and consistency Contain code divergence Achieve smaller managed code footprint; greater effectiveness of code quality efforts Existing Solutions Code Leverage Solution IDE, ALM find feature Asset management application Challenge / Problem with Solution Good for locating known code, not discovery Multi project search is error prone, time consuming Automated search scope limited to single project Requires extensive, ongoing library management Inability to reliably detect divergence Reliance on vendor specific development tooling Summary An organization s most valuable resource is the code that has already been developed and the IP and knowledge behind that code. Code discovery capabilities help organizations capitalize on the value of this intellectual property in development of new software and maintenance of existing code. This paper highlights the four areas that can improve an organization s insight and discovery into their code. Code reuse, impact analysis, fix sharing and managing code leverage are all areas that can increase the maximization of code assets. With the insight and knowledge of code and IP, organizations are able to lower costs focused on maintenance and devote more of their IT budgets to code development and innovation. Page 6

7 Krugle Enterprise: Code and IP Discovery at Your Fingertips While there are many ways to attempt to leverage code, many solutions provide only part of the capabilities an organization needs to make the most of their greatest asset. Krugle Enterprise is the only solution that enables an organization to leverage all four ways in a single solution. Krugle Enterprise has been deployed in a range of IT and software development organizations to solve these critical issues. At its core, Krugle Enterprise automatically delivers a comprehensive, searchable library of code, code related documentation and development artifacts (Table 1). It is based on open, extensible technologies and is fully compatible with all common SCM systems. Table 1. Krugle Enterprise gives organizations the insight to discover their code and IP. It includes discovery, monitoring and analysis capabilities at the API, IDE or browser level. Table 2 summarizes the features that help development organizations get the most value from their code IP. Page 7

8 Krugle Enterprise Solution Area 1: Code Reuse Area 2: Impact Analysis Area 3: Fix Sharing Table 2. Krugle Enterprise Code Discovery Solution. Area 4: Managing Code Leverage Discover code from code features, development process metadata, code artifacts Easily examine & explore nonlocal code Locate similar code through precise or fuzzy queries of code patterns Identify defect injection points Assess defect propagation Organization wide impact analysis, vulnerability assessment Code space support single URL reference to code, documentation and artifacts Easy developer access (browser, IDE) Monitor code duplication, divergence Code related info access Ability to promote selected code in discovery, mark code for reuse By eliminating development waste associated with poor information access, Krugle Enterprise helps organizations focus on strategically significant development development that will move their business forward, even in the most challenging economic conditions. i Estimating Software Costs Bringing Realism to Estimating, Capers Jones, 2007 McGraw Hill, Inc. Page 8