Welcome!

Microservices Expo Authors: Zakia Bouachraoui, Pat Romanski, Elizabeth White, Liz McMillan, Gopala Krishna Behara

Related Topics: Java IoT, Eclipse

Java IoT: Article

i-Technology Viewpoint: The Future of Software Tools

i-Technology Viewpoint: The Future of Software Tools

In a recent press interview I was asked what I thought were some of the important trends for the future of software tools.

It's an interesting question, with many facets, so I was not sure how to respond. After some thought, here are the five areas I chose to highlight from my context of design and construction tool strategy. These are areas that have been occupying much of my thinking and discussions lately with customers, IBM Research, and the Rational teams. These are changing the kinds of software tools we are delivering, and the features the tools support.

1. Connecting business with IT: Business-driven development. The importance of understanding the business context for IT investment has never been more obvious than it is today. More organizations are recognizing the role of IT as a determining factor in the efficiency of their operations, and a bottleneck in their ability to innovate.

I am spending a lot of time with customers who want to explore business alternatives, drive IT projects more directly from business needs with well established business goals and ROI, choreograph services to realize their business processes, and monitor those services in execution to relate operations to the needs of the business. Support for that flow (in its myriad variations) is essential. As we use the current generation of tools in this context we are seeing the emergence of new roles, usage scenarios, and support needs. The lessons from this work are leading to a complete refactoring of tooling capabilities.


2. Greater transparency in the software development process:
Auditing, traceability, and accountability. Software plays a pivotal role in all our lives. It runs our financial institutions, controls the power and utility infrastructure, is embedded in almost every useful device we use, and so on. With this important role comes a certain responsibility.

Government regulators, lawyers, and auditors are beginning to pay increasing attention to the software industry to verify that the software we all rely on has been developed according to some provable quality standards. Sarbanes-Oxley and BASEL2 are just the tip of a very large iceburg. For example, in discussions with those in the auto industry I was overwhelmed by the role software plays in the design, manufacture, control, and management of automobiles, and the kinds of requirements they need fulfiled by the software tools they are using.

Suppose there is a major design flaw in the software managing the anti-lock brakes on a popular model of car that results in injury of a number of people. How does the manufacturer of the braking system prove that it was not negilgent in the design and implementation of that software? Were the engineers developing the software certified against some recognized standards? Were the processes used to develop the software audited for quality? How were software designs analyzed and validated before they were put into production? And so on.

This kind of rigour and auditability will become the norm. Tools must permit this level of access and control. I refer to this as transparency...of prcoess, design, realization, etc. New tooling will emerge that supports and enforces these design principles. Traceability and reporting at all levels will become essential.


3. RAD using new programming models: As Grady Booch likes to say, software drives the world's economies and in some regards we can consider software development to be the most important job in the world!. Yet we all know that the skills and qualities of the best software engineers are in short supply.

It must be possible for a larger community of people to develop sophisticated enterprise solutions and deploy them to heterogeneous runtime environments. We have a long way to go to make this happen. The gap between the way domain-focused users view the problem space and the way in which they must describe systems in the solution space is far too great. In the past, various ways of addressing this gap with CASE tools and 4GLs solved part of the problem, but created their own challenges in return (e.g., proprietary runtime layers, non-standard artifacts, lack of openness to integrate with other systems and services, inflexible high-ceremony design approaches, and so on).

Over the last few years we have seen ways to overcome these limitations with the emergence of robust patterns and frameworks for application development in many technology and business domains. We can raise the abstraction of programming model to be closer to the end-users' mental model of their problem space and use the patterns and frameworks to transform that to the solutions space for today's technologies. Techniques such as generative programming and MDA are a realization of this. We are seeing a lot of innovation in the software tools here.


4. Collaboration among individuals and teams: Much of the inefficiency in software development is a result of the friction between individuals and teams as they work together to share a common understanding of some element of concern, investigate issues from multiple perspectives to make a balanced decision, solve multi-dimensional problems, and so on.

There are many great advances in collaborative tools for interaction and sharing. It's great to be able to start a chat session in a new window while understanding a new piece of code, to view a remote desktop to see the problem a customer is experiencing in their environment, or to create a teleconference as needed to resolve a design issues among colleagues. But there is much more to be done to make those kinds of capabilities part of the software tools workbench of the teams. We'll see those ideas become much better aligned with software development tools so that software engineers can more easily work together on all aspects of the design process, and we'll see design practices evolve to take better advantage of their capabilities.


5. "Pay-per-use" software tools:
New licensing and subscription offerings. There are many pressures on software tool vendors to change the way in which tools are packaged and delivered. Initiatives such as open source software and hosted services via ASPs challenge conventional thinking on software tools.

We've seen some reaction in the marketplace (e.g., open source development tools workbenches such as Eclipse, and on-line testing services from different vendors). Customers are demanding more -- greater flexibility in how software tools are delivered, less overhead in upgrading software tools, more creative pricing based on how the tool is used, when it is used, and how much of it is used.

We are working on different kinds of software tool offerings in response to this by re-factoring the products we offer, increasing the ease with which different tool capabilities can be interchanged, and allowing access to software tool capabilities in a variety of access modes (various flavors of fat client and thin client access). Safe-to-say that lots of people building software in the future will not be buying, installing, and using tools in the way they do today.

Alan W. Brown blogged these comments originally at developerWorks.com. Reproduced here with the kind permission of the author.

More Stories By Alan W. Brown

Alan W. Brown is a Distinguished Engineer at IBM Rational software responsible for future product strategy of IBM Rational's Design and Construction products. He defines technical strategy and evangelizes product direction with customers looking to improve software development efficiency through visual modeling, generating code from abstract models, and systematic reuse.

Comments (2)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Microservices Articles
Digital Transformation is well underway with many applications already on the cloud utilizing agile and devops methodologies. Unfortunately, application security has been an afterthought and data breaches have become a daily occurrence. Security is not one individual or one's team responsibility. Raphael Reich will introduce you to DevSecOps concepts and outline how to seamlessly interweave security principles across your software development lifecycle and application lifecycle management. With ...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
All zSystem customers have a significant new business opportunity to extend their reach to new customers and markets with new applications and services, and to improve the experience of existing customers. This can be achieved by exposing existing z assets (which have been developed over time) as APIs for accessing Systems of Record, while leveraging mobile and cloud capabilities with new Systems of Engagement applications. In this session, we will explore business drivers with new Node.js apps ...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes how...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
Traditional IT, great for stable systems of record, is struggling to cope with newer, agile systems of engagement requirements coming straight from the business. In his session at 18th Cloud Expo, William Morrish, General Manager of Product Sales at Interoute, will outline ways of exploiting new architectures to enable both systems and building them to support your existing platforms, with an eye for the future. Technologies such as Docker and the hyper-convergence of computing, networking and...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...