Significance and Use
4.1 This guide provides a recommended transition plan for a marine software maintainer, when the maintainer is other than the supplier, to develop the capability to make extensive changes or extensions to the programs. Further, this guide provides a recommended interactive process model for managing and executing software maintenance activities. This guide applies principally to the marine software that requires design effort and for which the product requirements are stated principally in performance terms.
Scope
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity other than the maintaining activity. It further provides a recommended iterative process model for managing and executing software maintenance activities.
