Aseguradores de la calidad
The Primary project management issues for software projects are meeting deadlines and development costs. However, increasing the pressure to meet deadlines and reducing costs may cause product quality to suffer. When a project is behind schedule, features May Be dropped, and [...] testing times may reduce product quality.
It is necessary to find a new equation for the development of software. It shouldn't simply be "software product = time within cost". as it should be "software product = quality time within cost." For that, the conviction must be individual and management to consider calidadcomo a final goal, along with meeting deadlines and costs. As mentions, quality corresponds to a set of attributes to meet the desarrollador. Typically, those attributes are defined in the form of a standard, it should be fulfilled.
Activities and goals
Here are the activities and goals to be met by quality assurance.
Actividades |
Metas |
|---|---|
reviewing requirements documents and software guide | | make sure that the Requirements Specification is correct and complete unarepresentación expectations delcliente, and that is clear enough for the team dedesarrollo, especially for designers.|- |
management plan review |
Methodology
From the quality assurance activities, the most important is the departicipar in formal technical reviews (RTF). If these revisions are bienconducidas are the most effective way to find, disclose and correct mistakes and find cheap mientrasaún arreglarlos.el standard that includes revisions in phases. Not However, RTFs are especially required in the architectural design phase.This is because that design activities introduce between 50 and 65% of all errors during the development process.
It has been shown to discover RTFs about 75% of design errors.
The objectives of the RTFs are: 1. uncover errors in function, logic and implementation in any of the representations of the software 2. verify that the software under review meets the requirements 3. ensure that the software has been represented by the standards in use, 4. software is developed to achieve evenly and 5. make the project more manageable.
An RTF is a meeting between three to five people. Each has made preparation in advance of no more than two hours, and its duration should not either exceed two hours. The RTF is focused on a small software product, such as a portion of the requirements, the detailed design of a module, or the list of source code of a module.
Participants in a RTF are the producer (the person who developed the product review), in charge of the review evaluates the product generates copies of material, and distributes it to two or three reviewers to prepare beforehand. One of the reviewers takes on the role of documenting the most important aspects that appeared during the review.
At the end of the review, participants must decide whether to: 1. accept the product without subsequent amendment 2. reject the product due to serious errors, or 3. accept product with minor errors to be corrected, but not required further review.