Buy This Standard. Access Via Subscription. Explore This Standard. Standard Details.
|Published (Last):||26 April 2004|
|PDF File Size:||14.55 Mb|
|ePub File Size:||6.11 Mb|
|Price:||Free* [*Free Regsitration Required]|
It also establishes definitions for the various types of maintenance. It provides the framework, precise terminology and processes to allow the consistent application of technology tools, techniques and methods to software maintenance. It defines the activities and tasks of software maintenance, and provides maintenance planning requirements.
It does not address the operation of software and the operational functions, e. It may also be used by acquirers and users of systems containing software who may provide inputs to the maintenance plan. Check out our FAQs. Buy this standard.
CHF Buy. Life cycle A standard is reviewed every 5 years 00 Preliminary. Final text received or FDIS registered for formal approval. Proof sent to secretariat or FDIS ballot initiated: 8 weeks. Close of voting. Proof returned by secretariat. International Standard under periodical review. Got a question? Customer care. Keep up to date with ISO Sign up to our newsletter for the latest news, views and product information Subscribe.
Store Standards catalogue ICS 35 English Russian.
ISO provides guidance that applies to planning, execution and control, review and evaluation, and closure of the software maintenance process. The scope of the standard includes maintenance for multiple software products with the same maintenance resources. ISO provides the framework within which generic and specific software maintenance plans may be executed, evaluated, and tailored to the maintenance scope and magnitude of given software products. It provides the framework, precise terminology, and processes to allow the consistent application of technology tools, techniques, and methods to software maintenance. ISO defines the activities and tasks of software maintenance, and provides maintenance planning requirements.
AFNOR Editions Online Store
Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes. A common perception of maintenance is that it merely involves fixing defects. Software maintenance and evolution of systems was first addressed by Meir M. Lehman in Over a period of twenty years, his research led to the formulation of Lehman's Laws Lehman