Software development process is defined as a set of activities that begin with the identification of a need and concludes with the retirement of a product that satisfies the need. Software development should be guided by an explicit process, with environment and tools integrated to support this process. Process definition is a prerequisite to process improvement. Process management supports improvement of the defined process through measurement and feedback.
Current implementations of process management combine three steps: definition, control, and improvement. Process definition provides an exact description for the work to be performed. The current process is used as a baseline against which changes will be compared. Process control works to keep significant quality parameters within some predefined limits. Process improvement involves analyzing problems for root causes and working to correct them.
Product quality is seen as a result of continuously improving process quality. A process is said to be under statistical control if its future performance can be predicted within established statistical limits.The Software Engineering Institute (SEI) capability maturity model defined five levels process improvement model as shown in figure. The five stages are called maturity levels. Each represents an improvement in the software process.
The initial software process is characterized as ad hoc. Typically, the organization operates without formal procedures, cost estimates or project plans. There are few mechanisms to ensure that procedures are followed. At the repeatable level, project controls have been established over quality assurance, change control, cost, and schedule. This discipline enables earlier successes to be repeated.
The defined software process, for both management and engineering activities, is documented, standardized, and integrated across the organization. The process is visible; that is, it can be examined and improvements suggested. Achieving the fourth, or managed level, requires that measures of software process and product quality be collected so that process effectiveness can be determined quantitatively.
Current implementations of process management combine three steps: definition, control, and improvement. Process definition provides an exact description for the work to be performed. The current process is used as a baseline against which changes will be compared. Process control works to keep significant quality parameters within some predefined limits. Process improvement involves analyzing problems for root causes and working to correct them.
Product quality is seen as a result of continuously improving process quality. A process is said to be under statistical control if its future performance can be predicted within established statistical limits.The Software Engineering Institute (SEI) capability maturity model defined five levels process improvement model as shown in figure. The five stages are called maturity levels. Each represents an improvement in the software process.
The initial software process is characterized as ad hoc. Typically, the organization operates without formal procedures, cost estimates or project plans. There are few mechanisms to ensure that procedures are followed. At the repeatable level, project controls have been established over quality assurance, change control, cost, and schedule. This discipline enables earlier successes to be repeated.
The defined software process, for both management and engineering activities, is documented, standardized, and integrated across the organization. The process is visible; that is, it can be examined and improvements suggested. Achieving the fourth, or managed level, requires that measures of software process and product quality be collected so that process effectiveness can be determined quantitatively.
0 Komentar untuk "PRODUCT QUALITY THE RESULTS OF DEVELOPMENT EFFORTS"