Better Software magazine editor Ken Whitaker highlights the contents of the July/August issue with two articles featuring mobile and wearable intelligent devices and the challenges they present to typical software development. Ken also provides information on ordering a print copy of Better Software.
With the cloud providing tremendous freedom like instant deployment of updates, you're definitely going to have to adjust how you develop and deploy apps. Pete and Matt have created a list of things you need to consider when developing apps for the cloud.
To fully detect, isolate, and resolve quality issues in a traditional, large-scale data warehouse requires that several approaches be used together. Wayne identifies types of data quality issues and then illustrates how to best attack and resolve those pesky issues.
When you think of configuration management, build automation and version control usually come to mind. Dave presents a perspective that shows the important role CM plays in the entire product and project lifecycle.
A common mistake made when building applications to meet business needs is not properly defining business requirements from the get-go. Poorly defined requirements compromise the quality of applications and lead to projects that deliver marginal value or fail outright.
The shiniest software application in the world, shipped on time and under budget, is a failure if it doesn't make someone's job easier. Failures cost us customers and money. How can we design software that our customers want to use and that will reduce our cost of failure?
For large-scale Java applications, understanding memory-related options might mean the difference between a wonderful user experience and recurring system slow downs. This article offers insight into the workings of Java memory management and shows how it cleans up after programmers, recovering memory associated with objects that are no longer being used.
Many systems architects have a technology—centric view of service-oriented architecture. This article emphasizes the need to understand the business side of SOA before tackling the technology and illustrates this need with a look back in time.