utom.pl

blog.hello2morrow.com

December 2014 – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/2014/12

Skip to main content. Assess and Control Component Coupling in Software Systems. December 17, 2014. February 5, 2015. Except for very small systems the manual control of the overall coupling is a tedious task a tool-based approach is needed. Sonargraph-Explorer. The following content introduces the needed definitions and terms related to component coupling (one way to express the overall system coupling). It explains how to use Sonargraph Explorer to visualize the corresponding dependencies and deter...

blog.hello2morrow.com

Tips & Tricks – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/category/tips-tricks

Skip to main content. April 28, 2016. Sonargraph is our tool to quickly assess the quality of a project. I get frequently asked, how Sonargraph supports the Enterprise Architect who needs to answer quality-related questions in the broader context across several projects. Since we recently released new functionality that allows the automation of re-occurring quality checks, it is now the right time to write a blog post. Example questions that an enterprise architect wants to answer:. Export a quality model.

blog.hello2morrow.com

About this blog – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/about

Skip to main content. Is an independent software vendor that was founded in 2005 by Dietmar Menges and Alexander von Zitzewitz. We strive to create powerful tools that empower software craftsmanship and make it easier to create great software that is easy to change and to maintain. Our focus is on software architecture, code comprehension and quality assessment. By end of 2014 we have more than 300 customers in Europe, the Americas and Asia. Alexander von Zitzewitz (Author). Leave a Reply Cancel reply.

blog.hello2morrow.com

Software Craftsmanship – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/category/software-craftsmanship

Skip to main content. How to Organize your Code. August 30, 2016. September 9, 2016. In this article I am going to present a realistic example that will show you how to organize your code and how to describe this organization using our architecture DSL (domain specific language) implemented by our static analysis tool Sonargraph-Architect. Let us assume we are building a micro-service that manages customers, products and orders. A high level architecture diagram would look like this:. April 28, 2016.

blog.hello2morrow.com

Love your Architecture – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/2015/06/love-your-architecture

Skip to main content. June 3, 2015. December 3, 2015. Ie there is not a lot of the original architectural structure left in them, and coupling and dependencies are totally out of control. 48 Packages in a cyclic dependency group (Apache Cassandra Project). The screenshot ( Sonargraph-Explorer. All this leads to a growing accumulation of the most toxic form of technical debt, architectural debt. How to set up an architecture. Architectural model with layers and slices. Possible naming conventions could be:.

blog.hello2morrow.com

Not all Technical Debt should be Treated Equally – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/2014/12/not-all-technical-debt-should-be-treated-equally

Skip to main content. Not all Technical Debt should be Treated Equally. December 3, 2014. October 9, 2015. The metaphor of technical debt is gaining more and more traction. Originally Ward Cunningham. Used the term for the first time in 1992, describing it like this:. To measure technical debt we would need a more precise definition. How do you define “not quite right” in more technical terms? Well, you could define “right” in terms of programming rules, architectural rules and other rules&#4...It makes ...

blog.hello2morrow.com

Dietmar Menges – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/author/dietmar

Skip to main content. Identifying Dependencies for Breaking Cycles. February 5, 2015. October 23, 2015. Dependency cycles in software systems have very negative impact on characteristics like testability, understandability and reuse ( as explained here. Assess and Control Component Coupling in Software Systems. December 17, 2014. February 5, 2015. Except for very small systems the manual control of the overall coupling is a tedious task a tool-based approach is needed. Sonargraph-Explorer. The following ...

blog.hello2morrow.com

June 2015 – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/2015/06

Skip to main content. June 3, 2015. December 3, 2015. Ie there is not a lot of the original architectural structure left in them, and coupling and dependencies are totally out of control. How to Organize your Code. Meet the Sonargraph Gradle Plugin – and Say Goodbye to JDepend. Designing a DSL to Describe Software Architecture (Part 3). Designing a DSL to Describe Software Architecture (Part 2). How to Organize your Code - JAX London. On Designing a DSL to Describe Software Architecture (Part 1).

blog.hello2morrow.com

Identifying Dependencies for Breaking Cycles – hello2morrow – Empowering Software Craftsmanship

http://blog.hello2morrow.com/2015/02/identifying-dependencies-for-cycle-removal

Skip to main content. Identifying Dependencies for Breaking Cycles. February 5, 2015. October 23, 2015. Dependency cycles in software systems have very negative impact on characteristics like testability, understandability and reuse ( as explained here. Extending the Algorithm with User Input. Leave a Reply Cancel reply. Your email address will not be published. Required fields are marked *. The Importance of Defining “Done” Correctly. How to Organize your Code. Designing a DSL to Describe Software Archi...