Business Services Industry

Enterprise Architecture For Dod Acquisition

Acquisition Review Quarterly, Spring, 2000 by David P. Brown

REFERENCES

Enterprise Architecture Project Final Report. (1996). Stanford University.

Farrow, V. (1999, April). Responding to Change: A Lucent Technologies Program for Growth. Presentation to PEO/SYSCOM Commanders' Workshop.

Government Accounting Office. (1996, August 26). Federal downsizing: Better workforce and strategic planning could have made buyouts more effective (Chapter Report No. GAO/GGD-96-62). Washington, DC: Author.

Industrial automation systems--Requirements for enterprise-reference architectures and methodologies. (1998). http://www.mel.nist.gov/sc5wg1/gera-std/15704dis.htm, ISO Central Secretariat, Geneva, Switzerland.

Stevenson, D. A. (1995, June). Business themes and enterprise architecture -- conclusions. http://users.iafrica.com/d/de/denniss/text/busthemx.html, University of Cape Town, Cape Town, South Africa.

Spewak, S. H., with Hill, S. C. (1993). Enterprise architecture planning: Developing a blueprint for data, applications, and technology. New York: John Wiley & Sons.

Zachman, J. A. (1997, March). Enterprise architecture: The issue of the century http://www.zifa.com/zifajz01.htm, Database Programming and Design, Zachman International.

COPYRIGHT 2000 Defense Acquisition University Press
COPYRIGHT 2004 Gale Group
 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
advertisement
  • Click Here
  • Click Here
  • Click Here
advertisement
Click Here

Content provided in partnership with Thompson Gale