Model-Driven Software Lifecycle for System Modernisation

At WorkingMouse, we deliver tools engineered to modernise and optimise your software systems by seamlessly integrating Model Driven Engineering (MDE), traditional software development, and DevOps practices. Using our proprietary Internal Development Platform (IDP), Codebots, we've crafted a holistic approach that places the power of system control into the hands of all stakeholders. This approach synergises technology, collaboration, and quality control, allowing stakeholders to manage systems from a concurrent model. The process breakdown is designed to elucidate our methodology for prospective stakeholders eager to comprehend how Codebots serves as a DevOps-compatible internal engineering platform.

Model-Driven Software Lifecycle

1. Codebots

a. The technical team create the Meta-Models and initial application models. The all stakeholders collaborate on the models.

b. The Codebots Pipelines input and process the models to generate the target application artefacts.

c. Active Collection API's update data during process step relevant to compiling the application.

d. The Artefacts are both the updates application compile files and documentation based upon the models.

2. Git & CI/CD

a. Codebots commits to Git just like another developer. The models and requirements also match with the automated regression Testing with then run on a CI/CD pipeline.

b. Automated Quality Control for Code, Performance and Security test tools are run to ensure the application matches organisational standards.

c. The technical team can working alongside the Codebot and artefact to update and configure at the code level within protected regions using their Local Dev Environments just like the traditional development process and with their existing tools.

3. Target Application

a. The bot is setup to whatever the organisations preferred standards are for Client-Side Framework, this is usually React, VueJS or other widely supported open source framework. This also includes the component library, HTML, CSS and Client Side JavaScript.

b. The bot also writes all Server-Side logic for the database and API to the client-side and external systems. Common technologies used are C#, Spring and include application environments and containerisation.

4. Testing & Acceptance

a. The CI/CD process enables a new Beta Environment to be automatically released to the customer preferred Beta environment on prem, private or public cloud.

b. The Product Owners complete User Acceptance Testing (UATs) to ensure the model updates satisfy the requirements. The model can be iterated and pipelines re-run or the application can be released to production.

5. Production Release – Yay!

6. Operate and Monitor

a. The technical stakeholder can Support the Application’s users.

b. The non-technical stakeholders Operate the business system and target application.

c. The technical team Monitor for usage and security to ensure uptime for the operational team.

d. All stakeholders provide further Enhancements as required to optimise the business process.

Summary

At WorkingMouse, we deliver specialised tools designed to modernise and optimise your software landscape. Our proprietary platform, Codebots, bridges Model Driven Engineering (MDE), traditional software development, and DevOps practices in a holistic framework that empowers all stakeholders. This unique synergy of technology, collaboration, and quality control allows for managing systems at a more abstract level through modelling. This process breakdown is crafted to clarify our methodology, providing prospective stakeholders with insights into how Codebots functions as a DevOps-compatible internal engineering platform.