The Internet of Things is increasingly changing what we mean by a "product," as the emphasis is moved from hardware to its attached software and service components. This puts product developers in a new situation: They have to face the challenges of managing these additional, interrelated, and overlapping development lifecycles.
The nature of software delivery has evolved significantly over the years. This has led to a change in how application teams work, so the tools they should use to help them deliver software have also changed. Integrating application performance monitoring into the software development lifecycle means issues affecting performance can be fixed before applications are deployed.
Most organizations have accepted the commercial benefits of using enterprise service bus-based integration products in their software projects. However, the industry expectations for an ESB product are ever increasing. This article will explain how vendors are trying to cope with the demand.
Identifying the right vendor for an ESB-based integration platform is not an easy task. It depends on several factors associated with your current ALM use case and requirements. Project stakeholders should decide on the integration flow, future tool enhancements, tool accessibility, and configurability before coming to a conclusion. This article takes them through the steps of identifying value propositions in an ESB-based integration solution.
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.
Agile practices go a long way toward providing value to our customers. But in today's market, we must endeavor to adopt a more user-centered approach to create products our customers can't live without.
Extreme Programming (XP) takes practices that are known to be good and combines and applies them in a revolutionary way. Before you turn your team on to XP, check out the steps to take, and pitfalls to avoid, to make your project an "Xtreme" success.
In what ways should software be like a house? In a recent issue of STQE magazine, Technical Editor Brian Marick’s musings about the concept of “tinkerable software” generated some interesting discussion about the very nature of software design. This week’s column runs a portion of that piece so that our Sticky-minded readers can sink their thoughts into the concept.
David Oddis talks about the importance of having an effective defect analysis process, as well as insight on how to manage testing across various SDLCs and the challenges it could present for teams. He also shares his opinions on today's hot topics.
DevOps and regulatory compliance are two critically important ingredients in today’s connected organizations. DevOps enables you to move quickly and respond to change in an era where change is increasing at an exponential rate with no sign of slowing down. Regulatory compliance ensures...
Leading a QA organization is not what it once was. Software and technology are exponentially more complex. The workforce is global. There are a variety of testing techniques and areas of focus. Tons of tools are available that help in a range of ways. Expectations of delivering quality...
The good news: Agile methods deliver superior results compared to traditional approaches. The bad news: For IT projects, mainstream agile methods-Scrum, Extreme Programming (XP), and Agile Modeling (AM)- provide only part of the overall solution. Agile IT projects require some time and effort for upfront planning at the start and activities for sophisticated deployment scenarios at the end. Additionally, most agile projects in large IT organizations cannot escape compliance with governance standards. Mark Lines describes and explores the realities of agile development in enterprise IT environments. Discover how IBM’s freely available Disciplined Agile Delivery (DAD) process framework combines common practices and strategies from mainstream agile methods to address the full delivery lifecycle-from project initiation to solution release into production.