kb:alm

Differences

This shows you the differences between two versions of the page.


Previous revision
—kb:alm [2023/05/01 18:37] (current) – [ALM vs DevOps] Henrik Yllemo
Line 1: Line 1:
 +====== What is ALM? ======
 +<lead>**Application Lifecycle Management (ALM)** defines how a software application is managed from conception, through its creation and deployment, to its eventual retirement.
 +</lead>
 +
 +It's all about real-time collaboration, cross-team visibility, better project monitoring and reporting with an established process to develop <wrap hi>quality software in less time</wrap>.
 +
 +ALM is a continuous process of managing the life of an application through <label type="info">[[gov:gov]]</label>, <label type="warning">[[dev:dev]]</label> and <label type="success">[[ops:ops]]</label>
 +
 +{{ :kb:almbok.com_alm.mp4  }}
 +
 +{{::almbok_application_lifecycle_management.png|}}
 +
 +<button icon="glyphicon glyphicon-book">[[:ALM Definitions]]</button>
 +
 +
 +
 +
 +<jumbotron>
 +<WRAP group>
 +<WRAP row>
 +{{youtube>plzJFh76DJc?full}}
 +</WRAP>
 +<WRAP row>
 +<WRAP column right><fs 12px>Source: [[https://www.youtube.com|YouTube]]</fs></WRAP>
 +</WRAP>
 +</WRAP>
 +</jumbotron>
 +
 +<callout type="primary" title="What is ALM?" icon="fa fa-question-circle">
 +
 +Application Lifecycle Management (ALM) is a process that helps organizations plan, develop, deliver, and maintain software applications effectively. It encompasses the entire lifecycle of an application, from idea and requirement gathering, to design and development, to testing and deployment, to maintenance and updates.
 +
 +ALM involves a set of tools, processes, and best practices that help teams manage the development and maintenance of software applications in a coordinated and efficient manner. It aims to improve collaboration and communication among teams, reduce risks and errors, and ensure that applications meet the needs of stakeholders and customers.
 +
 +Some common activities in ALM include:
 +
 +  * Requirements gathering and management: Identifying and documenting the functional and non-functional requirements of an application.
 +  * Development and testing: Designing, coding, testing, and debugging the application.
 +  * Deployment and release management: Packaging and releasing the application to different environments (e.g., development, staging, production).
 +  * Version control: Managing changes to the application code and other assets over time.
 +  * Change management: Tracking and managing changes to the application, including defects and feature requests.
 +  * Performance and quality management: Monitoring and improving the performance, security, and quality of the application.
 +  * Maintenance and support: Providing ongoing support and maintenance for the application.
 +
 +</callout> 
 +
 + 
 +
 +<button icon="glyphicon glyphicon-book">[[:Continuous...]]</button>
 +<button icon="glyphicon glyphicon-book">[[dic:dic]]</button>
 +
 +
 +{{wp>application lifecycle management}}
 +
 +
 +<callout type="" title="YouTube" icon="fa fa-youtube">
 +  * https://www.youtube.com/hashtag/alm
 +</callout> 
 +
 +<callout type="" title="GitHub Topics" icon="fa fa-github">
 +  * https://github.com/topics/alm
 +</callout> 
 +
 +===== ALM vs DevOps =====
 +
 +Both Application Lifecycle Management (ALM) and [[method:devops|DevOps]] is improving software quality and developer productivity. ALM strives to cover the entire existence – from initial design to decommissioning of an application, regardless what methodology (read  [[agile:agile|Agile]]) is used.
 +
 +
 +
 +<WRAP group>
 +<WRAP half column>
 +{{:method:almbok_devops_continuous_delivery_integration_agile.png}}
 +</WRAP>
 +
 +<WRAP half column>
 +{{ :alm_devops_operations_development_test_management.png|}}
 +</WRAP>
 +</WRAP>
 +<WRAP clear />
 +ALM [[gov:gov|Governance]] focus the discipline of [[method:software_asset_management|asset management]] of software assets and this process becomes increasingly important as organization grow, mature and collect more software assets. ALM provides effective processes and guidelines for onboarding new technologies and applications as well as retiring those that have served their purpose.
 +
 +ALM can also include:
 +  * [[method:sdlc|SDLC]]
 +  * [[method:waterfall_model|Waterfall model]]
 +  * [[project:project|Project management]]
 +  * Business Management
 +  * Security
 +  * Compliance 
 +  * ...
 +
 +See also [[agile:agile|Agile]], [[architecture:architecture|Architecture]]
 +
 +<table ?p "ALM Suits" ?b "Short Name" ?c "Company">
 +?p is a: almsuit
 +?p Short Name : ?b
 +?p Company: ?c
 +</table>
 +
 +<callout type="primary" title="Related:">
 +{{topic>alm}}
 +</callout>
 +=== ## ToDo ## ===
 +  * FIXME
 +  * Application Lifecycle Management (ALM) Suites
 +  * Application Performance Management (APM)
 +  * Application Requirements Management
 +  * Application Security Tools
 +  * Build Automation
 +  * Architecture Management
 +  * Release Automation
 +  * Software Configuration Management
 +  * Software Distribution
 +  * Version Control
 +  * Mainframe Management
 +  * IT Operations Analytics
 +  * Mobile APM
 +  * Test Design Automation
 +  * Software Composition Analysis (SCA)
 +  * Regression Testing Tools
 +  * Application Security Training Software
 +  * API Monitoring Software
 +  * Patch Management
 +  * Application Control
 +  * Enterprise Agile Planning Tools
 +  * Software Development Analytics
 +  * Value Stream Management Software
 +  * Static Code Analysis
 +  * API Security
 +
 + 
 +  * Requirements management
 +  * Project management
 +  * Software testing
 +  * Continuous integration
 +  * Release management
 +  * Change management
 +  * Software maintenance
 +  * DevOps
 +  * Digital transformation
 +  * Agile methodologies
 +  * Waterfall methodologies
 +  * Collaboration
 +  * Traceability
 +  * Quality assurance
 +  * Test automation
 +  * Version control
 +  * Deployment automation
 +  * Continuous delivery
 +  * Monitoring and feedback
 +  * Security and compliance
 +
 +{{tag>kb    alm    whatis        }}