Brownfield (software development)

Brownfield development is a term commonly used in the <a href="/facts/Information_technology/glMzunwe">information technology</a> industry to describe problem spaces needing the development and deployment of new <a href="/facts/Software/RP79lVSW">software</a> systems in the immediate presence of existing (legacy) software applications/systems. This implies that any new <a href="/facts/Software_architecture/1Hokp0Ed">software architecture</a> must take into account and coexist with live software already <a href="/facts/In_situ/YolKlaCC">in situ</a>.
In contemporary <a href="/facts/Civil_engineering/avh5kEq2">civil engineering</a>, <a href="/facts/Brownfield_land/E1su5meG">brownfield land</a> means a property, the expansion, redevelopment, or reuse of which may be complicated by the presence or potential presence of a hazardous substance, pollutant, or contaminant.
Brownfield development adds a number of improvements to conventional <a href="/facts/Software_engineering/KX6cE9kz">software engineering</a> practices. These traditionally assume a "clean sheet of paper", <a href="/facts/Tabula_rasa/esxlgDCh">tabula rasa</a> or "<a href="/facts/Greenfield_land/oUhS1AN8">greenfield land</a>" target environment throughout the design and implementation phases of software development. Brownfield extends such traditions by insisting that the context (local landscape) of the system being created be factored into any development exercise. This requires a detailed knowledge of the systems, services and data in the immediate vicinity of the solution under construction.

Brownfield (software development) open-in-new

Brownfield (software development)