• International Journal of Safety
• /
• 제8권2호
• /
• pp.31-36
• /
• 2009

In accordance with the development of recent computer technology, railway signaling software became more complex for the intellectualization. Therefore the importance and dependency of railway signaling system on the computer software is getting more increased further, and the testing for the safety and reliability of railway signaling system software became more important. It is started to become influential as very important issue for the reliability and safety of vital embedded software like railway signaling system. The software coding which can have an effect on the safety at the coding level of software shall not be included preferentially, for the safety of software, and must be checked. This thesis suggested an automated testing tool for coding rules on this railway signaling system software, and presented its applied result for railway signaling system software. The testing items in the implemented tool had referred to the international standards in relation to the software for railway system and MISRA-C standards. This automated testing tool for railway signaling system can be utilized at the assessment stage for railway signaling system software also, and it is anticipated that it can be utilized usefully at the software development stage also.

• 지식경영연구
• /
• 제18권2호
• /
• pp.45-63
• /
• 2017

In the success of an IT project, the role of S/W developer in carrying out the project is critical and crucial. However, compared to its importance, there is only a few studies on the role of human resources in software engineering field, mainly focusing on technology. Based on regulatory focus theory, this study examines how the effect of technology recency on developer's intention to participate in the IT project changes depending on the regulatory focus of the software developer. As a result of the experiment, it was confirmed that there is a difference in the effect of technology recency on project participation intention according to the condition of developer's regulatory focus. This study is meaningful because it extends regulatory focus theory to software engineering field and made theoretical contribution to the research field of behavioral software engineering. In practical, it was possible to suggest a way to improve the intention of the developer to participate in the project, by understanding the software developer in the IT project, considering the software developer propensity and project characteristics.

• 정보처리학회논문지:소프트웨어 및 데이터공학
• /
• 제2권10호
• /
• pp.691-696
• /
• 2013

소프트웨어 개발방법론은 새로운 소프트웨어를 개발하는데 가장 효율적인 개발 방법과 관리 방법 등을 제시하고 있다. 그러나 소프트웨어 개발방법론은 많은 비용과 시간을 필요로 하고 있으며, 소프트웨어공학 전문가를 필요로 하고 있다. 이러한 이유로 필요성은 인정받고 있으나 대규모 소프트웨어에서만 적용되는 문제점들을 안고 있다. 본 논문에서는 현재 많이 사용되고 있는 소프트웨어 개발방법론을 전문가 없이 소규모 소프트웨어를 개발하는데 적용할 수 있도록 반드시 필요한 단위 일(Task)을 선별하고 대안으로 정의하여 AHP(Analytic Hierarchy Process) 기법을 통해 대안에 대한 적합도를 평가하였다. 이를 통해 중소기업에서도 평가된 소프트웨어 개발방법론을 사용하여 소프트웨어를 효율적으로 개발하고 관리할 수 있다.

• 한국IT서비스학회지
• /
• 제11권1호
• /
• pp.197-210
• /
• 2012

This paper presents the ways that can improve the Software Cost Estimation Guidelines in order to replace those that are expected to be abolished at February, 2012, and solve the problems that are being occurred in the current Software Cost Estimation Guidelines. By using multidimensional modeling of OLAP(On-Line Analytical Processing), this paper does three dimensional modeling that considers the product/service view, process view and skill view. Also, it presents the identification method of cost estimation data through the view of each dimension. Furthermore, it defines the software cost estimation process and adapts them into the bottom up estimation and the top down estimation. Finally, it proposes the access of cost estimation data by the multidimensional analysis of OLAP.

• International journal of advanced smart convergence
• /
• 제9권4호
• /
• pp.149-155
• /
• 2020

In the software industry of Korean Small and Medium-sized Enterprise(SME)s, the development process is often not mature. This may lead to failures in quality control and output management. As a result, the quality of the software can be degraded. To solve the problem, the software visualization technique, which is from the National IT Industry Promotion Agency Software Engineering Center can be applied. We have experienced with mentoring not only the visualization of software development process, but also various visualization process of SMEs. However, the existing software visualization method was difficult to install environment and its time cost was high. This paper proposes a software visualization environment through a cloud service along with a case of building a software visualization environment. We expect that this method will make it easier to build a visualization environment and improve the quality of SME software.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제30권5_6호
• /
• pp.515-528
• /
• 2003

