Letter: For enterprise architecture, keep it simple

Regarding "DOD's Wisnosky: EA needs notation" : I like Wisnosky's idea on a common symbology for enterprise architecture. But if techies and network experts develop this new language, it will likely be too complex and burdensome to effectively communicate to a broad audience. If it can't communicate to a broad audience, it will doom EA rather than advance it. EA serves to make transparent and communicate and make plain, not take concepts that are Greek to most and make them Chinese.  The reason EA has not advanced is because it has been largely the realm of techies. To advance EA, we need to involve people who understand mission, process, and data more than anyone else. What holds EA back is the fact that it is viewed as the domain of hardware and software experts, when it is not.

Anonymous

What do you think? Paste a comment in the box below (registration required), or send your comment to letters@fcw.com (subject line: Blog comment) and we'll post it.

Featured

  • FCW PERSPECTIVES
    sensor network (agsandrew/Shutterstock.com)

    Are agencies really ready for EIS?

    The telecom contract has the potential to reinvent IT infrastructure, but finding the bandwidth to take full advantage could prove difficult.

  • People
    Dave Powner, GAO

    Dave Powner audits the state of federal IT

    The GAO director of information technology issues is leaving government after 16 years. On his way out the door, Dave Powner details how far govtech has come in the past two decades and flags the most critical issues he sees facing federal IT leaders.

  • FCW Illustration.  Original Images: Shutterstock, Airbnb

    Should federal contracting be more like Airbnb?

    Steve Kelman believes a lighter touch and a bit more trust could transform today's compliance culture.

Stay Connected

FCW Update

Sign up for our newsletter.

I agree to this site's Privacy Policy.