Software maintenance in software engineering is the modification of a software product after . These have since been updated and ISO/IEC presents. This International Standard describes in greater detail management of the Maintenance Process described in ISO/IEC , including Amendments. ISO/IEC/IEEE was prepared by Joint Technical Committee ISO/IEC the harmonization of ISO/IEC and IEEE Std
|Genre:||Health and Food|
|Published (Last):||23 February 2015|
|PDF File Size:||1.67 Mb|
|ePub File Size:||15.52 Mb|
|Price:||Free* [*Free Regsitration Required]|
ISO standards by standard number. Key technical issues are: Views Read Edit View history. Maintenance may span for 20 years, [ citation needed ] whereas development may be 1—2 years. The purpose is to preserve the value of software over the time. Cryptography Formal methods Security services Intrusion detection system Hardware security Network security Information security Application security. Archived from the original PDF on 1464 Wikipedia references cleanup from September All articles needing references cleanup Articles covered by WikiProject Wikify from September All articles ice by WikiProject Wikify Articles needing additional references from January All articles needing additional references Articles with multiple maintenance issues All articles with unsourced statements Articles with unsourced statements from January Articles with unsourced statements from October All articles with specifically marked weasel-worded phrases Articles with specifically marked weasel-worded phrases from January Wikipedia articles with BNF identifiers Wikipedia articles with GND identifiers Wikipedia articles with LCCN identifiers.
And this is the main cause of any problem during software evolution and maintenance. Software development process Requirements analysis Software design Software construction Software deployment Software maintenance Programming team Open-source model.
Because change is inevitable, mechanisms must be io for evaluation, controlling and making modifications. Iiso the late s, a famous and widely cited survey study by Lientz and Swanson, exposed the very high fraction of life-cycle costs that were being expended on maintenance. It should specify how users will request modifications or report problems.
Software maintenance is a very broad activity that includes error correction, enhancements of capabilities, deletion of obsolete capabilities, iev optimization.
Best practices for managing your software investment. Key findings of his research include that maintenance is really evolutionary development and that maintenance decisions are aided by understanding what happens to systems and software over time.
This article has an unclear citation style. Proceedings of the 2nd international conference on Software engineering, San Francisco,pp — “. The selection of proper enforcement of standards is the challenging task right from early stage of software engineering which has not got definite importance by the concerned lso.
September Learn how and when to remove this template message. Below describe some of the factors and the range of impact on software maintenance. A new decision should be addressed for the developing of every new system feature and its quality objectives.
Retrieved 5 November Note also that some academic ie [ who?
Software maintenance – Wikipedia
P P P P P Studies show that contribution of end user is crucial during the new requirement data gathering and analysis. They categorized maintenance activities into four classes:. Interaction design Social computing Ubiquitous computing Visualization Accessibility.
The references used may be made clearer with a different or consistent style of citation and footnoting. From Wikipedia, the free encyclopedia.
Computer science Computer engineering Project management Risk management Systems engineering. The management of coupling and cohesion of the software.
Assessing Evidence from Change Management Data. So any work done to change the software after it is in operation is considered to be maintenance work.
ISO/IEC – Software Engineering — Software Life Cycle Processes — Maintenance
Please help improve this article by adding citations to reliable sources. This page was last edited on 22 Octoberat Key management issues are: Lec Learn how and when to remove this template message. Data modeling Enterprise architecture Functional specification Modeling language Orthogonality Programming paradigm Software Software archaeology Software architecture Software idc management Software development methodology Software development process Software quality Software quality assurance Software verification and validation Structured analysis.
The budget should include resource and cost estimates. Many subsequent studies suggest a similar magnitude of the problem.