We can break the traditional, or closed-source, software engineering quality model into two broad areas: quality assurance and quality control. Quality assurance occurs throughout the software organization and focuses on process and procedure, learning from mistakes, and ensuring good management practice. Quality control is the process of verification and validation, usually within a structured testing process, using highlevel plans and detailed test scripts to document and manage the testing process. OSS development casts aside traditional notions of quality assurance and control, and a review of the body of research shows a wide range of deviations. Table 1 demonstrates this by com
paring quality management in open source and closed-source software development. OSS development must also manage a geographically distributed team, requiring focus on coordination tasks. Yet OSS development seems to eschew best practices without software quality suffering. Indeed, an extensive study of 100 open source applications found that structural code quality was higher than expected and comparable with commercially developed software.1 The body of research demonstrates that OSS development does retain some of the underlying best-practice tasks from closed-source development—central management, code ownership, task ownership, planning and strategy, system testing, leadership, and decision making—but these tasks are executed differently. Further analysis of the differences shows that many of OSS development’s deviations are procedural—such as risk assessment, measurable goals and milestones, early defect discovery, quality metrics, and planning and scheduling— that help meet that key traditional software de
feature Achieving Quality in Open Source Software The open source software community has published a substantial body of research on OSS quality. Focusing on this peer-reviewed body of work lets us draw conclusions from empirical data about how to achieve OSS quality, rather than relying on the large volume of evangelical opinion that has historically dominated this field. This body of published research has become much more critical and objective in its efforts to understand OSS development, and a consensus has emerged on the open source Mark Aberdour, opensourcetesting.org Reviewing objective studies of open source software quality can help us better understand how to achieve software quality in both open and closed-source development.
velopment goal, the release deadline. As concrete release deadlines are less of an issue in OSS development, it might be that these deviations don’t negatively impact software quality. Current research excludes this area, but it would make an interesting area for further study.
เราสามารถแบ่งแบบจำลองคุณภาพวิศวกรรมซอฟต์แวร์แบบดั้งเดิม หรือปิด แหล่ง พื้นที่กว้างสอง: การประกันคุณภาพและควบคุมคุณภาพได้ การประกันคุณภาพเกิดขึ้นทั่วทั้งองค์กรซอฟต์แวร์ และเน้นกระบวนการและขั้นตอน เรียนรู้จากความผิดพลาด และฝึกบริหารดีเด่น การควบคุมคุณภาพเป็นกระบวนการตรวจสอบและตรวจสอบ ปกติภายในโครงสร้างทดสอบกระบวนการ การใช้แผน highlevel และสคริปต์ทดสอบรายละเอียดเอกสาร และจัดการกระบวนการทดสอบ OSS พัฒนา casts แบบดั้งเดิมไว้ความเข้าใจการประกันคุณภาพ และควบคุม และทบทวนเนื้อหาของงานวิจัยแสดงความแตกต่างหลากหลาย ตารางที่ 1 แสดงให้เห็นนี้ โดย comparing quality management in open source and closed-source software development. OSS development must also manage a geographically distributed team, requiring focus on coordination tasks. Yet OSS development seems to eschew best practices without software quality suffering. Indeed, an extensive study of 100 open source applications found that structural code quality was higher than expected and comparable with commercially developed software.1 The body of research demonstrates that OSS development does retain some of the underlying best-practice tasks from closed-source development—central management, code ownership, task ownership, planning and strategy, system testing, leadership, and decision making—but these tasks are executed differently. Further analysis of the differences shows that many of OSS development’s deviations are procedural—such as risk assessment, measurable goals and milestones, early defect discovery, quality metrics, and planning and scheduling— that help meet that key traditional software defeature Achieving Quality in Open Source Software The open source software community has published a substantial body of research on OSS quality. Focusing on this peer-reviewed body of work lets us draw conclusions from empirical data about how to achieve OSS quality, rather than relying on the large volume of evangelical opinion that has historically dominated this field. This body of published research has become much more critical and objective in its efforts to understand OSS development, and a consensus has emerged on the open source Mark Aberdour, opensourcetesting.org Reviewing objective studies of open source software quality can help us better understand how to achieve software quality in both open and closed-source development.velopment goal, the release deadline. As concrete release deadlines are less of an issue in OSS development, it might be that these deviations don’t negatively impact software quality. Current research excludes this area, but it would make an interesting area for further study.
การแปล กรุณารอสักครู่..