• Journal of the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.295-306
• /
• 2002

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort are variable according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differ from project to project. This paper suggests the criteria for effort allocation in planning, specifying, building, testing and implementing phase followed by the project total effort. These criteria are derived from 183 different projects. This result can be considered as a practical guideline in management of project schedule and effort allocation.

• Journal of the Korean Professional Engineers Association
• /
• v.42 no.5
• /
• pp.29-31
• /
• 2009

A general practice in software ordering behavior in public sector has been an enormous obstacle standing in development path of Korea's software industry. Standard on software development cost estimation is supposedly based on Function Point, but in general, it is on headcounting (a number of people involved in a project). Moreover, it is difficult to change a contract in an on-going project, since statement of work is not precisely and carefully described. But it has a simple solution. Design and Implementation should be a separate project, as in construction industry, and both power and responsibility for design should be given to an expert with a national-level qualification. Here, there is a simple way for Korea to reborn as one of the strongest software country.

• Asia pacific journal of information systems
• /
• v.12 no.4
• /
• pp.101-120
• /
• 2002

Risk management or risk-based approach of software project management was developed to explain the effects of requirement uncertainty, control standardization, interactions on software quality. Based on a prior theory, five hypotheses were derived and empirically tested using a survey design. Data from 117 members in 3 SI companies support for the path model, and three of five hypotheses. The results showed that decreases in requirement uncertainty and increases in control standardization were directly associated with increases in the interactions between user and project teams, which, in turn, led to increases software quality. The findings suggested that the direct effect on software quality is primarily due to the interactions between user and project teams, rather than requirement uncertainty and control standardization.

• Journal of Construction Engineering and Project Management
• /
• v.1 no.2
• /
• pp.28-36
• /
• 2011

Risk management is popularly and widely used in various industries to handle uncertainty that can negatively affect their businesses. While in the current Information-Technology oriented age, software packages are designed to assist in carrying out risk management processes, the construction industry does not seem to have software that is tuned to its specific characteristics and processes. Therefore, this study first explores the types of software that are commonly used for risk management in the Singapore construction industry. Also, using one-sample t-test, it is tested if the software programs used in the construction industry have effectively catered the needs of the users. For the analysis, a survey questionnaire was developed and the representatives from 34 companies participated in the survey. Furthermore, this study also makes use of the current risk management framework defined in ISO31000 to design a risk management software algorithm that can suit the needs for the Singapore construction industry. The results from this study will contribute to identifying strategic areas, in terms of use of risk management software, on which the industry needs to focus, ultimately enhancing their performance of risk management.

• 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 the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.65-72
• /
• 2018

In this paper, we have studied how to reuse common data link software by applying software product line engineering. Existing common data link software performed different stages of design, implementation, and testing without sharing the accumulated knowledge of different developers. In this situation, developers agreed that sharing the assets of each project and reusing the previously developed software would save human and time costs. Even with the initial difficulties, the common Data Link is a continually proposed project in the defense industry, so we decided to build a product line. The common data link software can be divided into two domains. Among them, the initial feature model for the GUI software was constructed, and the following procedure was studied. Through this, we propose a plan to build a product line for core assets and reuse them in newly developed projects.

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

• The Journal of Society for e-Business Studies
• /
• v.7 no.2
• /
• pp.173-190
• /
• 2002

Over the past decade, numerous software managers and engineers have been concerned with measuring the size and complexity of software systems. Function point analysis technique is one of the most popular software sizing techniques. A reasonable software development plan through cost and time estimation should be a prerequisite for the successful project at the beginning stage of the project. It is generally known that software size measurement is useful for this kind of estimation and the function point analysis technique would be more effective than the others. However, it is difficult to apply the technique to object-oriented methodology widely used in the software industry. Thus, the purpose of this study is to present a case study on how to apply function point analysis technique to sizing of the software systems based on UML. The results of this study can be useful to managers and engineers.

• International journal of advanced smart convergence
• /
• v.10 no.2
• /
• pp.130-137
• /
• 2021

In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigousrequirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.

• Journal of the Korea society of information convergence
• /
• v.1 no.1
• /
• pp.33-40
• /
• 2008

When performing a software development project, the most important thing is building a result with planned quality within development period. Particularly, if the project is delayed or has no good quality in the case of the content software development project which is sensitive to the release time and quality, it is immediately connected to the failure of the whole project. Extreme programming is a methodology that divides the development cycle into smaller units for reducing the risk factor of the project in which the development period is important. In this paper, we suggest the expanded extreme programming which can consider the development period and quality at the same time for content software development environment. The suggested methods are documentation mechanism that is upcoming during the development project and multiple role model which is extended from pair programming method.