• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.22 no.6
• /
• pp.1407-1417
• /
• 2012

In order to protect a software system from security attacks, it is important to remove the software security weaknesses through the entire life cycle of software development. To remove the software weaknesses more effectively, software weaknesses are prioritized and sorted continuously. In this paper, we introduce the existing scoring systems for software weakness and software vulnerability, and propose a new quantitative standard for the scoring system, which helps evaluate the importance of software weakness objectively. We also demonstrate the practicability of the proposed standard by scoring 2011 CWE/SANS Top 25 list with the proposed standard and comparing it to the original score of MITRE.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.11a
• /
• pp.330-331
• /
• 2010

소프트웨어 아키텍처는 소프트웨어의 품질에 지대한 영향을 미치는 요소 중 하나이다. 소프트웨어 개발 생명주기 초기에 아키텍처를 분석하고 평가하지 않으면, 점점 품질결함을 발견하고 수정하는 비용이 증가한다. 기존 소프트웨어 아키텍처 분석 및 평가 방법은 아키텍처라는 상당히 추상화된 수준에서 분석 및 평가가 이루어지기 때문에 평가기준이 주관적이며, 선택된 아키텍처 후보들만으로 서로에게 미치는 품질속성의 영향을 파악하기 힘들다. 따라서 품질 속성 시나리오나 아키텍처 전략을 구현하기 위한 세부적인 아키텍처 전술들의 품질평가가 필요하다. 본 연구는 이러한 아키텍처 전술의 품질 평가를 위해, Q-SIG(Quantified Softgoal Interdependency Graph)을 이용한 품질속성과 이를 달성하기 위한 아키텍처 전술의 관계를 정성적, 정량적으로 표현한다. 또한 Bayesian Belief Network(BBN) 모델 구축을 통해 Q-SIG에서 표현할 수 없는 다수의 품질속성을 만족하는 아키텍처 전술들 간의 조합에 대해 분석하고, 평가하여 아키텍트가 소프트웨어 디자인 단계에서 높은 품질속성을 달성할 수 있는 아키텍처 전술들의 조합을 선택할 수 있는 방법을 제시한다.

• The KIPS Transactions:PartD
• /
• v.16D no.1
• /
• pp.105-112
• /
• 2009

Risk management is increasingly seen as one of the main jobs of project managers. It involves anticipating risks that might affect the project schedule or the quality of the software being developed and taking action to avoid these risks. The results of the risk analysis should be documented in the project plan along with an analysis of the consequences of a risk occurring. Effective risk management makes it easier to cope with problems and to ensure that these do not lead to unacceptable budget or schedule slippage. This research provides criteria of analysis of risk items to the estimation of process milestone on software development. Also, In this paper propose to a fixed quantity and transition phase.

• The KIPS Transactions:PartD
• /
• v.15D no.3
• /
• pp.313-320
• /
• 2008

A typical software development life cycle consists of a series of phases, each of which has some ability to insert and detect defects. To achieve desired quality, we should progress the defect removal with the all phases of the software development. The well-known model of phase-based defect profile is Gaffney model. This model assumes that the defect removal profile follows Rayleigh curve and uses the parameters as the phase index number. However, these is a problem that the location parameter cannot present the peak point of removed defects when you apply Gaffney model to the actual situation. Therefore, Gaffney model failed to represent the actual defect profile. This paper suggests two different models: One is modified Gaffney model that introduce the parameter of Putnam's SLIM model to replace of the location parameter, the other is the growth function model because the cumulative defect profile shows S-shaped. Suggested model is analyzed and verified by the defect profile sets that are obtained from 5 different software projects. We could see from the experiment, the suggested model performed better result than Gaffney model.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.06c
• /
• pp.220-222
• /
• 2006

