• Journal of the Korea Society of Computer and Information
• /
• v.17 no.8
• /
• pp.123-133
• /
• 2012

Recently, as IT convergence has seen rapid growth the role and scope of software has been extended. many software companies are trying to improve the software quality and project outcome using software process improvement approach to cope with increasing software demands and software quality. Although software process improvement is difficult task which requires a lot of cost and time, there is still insufficient objective evidence on business benefits by its deployment. The purpose of this study is to analyze the relationship between software process improvement and software project productivity. That is, we investigated whether there is difference in software development productivity depends on software engineering level using statistical methods. We found that the software development productivity is different across the software engineering levels and the higher software engineering level can lead to improved software development productivity.

• Journal of Information Technology Services
• /
• v.4 no.1
• /
• pp.41-55
• /
• 2005

In this research, we've studied to the software productivity and quality measures and metrics for raise UP the advanced software industry. For the purpose, we've studied relative research and reorganized 74 metrics. Reorganized 74 metrics were developed considering scalability, measurement and acquisition possibility and verified by software development experts. Finally, we've conducted a survey on the high measurement possibility metrics. Data were gathered from 20 software development project. It was found from the result need more efforts for the software development productivity improvement for advanced software industry.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 1998.11a
• /
• pp.43-50
• /
• 1998

The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.

• Journal of Information Technology Services
• /
• v.13 no.2
• /
• pp.195-217
• /
• 2014

This paper has explored when implementing SW development project of the IT service corporations, what factors affect its productivity in SW development methodology. The importance of the AHP analysis surveyed from the experts in IT service companies and related committee, was shown in the order of the following processes : 1) Deployment process 2) Management process 3) Establishment process. It is measured the methodology levels of establishment, deployment and management in each project using the survey results collected from project execution members and analyzed the productivity of projects that have been executed within 2 years. Using project methodology level, productivity correlation analysis, and regression analysis, this study confirms that the methodology deployment level brings positive effects significantly to SW development productivity. The significance of this study would be not only to research and analyze SW development productivity using the real project execution data but also to underline the necessities and the importance of steady research, deployment and support for SW development productivity improvement.

• Journal of KIISE:Software and Applications
• /
• v.31 no.1
• /
• pp.20-28
• /
• 2004

Estimation of software project cost, effort, and duration in the early stage of software development cycle is a difficult and key problem in software engineering. Most of development effort and duration estimation models presented by regression model of simple relation function point vs. effort and effort vs. duration instead of considering developer's productivity. But different project have need for different effort according to developer's productivity if the projects are same software size. Also, different duration takes according to developer's productivity if the projects require the same effort. Therefore, models that take into account of productivity have a limited application in actual development project. This paper presents models that can be estimate the duration according to productivity in order to compensate a shortcoming of the previous models. Propose model that could presume development period by various methods based on productivity and compared models' performance. As a result of performance comparison, an estimating model of development period from software size got simple and most good result. The model gives decision-making information of development duration to project management in the early stage of software life cycle.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.3
• /
• pp.1-7
• /
• 2008

This paper proposes an object-oriented software development guidance and an evaluation index for the productivity related to EJB(Enterprise JavaBeans). EJB is a known successful standard model for LSDO(Large Size Distributed Object). However, there is no comparison research about the performance of EJB 2.0 and 3.0 with same identical platform. Quantitative analysis is supported as a part of LOC(Line Of Code) analysis. There is a limit to develop the updated software with no the specific evaluating index for the productivity of software. This work proposes an specific index for evaluating the productivity of new version EJB on a platform. Base on the result, the specific guidance of the developing software is obtained.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.179-188
• /
• 2006

MDD/MDA which recently raising its head is technology that increase software development productivity through automatic transformation form higer abstract model into lower abstract model, or from model to code. This paper analyzes the effect on productivity by measuring Function Point per MM(man-month) in a software development project which performed in CBD methodology, and introduce the method of applying MDD/MDA technology in the project.

• Journal of Digital Convergence
• /
• v.8 no.2
• /
• pp.1-12
• /
• 2010

No one can deny that information technology has enormously contributed to the recent economic growth of Korea. Software serves as an essential part of most products and services today. However, economic treatments and social status of software technicians, who are the key players and core elements of the software industry, are in a very unsatisfactory situation. Despite this circumstance, discussion or study on the productivity of software people and approaches to raise value of technical manpower in software industry is scarce. The purpose of this study is to suggest a policy program to uplift the value of technical manpower in the software industry. To achieve this purpose, this paper will examine the present status of software manpower, analyze the productivity of software technicians, and suggest policy programs to improve the value of technical manpower in the software field.

• IE interfaces
• /
• v.17 no.spc
• /
• pp.122-130
• /
• 2004

Since the cost of software maintenance occupies about 50~75% in a general successful organization, the software maintenance plays an important role in software life cycle. In particular, if the managed system needs to be operated in a long term or the system is very large and complex, then the maintenance is especially more important. Software maintenance is defined as software modification activities after customer delivery, such as improvement of performance or functionality, error correction, adaptation to environmental changes, etc. In this paper, software cost estimation models are proposed, that is based on productivity of manpower in maintenance projects. In order to do this, the activities of maintenance are classified into function change, non-function change, user support and application operation. The proposed models are constructed and verified based on the real size and cost information of projects in the real world. The approach in this paper is to discriminate the heterogeneous activities in maintenance projects, and then to calculate the respective cost of each discriminated activity. By using the proposed models, the total cost of maintenance project is summed from the costs of four activities. In addition the number of conflicts between owner and order receiver about the amount of cost will be reduced and the reasonable cost estimation system will be established.

• Journal of Digital Convergence
• /
• v.8 no.1
• /
• pp.93-107
• /
• 2010

Performance of software development is measured by two major criteria - roductivity and quality. Although the criteria is empirically tested in software engineering research, they often present with a limited way under consideration of a few factors or contexts for developers to focus on the either productivity facets or quality facets. Analyzing data on software development performance collected over a 13-year period from 20 countries, we investigated how major software development factors - development type, development platform, development technique, language type, DBMS, methodology, methodology acquisition, CASE,, summary of work effort, resource level, max team size, affect the performance of software development. The results suggest that productivity and quality of software development are affected by different factors and context: function points, line of code, extreme defects, major defects, or minor defects. This research provides the empirical evidence that the two performance criteria require for software developer to have careful attention to find the optimal balance between the two performance criteria.