In our knowledge area we have prepared blog articles, wiki articles and case studies on the topic of software for you.
Cape of Good Code identifies different groups of key developers and the overall distribution of effort and knowledge within a Sofware Due Diligence.
Identifying risky hotspots must consider more than code quality and change rates. It's all about the architecture!
10 rules & best practices your supplier should absolutely follow if they want to be listed as a stress-free supplier to their customers.
Data-based analysis shows that Collective Code Ownership can do harm and affected code areas can probably become hotspots of maintenance.
Despite good SonarQube code quality metrics for the Corona-Warn-App, there are noticeable findings based on DETANGLE® that contradict this good...
Fields of investigation such as technical debt, architecture, documentation, knowledge distribution and development processes must be analyzed using...
Software targets have special valuation risks. A software due diligence is therefore a prerequisite for evaluating these technological risks.
Structural dependency analyses are of limited value in identifying architectural hotspots. There are more precise alternatives.
Pitfalls of agile remote development and countermeasures for effective collaboration in geographically distributed teams.