Keywords: , , , , , , , , , , , , ,

Thomas Mowbray


The District of Columbia’s Office of the Chief Technology Officer (OCTO) recently completed a set of Citywide Enterprise Architecture (EA) blueprints that illustrate IT systems and enterprise business processes with a near-term focus of the nine Services Modernization Programs (SMP). The Citywide WA is compliant with the Federal Enterprise Architecture Framework Level III. The Citywide EA is comprises four blueprints: business architecture, information architecture, application architecture, and infrastructure architecture. The Citywide EA application blueprint comprises a Services Oriented Architecture for hared software components. Three of these EA blueprints will be published in the District’s IT Strategic Plan 2005-2008. The fourth viewpoint, infrastructure architecture, is classified as Protected Critical Infrastructure Information by the U.S. Department of Homeland Security. In addition, the District is designing long-term Concepts of Operations that constitute strategic program plans and target architectures for each SMP. The District’s to-be planning approach incorporates best practices from Business Process Reengineering and EA.


enterprise architecture, strategic planning, business process reengineering, modernization, systems integration, enterprise licensing, service oriented architecture, process improvement, cost benefit analysis, benefits realization

About the author

Dr. Thomas Mowbray is the District of Columbia’s Chief Enterprise Architect. Dr. Mowbray is a FEAC-certified Federal Enterprise Architect. He has served as Chief Architect on multiple projects for the District, the United States Marine Corps, the State of Maryland, and the United States Air Force. His education includes an MS in Computer Engineering from Stanford and Ph.D. in Computer Science from University of Southern California. Dr. Mowbray has co-authored five books including: CORBA Design Patterns, Projects in Crisis, Software Architect Bootcamp (2nd Edition), AntiPatterns: Refactoring Software Architectures.

The author would like to thank Suzanne Peck, the District’s Chief Technology Officer, for her architectural vision, and Mayor Anthony Williams for his technology leadership, which drives District IT modernization. The Enterprise Architects who contributed EA models and modeling information to the City-wide Enterprise Architecture include: Alex Zbarsky, Mustafa Hajjar, Terrence Lillard, Dr. Minhua Wang, John Chelen, Susan Volpi, J.B. MacKenzie, Taha Siddiqui, Judd Nielsen, Tom Cosgrove, Dan Thomas, Paul Liderman, Rob Mancini, Torn Massie, Lesley Overton, Alexander Rudnev, John Choi, Joe Ross, Norrnan Peterson, Bruce King, Malcolm Hill, Tom Fontenot, Viraj Ghandi, and Ryan Bissett.


Bing, S. (1992). Crazy Bosses: Spotting Them. Serving Them. Surviving Them, William Morrow and Company, New York, NY.

Curran, C. (2005). “Link IT Investments to Business Metrics,” Enterprise Architect. Volume 3, Number 1, Spring 2005.

Federal Chief Information Officers Council (1999). Federal Enterprise Architecture Framework (Version 1.1). Washington DC.

Malveau, R., and Mowbray, T. (2003). Software Architect Bootcamp (2nd Edition). Prentice Hall PTR, Upper Saddle River, NJ.

Sewell, M. and Sewell, L. (2004). Business Design and Blueprints: Effective Business Communication Using the Simon Visual Language (Version 4.1). Simon Labs Incorporated, Atlanta, GA. www.simonvisuallanguage.coml

Spewak, S.H., Hill S.C. (1992). Enterprise Architecture Planning. Developing a Blueprint for Data. Applications and Technology. John Wiley and Sons, Inc., New York.

Whittle, R., and Myrick, C. (2004). Enterprise Business Architecture: The Formal Link between Strategy and Results. www.enterprisebusinessarchitecture.comldocuments/EBA3he_FormaLLi nk.pdf.

Journal of Enterprise Architecture

Leave a Comment