• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.418-420
• /
• 2005

소프트웨어 프로덕트 라인 공학은 두 가지 측면에서 재사용 활동을 정의한다. 첫째는 자산들의 공통성과 가변성을 분석하고 이를 명시적으로 표현하고자 하는 재사용 계획 프로세스 즉, 도메인 공학 프로세스이다 둘째는, 존재하는 핵심자산들을 이용하여 실제 프로덕트를 개발하는데 초점을 두고 있는 재사용 적용 프로세스 즉, 애플리케이션 공학 프로세스이다. 지금까지 프로덕트 라인 공학에서 많은 연구들은 재사용 계획 프로세스에 초점을 두고 있었으며, 재사용 적용 프로세스는 핵심자산의 단순한 커스터마이즈 또는 인스턴스화하는 수준으로 언급하고 있었다. 그로인해, 핵심자산들은 각기 다른 개발 프로세스에서 사용 표준 없이 적용되거나 핵심자산에 의존하여 개발 프로세스가 변경되어야 하는 문제를 발생시켰다. 본 논문에서는 프로덕트라인 핵심자산이 각기 다른 프로덕트 개발 프로세스에서 효율적으로 재사용 될 수 있도록 가이드해 주는 적용지침서 개발 방법을 제시한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.05a
• /
• pp.265-268
• /
• 2004

최근 사회의 다양성과 기업환경의 변화, 정보기술(IT)의 발달로 조직운영의 생산성 및 효율성 제고와 대고객 서비스 수준향상을 위해 업무처리를 자동화 시키고자 하는데 많은 관심을 가지게 되었다. 현재는 누가 무슨일을 하고 있는지 파악이 어렵고, 조직에 의해 정의된 룰과 시스템에 따르기 보다는 개인의 주관과 판단에 따른 업무 수행이 되고, 무엇보다 변화하는 시장환경에 유연하게 대응하는데 어려움이 많다. BPM(Business Process Management)은 조직내의 사람과 시스템, 어플리케이션을 통합하는 개념으로서 워크플로우와 응용프로그램통합기술(EAI)이 결합된 시스템으로 업무의 자동화는 물론 모니터링, 평가등을 통하여 획기적으로 ROI를 개선해 주며 적용을 위해서는 프로세스와 시스템을 아우러는 컨설팅과 구현이 따른다. 그러나 BPM의 개념적 만족은 하지만 초기단계로서 적용사례가 부족하여, 적용하기 위한 의사결정은 쉽지 않다. 본 논문은 BPM의 개념파악과 BPR, 워크플로우와 BPM의 차이점을 비교분석 하고, 대규모 대량의 트랜잭션과 수천명의 사용자 및 다수의 비즈니스 어플리케이션이 관여하는 금융여신 프로세스에 BPM을 적용하는 사례를 제시하고자 한다.

• The Journal of Korean Association of Computer Education
• /
• v.8 no.6
• /
• pp.1-12
• /
• 2005

IT education in the colleges or universities and IT industry in producing IT manpower are urgently called for to balance its supply and demand. To correct this problem, Ministry of Information and Communication launched a program where demand-oriented curriculums are developed and applied to colleges. This paper proposes a design technique based on meta-model and software development process in developing curriculums and courses. This meta-modeling technique is proven to result in the extendibility, flexibility and quality improvement in software design. Therefore, we expect that proposed technique makes it possible to be improved in quality.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.36 no.4B
• /
• pp.332-345
• /
• 2011

As weapon systems are evolving into more advanced and complex ones, the role of the software is becoming heavily significant in their developments. Particularly in the war field of today as represented by the network centric warfare(NCW), the reliability of weapon systems is definitely crucial. In this context, it is inevitable to develop software reliably enough to make the weapon systems operate robustly in the combat field. The reliability engineering activities performed to develop software in the domestic area seem to be limited to the software reliability estimations for some projects. To ensure that the target reliability of software be maintained through the system's development period, a more systematic approach to performing software reliability engineering activities are necessary from the beginning of the development period. In this paper, we consider the software reliability in terms of the development of a weapon system as a whole. Thus, from the systems engineering point of view, we analyze the models and methods that are related to software reliability and a variety of associated activities. As a result, a process is developed, which can be called the software reliability engineering process for weapon systems (SREP-WS), The developed SREP-WS can be used in the development of a weapon system to meet a target reliability throughout its life-cycle. Based on the SREP-WS, the software reliability could also be managed quantitatively.

• Journal of Platform Technology
• /
• v.8 no.4
• /
• pp.47-58
• /
• 2020

DO-330 Software Tool Qualification Considerations is a guideline for development of tools used to develop/verify software and hardware installed on aircraft. And among several processes, the verification process is very crucial as it occupies a large proportion for DO-330. Especially, in order to qualify tool with high safety level, test objectives must be performed with independence, accordingly, more time, cost, and manpower are required than other objectives. In addition, even if the test cases or test procedures are well defined, the higher the complexity of the test the higher probability of human error occurs. In this paper, we propose Script-based Test Automation Agent software structure for efficient DO-330 verification process of A661UAGEN tool developed by Hanwha Systems. Compared to the test performed manually by the test engineer, testing time of the Script-based Test Automation Agent is reduced by 87.5% and testing productivity is increased by 43.75%.

