Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Blackboard and Software Complexity

DZone's Guide to

Blackboard and Software Complexity

Blackboard has suffered complexity issues. Learn more about enterprise software, how it ages, and management or mismanagement.

· Integration Zone ·
Free Resource

SnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.

A comment on Blackboard’s complexity problems.

If either the author of this article or the otherwise knowledgeable Feldstein have ever worked in software development, it’s not apparent from this article and the ensuing comments thread. The list of architectural scare factors – multiple deployment environments, wide use of 3rd party libraries, legacy code – is simply business as usual for any substantial software product. And the assertion that “few other companies support this sheer raw complexity of configuration combinations” is just plain wrong. Many, many companies deal with exactly this. Cross-platform release engineering is a demanding but well-understood discipline.

To pick on a couple more representative points: “All enterprise software ages poorly.” No, all software ages. Whether it ages poorly or well depends on whether it’s worth the vendor’s time to manage its aging. Go and ask the IBM shops running 1960’s-vintage System 360 applications on modern virtualized environments whether they’re happy with 50 years of ROI on those applications. And then: “Microsoft control their entire ecosystem.” Please, please, go and talk to a Microsoft release test engineer about how controlled their release targets are. Make sure you have a very comfortable seat and lots of beer money, because you’ll be buying and you’ll be there for a looong time.

I don’t challenge the author’s underlying premise that Blackboard has mismanaged its software assets – I don’t have the inside knowledge to confirm or deny that. And the notion that Blackboard, like every software developer, needs to actively manage and reduce complexity is incontestable. But I don’t accept the notion that the architectural factors listed are any kind of indicator. I would bet that inside Blackboard there are some very frustrated developers who know exactly how to support that range of configurations, led by a management group who is telling them not to spend time refactoring and reducing technical debt, but rather to crack on with adding to the feature list smorgasbord. As if that’s an either/or choice.

Download A Buyer's Guide to Application and Data Integration, your one-stop-shop for research, checklists, and explanations for an application and data integration solution.

Topics:
integration ,ei ,enterprise integration ,software quality ,software complexity

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}