IEEE 1219-1998 pdf download IEEE Standard for Software Maintenance
1. Overview
1.1 Scope
This standard describes an iterative process for managing and executing software maintenance activities.Use of this standard is not restricted by size, complexity, criticality, or application of the software product.This standard uses the process model, depicted in Table 2. to discuss and depict each phase of softwaremaintenance. The criteria established apply to both the planning of maintenance for software while underdevelopient, as well as the planning and execution of sotware maintenance actiyities for existing softwareproducts. Ideally. maintenance planning should begin during the stage of planning for software development(see A.3 for guidance).
This standard prescribes requirements for process, control, and management of the planning, execution, anddocumentation of software maintenance activities. In totality, the requirements constitute a minimal set ofcriteria that are necessary and sufficient conditions for conformance to this standard. Users of this standardmay incorporate other items by reference or as text to eet their specific needs.
The basic process model includes input, process, output, and control for software maintenance. Metrics)measures captured for maintenance should enable the manager to manage the process and the implementorto implement the process (see Table 3). This standard does not presuppose the use of any particular development model (e.g., waterfall, spiral, etc.)
This standard provides additional software maintenance guidance on associated topics in Annex A and toolstechnology assistance in Annex B. Maintenance plan guidelines are provided in Annex C and guidelines forcompliance with IEEE/EIA 12207.1-1997 are provided in Annex D
1.2 Terminology
The words shall and must identify the mandatory (essential) material within this standard. The words shouldand may identify optional (conditional) material The terminology in this standard is based on IEEE Std610.12-1990,’ New terms and modified definitions as applied in this standard are included in Clause 3.
The term associated processes refers to external processes that are defined in other standards; i.e., softwarequality assurance (SOA). software configuration management (SCM), and verification and validation(V&V). The term associated processes also refers to the metrics process illustrated within this standard.
2. References
Table 1 provides a cross-reference of IEEE standards that address various topics related to software maintenance. This standard shall be used in conjunction with the following publications. When the following stan-dards are superseded by an approved revision, the revision shall apply.
IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology.
IEEE Std 730-1998, IEEE Standard for Software Quality Assurance Plans.
IEEE Std 730.1-1995,IEEE Guide for Software Quality Assurance Planning.
IEEE Std 828-1998,1EEE Standard for Software Configuration Management Plans.
IEEE Std 829-1998,1EEE Standard for Software Test Documentation.“
IEEE Std 982.1-1988, IEEE Standard Dictionary of Measures to Produce Reliable Software.
IEEE Std 982.2-1988. IEEE Guide for the Use of EEE Standard Dictionary of Measures to Produce Reli-able Software.
IEEE Std 1012-1998,IEEE Standard for Software Verification and Validation.
IEEE Std 1012a-1998.IEEE Standard for Software Verification and Validation: Content Map to EEE/EIA12207.1-1997.5
IEEE Std 1028-1997IEEE Standard for Software Reviews.
IEEE Std 1042-1987 (Reaff 1993), EEE Guide to Software Configuration Management.
IEEE 1219-1998 pdf download
PS:Thank you for your support!
