As a software architect for your organization, you may be required to efficiently and effectively evaluate the validity, quality, health, or maturity of a proposed, new, or legacy software architecture. This presentation describes a simple process you can follow to perform a rapid assessment of any software architecture effort, regardless …
Projects that don’t change are the ones that get canceled. Any relevant and useful software has to continuously evolve. Agile development greatly emphasizes an evolutionary approach to software design and software architecture. That’s because big up-front design and architecture are risky. But the evolutionary approach also has risks. This session …
Here is our monthly selection of knowledge on programming, software testing and project management. This month you will find some interesting information and opinions about team complexity, developer burnout, blaming, tester skills, code coverage, integration testing, front end architectures and agile antipatterns.
Evolving the software architecture of legacy systems for unintended use is difficult. The architectures are not documented well, the team that built the system has often moved on, old and out-of-date code is permanently intertwined, and the technology trends of the present are dramatically different from when the system was …
Software developers keep looking to CQRS as a software architecture to boost performance. But the more I work with companies the more I discover there’s a sweet spot where Theory of Constraints, Kanban, CQRS, Domain-Driven Design, EventStorming and UX blend together to solve ‘the really real problems’. Once you’re there, …
We can think of the whole computer systems as a human body that consist of cells of various types. They can be hardware or software. When they are software units, the smaller they are, the easier it is for them to self-heal, recuperate from failures, multiply or even get destroyed …
