Forensic software engineering
Software engineering discipline
| 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.
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.[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.
See also
Computer programming portal
- 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?"
- v
- t
- e
- Comparison
- Forensic engineering
- History
- List
- Timeline
- Usage share
- User features comparison
| Architectures | |
|---|---|
| Components |
| Concepts |
|
|---|---|
| Scheduling algorithms |
resource protection
file systems
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |
- v
- t
- e
