Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Software Reuse Is Dead, Long Live Software Reuse

Make yourself a hero

I know what you're probably thinking as you look at the title of this article: "software reuse - been there, done that, and it doesn't work...."

And it's true that many a software architect or project leader on a WebLogic project has broken his or her pick on the slag heap of reuse efforts and that the legacy of monolithic CASE tool suites has left a bad taste in many developers' mouths when it comes to developing reusable software. So, what has changed to make software reuse feasible today? Three key factors make software reuse initiatives worth considering or reconsidering at this juncture:

  • Mature, component-based development environments
  • Web services and service-oriented architectures
  • Software engineering processes and tools oriented towards reuse
I'll be discussing why each of these factors makes a difference towards the goal of effective software reuse, and why, in many cases, they combine with business factors to make a software reuse initiative a mandatory part of standard operating procedure in a rapidly increasing number of IT organizations.

Mature, Component-Based Development Environments
As we look at the past 20 years in software development, we see steady progress being made, both in the sophistication of programming techniques and the language-specific services being made available to the developer. From the early days of C, with its limited set of standard libraries and very much of a do-it-yourself mentality, to structured programming initiatives, to the early days of widespread object-oriented programming, to CORBA's distributed component infrastructure and services to today's modern J2EE and .NET component infrastructures, we can identify some major elements that make building and consuming reusable software feasible.

Structured programming techniques contributed to the notion of well-defined functional contracts to be consumed by callers of a module. Defining a contract in terms of its preconditions, expected input and output parameters (including the semantics of those parameters), side effects, and any exception conditions that may result from invocation of the function being described went a long way towards instilling a clean delineation between caller and invoked module.

Object-oriented programming introduced the concepts of data encapsulation and polymorphism, each of which contributed to effective software reuse. Data encapsulation freed the caller of an object from exposure to the underlying data structures used to manage persistent data and allowed the information being passed on a method call to be aligned more precisely with the caller's objectives. Polymorphism enabled the developers of a class to provide meaningful abstractions combined with underlying flexible implementations tuned to specific algorithmic needs, while allowing the calling code to be effectively decoupled from those implementations.

Taking the notion of decoupling one step further, distributed component technology provided developers with the ability to define and deploy coarse-grained component interfaces whose underlying implementations assembled a cluster of cohesive operations dealing with common data and functional objectives. While the tools provided with early component infrastructures such as CORBA were limited, and developers often had to be "rocket scientists" to get everything to work together correctly, when done right, the resulting deployed component landscape provided an efficient, flexible, and reusable application infrastructure.

Finally, the maturity of the two major component architectures, J2EE and .NET, gave developers a rich and stable platform upon which to build and deploy their components. The technical services provided by these two architectures, such as transactional integrity, messaging and directory services, security, exception processing, remoting, and many others make it possible for developers to focus on the function of their components rather than all of the underlying technical infrastructure required to make them work.

Web Services and Service-Oriented Architectures
I'm sure some of you are wondering, "Aren't Web services synonymous with service-oriented architectures? What exactly is a service-oriented architecture and how does it differ from Web services?" Simply put, a service-oriented architecture is one in which application functions are consolidated and presented in a loosely coupled form independent of their underlying implementation. These loosely coupled services typically present coarse-grained capabilities that are meant to be assembled together through some form of messaging runtime.

With that said, many, if not most, service-oriented architectures take advantage of the Internet-based Web service infrastructures being implemented and promoted by the major application server vendors. Web services and service-oriented architectures encourage - in fact, they demand - reuse by their very nature, as the sole purpose of a service is to expose a set of functional capabilities to multiple consumers. If that isn't reuse, then what is? In addition, because services are meant to be deployed once and accessed in place, they encourage the notion of business process assembly that crosses application boundaries - weaving together a series of services in support of a business process that may be described through a graphical design-time user interface. While the tools and underlying mechanisms to support this notion are still in their infancy, initiatives such as BPEL4WS (Business Process Execution Language For Web Services) show great promise in enabling this form of application development. Although it's unrealistic to expect that graphical application assembly will ever fully take the place of other development techniques, it will certainly take its place alongside those techniques and, in the process, encourage more effective reuse of underlying services.

Services and components also have a very symbiotic relationship that supports software reuse. Components are often the underlying mechanism behind a service, either fully implementing the functionality defined by the service or providing the necessary glue code to connect the modern Web service infrastructure with one or more legacy systems.

Software Engineering Processes and Tools
Great strides have been made in the past decade toward more disciplined and effective software development processes. Iterative methods such as RUP (Rational Unified Process) encourage early discovery, implementation, and refinement of key requirements. Incremental enhancements delivered on a regular and timely basis are a far cry from the heavyweight waterfall methodologies that typically resulted in late delivery of software that didn't meet user needs, not the least because those user needs changed from the time the original requirements were defined.

RUP and other modern software development processes encourage reuse by injecting specific software development asset (SDA) search and reuse review checkpoints into the development process. These search-and-review activities occur at all levels of the development life cycle from initial requirements definition, through analysis and design, and down to implementation. Modern UML-based modeling techniques also encourage reuse by providing analysts and developers with a concise, graphical means to crisply define functional requirements. Requirements in this form can then be consumed by other development tools such as code generators, mapping engines, and asset metadata repositories. UML-based IDE tools can be used not only to create UML but also to apply reusable knowledge SDAs such as design patterns to the resulting code, automatically preserving consistency between source code and model.

The Business Case for Reuse
With these tools and techniques in hand, and with IT budgets continuing to experience strong cost-cutting pressures, it's hard not to see the justification for a reuse initiative within an IT organization of any size. Dr. Jeffrey Poulin, noted software industry reuse expert, has compiled numerous studies that indicate reuse payback occurs on the first reuse of an SDA, even taking into account the extra effort required to build the asset for reuse. Michael Blechar, vice president and research director at Gartner Research, states, "Enterprises can substantially improve application development productivity and quality, while also decreasing time-to-market, by a factor of 5:1 or more through a committed software asset reuse program. At the heart of this initiative must be the ability for analysts and developers to easily locate and reuse these assets." Take the time to investigate the tools available to you to encourage reuse. (I'll cover process and tools in more detail in a future editorial.) Even something as seemingly simple as disseminating architectural guidance to development teams as UML models distributed through an asset metadata repository can produce significant payback in the form of code implemented using industry and organizational best practices, thus greatly reducing the chance of rewriting or experiencing heavy maintenance costs down the road. Adding the ability to define and distribute well-structured, coarse-grained components and services throughout your organization can accelerate productivity and, just as important, improve application consistency dramatically throughout your organization - and maybe make you a hero in the bargain!

More Stories By Brent Carlson

Brent Carlson is vice president of technology and cofounder of LogicLibrary, a provider of software development asset (SDA) management tools. He is the coauthor of two books: San Francisco Design Patterns: Blueprints for Business Software (with James Carey and Tim Graser) and Framework Process Patterns: Lessons Learned Developing Application Frameworks (with James Carey). He also holds 16 software patents, with eight more currently under evaluation.

Comments (0)

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.

IoT & Smart Cities Stories
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...