Lesson plan
Brownfield (software development)
Brownfield development is a term commonly used in the information technology industry to describe problem spaces needing the development and deployment of new software systems in the immediate presence of existing (legacy) software applications/systems. The term was introduced in 2008 by Hopkins and Jenkins. This implies that any new software architecture must take into account and coexist with live software already in situ. In contemporary civil engineering, brownfield land 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 software engineering practices. These traditionally assume a "clean sheet of paper", tabula rasa or "greenfield land" 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.
Article summary
Brownfield development is a term commonly used in the information technology industry to describe problem spaces needing the development and deployment of new software systems in the immediate presence of existing (legacy) software applications/systems. The term was introduced in 2008 by Hopkins and Jenkins. This implies that any new software architecture must take into account and coexist with live software already in situ. In contemporary civil engineering, brownfield land 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 software engineering practices. These traditionally assume a "clean sheet of paper", tabula rasa or "greenfield land" 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.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.