This International Standard describes in greater detail management of the Maintenance Process described in ISO/IEC , including Amendments. ISO/IEC. IEEE. Std Second edition. Software Engineering — Software Life. Cycle Processes — Maintenance. ISO , Software Engineering – Software Life Cycle Processes – Maintenance, describes in greater detail management of the software maintenance.
|Country:||Papua New Guinea|
|Published (Last):||22 February 2013|
|PDF File Size:||3.55 Mb|
|ePub File Size:||18.29 Mb|
|Price:||Free* [*Free Regsitration Required]|
Adopted From Standards Australia Standard: Unsourced material may be challenged and removed.
Logon details will isoo provided by email. ISO provides guidance that applies to planning, execution and control, review and evaluation, and closure of the software maintenance process. Interaction design Social computing Ubiquitous computing Visualization Accessibility.
And this is the main cause of any problem during software evolution and maintenance. It provides the framework, precise terminology, and processes to allow the consistent application of technology tools, techniques, and methods to software maintenance.
The standard was written primarily for maintainers of software and additionally for those responsible for development and 1764 assurance. Lehman demonstrated that systems continue to evolve over time. The key software maintenance issues are both managerial and technical. ISO standards by standard number.
Because change is inevitable, mechanisms must be developed for evaluation, controlling and making modifications. Many subsequent studies suggest a similar magnitude of the problem. As they evolve, they grow more complex unless some action such as code refactoring is taken to reduce the complexity.
Standard: IEEE Std 14764-2006 – Software Engineering & Software Life Cycle Processes & Maintenance
Supervised learning Unsupervised learning Reinforcement learning Multi-task learning Cross-validation. P P P P P In 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.
147764 contents of this Web Site are copyright of Project Performance Australia Pty Ltd and are made available for your information only, on the condition that you do not incorporate their contents, in whole or in part, into any isk material of any nature without permission in writing from Project Performance Australia Pty Ltd. Assessing Evidence from Change Management Data. This article has an unclear citation style.
ISO for Software Maintenance. Key management issues are: Maintenance may span for 20 years, [ citation needed ] whereas development may be 1—2 years.
The references used may be made clearer with a different or consistent style of citation and footnoting. Please help improve it or discuss these issues on the talk page.
Access the SE Goldmine A username and password is required for access to the resources. We apologise for being unable to respond to access requests that are declined. Artificial intelligence Computer science Electrical and electronics engineering. A new decision should be addressed for the developing of every new system feature and its quality objectives.
The purpose is to preserve the value of software over the time. There are a number of processes, activities and practices that are unique to maintainers, for example:.
ISO/IEC – Software Engineering — Software Life Cycle Processes — Maintenance
A very common situation which often degrades performance is lack of suitable maintenance tools, such as defect tracking software, change management software, and test library software. Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.
Archived from the original PDF on Burt Swanson, The dimensions of maintenance. ISO defines the 147664 and tasks of software maintenance, and provides maintenance planning requirements. Note also that some academic institutions [ who?
It may also be used by acquirers and users of systems containing software who provide inputs to the maintenance plan. Computer science Computer engineering Project management Risk management Systems engineering. Views Read Edit View history. Key technical issues are: Below describe some of the factors and the range of impact on software maintenance. It does not address the operation of software and operational functions, e. An integral part of software is the maintenance one, which requires an accurate maintenance plan to be prepared during the software development.
Swanson initially identified three categories of maintenance: Model of computation Formal language Automata theory Computational complexity theory 1476 Semantics. Studies show that contribution of end user is crucial during the new requirement data gathering and analysis. It should specify how users will request modifications or report problems.