ISO = 'International Organization for Standardization' - The ISO 9001:2000 standard (which replaces the previous standard of 1994) concerns quality systems that are assessed by outside auditors, and it applies to many kinds of production and manufacturing organizations, not just software. It covers documentation, design, development, production, testing, installation, servicing, and other processes. The full set of standards consists of: (a) Q9001-2000 - Quality Management Systems: Requirements; (b) Q9000-2000 - Quality Management Systems: Fundamentals and Vocabulary; (c) Q9004-2000 - Quality Management Systems: Guidelines for Performance Improvements. To be ISO 9001 certified, a third-party auditor assesses an organization, and certification is typically good for about 3 years, after which a complete reassessment is required. Note that ISO certification does not necessarily indicate quality products - it indicates only that documented processes are followed. Also see http://www.iso.ch/ for the latest information. In the U.S. the standards can be purchased via the ASQ web site athttp://e-standards.asq.org/ IEEE | IEEE = 'Institute of Electrical and Electronics Engineers' - among other things, creates standards such as'IEEE Standard for Software Test Documentation' (IEEE/ANSI Standard 829), 'IEEE Standard of Software Unit Testing (IEEE/ANSI Standard 1008), 'IEEE Standard for Software Quality Assurance Plans' (IEEE/ANSI Standard 730), and others § Process or standard-compliant You might adopt IEEE 829 standard for your testing
|
The ISO 9126 Quality standard is divided into four parts which addresses, respectively, the following subjects: –Quality model –Internal metrics –External metrics –Quality in use metrics ISO/IEC 14764 this international standard describes the 6 software maintenance processes as: | | | | •The implementation process contains software preparation and transition activities, such as the conception and creation of the maintenance plan, the preparation for handling problems identified during development, and the follow-up on product configuration management. | | •The problem and modification analysis process, which is executed once the application has become the responsibility of the maintenance group. The maintenance programmer must analyze each request, confirm it (by reproducing the situation) and check its validity, investigate it and propose a solution, document the request and the solution proposal, and, finally, obtain all the required authorizations to apply the modifications. | | •The process considering the implementation of the modification itself. | | •The process acceptance of the modification, by checking it with the individual who submitted the request in order to make sure the solution provided a solution. | | •The migration process (platform. migration, for example) is exceptional, and is not part of daily maintenance tasks. If the software must be ported to another platform. without any change in functionality, this process will be used and a maintenance project team is likely to be assigned to this task. | | •Finally, the last maintenance process, also an event which does not occur on a daily basis, is the retirement of a piece of software |
Types of Maintenance Testing – Corrective maintenance is maintenance performed to correct faults in hardware or software [IEEE 1990] • Determining how the existing system may be affected by changes is called impact analysis, and is used to help decide how much regression testing to do. – Adaptive maintenance is software maintenance performed to make a computer program usable in a changed environment [IEEE 1990]. – Perfective maintenance is software maintenance performed to improve the performance, maintainability, or other attributes of a computer program. [IEEE 1990] – Preventative maintenance is maintenance preformed for the purpose of preventing problems before they occur [IEEE 1990] |