본 논문은 안전등급 제어기기(Safety-Grade Programmable Logic Controller)에서 사용하는 프로세서모듈 운영체제에 대한 컴포넌트 시험에 대해 기술한다. 디지털 소프트웨어에 대한 NRC(Nuclear Regulatory Commission)의 지침에 따라 운영체제는 소프트웨어 생명주기에 따라 개발되고 있으며 요구사항과 설계명세, 그리고 구현코드를 가지고 다양한 시험을 수행하고 있다. 컴포넌트 시험은 구현된 코드가 테스트 커버리지를 만족하는 지 파악하는 시험이다. 이를 위해 설계명세서를 참조하여 시험대상을 구분하고 각각의 시험대상에 대한 시험항목을 세분화한 이후 시험방법과 절차, 그리고 시험환경을 구축한 후 컴포넌트 시험을 수행한다.

• Journal of Advanced Navigation Technology
• /
• v.15 no.3
• /
• pp.419-431
• /
• 2011

Design traceability has been widely recognized as being an integral aspect of software development. Also many projects for software application development have failed because that the projects did not analyze user requirements sufficiently and reflected them in the projects adequately. This thesis proposes a specification and tracing technique for object-oriented analysis and design. The subject of this study is the artifacts of UML development methodology. Therefore, to improve the quality of the software development cycle, in short, the system requirement of customers will be able to respond quickly.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2007.11a
• /
• pp.336-339
• /
• 2007

모바일의 소프트웨어 테스팅은 매우 중요하다. 그러나 모바일 특성상 일반 어플리케이션의 테스팅과 다른 점이 있으며, 짧은 생명주기 등으로 빠른 출시를 목적으로 테스팅을 소홀히 하는 경우가 있다. 이렇게 테스팅을 소홀히 함으로써 추가적인 유지보수등의 비용으로 기업의 손실로 직결될 수 밖에 없다. 하지만 현재 모바일의 단위 테스트 방법 및 테스트 개발 방법이 미미한 실정이다. 본 논문에서는 TDD방법을 적용하여 모바일의 테스트 방법 및 개발 절차에 대하여 제시하고자 한다.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.5
• /
• pp.115-126
• /
• 2012

It is very important to trace whether all the requirements has been reflected in the developed system. However, most existing researches apply Requirement Traceability Matrix(RTM) to the whole SDLC according to the development methodology. RTM has no practical value because it has not only too many pursuit items but also its tracking method is very complicated and the practical management in developing the information system is not accomplished nearly. Therefore, in this study, we proposed an enhanced RTM which was composed of only necessary items and allow us to manage the applied area effectively from Request for Proposal(RFP) or the proposal stage to SDLC stage then confirmed the effect through six actual applicable cases of information system development project of "K" company.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.75-80
• /
• 2002

Putnam develops SLIM (Software LIfecycle Management) model based upon the assumption that the manpower utilization during software project development is followed by a Rayleigh distribution. To obtain the manpower distribution, we have to be estimate the total development effort and difficulty ratio parameter. We need a way to accurately estimate these parameters early in the requirements and specification phase before investment decisions have to be made. Statistical tests show that system attributes are highly correlation (redundant) so that Putnam discards one and get a parameter estimator from the other attributes. But, different statistical method has different system attributes and presents different performance. To select the principle system attributes, this paper uses the principle component analysis (PCA) instead of Putnam's method. The PCA's results improve a 9.85 percent performance more than the Putnam's result. Also, this model seems to be simple and easily realize.

• Journal of Internet Computing and Services
• /
• v.6 no.2
• /
• pp.13-24
• /
• 2005

Software development by component integration is the mainstream for time-to-market and is the solution for overcoming the short lifecycle of software. Therefore, the effective techniques for component integration have been working. However, the systematic and practical technique has not been proposed. One of main issues for component integration is how to specify integration and the component architecture for operating the specification, in this paper, we propose a workflow variability design technique for component integration, This technique focuses on designing to a connection contract based on the component architecture. The connection contract is designed to use the provided interface of component and the architecture can assemble and customize components by the connection contract dynamically.