Modeling and Solving Alternative Financial Solutions Seeking

International audienceIn this paper we build a method to optimize Multi-Year Prospective Budgets. First we present a systemic model of Local Community Finances. Then, from two acceptable Multi-Year Prospective Budgets the method implements a Genetic Algorithm to generate a collection of admissible Multi-Year Prospective Budgets among which Decision-Makers can choose. The method is tested on simplified cases and on in operational situation and gives satisfactory results

Business-IT alignment anti-patterns: a thought from an empirical point of view

International audienceThis preliminary work aims to formalizes observed recurring bad business-IT alignment scenarios. This observation has been conducted subsequently to a 6-years empirical experience of audits of about thirty companies. It considers two research questions: 1) are there recuring BITA problems independently of the business domains? 2) how to formalize them? 14 BITA anti-patterns have been identified. A visual representation and an identity card are proposed to formalize them and illustrated on the 4 most encountered BITA antipatterns. A first milestone is thus proposed towards a common base of BITA anti-patterns and open the discussion with BITA experts among researchers and practitioners, to pooling our efforts and identify research tracks. In fact, BITA is steel a crucial challenge for companies to have a good alignment between business and software. Moreover, handling misalignments is becoming much more sensitive for companies to move towards adoption of new digital capabilities in Digital Transformation challenges

Business-IT alignment anti-patterns: a thought from an empirical point of view

International audienceThis preliminary work aims to formalizes observed recurring bad business-IT alignment scenarios. This observation has been conducted subsequently to a 6-years empirical experience of audits of about thirty companies. It considers two research questions: 1) are there recuring BITA problems independently of the business domains? 2) how to formalize them? 14 BITA anti-patterns have been identified. A visual representation and an identity card are proposed to formalize them and illustrated on the 4 most encountered BITA antipatterns. A first milestone is thus proposed towards a common base of BITA anti-patterns and open the discussion with BITA experts among researchers and practitioners, to pooling our efforts and identify research tracks. In fact, BITA is steel a crucial challenge for companies to have a good alignment between business and software. Moreover, handling misalignments is becoming much more sensitive for companies to move towards adoption of new digital capabilities in Digital Transformation challenges

“Functional-first” recommendations for beneficial microservices migration and integration. Lessons learned from an industrial experience

International audienc

From Monolith to Microservices: Lessons Learned on an Industrial Migration to a Web Oriented Architecture

International audienc

Business-IT Alignment Anti-Patterns: A Thought from an Empirical Point of View

This preliminary work aims to formalizes observed recurring bad business-IT alignment scenarios. This observation has been conducted subsequently to a 6-years empirical experience of audits of about thirty companies. It considers two research questions: 1) are there recuring BITA problems independently of the business domains? 2) how to formalize them? 14 BITA anti-patterns have been identified. A visual representation and an identity card are proposed to formalize them and illustrated on the 4 most encountered BITA antipatterns. A first milestone is thus proposed towards a common base of BITA anti-patterns and open the discussion with BITA experts among researchers and practitioners, to pooling our efforts and identify research tracks. In fact, BITA is steel a crucial challenge for companies to have a good alignment between business and software. Moreover, handling misalignments is becoming much more sensitive for companies to move towards adoption of new digital capabilities in Digital Transformation challenges

“Functional-first” recommendations for beneficial microservices migration and integration. Lessons learned from an industrial experience

International audienc

Microservice Maturity of Organizations: towards an assessment framework

International audienceThis early work aims to allow organizations to diagnose their capacity to properly adopt microservices through initial milestones of a Microservice Maturity Model (MiMMo). The objective is to prepare the way towards a general framework to help companies and industries to determine their microservices maturity. Organizations lean more and more on distributed web applications and Line of Business software. This is particularly relevant during the current Covid-19 crisis, where companies are even more challenged to offer their services online, targeting a very high level of responsiveness in the face of rapidly increasing and diverse demands. For this, microservices remain the most suitable delivery application architectural style. They allow agility not only on the technical application, as often considered, but on the enterprise architecture as a whole, influencing the actual financial business of the company. However, microservices adoption is highly risk-prone and complex. Before they establish an appropriate migration plan, first and foremost, companies must assess their degree of readiness to adopt microservices. For this, MiMMo, a Microservices Maturity Model framework assessment, is proposed to help companies assess their readiness for the microservice architectural style, based on their actual situation. MiMMo results from observations of and experience with about thirty organizations writing software. It conceptualizes and generalizes the progression paths they have followed to adopt microservices appropriately. Using the model, an organization can evaluate itself in two dimensions and five maturity levels and thus: (i) benchmark itself on its current use of microservices; (ii) project the next steps it needs to achieve a higher maturity level and (iii) analyze how it has evolved and maintain a global coherence between technical and business stakes