Editorial: Sexing up EA

nterprise architectures have come a long way in a relatively short period of time. Most agencies not only have one but also use it to help them make decisions, in most cases.

There is no better illustration of that progress than when Tom Ridge was named secretary of the Homeland Security Department and said that establishing an enterprise architecture was a top priority.

Those responsible for developing and implementing such architectures generally acknowledge that most senior agency officials and frontline workers understand the importance of enterprise architectures. The problem, they argue, is educating those in between.

The difficulty with enterprise architectures is that they simply do not have much meaning for those outside information technology and

chief information officer offices. Even some people within IT shops regard architectures as an exercise that they do not fully understand or

appreciate.

The lack of understanding is, at least in part, the result of enterprise architectures' complexity. As with so many concepts in the IT world, enterprise architecture has its own culture and language. Just a quick pop quiz: How many of us really know what a reference model is? And how many could explain the relationship between the federal enterprise architecture and individual agency enterprise architectures?

As part of this week's feature, we answered some frequently asked

questions under the assumption that some of you, even within the IT community, do not fully understand all of the elements of enterprise

architecture.

The goal of an architecture is a good one: to move beyond stand-alone systems to those that use resources and data more efficiently. But getting there seems overly complex. And the language of enterprise architecture is a big hurdle to overcome if the goal is to become a reality for those who are not CIOs and IT officials.

Office of Management and Budget officials are in the process of hiring a new enterprise architect. We hope this person, working with members of the CIO Council, can come up with a creative way to broaden the understanding of this important concept.

No small task, but a very important one.

FCW in Print

In the latest issue: Looking back on three decades of big stories in federal IT.

Featured

  • FCW @ 30 GPS

    FCW @ 30

    Since 1996, FCW has covered it all -- the major contracts, the disruptive technologies, the picayune scandals and the many, many people who make federal IT function. Here's a look back at six of the most significant stories.

  • Shutterstock image.

    A 'minibus' appropriations package could be in the cards

    A short-term funding bill is expected by Sept. 30 to keep the federal government operating through early December, but after that the options get more complicated.

  • Defense Secretary Ash Carter speaks at the TechCrunch Disrupt conference in San Francisco

    DOD launches new tech hub in Austin

    The DOD is opening a new Defense Innovation Unit Experimental office in Austin, Texas, while Congress debates legislation that could defund DIUx.

  • Shutterstock image.

    Merged IT modernization bill punts on funding

    A House panel approved a new IT modernization bill that appears poised to pass, but key funding questions are left for appropriators.

  • General Frost

    Army wants cyber capability everywhere

    The Army's cyber director said cyber, electronic warfare and information operations must be integrated into warfighters' doctrine and training.

  • Rising Star 2013

    Meet the 2016 Rising Stars

    FCW honors 30 early-career leaders in federal IT.

Reader comments

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group