Monday, December 7, 2009

Embedded Market Forecasters study finds commercial middleware reduces cost and risk

FRAMINGHAM, USA: Embedded Market Forecasters, a premier market intelligence and advisory firm for the embedded technology industry, today released a report titled “Choosing Between Commercial and ‘Roll Your Own’ Embedded Communication Integration Middleware” and survey results that provide a cost-based evaluation framework for embedded developers evaluating the relative merits of developing in-house, or “Roll Your Own” (RYO), middleware or using a commercial alternative.

The study marks the first time that ROI metrics have been developed from comprehensive data derived from an extensive survey of embedded developers. The findings show that middleware selection can have a very significant impact on a project’s cost, timeliness, risk and performance.

The Embedded Market Forecasters report is based on a sample of 166 developers that identified themselves as communication middleware users (out of 476 total survey respondents). Slightly over half, or 55.6% used in-house, “Roll-Your-Own” solutions and the remainder comprised commercial communication middleware users, including both embedded and IT communication middleware products.

Applications included avionics, automotive, medical, telecom, Datacom, electronic instrumentation, industrial automation, military and consumer electronics, among others. The total cost of application development for each project was estimated by multiplying the average development project time to market by the software development team size and average monthly industry cost per developer.

Commercial communications middleware consists of embedded vendors and IT middleware vendors selling into the embedded space. There is a significant difference in the comparative data; however, for purposes of this study they were combined under the “commercial” category as they together comprise the market.

In addition to comparing the results of commercial and in-house, “Roll Your Own” middleware, EMF also compared the results of these two categories with those of the two most popular vendors of embedded integration middleware, Objective Interface Systems and Real-Time Innovations.

According to EMF’s research:
Total Cost of Development: The average cost of application development was substantial for projects using RYO middleware ($1.61 million), most commercial solutions ($1.34 million), and OIS ($1.49 million); however, projects using RTI enjoyed much lower costs ($0.89 million).

Average Cost Overrun: The average cost overrun was similar for projects using RYO (11.3 percent) and commercial (10.1 percent) middleware. Projects using RTI finished closest to expected cost (6 percent) and projects using OIS ran significantly over budget (14.1 percent).

Testing Costs: In projects where the cost of testing was less than 30 percent of the total development cost, RYO (72.5 percent) showed an advantage over commercial (65.5 percent) middleware. Projects using RTI’s commercial middleware, however, had testing costs less than 30 percent of the total development cost 84.6 percent of the time.

Design Completion and Outcomes: Final Design outcomes using commercial embedded middleware in general, and RTI in particular, were much closer to pre-design expectations than RYO developments for performance, functionality, features and schedule.

"Middleware choice can have a critical impact on development costs, schedules, risk and performance,” said embedded industry expert Dr. Jerry Krasner. "Developers are challenged by projects that are increasingly complex, with ever-shrinking market windows and increased support requirements.

"While RYO developers often believe that they can develop their middleware at a lower cost or with higher performance than commercial middleware, this study indicates otherwise. They and cost-conscious company management alike should strongly consider the advantages of commercial communication integration middleware and the embedded offerings of OIS and RTI in particular."

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.