• Proceedings of the Korean Information Science Society Conference
• /
• 2002.04b
• /
• pp.445-447
• /
• 2002

최근 국내 기업들은 S/W Process심사를 통하여 기업의 Process수준 향상과 개발 제품의 품질을 향상시키고자 하는 관점에서 CMM, SPICE와 같은 표준에 많은 관심을 보이고 있다 이러한 표준들에서는 소프트웨어 품질 향상을 위만 기반으로 요구사항 관리를 중요시하고 있다. 많은 기업들이 요구사항을 추출하여 분석하고, 관리하는 방안에 대해 관심을 가지고 적용하고 있다. 요구사항 관리는 요구사항 개발, 변경 및 연계성과 관련된 모든 활동을 포함한다. 즉, 상호적이고 협력적인 공정을 통해서 요구사장을 추출, 분석하고 분석된 결과를 문서화하고, 요구 사항들 간의 연계성을 설정 관리하고, 변경 사장을 관리해야 한다. 본 논문에서는 요구사항추출 단계에서부터 개발 완료 시점가지 요구사항을 관리하는 소프트웨어 요구사장 프로세스를 제안하고, 이를 적용한 사례를 제시한다.

• Journal of Digital Convergence
• /
• v.13 no.12
• /
• pp.319-324
• /
• 2015

This paper proposes an integrated management system for products of game software development. Those products generated over software life-cycle are generally huge in numbers, various in kinds and interconnected in relationships among them. Especially they are highly complex and tightly coupled each other because they are used to build another world which is composed of multi-modal data such as graphics, sound, logics and so on. Therefore it is critical to manage development products in an integrated manner to guarantee the quality of software. The proposed system is designed to provide project/requirement/configuration/traceability management capabilities and interfacing to CASE standards. To achieve the objective, it is based on data warehouse technologies which provide central repositories of heterogeneous data, multi-aspect reporting&analysis capabilities, traceability, verification, etc.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.328-341
• /
• 2007

When the decision to initiate a software product line has been taken, the first step is the domain analysis describing the variability in the requirements, the second important step is the definition of a domain architecture that captures the overall structure of a series of closely related products. A domain architecture can be a core asset in product line by describing the commonalities and variabilities of the products contained in the software product line. The variabilities, which are identified at each phase of the core assets development, are diverse in the level of abstraction. Therefore, it is important to clearly define, systematically identify, and explicitly represent variability at the architectural level. However, it is difficult to identify and represent the variability which should be considered at the architecture level, because these may be appeared in architecture elements and in architecture configuration. In this paper, we suggest a method of developing domain architecture as a core asset in product line where commonality and variability are explicitly considered. First of all, we will describe a domain architecture metamodel that can explicitly define commonality and variability concepts by extending the Object Management Group's ($OMG^{TM}$ Reusable Asset Specification eRAS) model. Using the domain architecture metamodel, architecture elements are defined and the variations that can be identified at the architecture level are classified into two types in according th abstract level. Additionally, we describe a domain architecture where commonality and variability are explicitly considered on basis of this metamodel.

• Journal of Information Technology and Architecture
• /
• v.10 no.3
• /
• pp.335-346
• /
• 2013

With the overwhelming development of information technologies, the need for software development that can deal with diversified and complex business processes has increased dramatically. As a result, companies prefer softwares that can handle far more complex processing ability and also it should be stable as well as easier to maintain. These ambivalent requirements keep the software development organizations from assessing the quantitative abilities, so that under the support of the U.S. Department of Defense the Capability Maturity Model (CMM) and Capability Maturity Model Integration (CMMI) have been developed. The CMMI upper levels for the software development companies will be evaluated to be excellent and authenticated, which drives the companies to get and maintain high levels of maturity. In this paper, a case study for a domestic software company has been exploited how to achieve CMMI level 4 and what kind of factors have been played an effective role. These issues at the domestic and international software and maintenance program, can influence the trustworthiness and marketing effects for the global market. In this paper, the company's actual case study will give clues to find out the important factors for the development and maintenance of software companies maturity levels.

• Knowledge Management Research
• /
• v.16 no.2
• /
• pp.227-248
• /
• 2015

SPI (Software Process Improvement) activities have been considered one of the crucial approaches to achieve high quality, productivity and timely delivery of software products and services. The basic premise of SPI model is that higher maturity levels lead to better performance. In this research, the relationships between SPI results and performance were empirically investigated with Korean software companies. CMM key process areas were categorized into two dimensions, "Process Implementation" and "Quantitative Management". The relationship between process implementation and performance was significant, but the relationship between quantitative management and performance was insignificant. The control variable, size of OU(Organizational Unit), did not have significant impact on the relationships between SPI activities and OU performance.