Testing is an important means to obtain information about implementations. Likewise, code reviews help to keep the code quality high. What is very common for code, gets sometimes neglected for software architecture. But how can a project team test the architecture itself? Software architecture assessment represents an effective approach for introspecting and assessing software design.
Commitment is defined as the act of binding yourself to a course of action. In Scrum, commitment has a strong meaning and Scrum practitioners suggest that authentic Scrum is not possible if people are not keeping commitments. In-spite of this, forums have a lot of questions about commitments not being met. Do we understand the real meaning of commitment?
Gartner hype cycle is a representation about the maturity of any new technology. As a part of its cycle, it characterizes the over enthusiasm and the following disillusionment which occurs when a new technology is introduced. Given that Agile recently celebrated 10 years, disillusionment should be the last thought. Or is it?
Retroflection is a concept in which one substitutes self for environment, as in doing to self what one wants to do to someone else or doing for self what one wants someone else to do for self. Introspection is a form of retroflection that can be pathological or healthy. Based on a similar concept Yves Hanoulle started the Agile Retroflection of the day project.
“SOA Principles of Service Design” by Thomas Erl is an encyclopedia of service design principles needed to build SOA solutions. This article contains three supporting practices taken from the book: Service Profiles, Vocabularies, and Organizational Roles.
Patterns from Thomas Erl’s book, “SOA Design Patterns”. Today, we present Chapter 16, Service Governance Patterns, comprising a number of 8 patters. Compatible Change, Version Identification, Termination Notification, Service Refactoring, Service Decomposition, Proxy Capability, Decomposed Capability, and Distributed Capability.
In this article we present 3 Inventory Governance Patterns from chapter 10 of the book SOA Design Patterns by Thomas Erl: Canonical Expression, Metadata Centralization, and Canonical Versioning. They are part of an 85 patterns catalog that serves enterprise architects and developers to find and build strong SOA solutions based on tested and proven SOA practices.
Guillaume Laforge reviews the main features brought by Groovy 1.6 – better performance, multiple assignments, optional return, AST transformations, Grape, OSGi -, what’s most interesting and new in Groovy 1.7 – anonymous classes, annotations, power asserts, AST viewer and builder -, and what’s coming in Groovy 1.8: closures, modularization, Java 7 support, DSL, AST templates, better performance.
In this presentation held during OOPSLA 2008, Rebecca Wirfs-Brock reviews various forms of driven development in order to understand the principles and values of several design practices used today. By comparing them, a designer will get a broader view over design and will better understand which design practice is more appropriate for him.
