• Korean Journal of Remote Sensing
• /
• v.20 no.3
• /
• pp.189-196
• /
• 2004

This paper describes what an operational change detection tool requires and the software which was designed and developed according to the requirements. The top requirement for the application of the software to operational change detection was identified: minimization of false detections, missing detections and operational cost. In order to meet such a requirement, the software was designed with the concept that the ultimate decision and isolation of changes must be performed manually by visual interpretation and all automatic algorithms and/or visualization techniques must be defined as support functions. In addition, the modular structure of the proposed software enables the addition of a new support function with the minimum development cost and minimum change of the operational environment.

• Journal of Korean Society for Quality Management
• /
• v.20 no.2
• /
• pp.94-108
• /
• 1992

This study involves an experiment for the cognitive experiment design and the human reliability in software engineering. Its overall objectives are to analyze common-cause human domain error and reliability in human-software interaction. A laboratory study was performed to analyze software engineers' task behavior in software production and to identify software design factors contributing to the effects in common cause failure redundancy. Common-cause model and its function were developed, then the main experiment using programming experts was conducted in order to define a new cognitive paradigm, in the aspects of identification, pattern recognition, and behavior domain for human reliability and quality control in software development. The results and analytical procedures developed in this research can be applied to reliability improvement and cost reduction in software development for many applications. Results are also expected to provide guidelines for software engineering quality control and for more effective design of human-software interface system.

• Journal of Advanced Navigation Technology
• /
• v.14 no.6
• /
• pp.900-908
• /
• 2010

Recently, OOM(Object-Oriented Method) access method which begins to apply to software development is emphasizing development cost and time reduction through independent software reuse. But because of planning to the exclusion of the lack of knowledge and expansion or performance for development technology many problems are coming out. Therefore, this thesis suggests Effective Object-Oriented Modeling methods considering the plan for higher productivity enhancement of software in the software development life cycle. Effective Object-Oriented Modeling method includes, methods, Use Case modeling methods, Analysis Modeling methods, Design Modeling methods and others.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.6 no.3
• /
• pp.9-17
• /
• 2010

Decision problem called an optimal release policies, after testing a software system in development phase and transfer it to the user, is studied. The applied model of release time exploited infinite non-homogeneous Poisson process. This infinite non-homogeneous Poisson process is a model which reflects the possibility of introducing new faults when correcting or modifying the software. The failure life-cycle distribution used superposition which has various intensity, if the system is complicated. Thus, software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement becomes an optimal release policies. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, estimated software optimal release time. Through this study, in terms of superposition model and simply model, the optimal time to using superposition model release the software developer to determine how much could count will help.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1164-1177
• /
• 2005

As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.6
• /
• pp.119-129
• /
• 2020

Software development activities are influenced by stochastic theory rather than deterministic one due to having process variability. Stochastic methods factor in the uncertainties associated with project activities and provides insight into the expected project outputs as probability distributions rather than as deterministic approximations. Thus, successful software projects systematically manage and balance five objectives based on historical probability: scope, size, cost, effort, schedule, and quality. Although software size estimation having much uncertainty in initial development has traditionally performed using deterministic methods: LOC(Lines Of Code), COCOMO(COnsructive COst MOdel), FP(Function Point), SLIM(Software LIfecycle Management). This research aims to present a function point method based on stochastic distribution and a case study based on Monte Carlo Simulation applying on an automotive electrical and electronics system software development. It is expected that the result of this paper is used as guidance for establishing of function point method in organizations and tools for helping project managers make decisions correctly.

• Journal of Information Technology Services
• /
• v.5 no.1
• /
• pp.97-109
• /
• 2006

As software becomes more complex and its scope dramatically increases, the importance of research on developing methods for estimating software development efforts has been increased. Such accurate estimation has a prominent impact on the development projects. To develop accurate effort estimation models, many studies have been conducted among the academia and the practitioners. Out of the numerous methods, Constructive Cost Model (COCOMO) based on Line of Code (LOC), Regression Model based on Function Point (FP) were the most popular models in the past. As today's development environments are dynamically changing, these traditional methods do not work anymore. There is an impending need to develop an accurate estimation model which accommodates itself to the new environments. As a possible solution, this research proposes and evaluates an software development estimation model based on function points and neural networks.

• Journal of Korea Technology Innovation Society
• /
• v.8 no.spc1
• /
• pp.297-322
• /
• 2005

The paper aims to analyze the logic and power of open source software (OSS), and to show the ways in which Korean government and companies support developing countries in the field of software development. Many developing countries are considering software industry to be a strategic industry due to the fact that software industry seems to be labor-intensive, or rather knowledge-intensive industry. In this regard, developing countries without huge financial investment can achieve certain level of economic development while leveraging software industry. Concerning software development tools, among recent trends OSS has been regarded as a viable alternative software development tool for developing countries. In developing countries, OSS is believed to resolve some difficulties caused by proprietary software such as Microsoft Windows, which is too expensive to buy for users and developers in low-income developing countries. In this sense, OSS has been considered as only solution for software developing because OSS is able to reduce the cost of software development and to enhance the technological capabilities of developing countries. In addition to the benefit of low cost, we have to shed light on the business model of OSS that is not to sell software licence, but to provide technical support and services. In order to use OSS as much as they can, developing countries have to invest for educating human resources who can develop and implement software system using OSS. These OSS-related policies can lead developing countries to developed countries.

• The KIPS Transactions:PartD
• /
• v.14D no.6
• /
• pp.641-648
• /
• 2007

To develop a dynamic system project in which the requirement changes frequently, it's impossible to finish the development within a fixed-cost due to additional budget occurring in need of requirement creep. To manage the successive project within a fixed-cost, it's better to manage the ratio of necessarily changed size of project and necessary optional requirement. According to Bhagwat, it is occurred in the construction phase. Also, he stated that the software development cost, construction phase cost and requirement cost are equal and it was wrong explanation in the ratio of requirement creep and optional requirement. This paper assumes the requirement creep to be happening in the phase of elaboration and construction. In addition, some differences were supposed to happen between software development cost, construction phase cost, and requirement creep cost. As a result, the reality was preferred rather than the ratio of optional requirement and the ratio of requirement creep.

• Smart Media Journal
• /
• v.1 no.4
• /
• pp.79-83
• /
• 2012

In software development process, increasing the size of project(scaling up) is not a same problem as scaling up the parts of small project. Scaling up a project should accompany the communications, and cost, productivity, qualities, development activity, methodologies etc should be considered with it. In this paper, the effective usage of the important elements are discussed in order not to fail to scale up a project.