InfoQ Homepage Quality Content on InfoQ
-
How can Agile make you Faster?
Delivering faster is one of the reasons that enterprises mention why want to use agile for software development. How can agile be used to become faster?
-
Sonar Quality Dashboard 3.0: New Commercial Editions And The Developer's Cockpit
Sonar Quality Dashboard version 3.0 has recently been released including separate commercial editions and a new plugin allowing developers to see how their individual commits affect project quality.
-
The Impact of Software Testing on Embedded Systems
In its recent issue the Chip Design Magazine points out that the huge growth of portable and wireless systems combined with the increasing relevance of software in embedded systems poses a challenge. Quality issues need special attention, especially in safety-critical systems. This is why software test tools for software systems will become increasingly important.
-
An Introduction to Software Quality
In two recent papers, David Chappell, Principal of Chappell & Associates, outlines the different aspects of software quality – functional, structural, and process-, the groups of people directly interested in quality –users, developers, and sponsors-, and the outcome of defects in externally or internally facing software over time.
-
Individual Yield
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
-
Cooperation between European Space Agency and Lero
As announced on 18th August 2011, the Irish Software Engineering Research Center (Lero) has signed a €300.000 contract for a research project with the European Space Agency (ESA). Goal of the research activities is to provide a solution framework for future space missions.
-
Agile and Architecture Conflict
There is a constant tussle between following Agile techniques and still managing to do enterprise architecture. While Agile development focuses on adjusting the design as more insight is gained, architecture establishes the technology stack and addresses quality attributes. Combination of the two is successful when agile techniques are leveraged to drive towards the desired architecture.
-
Representing Agile Testing
Several members of the Agile community describe different styles for expressing user story tests and the testing of an entire theme.
-
Ensuring Product Quality at Google
James Whittaker, a former Microsoft architect, author of several books in the “How to Break Software” series, and currently Director of Test Engineering at Google, has written a series of posts on how Google does testing. Google blends development with testing, having relatively few testers, and each product goes through successive channels before is ready for prime time.
-
The Holy Grail of Zero Defect Systems
While, zero defects sounds very good to hear, is it really possible or is it an unachievable goal? Many organizations adopt a 'zero defects methodology'. Does it really mean anything?
-
How To Complete Stories Without Leaving Bugs Behind
What can you do when unacceptable numbers of stories are "done" with development, but they still have many quality problems?
-
Big Ball of Mud, Still the Most Popular Software Design
Big Ball of Mud, is a code jungle which is haphazardly structured, sprawling, sloppy and connected by duct-tape. Over the years we have been introduced to various guidelines such as SOLID, GRASP and KISS amongst age old, high cohesion and low coupling to deal with this Mud. However, the situation still remains bleak and Big Ball of Mud seems to be a popular way to design and architect software.
-
W3C Releases Unicorn Web Validation Tool
W3C has released Unicorn, a one-stop tool to help people improve the quality of their Web pages. Unicorn combines four popular tools, including the Markup validator, CSS validator, mobileOk checker, and Feed validator, with a single interface.
-
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.
-
Temporary Code, Sustainable Code and Everything in Between
There is code which is well tested, well re-factored and built to last. There is also code which is planned to be thrown away in a few days. Between these two extremes, there is a lot of gray area. The code in this gray area is written with the presumption that it would be cleaned up later but is never done.