• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.27 no.10C
• /
• pp.887-901
• /
• 2002

Software management model divided into the software project model and design estimation model, software matrices model, reliability growth model, process improvement model(or process maturity model) etc. Among these software management models, software complexity model make an estimated of the product software. For a practice of software managed, need to guideline of the static analysis of software. Especially, Software complexity model introduced for the estimation of software quantity and program complexity. In case of measurement the software matrices, its need for us to analysis of software quality and products. On the other hand, we known that complexity program include many defects and consuming of source cost. So, we apply to complexity model using of the program complexity, control structure and volume matrices, interface metrics, process complexity metrics method. In this paper, we represent that the analysis of fault data detected during the system test. Also, we analysis of program control structure and interface, volume matrices in various aspect of switching software. Others, their results utilized similar of project and system development.

• Management & Information Systems Review
• /
• v.18
• /
• pp.201-222
• /
• 2006

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown. so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• The Journal of Information Systems
• /
• v.14 no.2
• /
• pp.173-189
• /
• 2005

Recently, Korean software industry has enjoyed fast growth, thus phenomenon drew attention to the need for more precise and standardized cost estimation system for software development. However, many obstacles exist in achieving a more precise and universally applicable cost measurement. These obstacles include : (1) the intangible nature of intellectual efforts, (2) lack of cost standards, (3) lack of quantitative yardstick to determine the potential complication, (4) lack of both cost monitoring during development and coordinating between acquisition process and cost estimation. The purpose of this study is to facilitate software development cost estimation considering acquisition process that will meet korean user's needs, and to create better models that will be cost for software development particularly for Korean environment.

• Journal of Computing Science and Engineering
• /
• v.4 no.4
• /
• pp.253-275
• /
• 2010

In this article we review the metaphor of service-oriented architecture for enterprise computing. In typical definitions service-oriented architecture appears as a single message and a consistent roadmap for building flexible software system landscapes. But it is not. Different communities have elaborated different SOA (service-oriented architecture) concepts to address different problem areas, i.e., enterprise application integration, business-to-business, business process management, and software productizing. If software architects and software managers are aware of these strands of SOA when talking about SOA in their projects they can avoid misunderstandings and detours better. This article contributes a clarification of the different strands of SOA concepts and technologies and their mutual dependencies and identifies particular SOA concepts as instances of more general software engineering principles.

• Journal of Advanced Information Technology and Convergence
• /
• v.8 no.2
• /
• pp.111-118
• /
• 2018

Information communication authority module software contains various functions and services. A software test is the only acceptance test step. Recently, however, all development steps have become important. In particular, the software acceptance step is very high, and a study of the effective use of limited time and resources on acceptance step is needed. This study examined the efficiency of the Test Design Technique for Software Test. The proposed Test Design process was applied to the domain systems of info-communication and the degree of improvement was measured. This paper establishes Software Test design process Infrastructure based on the developed software.

• The KIPS Transactions:PartD
• /
• v.14D no.2
• /
• pp.203-210
• /
• 2007

Ontology can be used as a formal and demonstrative knowledgebase that can express the thinking process of human. Software Development Process is a collection of ideal practices and procedural system that is performed by mature organization with high capability. Due to complexity of process, however, Software development Process often results in obstruction of introducing and improving simple process activity. While introducing and improving software development process, application of ontology to complex software development process is more approachable by showing deductive results of relationship between ISO/IEC 15504 and CMMI. In this paper, we demonstrate a methodology that utilizes the improved process database conceptually mapping between ISO/IEC 15504 and CMMI using ontology.

• IE interfaces
• /
• v.17 no.spc
• /
• pp.1-10
• /
• 2004

The purpose of this paper is to reorganize cost adjustment factors of software development projects in estimating software development cost, and derive adjustment coefficients of application types and language types by analytical hierarchy process. We constructed a decision-making hierarchy of various criteria which determine the complexity of application types and language types, and conducted a survey on the pairwise comparison among alternatives. Finally, the cost adjustment coefficients of application types and language types were derived by analytic hierarchy process. This paper is the first study in which the analytic hierarchy process was applied to the field of estimating cost adjustment factors of software development projects.

• Management & Information Systems Review
• /
• v.15
• /
• pp.245-262
• /
• 2004

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown, so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• Proceedings of the Korea Contents Association Conference
• /
• 2007.11a
• /
• pp.591-594
• /
• 2007

We construct the test process site about X-Internet and X-Forms base software. This software is developed with X-Forms base web UI tool. Basically, this software is operated on the Client. Even in operating process, this kind of software could be updated because of user's request, improvement in efficiency, reformation and addition in functions and so on. In order to test a updated software, V-Model will be extended and transformed test process will be proposed. This proposed test process is starting with test plan which defines test object and activities for attainment of process's goal. The following steps are recognizing testcase and data, analysis and design for constructing process environment, setting forth testcase in detail, realization of test methodology, and the arrangement of results. This paper will be helpful to build more efficient process site by managing and recording the test process.

• Journal of KIISE:Software and Applications
• /
• v.29 no.9
• /
• pp.619-630
• /
• 2002

The various software engineering techniques have been come out in order to cope with the software crisis since 1980's. The software Engineering has focused on the process of software component development. The process products a development guide for a quality and productive improvement of software. But, most of the methodologies assume that a new system will be constructed and reused in the future. these do not actually support efficiently how we reuse legacy system's resources and construct a new system. In this paper, we present an efficient Reengineering Process for reusing legacy systems, RUP+re, which extends and customizes RUP. Rup+re consists of Reverse Engineering Workflow, Re-Engineering Workflow and forward Engineering Process. We describe RUP+re's workflows with their own detail steps and verify them practically through the case study. So, we provide efficient guidelines to the software Reengineering process construction which reuses the resources of a legacy system.