컴포넌트 기반 소프트웨어 개발 방법은 새로운 패러다임으로 인식되고, 활발한 연구가 진행되고 있다. 그러나 컴포넌트 기반 개발에서 컴포넌트의 재사용성과 효율적인 소프트웨어 개발을 보장하기 위해서는 소프트웨어 아키텍처를 기반으로 한 개발이 필요하다. 본 논문에서는 컴포넌트 기반 소프트웨어 개발을 지원하기 위해, Kruchten이 제시한 4+1 뷰 모델을 기반으로 재 정의한 컴포넌트 기반 4+1 소프트웨어 아키텍처 뷰 모델을 제안한다. 또한 뷰 모델의 요소와 UML을 이용한 뷰 모델 요소의 표현을 제시한다 이 아키텍처는 컴포넌트의 사용문맥을 각 뷰에 반영함으로써 소프트웨어에 대한 이해와, 컴포넌트의 상호 작용에 대한 정보 등 컴포넌트 기반 소프트웨어 구성에 대한 틀을 구성한다.

• 한국콘텐츠학회논문지
• /
• 제9권7호
• /
• pp.110-120
• /
• 2009

최근 소프트웨어 품질평가 및 인종에 대한 인식의 제고와 더붙어 소프트웨어 개발 기업에서 품질투자를 통한 고품질 확보의 중요성에 대한 인식이 증대되고 있다. 그러나 실질적으로 어느 정도 수준에서 품질투자가 이루어져야 하는지, 품질투자를 통해 실질적으로 소프트웨어 품질 개선의 검증이 이루어지지 않음으로 해서 품질투자를 통한 품질개선을 원하는 기업들이 정확한 방향을 설정하지 못하고 있는 문제가 발생 하고 있다. 본 연구에서는 국제표준인 ISO/IEC 9126과 소프트웨어 시험에 관한 지침인 ISO/IEC 12119를 기반으로 메트릭을 구축하였으며 소프트웨어 시험사례를 통해 축적된 결함 데이터를 분석, 결과를 도출하고 미들웨어 소프트웨어의 품질 평가 사례를 조사/분석하여 품질수준과 결함 수준을 분석하고 개발 과정 에서 취약한 부분을 도출하여 대처 방안을 검토하였다. 본 연구를 통해 미들웨어 소프트웨어의 품질향상을 유도하고 양적/질적인 수요를 충족할 수 있다고 본다.

• Journal of Information Technology Applications and Management
• /
• 제27권2호
• /
• pp.37-50
• /
• 2020

This paper is very exploratory and addresses the issue 'Is a general quality model of software possible?'. If possible, how specific can/should it be?' ISO 25000 Series SQuaRE is generally regarded as a general quality model which can be applied to most kinds of software. Usability is one of the 8 characteristics of SQuaRE's Product Quality Model. It is the main issue associated with SQuaRE's Quality in Use Model too. it is the most important concept associated software quality since using is the only ultimate goal of software products. Playability, however, is generally regarded as a special type of usability, which can be applied to game software. This common idea contradicts with the idea that SQuaRE is valid for most kinds, at least many kinds, of software. The empirical evidences of this paper show that SQuaRE is too specific to be a general quality model of software.

• 대한임베디드공학회논문지
• /
• 제7권3호
• /
• pp.135-142
• /
• 2012

The Quality of embedded system depends on the embedded software. As the complexity and the size of embedded software have been increasing, it is more likely that the software may include faults, and the reliability and stability issues are getting more important. In this paper, we propose a remote test tool for software based on VxWorks by using fault injection method. The test tool consists of test server and test client for testing on the cross development environment. The test server operates in the host system and user can not only test but also monitor the software by using it. The test client operates in the target system and it controls kernel objects and sends the input data into the software when receiving the control and data from the test server. We developed the prototype software and demonstrated the ability of testing software robustness by injecting faults.

• 한국IT서비스학회지
• /
• 제8권1호
• /
• pp.125-142
• /
• 2009

The Ministry of Information and Communication announced "The Guideline for Management of Software Project" in October 2006. The public employees(acquirer) have to manage software projects with this guideline. The guideline was based on the International standard(ISO/IEC 12207) and IEEE standard(IEEE/EIA 12207), and was developed by considering the domestic software industry environment. The guideline can help to establish a software acquisition process for appropriate management of software projects, and the process can increase the management productivity of software projects. This study provides the explanation about the guideline with terms of 5W1H(who(user), what(summary), when(time to apply), where(domain of application), why(objective), how(method of use)) for understanding of the guideline.