A Domain-Specific Language (DSL), named RI language, designed for the declarative description of microservices, along with a supporting tool, TSE (Toolbox Service Executor), implemented in Python and based on the RI grammar, enables the representation of structural and operational aspects of services in a technology-agnostic manner.
It was concluded that Clean Architecture cannot be viewed solely as an ally or a villain, as its effectiveness depends on project characteristics, team experience, and the proportionate application of its principles.
Algorithm-Driven Development is introduced, a methodology developed from industrial practice to address recurring challenges in translating requirements into reliable, testable, and maintainable software behavior that provides systematic coverage of functional scenarios from the outset of development.
Philippe Jawish, Pierre Evrard, Alexandre Lemerle et al.· Journal of Systems and Softw...· 0 citations
Microservice-based systems evolve continuously through API changes, service splits and merges, dependency churn, and deployment-topology drift driven by DevOps practices. This rapid evolution erodes the assumptions encoded in formal models, test suites, and architectural descriptions, leaving practitioners with limited...
R. Gómez, Ebeid Elsayed, Enrique R. Zarate et al.· Software· 0 citations
In this project, one will be working on building a Continuous Integration and Continuous Deployment pipeline using Microsoft Azure to automate software delivery and improve overall efficiency.
Ashwani Kumar, Geetanjali Amarawat· International Journal for Re...· 0 citations
An empirical assessment indicating that DSAR supports comprehension, architectural reasoning, and communication; qualitative evidence on the strengths and limitations of the generated explanatory artefacts; and recommendations for practitioners and researchers on adopting and further developing DSAR for architectural s...
S. A. Rukmono, Lina Ochoa, Thijs Bressers et al.· SIGSOFT FSE Companion· 0 citations
A guide that facilitates the step-by-step adoption of five practices: version control, change requests controlled with manual code inspection, continuous integration, static code analysis, and implementing an automated pipeline for continuous integration is proposed.
M. Pastrana, Hugo-Armando Ordoñez-Erazo, C. Cobos-Lozada et al.· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.