• 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 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.

• 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 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.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.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.

• 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 Digital Convergence
• /
• v.12 no.3
• /
• pp.263-268
• /
• 2014

The purpose of this study is to provide a quantitative evaluation index of object-oriented software development productivity for EJB 3.0 and EJB 3.1. A lightweight container architecture is a newly-developed architecture in order to solve demerits that N-Tiers enterprise architecture has and to support merits therein. A lightweight container architecture is not as heavy as EJB(Enterprise JavaBeans) architecture is, whereas it provides all the functionality of the EJB container. However, there have been insufficient studies on a performance evaluation of EJB 3.0 and EJB 3.1 on an identical platform. Since a quantitative analysis has been performed only with respect to a partial LoC(Line of Code) analysis, there have been insufficient objective evaluation indeces and guidelines for a new specification released. Accordingly, there has been limited evaluation of software development productivity and on new innovations in a project. Therefore, this study designed and implemented a movie reservation system in EJB 3.0 and EJB 3.1, which was based on the same development platform environment. This study then intends to provide evaluation guidelines for an objective software development productivity cl LoC(Lineand standardization thereof by development platform environment.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.6 no.3
• /
• pp.183-189
• /
• 2011

For the rapid development of embedded software, a variety of development tools have been developed. But, the embedded software developers do not use the available tools fluently and do not improve software productivity as expect because there are short of supporting utilization convenience of development tools. In this paper, we suggest a tool of building custom development environment for improving the utilization convenience of embedded software development tools. The custom development environment helps developers to rapid selection and access of appropriate tools required to develop the embedded software on the specific embedded system. In addition, it enables developers to handle the outputs from development tools associatively. Moreover it is very flexible in extension and integration because it's implementation based on Eclipse technology. We also perform the evaluation of our tool and successfully validate the utilization convenience of embedded development tools. Therefore, we expect that this tool enables developers to use the embedded development tools efficiently, and then it help improving embedded software productivity.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.