...
Score | Software Application | Data | Integration |
|---|---|---|---|
1 | minor patch or security release, no end-user function affected | single schema | self-contained, single end-user transaction |
2 | major patch, "dot release" that effects end-user behavior | single database, multiple schemas | system of record, affects data feeds to warehouse |
3 | full application upgrade, new user functionality | external link or feed relationship to other system of record | service allows for real-time update of share enterprise data |
4 | operating-system upgrade as distributed release or affecting many underlying services | multiple external links or feed relationships | real time integration service, loss of service ends business productivity |
5 | packaged release of operating system, multicomponent or multi-transactional system | multiple production database servers changed |
|
ITIL Outline discovered by Pat on Wikipedia:
I found some tid bits on Wikipedia in the ITIL section that may or may not be helpful (high level)
Release categories include:
Major software releases and major hardware upgrades, normally containing large amounts of new functionality, some of which may make intervening fixes to problems redundant. A major upgrade or release usually supersedes all preceding minor upgrades, releases and emergency fixes.
- Minor software releases and hardware upgrades, normally containing small enhancements and fixes, some of which may have already been issued as emergency fixes. A minor upgrade or release usually supersedes all preceding emergency fixes.
- Emergency software and hardware fixes, normally containing the corrections to a small number of known problems.
Releases can be divided based on the release unit into:
Delta Release: a release of only that part of the software which has been changed. For example, security patches.
...
real-time integration service, requires client applications to refactor |
End Notes
(ed. to become properly formatted end notes later. sml)
...