This article relies largely or entirely on a single source. Relevant discussion may be found on the talk page. Please help improve this articlebyintroducing citations to additional sources.
Find sources: "Forensic software engineering" – news · newspapers · books · scholar · JSTOR (March 2024) |
History of computing |
---|
![]() |
Hardware |
Software |
Computer science |
Modern concepts |
By country |
Timeline of computing |
Glossary of computer science |
|
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.
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.[1]
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.
| |||||
---|---|---|---|---|---|
General |
| ||||
Variants |
| ||||
Kernel |
| ||||
Process management |
| ||||
Memory management, resource protection |
| ||||
Storage access, file systems |
| ||||
Supporting concepts |
|
![]() | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |