Although there is indication of only a partial relationship between component size and user satisfaction, these findings could be still used when deciding the contents of an open source release. Release configuration is a frequent activity in open source development and might take place even daily (Raymond, 2000). When more than one candidate exists for a new version of an application,our analysis suggests that,all things being equal,the version characterized by the smaller component size could be selected for participation in the new release. Intuitively, less component size is the result of better design and, consequently, of lower defect density and better user satisfaction. In addition, smaller component size should facilitate program maintenance and evolution. Given that this approach is easily automated, we believe that it can be easily integrated in the open source process.
Although there is indication of only a partial relationship between component size and user satisfaction, these findings could be still used when deciding the contents of an open source release. Release configuration is a frequent activity in open source development and might take place even daily (Raymond, 2000). When more than one candidate exists for a new version of an application,our analysis suggests that,all things being equal,the version characterized by the smaller component size could be selected for participation in the new release. Intuitively, less component size is the result of better design and, consequently, of lower defect density and better user satisfaction. In addition, smaller component size should facilitate program maintenance and evolution. Given that this approach is easily automated, we believe that it can be easily integrated in the open source process.
การแปล กรุณารอสักครู่..