| 词条 | Software quality management |
| 释义 |
Quality management activitiesSoftware quality management activities are generally split up into three core components: quality assurance, quality planning, and quality control.[1][2] Some like software engineer and author Ian Sommerville don't use the term "quality control" (as quality control is often viewed as more a manufacturing term than a software development term), rather, linking its associated concepts with the concept of quality assurance.[3] However, the three core components otherwise remain the same. Quality assuranceBy setting up an organized and logical set of organizational processes and deciding on that software development standards — based on industry best practices — that should be paired with those organizational processes, software developers stand a better chance of producing higher quality software. However, linking quality attributes such as "maintanability" and "reliability" to processes is more difficult in software development due to its creative design elements versus the mechanical processes of manufacturing.[1][2][3] Additionally, "process standardization can sometimes stifle creativity, which leads to poorer rather than better quality software."[3] This stage can include:
Quality planningQuality planning works at a more granular, project-based level, defining the quality attributes to be associated with the output of the project and how those attributes should be assessed. Additionally, any existing organizational standards may also be assigned to the project at this phase. Attributes such as "robustness," "accessibility," and "modularity" may be assigned to the software development project.[1][2] While this may be a more formalized, integral process, those using a more agile method of quality management may place less emphasis on strict planning structures.[3] The quality plan may also address intended market, critical release dates, quality goals, expected risks, and risk management policy.[2][3] Quality controlThe quality control team tests and reviews software at its various stages to ensure quality assurance processes and standards at both the organizational and project level are being followed.[1][2] (Some like Sommerville link these responsibilities to quality assurance rather than call it quality control.[3]) These checks are optimally separate from the development team so as to lend more of an objective view of the product to be tested.[2][3] However, project managers on the development side must also assist, helping to promote as part of this phase a "culture that provides support without blame when errors are discovered."[3] In software development firms implementing a more agile quality approach, these activities may be less formal; however, a switch to agile methods from a more formal quality management structure may create problems if management procedures aren't appropriately adapted.[3] Activities include:
Software quality and the software lifecycleThe measurement of software quality is different from manufacturing; tolerances aren't applicable (at least in the same way), and objective conclusions concerning if software meets specifications are difficult if not impossible to achieve.[3] However, software's quality and fit-for-purpose status can still be realized in various ways depending on the organization and type of realized project.[4] This done through the support of the entire software development lifecycle, meaning:
Links to IT methodsSoftware quality management is a topic strongly linked with various project management, development, and IT operation methods, including:
Associations and organizations
See also
References{{FOLDOC}}1. ^1 2 3 4 5 {{cite web |url=http://www.tankonyvtar.hu/en/tartalom/tamop412A/2011-0042_szoftverfejlesztesi_folyamatok_angol/2011-0042_szoftverfejlesztesi_folyamatok_angol.pdf |format=PDF |title=Software quality management |work=Software Development Processes and Software Quality Assurance |author=Zsolt, U. |publisher=University of Pannonia |pages=117–121 |date=February 2014 |accessdate=7 December 2017}} 2. ^1 2 3 4 5 6 7 {{cite web |url=http://groups.umd.umich.edu/cis/course.des/cis376/ppt/lec14.ppt |format=PPT |title=Software Quality Management |author=Maxim, B.R. |publisher=University of Michigan - Dearborn |date=2014 |accessdate=7 December 2017}} 3. ^1 2 3 4 5 6 7 8 9 10 11 {{cite book |chapter=Chapter 24: Quality Management |title=Software Engineering |author=Sommerville, I. |publisher=Addison-Wesley |edition=9th |pages=651–680 |year=2011 |isbn=9780137035151}} 4. ^Kelemen, Z. D. (2013). Process Based Unification for Multi-Model Software Process Improvement Eindhoven: Technische Universiteit Eindhoven. {{ISBN|978-90-386-3313-8}} 5. ^OGC (Office of Government Commerce) (2009). Managing Successful Projects with PRINCE2 (2009 ed.). TSO (The Stationery Office). {{ISBN|978-0-11-331059-3}} 6. ^A Guide to the Project Management Body of Knowledge, Fourth Edition, PMI, USA, 2008 7. ^Microsoft Solution Framework - Chapter 18 Stabilization phase, Published: April 27, 2005 [https://technet.microsoft.com/en-us/library/bb463142.aspx] 8. ^{{cite web |url=https://www.istqb.org/ |title=Certifying Software Testers Worldwide |publisher=International Software Testing Qualifications Board |accessdate=7 December 2017}} 1 : Software quality |
| 随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。