The following normative documents contain provisions which, through reference in this text, constitute provisions of this part of ISO/IEC/IEEE For dated. ISO/IEC IEEE Std Software Engineering — Software Life. Cycle Processes — Maintenance. Fabio Carollo. Institute of Electrical and. ISO/IEC. IEEE. Std Second edition. Software Engineering — Software Life. Cycle Processes — Maintenance.
|Published (Last):||11 June 2005|
|PDF File Size:||10.27 Mb|
|ePub File Size:||18.21 Mb|
|Price:||Free* [*Free Regsitration Required]|
You are authorised to print the contents provided that this copyright notice is included. They categorized maintenance activities into four classes:. There are a number of processes, activities and practices that are unique to maintainers, for example:.
Burt Swanson, The dimensions of maintenance. Natural language processing Knowledge representation and reasoning Computer vision Automated planning and scheduling Search methodology Control method Philosophy of artificial intelligence Distributed artificial intelligence. 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 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.
Interpreter Middleware Virtual machine Operating system Software quality. 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.
Because change is inevitable, mechanisms must be developed for evaluation, controlling and making modifications. Views Read Edit View history. Interaction design Social computing Ubiquitous computing Visualization Accessibility. Best practices for managing your software investment. Major fields of computer science. Discrete mathematics Probability Statistics Mathematical software Information theory Mathematical analysis Numerical analysis.
An integral part of software is the maintenance one, which requires an accurate maintenance plan to be prepared during the software development. Most access requests are approved. P P P P P Over a period of twenty years, his research led to the formulation of Lehman’s Laws Lehman Retrieved 5 November If you are not a client of PPI or CTI, limited access which permits download access to many of these resources may be available on an approved-registration basis.
Software maintenance – Wikipedia
The 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 other material of any nature without permission in writing from Project Performance Australia Pty Ltd. Algorithm design Analysis of algorithms Algorithmic efficiency Randomized algorithm Computational geometry.
Computer architecture Embedded system Real-time computing Dependability. Software maintenance and evolution of systems was first addressed by Meir M. 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. The purpose is to preserve the value of software over the time. Swanson initially identified three categories of maintenance: 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.
Many subsequent studies suggest a similar magnitude of the problem. Not only are error-prone modules troublesome, but many other factors can degrade performance too. We apologise for being unable to respond to access requests that are declined. Artificial intelligence Computer science Electrical and electronics engineering.
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.
A common perception of maintenance is that it merely involves fixing defects. 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.
Access the SE Goldmine A username and password is required for access to the resources.
If you are a client of PPI or subsidiary company CTI and wish to obtain a username and 14674, please use the email contact form. This page was last edited on 22 Octoberat Archived from the original PDF on Learn how and when to remove these template messages.
Software development process Requirements analysis Software design Software construction Software deployment Software maintenance Programming team Open-source model. ISO standards by standard number. Lehman demonstrated that systems continue to evolve over time. January Learn how and when to remove this template message.
The management of ieeee and cohesion of the software. Unsourced material may be challenged and removed. Key technical issues are: Concurrent computing Parallel computing Distributed computing Multithreading Multiprocessing. The value can be enhanced by expanding the customer base, meeting additional requirements, becoming easier to use, more efficient and employing newer technology.
And this is the main cause of any problem during software evolution and maintenance. As they evolve, they grow more complex unless some action such as code refactoring is taken to reduce the ueee.