Forensic software engineering
Appearance
move to sidebar
hide
|
This article relies largely or entirely on a single source. Relevant discussion may be found on the talk page. Please help improve this article by introducing 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 |
|
|
CategoryForensic 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.
See also
- Charles Babbage Institute
- History of operating systems
- IT History Society
- List of operating systems
- Timeline of operating systems
References
- ^ Johnson, Chris «Forensic Software Engineering: Are Software Failures Symptomatic of Systemic Problems?»
|
|||||
|---|---|---|---|---|---|
| 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. |
- v
- t
- e
