InfoQ Homepage Design Content on InfoQ
-
Naresh Jain Discusses "Simple Design & Testing" And The Conference Dedicated To It
"Simplicity" is a core agile tenet, particularly when it comes to software design and testing. Since 2006, Naresh Jain has been running a worldwide conference, the Simple Design & Testing Conference, for practitioners to collectively push the boundaries on the topic. Naresh tells InfoQ what's going on behind this small, but well-known conference and why he is so passionate about the topic.
-
Agile Architecture - Oxymoron or Sensible Partnership?
A number of commentators have been talking about the perceived dichotomy between Agile techniques and architectural thinking. This post investigates some of the tensions between Big Up Front Design (BDUF) and You Aint Gonna Need It (YAGNI) thinking and looks at how the two approaches can in fact work together in complimentary ways.
-
What Color is your Backlog?
At the recent SDC conference in Wellington Prof Philippe Kruchten delivered a talk titled “What Color is Your Backlog”. The thrust of his talk is about bringing a focus on architecturally significant aspects of software into Agile projects, along with delivering the functional components of the system. He uses a color metaphor to illustrate the importance of addressing four types of work.
-
Should We Define SOA Non-Principles?
In addition to well established principles and anti-principles, Steve Jones’ new post introduces the notion of non-principles of an SOA implementation and explains why they are important.
-
Emerging Industry SOA Best Practices
A new MITRE whitepaper documents a variety of best practices and key characteristics for a successful SOA implementation.
-
SOA Design: Is it about Contracts or Service Implementation?
A new Steve Jones’ post “Why contracts are more important than designs” discusses an important issue, service contracts, explaining why more time should be spent designing the services contracts.
-
Decoupling Your Application From Your Dependency Injection Framework
Dependency Injection has become a much more accepted and accessible approach in recent years, driven by many factors including increased popularity in SOA, TDD, and many other factors. With this has come increased usage of Dependency Injection frameworks. Bob Martin advises, with examples, applying a decoupling approach between your application code and your Dependency Injection framework.
-
Business-Driven SOA
A new whitepaper from the SOA consortium defines business driven SOA and the role of business architecture in its implementation. It also repositions business architecture from a collection of artifacts required for implementing IT solutions to a comprehensive approach to the entire business design.
-
Practical Advice for SOA Implementers
In his new post, Ganesh Prasad tries to describe the most complex issues of an SOA implementation and provides recommendations on how to solve them.
-
Software Katas - Practice in Public Makes Perfect
Thought leaders in the agile community are talking about software katas - where one practices specific exercises until they are memorized. Robert Martin has calls them "performance art". Lately there has been an increase in blog posts and sites devoted to katas. The latest addition: weekly screencasts at katas.softwarecraftsmanship.org.
-
Refactor or Rewrite?
The goal of refactoring and rewriting is to improve the sanity of the system by improving the code readability, structure and clarity. A clean code would be easier to maintain and enhance. However, on many occasions Agile teams have a tough time deciding between the two.
-
SOA as an Ecosystem
Today’s enterprise is always a part of a larger ecosystem including its buyers and suppliers. In his new post, Richard Veryard describes how this ecosystem should be reflected in a SOA design.
-
Where has the innovation gone?
Some commentators are questioning the level of innovation happening in the Agile space. Does iterative and incremental development lead us away from innovation towards reusing old solutions, building on what we already know rather than creating truly "out of the box" solutions. Adding an R&D stream is suggested as a way to bring innovation into Agile projects.
-
Enabling the Last Responsible Moment in Deployment
An interesting question can be asked during a design decision: "Does this approach create a commitment" rather than "is this the right design?". A conversation on the KanbanDev Yahoo! group explores this question, different approaches to implement an effective answer, and the benefits to be reaped by this approach.
-
Is CRUD Bad for REST?
In his new post, Arnon Rotem-Gal-Oz explains that REST is more than just a set of standards and APIs, and it requires following REST architectural principles for reaping its complete benefits.