The impacts of project activity scopes and knowndege transfer difficulties on the software engineering project's Performance

• Main Authors: Chih-Chieh Wang, 王致傑
• Other Authors: Sun-Jen Huang
• Format: Others
• Language: zh-TW
• Published: 2009
• Online Access: http://ndltd.ncl.edu.tw/handle/11323915968382736048

碩士 === 國立臺灣科技大學 === 資訊管理系 === 97 === In order to develop Software engineering projects core ability, or to work in coordination with specialized fields, we may divide the continuous software developing process into separated groups of works. These works may be shared between projects inside an organization, or between several organizations. In this kind of situation, software engineering projects need to face segmented or incomplete activity scopes. It may make uncertainty arise in software engineering projects, and the most serious factor of uncertainty is the knowledge transfer difficulty brought from the segmented activity scopes. It makes project groups spent more energy on dealing with the extra communication, coordination and the trustfulness of sharing information. This study focus on software engineering activity scope and factors of knowledge transfer impact, and then discuss how they affect software projects performance. This study use the ISBSG software engineering dataset, and use SEM ( Structural Equation Modeling) methodology to construct the model to verify the relationship among software engineering activity scopes, knowledge transfer impact factors and project performance. The major finding of this study includes: software engineering activity scopes has a positive effect on project performance. This study uses interaction quality as mediator, and finds that the complexity of the project decreases the quality of interaction. In the other hand, the interaction quality enhances the software engineering project performance and productivity. According to these findings, this study suggests software projects should follow the software engineering process, and keep it complete and continuous. Avoid skipping any engineering stages. Members of the project also need to control the project complexity, and make the number of system application types and associated user business units reasonable and controllable.