3G Software Development Quality Assessment Based On Rayleigh Model And Gompertz Model

Software engineering has entered quality era since1990s. Telecomoperators also pay attention to quality. Some telecom operators founded QuESTforum in1997. They setup TL9000Quality Management System, which hasbeen adopted by most telecom operators and vendors. A telecom vendor meetstelecom operator’s requirements and beats other competitors only if it delivershigh quality products. So study in quality management model of softwaredevelopment project is important in theory and practice.Many documents about software quality management model and workexperience has been studied. An integration solution to use “RayleighModel”、“Gompertz Model”and “four quadrant analysis model”has beensubmitted.The object is software development process of TD-SCDMA RAN(NodeBSW、RNC SW and OMC). The project’s duration from kickoff to6months afterGA is traced,3contents are studied.First, the thesis validates the defect distribution conforms to Rayleighcurve, and predicts products’ potential defects in system test phase and fieldbased on Rayleigh model.Second, the thesis uses four quadrant analysis model to evaluate thesufficiency of review effort and validity of defect data of document reviewphase in Rayleigh model. Third, the thesis uses Gompertz model to predict products’ potential defects,and estimate the date until which the software products can be delivered.Finally, field errors of6months after GA are collected. The error numbersare compared with which of predicted defect with Rayleigh model andGompertz model. The validity difference of Rayleigh model and Gompertzmodel in defect estimation is analyzed. The scene in which Rayleigh model andGompertz model apply is also analyzed. The analysis methods of all3qualitymanagement models are summarized.The project’s software development method is CMM, which has longduration. Effectiveness of Rayleigh Model and Gompertz Model depends onrequirement stability. However, change request is more and more in project.Some agile development methods(XP, Scrum, etc.) are popular gradually. Agiledevelopment methods are not afraid of changes, instead, they hail changes andaccept changes. Are agile development methods suitable for big projects? Isthere any quality management model of agile methods to guarantee productquality and reduce development duration? The topic is to be further studied andexperimented.