Contribute/Quality Team: Difference between revisions
m (style change forexternal links) |
(→Domains in KDE where Quality Assurance is needed: Updated Bugsquad url) |
||
| Line 22: | Line 22: | ||
*[http://community.kde.org/Getinvolved/documentation Documentation] | *[http://community.kde.org/Getinvolved/documentation Documentation] | ||
*[http://community.kde.org/Getinvolved/translation Translation] | *[http://community.kde.org/Getinvolved/translation Translation] | ||
*[ | *[https://community.kde.org/Bugsquad Bug handling] | ||
*[http://techbase.kde.org/Projects/Release_Team KDE releases] | *[http://techbase.kde.org/Projects/Release_Team KDE releases] | ||
Revision as of 12:45, 16 June 2016
A software project is only complete when there also is a general Quality Assurance. A broader definition of Software Quality Assurance can be found in the following links:
- http://en.wikipedia.org/wiki/Software_quality_assurance
- http://en.wikipedia.org/wiki/Software_quality_management
Software Quality is usually defined by various standards, on being the recommendations made by CISQ:
Reliability - Efficiency - Security - Maintainability - adequate Size
A more detailed information about this can be found here: http://en.wikipedia.org/wiki/Software_quality
Domains in KDE where Quality Assurance is needed
Archive
For a more in-depth view on Software Quality, see Contribute/Quality Team/Essay