http://chineseinput.net/에서 pinyin(병음)방식으로 중국어를 변환할 수 있습니다.
변환된 중국어를 복사하여 사용하시면 됩니다.
A Novel Effort Estimation Approach for Requirement Changes during Software Development Phase
Sufyan Basri,Nazri Kama,Roslina Ibrahim 보안공학연구지원센터 2015 International Journal of Software Engineering and Vol.9 No.1
Managing software changes and achieving an effective change acceptance decision is one of the crucial factors in ensuring the software project success. Accepting too many changes will cause expense and delay and rejecting the changes may cause customer dissatisfaction. One of the inputs that help in achieving an effective change acceptance decision is by having reliable estimation on the change effort. From software development perspective, the estimation has to take into account the inconsistent states of software artifacts across project lifecycle i.e., fully developed or partially developed. These inconsistent states require different ways of estimation such as the fully developed artifacts may have different calculation compared to the partially developed artifacts. Many change effort estimation approaches have been developed and one of them is using impact analysis. One main challenge of this technique from software development perspective is that this technique is specifically used for software maintenance phase in which all software artifacts have been completely developed. This research introduces a new change effort estimation approach that is able to use different estimation techniques for different states of software artifacts. The outcome of this research is a new change effort estimation approach for software development phase using the extended version of the static and dynamic analysis techniques from our previous works.
A Change Impact Analysis Tool for Software Development Phase
Sufyan Basri,Nazri Kama,Roslina Ibrahim,Saiful Adli Ismail 보안공학연구지원센터 2015 International Journal of Software Engineering and Vol.9 No.9
Accepting too many software change requests could contribute to expense and delay in project delivery. On the other hand rejecting the changes may increase customer dissatisfaction. Software project management might use a reliable estimation on potential impacted artifacts to decide whether to accept or reject the changes. In software development phase, an assumption that all classes in the class artifact are completely developed is impractical compared to software maintenance phase. This is due to some classes in the class artifact are still under development or partially developed. This paper extends our previous works on developing an impact analysis approach for the software development phase in automating the approach which we call it CIAT (Change Impact Analysis Tool). The significant achievements of the tool are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the accuracy over current impact analysis results.