Writers' First Review Draft:    (2VAD)

Term    (2XU2)

Legacy System    (2XU3)

Origin/Source for Inclusion of the Term    (2XU4)

CAF Glossary v0    (2XU5)

OMB Context Definition    (2XU6)

Reference/URL OMB Context Definition    (2XU7)

Business Definition    (2XU8)

An existing application or system that is not full integrated into the "To Be" enterprise architecture. It may duplicate services of newer applications or systems or it may lack planned interface capabilities. Typically, legacy applications and systems were developed without modularity, using older technologies, and often lack documentation and source code.    (2XU9)

Reviewer Comment: My/Industry's definition of a Legacy System is one that is in the "As Is" architecture. It may or may not be included in the "To Be" Architecture. If this is the Govt's definition, I need to modify my constructs. Also make shorter.    (2XUA)

Reference/URL for Business Definition    (2XUB)

Technical Definition    (2XUC)

Reference/URL Technical Definition    (2XUD)

Context Definition 1    (2XUE)

"A listing of the defense business systems as of December 2, 2002 (known as `legacy systems'), that will not be part of the objective defense business enterprise architecture…"    (2XUF)

Reference/URL Context Definition 1    (2XUG)

As used in Title 10 USC Sec. 2222, Defense Business Systems: Architecture, Accountability, and Modernization, of Public Law 108-375, the Ronald W. Reagan National Defense Authorization Act (NDAA) for Fiscal Year 2005    (2XUH)

Context Definition 2    (2XUI)

Reference/URL for Context Definition 2    (2XUJ)

Context Definition 3    (2XUK)

Reference/URL for Context Definition 3    (2XUL)

See Also Related Terms    (2XUM)