Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replacement of a system with COTS or OSS #264

Open
perelandra opened this issue Feb 7, 2021 · 3 comments
Open

Replacement of a system with COTS or OSS #264

perelandra opened this issue Feb 7, 2021 · 3 comments

Comments

@perelandra
Copy link

Would it be possible to add the improvement approach with the evolution from custom built software to a COTS (commercial of the shelf) oder opensource software based system?

@aheusingfeld
Copy link
Member

aheusingfeld commented Feb 7, 2021

Hi Perelandra,
can you elaborate on what you have in mind by "from custom built (...) to opensource software-based system"?

Regarding "from custom built (...) to COTS", I'd say a "build vs. buy" decision always depends on the context. E.g. buying a solution which is less expensive but reduces flexibility and "Unique Selling Points", might in the long-term turn out to not have been an improvement but the death for a company. Thus I'd be very much interested in your reasoning/thoughts behind this suggestion?

@perelandra
Copy link
Author

Hi aheusingfeld
After 10 years, the evolution of the ecosystem IDE, CI/CD, frameworks and services needs fundamental rearchitecture.
E.g. custom built frameworks may be opensourced, expensive libraries can be rented as a cloud service.
Simon Wardley has an interesting approach of this kind of evolution: https://medium.com/wardleymaps/finding-a-path-cdb1249078c0. How do you think, that this kind of evolution could be integrated in aim42?

@feststelltaste
Copy link
Member

feststelltaste commented Feb 10, 2021

Wardley Maps would be a great addition. Using strategic classification from DDD to find out which components should be developed in-house or which should be outsourced, too. We are currently gathering more and more experience with theses techniques in the industry (e. g. look at Nick Tune's work). But both topics are huge. The key would be to split up these topics and put the essence of that into small activities IMHO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants