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

Author: Kekree Moogutaxe
Country: Algeria
Language: English (Spanish)
Genre: Relationship
Published (Last): 23 January 2011
Pages: 41
PDF File Size: 19.37 Mb
ePub File Size: 10.73 Mb
ISBN: 923-4-16239-267-2
Downloads: 13973
Price: Free* [*Free Regsitration Required]
Uploader: Kigazuru

Natural language processing Knowledge representation and reasoning Computer vision Automated planning and scheduling Search methodology Control method Philosophy of artificial intelligence Distributed artificial intelligence.

A new decision should be ixo for the developing of every new system feature and its quality objectives. Model of computation Formal language Automata theory Computational complexity theory Logic Semantics. Maintenance may span for 20 years, [ citation needed ] whereas development may be 1—2 years.

Computer programming Requirements engineering Software deployment Software design Software maintenance Software testing Systems analysis Formal methods. Learn how and when to remove these template messages. Swanson initially identified three categories of maintenance: The references used may be made clearer with a different or consistent style of citation and footnoting. This article has multiple issues.

Data modeling Enterprise architecture Functional specification Modeling language Orthogonality Programming paradigm Software Software archaeology Software architecture Software configuration management Software development methodology Software development process Software quality Software quality assurance Software verification and validation Structured analysis. Below describe some of the factors and the range of impact on software maintenance.

Computer science Computer engineering Project management Risk management Systems engineering. Many subsequent studies suggest a similar magnitude of the problem.

14746 architecture Embedded system Real-time computing Dependability. Wikipedia references cleanup from September All articles needing references cleanup Articles covered by WikiProject Wikify from September All articles covered by WikiProject Wikify Articles needing additional references ied 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.


Views Read Edit View history. This page was last edited on 22 Octoberat Software maintenance is a very broad activity that includes error correction, enhancements of capabilities, deletion of obsolete capabilities, and optimization.

Retrieved from ” https: Concurrent computing Parallel computing Distributed computing Multithreading Multiprocessing. Please help improve this article by adding citations to reliable sources. Lehman demonstrated that systems continue to evolve over time. Interaction design Social computing Ubiquitous computing Visualization Accessibility.

ISO/IEC – Software Engineering — Software Life Cycle Processes — Maintenance

Unsourced material may be challenged and removed. Over a period of twenty years, his research led to the formulation of Lehman’s Laws Lehman Cryptography Formal methods Security services Intrusion detection system Hardware security Network security Information security Application security.

A very common situation which often degrades performance is lack of suitable maintenance tools, such as defect iwc software, change management software, and test library software.

E-commerce Enterprise software Computational mathematics Computational physics Computational chemistry Computational biology Computational social science Computational engineering Computational healthcare Digital art Electronic publishing Cyberwarfare Electronic voting Video games Word processing Operations research Educational technology Document management. Retrieved 5 November Archived from the original PDF on Not only are error-prone modules troublesome, but many other factors can degrade performance too.

P P P P P Please help improve it or discuss these issues on the talk page. 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. Interpreter Middleware Virtual machine Operating system Software quality.

Software maintenance

January Learn how and when to remove this template message. Key management issues are: Software maintenance and evolution of systems was first addressed by Meir M.

  88957 MANUAL PDF

Because change is inevitable, mechanisms must be developed for evaluation, controlling and making modifications. And this is the main cause of any problem during software evolution and maintenance. The value can be enhanced by expanding the customer base, meeting additional requirements, becoming easier to use, more efficient and employing newer iiso.

The selection of proper enforcement of standards is the challenging task right from early stage of software engineering which isp not got definite ios by the concerned stakeholders. Note also that some 1764 institutions [ who? Best practices for managing your software investment. Proceedings of the 2nd international conference on Software engineering, San Francisco,pp — “.

Key technical issues are: By using this site, you agree to the Terms of Use and Privacy Policy. Network architecture Network protocol Network components Network scheduler Network performance evaluation Network service. ISO standards by standard number. So software maintenance is important because it consumes a large part of the overall lifecycle costs and also the inability to change software quickly and reliably means that business opportunities are lost.

As they evolve, they grow more complex unless some action such as code refactoring is taken to reduce the complexity. In the late s, a famous and widely cited is study by Lientz and Swanson, exposed isso very high fraction of life-cycle costs that were being expended on maintenance. The management of coupling and cohesion of the software. So any work done to change the software after it is in operation is considered to be maintenance work.