• 한국통신학회논문지
• /
• 제23권8호
• /
• pp.1915-1925
• /
• 1998

교환 시스템이 고장과 장애를 일으키면 서비스에 치명적인 영향을 미치게 된다. 다시 말해서 시스템을 제어하는 교환 소프트웨어의 역할은 매우 중요하다. 그렇기 때문에 정량적인 소프트웨어의 품질 평가 방법은 더욱 중요하다. 본 논문에서는 기능 블록으로 구성된 교환 소프트웨어를 시험하여 얻어진 각종 고장 데이터를 수집, 분석하고 이를 이용하여 각 버전별, 개발 전과정에 대한 소프트웨어 신뢰도를 평가해보고, 기타 고려할 사항에 대해 논한다. 대표적인 2개의 신뢰도 모형(G-O model, S-Shaped model)을 선택하여 소프트웨어 신뢰도를 비교해 보고 품질 향상을 위한 제반 활동과 소프트웨어 개발 프로젝트에 맞는 소프트웨어 신뢰도 모형을 제시하였다.

• 경영과정보연구
• /
• 제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.

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

하드웨어와 소프트웨어가 조합된 내장형 시스템이 복잡해지면서, 내장형 시스템에 탑재되는 내장형 소프트웨어 테스트가 중요하게 인식되고 있다. 특히, 원자력 발전소와 같이 안전 등급이 높은 시스템에 들어가는 소프트웨어 테스트는 필수적이다. 내장형 시스템 테스트의 경우 하드웨어와 소프트웨어의 상호작용에 의해 발생하는 오류를 발견하기 위한 효과적인 테스트 기법이 필요하다. 본 논문에서는, 하드웨어와 소프트웨어 사이의 상호작용에 의해 생성되는 오류를 발견하기 위하여, 오류 삽입 기법을 이용한 테스트 데이타 선정 기법을 제안하고, 이 기법을 Digital Plant Protection System에 적용하였으며, 실험을 통해 제안한 기법의 우수성을 분석한다.

• Asia pacific journal of information systems
• /
• 제6권1호
• /
• pp.241-267
• /
• 1996

The problems like exceeding estimated cost, late due-date, expensive maintenance, insuffiency of experts and low productivity are becoming emphasized related with the software development. In order to overcome these problems and to develop the highly qualified software within the limited resources, a project management tool is used. The purpose of this study is to develop a conceptual model of the project management system which can plan, analyze and control the software development projects effectively. The model is constructed with plan and track management system, cost management system and operation management system for the efficient project management. It is named by LSD-PMS : Large-scale Software Development Project Management System. We reviewed 5 cases of project management. LSD-PMS is evaluated and reviewed by the project managers in the field. It is proved that LSD-PMS is a tool which can help project managers develop software successfully given budget and time schedule. In the future, this system should be further developed as an integrated model with system implementation tools such as CASE products.

• 한국철도학회:학술대회논문집
• /
• 한국철도학회 2007년도 춘계학술대회 논문집
• /
• pp.987-992
• /
• 2007

Safety critical systems are those in which a failure can have serious and irreversible consequences. Nowadays digital technology has been rapidly applied to critical system such as railways, airplanes, nuclear power plants, vehicles. The main difference between analog system and digital system is that the software is the key component of the digital system. The digital system performs more varying and highly complex functions efficiently compared to the existing analog system because software can be flexibly designed and implemented. The flexible design make it difficult to predict the software failures. This paper reviews safety standard and criteria for safety critical system such as railway system and introduces the framework for the software lifecycle. The licensing procedure for the railway software is also reviewed.

• 대한전기학회:학술대회논문집
• /
• 대한전기학회 2007년도 제38회 하계학술대회
• /
• pp.1201-1202
• /
• 2007

Safety critical systems are those in which a failure can have serious and irreversible consequences. Nowadays digital technology has been rapidly applied to critical system such as railways, airplanes, nuclear power plants, vehicles. The main difference between analog system and digital system is that the software is the key component of the digital system. The digital system performs more varying and highly complex functions efficiently compared to the existing analog system because software can be flexibly designed and implemented. The flexible design make it difficult to predict the software failures. This paper reviews safety standard and criteria for safety critical system such as railway system and introduces the framework for the software lifecycle. The licensing procedure for the railway software is also reviewed.

• 품질경영학회지
• /
• 제17권2호
• /
• pp.27-35
• /
• 1989

Software developers often allocate a significant amount of effort to software testing. But for most business-related software system it is natural to expect the continued discovery of defects after the software system is released into field. Such defects are usually very expensive to fix and have the potential to cause great damages to the users. It is important to stop testing the software and release it to the users at the correct time. In this paper, we propose the determination of the optimal number of software test oy minimizing a total expected software cost. A numerical example is used when the criterion is the expected profit. The result indicates that the proposed software release policy based on the number of software test can be a good alternative to the existing policy.

• Journal of Information Technology Applications and Management
• /
• 제20권3호
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.

• 정보처리학회논문지D
• /
• 제8D권4호
• /
• pp.401-408
• /
• 2001

객체지향 모델은 구조적 모델에 비해 모듈성, 재사용성, 유지보수성, 확장성 등의 장점을 제공한다. 이러한 이유로 객체지향 소프트웨어 개발 방법들을 정보 시스템 개발에 광범위하게 적용되고 있다. 그러나 현재의 객체지향 소프트웨어 개발 방법들은 목적 소프트웨어 시스템의 객체지향 모델링을 지원할 뿐, 방법론 그 자체는 구조적 및 절차적 체계를 기반으로 하고 있다. 본 논문에서는 객체지향 소프트웨어 개발 방법론을 객체지향적으로 모델링한 OMOS(Object-oriented software development Method for Object-oriented software System)를 제시한다. OMOS에서는 개발 산출물과 관련된 활동이 객체로써 모델링 되며, 개발 생명주기 프로세스가 객체간의 상호작용으로 모델링 된다. 소프트웨어 개발 방법론의 객체지향적 모델링은 방법론 자체의 재사용성, 유연성, 확장성, 유지보수성의 용이성 등의 장점을 제공한다.

• 한국정보통신학회:학술대회논문집
• /
• 한국해양정보통신학회 2007년도 추계종합학술대회
• /
• pp.725-728
• /
• 2007

Software security is about making software behave correctly in the presence of a malicious attack, even though software failures usually happen spontaneously in the real world. Standard software testing literature is concerned only with what happens when software fails, regardless of intent. The difference between software safety and software security is therefor the presence of an intelligent adversary bent on breaking the system. Software security for attacking the system is presented in this paper