Contribute/Quality Team: Difference between revisions

Revision as of 10:36, 11 May 2013

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:

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

@@ Line 1: / Line 1: @@
 [[Category:Quality]]
+[[Category:Testing]]
+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 [http://en.wikipedia.org/wiki/CISQ 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 ==
+*[http://community.kde.org/Getinvolved/Testing Software Testing]
+*[http://techbase.kde.org/Contribute#User_Interface Usability]
+*[http://community.kde.org/Getinvolved/accessibility Acessibility]
+*[http://community.kde.org/Getinvolved/documentation Documentation]
+*[http://community.kde.org/Getinvolved/translation Translation]
+*[http://techbase.kde.org/Contribute/Bugsquad Bug handling]
+*[http://techbase.kde.org/Projects/Release_Team KDE releases]
+=== Archive ===
 For a more in-depth view on Software Quality, see [[Contribute/Quality Team/Essay]]