Then there is the question of how to test the functionality. Classic software development invests a large part of the work in test procedures which require specialists with specific competence. Mashups, just like all software objects, must be tested. Users must be trained, and the design tools must provide aids such as simulations. This is where the limits to user-driven innovation begin to appear.
Closely related to the problem of testing is the question of what is to be done in the event of poor quality in corporate data. While a classic development project can be combined with a complex data clean-up, mashups must work with the status given to them. Data governance in the context of the SOA ecosystem can improve the framework conditions. But even when users are supported by powerful design tools, training and experience are still required. Competence classes among users have become established in comparable application areas which depend on user-generated programming, e.g., business intelligence. One can expect normal users who utilize a mashup; “power users” or “gurus” who design a mashup, and dedicated programmers for more complex tasks.
Finally, the IT department finds itself faced with a new challenge in support. Although the staff will be given relief with respect to design, they also lose a certain amount of control, but are also expected to support users when something goes wrong. The IT support must be prepared for this and take on the role of a “coach” in development rather than that of a “bug fixer”.
Business mashups are a fascinating enhancement of today’s methods for application development in a complex corporate environment. They bear promise of being able to unlock innovation potential among the employees of a company. They open up new opportunities for making data and functions in the SOA ecosystem of a company available for use while simultaneously relieving the IT department of some of its work. But their development is still at the beginning and must prove that it is suitable for use in companies. Challenges such as IT security, wild growth in mashups, and quality assurance must be mastered. If the promises can be kept, a company that implements one of the platforms competing on the marketplace will have a clear competitive advantage.
Published in DMR 02/2009
Next page