Complete and improve the technical undestanding (map of dependencies, documentation…) of the applications and transfer this knowledge to development teams.
Establish (if there weren’t any) and develop the regulations and standards of the deliverables to generate, and implement the metrics and controls for their verification.
Optimize the Requirements Management in areas such as verification or its traceability with code and tests.
Having the necessary technical and business information for prioritizing changes (structural and functional quality, technical debt, impact analysis).
Optimyth’s Software Maintenance Management solution provides a methodology for the effective management of the applications portfolio based on the industry best practices and the experience of carrying it out in tens of installations.
It is structured in the following phases:
1. UNRAVELLING THE COMPLEXITY OF THE APPLICATIONS
In order to facilitate the understanding of the tasks to do to a maintenance request, at this phase, the applications map and its components are built, which will help to:
– Discover and unravel the intrinsic complexity of the application.
– Provide the ability to run impact analysis on the constructed model, helping to indentify the components affected by the introduction of a change.
– Find obsolete components that could be deleted from the applications.
– Discover components and redundant functionality (duplicated code).
– Complete the documentation of the application.
2. DETECT POTENTIAL PROBLEMS IN DEVELOPMENT PHASE
Most of the solved problems during applications maintenance (up to 85%) could have been detected in development phase, where its solution is easier and cheaper.
In this phase:
– Source code rules are applied, identifying typical patterns that could trigger future incidences in production.
– The application maintainability is measured in all the development phases. For example, the indicator defined by the Software Engineering Institute (SEI); or the improved version designed by Optimyth.
– Code complexity metric is analyzed.
As a result of this phase, an Action Plan is developed to solve the incidences that can severely affect the maintainability of the analyzed application, operating at three levels:
– Interdependance of the applications.
– Dependence between components of the applications.
– Code intrinsic complexity.
3. ESTABLISH A QUALITY ASSURANCE PROCESS
– Focuses on the applications maintainability, that provides a holistic view, considering: the code, the documentation, the requirements traceability, the technical and functional tests, etc.
– Helps to proactively detect potential defects during development phase, defining the maintainability indicators.
– Integrates information from third-party systems to provide complete traceability, from requirements definition, through its implementation, and ending with related test cases. This information, centralized on Optimyth’s quality integrated portal, allows to greatly shorten maintenance periods.
As a result of this service, the customers obtain:
– Updated and updatable map of their applications.
– Technical evaluation of the maintainability of the software components making up the applications map.
– Action plan.
– Quality Assurance Process.
As a result of this solution, the companies obtain:
– A more efficient transfer of knowledge process, being able to generate, consolidate and provide the documentation to locate the complexity and the value of the applications.
– Improvement of the outsourcing management.
– To consolidate the applications functional and technical knowledge (unravel their complexity) and to align them with business’ needs.
– Costs reduction.
– Reduction of the number of incidences in production environments.
– An action plan to improve the maintainability of the analyzed applications.