|Title :||Software Maintenance Process|
|Process group :||6.4|
|Lower-level process of :||none|
|Replaced by process :||none|
|Specialization of :||none|
|Conforming instance of :||none|
Purpose : The purpose of the Software Maintenance Process is to provide cost-effective support to a delivered software product. NOTE Pre-delivery Software Maintenance activities include planning for post-delivery operations, supportability, and logistics determination. Post-delivery activities include software modification and operational support, such as training or operating a help desk.
List of outcomes : As a result of successful implementation of the Software Maintenance Process: a) a maintenance strategy is developed to manage modification and migration of products according to the release strategy; b) the impact of changes to the existing system on organization, operations or interfaces are identified; c) affected system and software documentation is updated as needed; d) modified products are developed with associated tests that demonstrate that requirements are not compromised; e) product upgrades are migrated to the customer’s environment; and f) the system software modification is communicated to all affected parties.warning.pngLa chaîne de représentation As a result of successful implementation o […] n is communicated to all affected parties. est trop grande pour ce site.
NOTE 1 The Software Maintenance Process in this International Standard is a specialization of the Maintenance Process of ISO/IEC 15288. Users may consider claiming conformance to the 15288 process rather than the process in this standard. NOTE 2 The Software Maintenance Process of this International Standard is compatible with ISO/IEC 14764:2006.
|Outcome||warning.pngLa chaîne de représentation As a result of successful implementation o […] n is communicated to all affected parties. est trop grande pour ce site.|
|Title||Software Maintenance Process +|