| || |
Can anybody say me what the letters QA means in QACenter, QARun, etc...
Another questions, are all QA products from Compuware?
Quality Assurance - but that's only a guess. It's a standard industry term.
That said, Compuware does not make the only quality assurance software in the world.
I'm not sure if they are the only ones who use QA as the beginning of their product's names.
Mercury, Segue, Rational and others make QA software as well.
A part Quality
A part Assurance
QA- Quality Assurance
Quality assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures.
·Processes include all of the activities involved in designing, developing, enhancing, and maintaining software.
·Products include the software, associated data, its documentation, and all supporting and reporting paperwork.
QA includes the process of assuring that standards and procedures are established and are followed throughout the software development lifecycle.
·Standards are the established criteria to which the software products are compared.
·Procedures are the established criteria to which the development and control processes are compared.
Compliance with established requirements, standards, and procedures is evaluated through process monitoring, product evaluation, audits, and testing.
The three mutually supportive activities involved in the software development lifecycle are management, engineering, and quality assurance.
·Software management is the set of activities involved in planning, controlling, and directing the software project.
·Software engineering is the set of activities that analyzes requirements, develops designs, writes code, and structures databases.
Quality Assurance ensures that the management and engineering efforts result in a product that meets all of its requirements
GOALS OF QUALITY ASSURANCE
Software development, like any complex development activity, is a process full of risks. The risks are both technical and programmatic; that is, risks that the software or website will not perform as intended or will be too difficult to operate/browse, modify, or maintain are technical risks, whereas risks that the project will overrun cost or schedule are programmatic risks.
The goal of QA is to reduce these risks. For example, coding standards are established to ensure the delivery of quality code. If no standards are set, there exists a risk that the code will not meet the usability requirements, and that the code will need to be reworked. If standards are set but there is no explicit process for assuring that all code meets the standards, then there is a risk that the code base will not meet the standards. Similarly, the lack of an Error Management and Defect Life Cycle workflow increases the risk that problems in the software will be forgotten and not corrected, or that important problems will not get priority attention.
The QA process is mandatory in a software development cycle to reduce these risks, and to assure quality in both the workflow and the final product. To have no QA activity is to increase the risk that unacceptable code will be released.
THE DEPARTMENT OF QUALITY ASSURANCE
QA is an activity that should be organizationally independent of the producing organizations. QA functions are best performed in an discrete QA testing environment by organizational entities that are separate from the ones doing engineering or management activities. Administratively, the QA organization should report to top corporate management and interface with the project manager.
The reason for this separation of function is that the QA organization is the arm of management that assures that standards are met and that procedures are followed. If QA is not independent of the development activity, clear and impartial assessment will be difficult. Additionally, organizational independence helps ensure that testing will be requirements-driven and not influenced by the design or coding details.
Staff devoted purely to QA activities is usually small compared to the project staff, but it is important to have people with specific QA responsibilities. Too often, the axiom “quality is everybody's business” becomes “quality is nobody's business” if specific QA responsibilities are not assigned.
QA is an essential part of the development and maintenance of software. It is part of the triad of activities, along with software management and software engineering, that determines the success of any software development, enhancement, or maintenance activity.
Hope this Helps.
Thank you very much.
Those explainations have been very useful to me.
Do you know where I could find a book, a document or a website specialised on this subject??