Software evolution and optimization - done right. Aim42 - systematic software evolution and improvement. Optimize your software and reduce maintenance cost. Control risks, issues and technical debt. Organizes patterns and practices in three phases. Grounded in practice , proven approaches, backed by serious research. See the online aim42 method guide.

Are you looking for ways to make better software. And to become more efficient in developing software. Are you involved in software development and do you want to improve, learn and grow? You have found the right place - On this site and others, I write actionable advice and technical articles for software developers, testers and manager on a regular basis. You know that something is not working well. You know what you want to achieve. You need some code to be written.

Linas and Tania trip back to NZ. Recent Updates Toggle Comment Threads. Notify me of new comments via email.

11 Why is software being changed? 12 Why does software need improvement? 13 How does aim42 work? 14 Patterns and Practices Provide No Guarantee. 23 Patterns and Practices for Analysis. 33 Pattern and Practices for Evaluation. 42 Structure of Improvement Practices. 5 Cross-Cutting Practices and Patterns. 54 Collect Opportunities for Improvement.

Skip to end of metadata. Last modified by arc42 confluence admin. On Jun 25, 2015. Go to start of metadata. This diagram shows the main topics covered by arc42. Found issues or bugs? Please report any issues or bugs in our GitHub repository. You can do that without registration or login! Arc42 template in English.

Domain Class Diagrams for Grails Projects. A Grails project can quickly grow into larger applications. In order to still keep an overview, some architecture documentation is quite useful. One of the most useful diagrams to dive into an application is the domain class diagrams which shows. I described how to use Spock-Reports. Now, if you try to use it with Grails 2. 5, it seems not to work from.

Vom Urknall bis zum Blick in die Zukunft. Kosten und Nutzen von Clean Coding. Conclusion of the dirt consideration-1. Our purpose is to achieve a SE that is clean, i. efficient, in all aspects. Software is the matter in the developer cosmos. This matter can be mapped onto the four dimensions Process, Knowledge, Handcraft. In this way, we are able to structure the complex world of SE reasonably.

It is based upon practical experience of many architecture projects of different sizes and domains. It includes feedback of its many users. Contains a template for development, documentation and communication of software architectures. Fits arbitrary technologies and tools. Therefore ensures better software- and system architectures.

Go to start of metadata. Skip to end of metadata. Last modified by Robert Reiner. On Dec 19, 2016. Go to start of metadata. What we can do for you. Team success is grounded in effective communication. Communication with your clients, within your organization and your individual teams. Choosing the right tools help you to make team collaboration more effective and more fun.