---
title: forensic software engineering
slug: forensic-software-engineering
qid: Q5468729
snapshot: forensic-software-engineering-622148-5c8e1faeb0be4429
content_hash: 5c8e1faeb0be4429687d773925a4bfed15f941e5a2e9589fa699880790c737f6
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1215725352
tags: [20340897, 23468805, 23603337, 24043274, 26220375, 29326830, 54849246, 60433035]
---

# forensic software engineering

> [!note] Provenance
> Snapshot `forensic-software-engineering-622148-5c8e1faeb0be4429` · content root `5c8e1faeb0be4429…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1215725352> · Licensed CC BY-SA 4.0

Forensic software engineering refers to the discipline of analyzing (and sometimes reconstructing) the functionality of software applications or services that have become defunct; are no longer accompanied by, or previously lacked, documentation; or for which the original engineers are no longer available.

Forensic software engineering refers to the discipline of analyzing (and sometimes reconstructing) the functionality of software applications or services that have become defunct; are no longer accompanied by, or previously lacked, documentation; or for which the original engineers are no longer available. ==Description== Usually, forensic software engineering is performed with an interest in understanding the functionality - and sometimes intent - of software that has been abandoned by its creators, with an eye to correcting unexpected outcomes or determining whether to port, rebuild, replace, or retire a functional software instance. Is often required as a result of a corporate mergers or acquisitions, or during the migration/transition from an old datacenter to a newer one. ==References==
