• 제목/요약/키워드: software test

검색결과 3,619건 처리시간 0.028초

A Development Environment for Embedded Software

  • Kang, Byeong-Do
    • 한국정보기술응용학회:학술대회논문집
    • /
    • 한국정보기술응용학회 2005년도 6th 2005 International Conference on Computers, Communications and System
    • /
    • pp.39-44
    • /
    • 2005
  • In recent years, embedded systems have become so complex and the development time to market is required to be shorter than before. As embedded systems include more functions for new services, embedded software gradually grow in size, and development costs and time are increasing. In order to overcome this serious matter, we need a customized design and test technique for embedded software. In this paper, we present a software architecture style for embedded software. It facilitates the composition of reusable functions and helps developers to reduce development time. Because the costs associated with revealing errors of embedded software in applications are rising. we propose a test method and tools for target environments.

  • PDF

Process Improvement for Quality Increase of Weapon System Software Based on ISO/IEC/IEEE 29119 Test Method

  • Park, Byung Hoon;Seo, Yeong Geon
    • 한국컴퓨터정보학회논문지
    • /
    • 제23권12호
    • /
    • pp.115-122
    • /
    • 2018
  • As the proportion of software in weapon systems increases, the impact of software on the overall system is growing. As a result, software quality management becomes important, and related regulations and work manuals for quality assurance activities at each stage in the R & D process are becoming more sophisticated. However, due to the characteristics of the weapon system software that is developed as a customized form for the purpose of a specific mission, there are limits to specifying and definitizing the detailed requirements (upper and lower level) according to various operational concepts during the development process. Due to this, software modification (patch change, shape change due to upgrade, etc.) occurs on account of many defects and performance improvement in the mass production and operation stage after the development is completed. In this study, we analyze the characteristics of these weapon system softwares and propose quality improvement methods based on ISO / IEC / IEEE 29119 test method.

변증 능력 평가 소프트웨어의 구현 (Development of the Software to test Pattern Diagnosis Ability in Oriental Medicine)

  • 김기왕;장재순
    • 대한한의진단학회지
    • /
    • 제14권1호
    • /
    • pp.70-78
    • /
    • 2010
  • Objectives : To qualify or enhance the diagnostic ability of students in Oriental Medicine, so called standardized patients are ideal modality, but because it's a man-based method, more convenient tools are required. Computer-based diagnostic ability test program gives effective way for the very purpose. So we made a pilot software evaluating Pattern Identification ability in Oriental Medicine. Methods and Materials : The pilot software was coded with Microsoft's EXCEL VBA. 87 names of Zheng (Symptom Pattern) and 674 names of symptom (including some signs) are adopted from the former standardization works conducted by Korean Institute of Oriental Medicine (KIOM) in 1996. Results : Compared with some manned modalities to test Pattern Identification ability, the test by this software shows superiority in convenience and objectivity. Conclusion : This software is world's first program to perform computer-based evaluation of Pattern Identification in Oriental Medicine, and it gives effective way to complement both written test and manned clinical performance test (CPX).

소프트웨어 결함 발견 및 제거 노력 기반 신뢰성 추정 모델 (Software Fault Detection and Removal Effort-based Reliability Estimation Model)

  • 강명묵;구태완;백종문
    • 한국정보과학회논문지:소프트웨어및응용
    • /
    • 제37권7호
    • /
    • pp.536-547
    • /
    • 2010
  • 최근 소프트웨어는 고성능의 많은 기능을 제공해야 하기 때문에 그 중요성이 증가할 뿐만 아니라 복잡도 또한 증가하고 있다. 그러므로 신뢰할 만한 소프트웨어를 개발하는 것이 중요한 이슈가 되고 있다. 신뢰할 만한 소프트웨어를 개발하기 위해서는 신뢰성을 초기단계에서부터 관리해야 할 필요성이 있지만 대부분 신뢰성 추정 모델의 경우 시스템 또는 운영 테스트 단계에서 주로 사용되고 있다. 신뢰성 높은 소프트웨어를 개발하기 위해서는 초기 테스트 단계에서부터 개별 유닛의 신뢰성을 관리할 필요성이 있기에 이 단계에서의 특징을 반영해야 한다. 그러나 초기 테스트 단계에서는 개발자와 테스터가 분리되는 것이 아니라 개발자가 테스트뿐만 아니라 디버그까지 함께 수행을 하게 된다. 그렇기 때문에 테스트 시간과 디버그 시간을 모두 고려하는 신뢰성 추정 모델이 필요하다. 본 논문에서는 초기 테스트 단계에서부터 개별 유닛의 신뢰성 관리를 지원하고자 새로운 신뢰성 모델을 제안하였다. 그리고 실제 산업에서 수집된 데이터를 이용하여 제안한 모델이 실제 데이터와 얼마나 일치하는지 그리고 기존 모델과 어떤 차이를 보이는지를 확인하기 위한 실험을 수행하였다.

UML 2.0 모델 기반의 교전통제 소프트웨어 아키텍처 개발 (Development of the Engagement Control Software Architecture Based on UML 2.0 Model)

  • 유명환;배정일;신진화;조길석
    • 한국군사과학기술학회지
    • /
    • 제10권4호
    • /
    • pp.20-29
    • /
    • 2007
  • The engagement control software embedded in the weapon control computer of the fire control center for air defense missile system is large-scale real-time software. The use of typical software development methodologies is not appropriate to develop such large-scale embedded software in terms of reusability, reliability, and productivity for the reason that it is significantly complicated, and highly dependent on hardware platforms and developers. In this paper, a model-based software architecture using components based on UML 2.0 for the engagement control software is presented in order to solve these problems. This software architecture is verified using the black-box test, the scenario-based test, and the Ethernet packet monitoring test methods. The results demonstrate that the developed software architecture can be employed to enhance reusability, maintainability, and productivity of large-scale embedded software.

기능 안전 관점에서의 의료기기 소프트웨어 신뢰성 평가 방법에 관한 연구 (Study on Reliability Assessment for the Medical Device Software from the Viewpoint of Functional Safety)

  • 김성민;고병각;도경훈;김혜진;함중걸
    • 한국신뢰성학회지:신뢰성응용연구
    • /
    • 제16권3호
    • /
    • pp.216-223
    • /
    • 2016
  • Purpose: This paper suggests the procedure to enhance the reliability of the software of the medical device that is to cure, treat, diagnose, and prevent a disease or an abnormal health conditions. Methods: After test requirements are classified by the software requirements specification for safety and backgrounds, reliability assessment methods are suggested. Results: Verification and validation for function and safety can be performed whether the medical device software are implemented as intended. Conclusion: Procedure on the static analysis, unit test, integration test, and system test are provided for the medical device software.

SW 테스트 자동화 구현을 위한 핵심성공요인에 관한 연구 (Critical Success Factors for Implementing Software Test Automation)

  • 김성용;민대환;임성택;채봉수
    • Journal of Information Technology Applications and Management
    • /
    • 제27권6호
    • /
    • pp.101-116
    • /
    • 2020
  • This study attempts to derive critical success factors and prioritize activities for implementing the automation of software test. Software testing proceeds in five steps of test plan, test case design, test scripting & test environment setup, test execution & evaluation, and test closure. From the literature, twenty influence factors in the five steps were identified. Focus Group Interviews with ten experts in software testing selected fourteen factors on the basis of importance and feasibility. Some factors were further divided to clarify their meanings and the number of influence factors finally became twenty one. A survey on the influence factors was conducted with 75 IT professionals. An importance-feasibility analysis was applied to the survey responses and classified the influence factors into four groups of essential factors, critical factors, low priority factors, and minimal factors. Essential factors include objectives for test automation, strategies for test automation, test automation training, test automation education, setting up test automation environment, setting up test environment, test automation tool selection. Critical factors include management's continued support, management's continued interest, role of automation engineers, and skills of automation engineers. This result suggests that a lot of efforts should be put into SW test plan for the successful SW test automation and SW automation should proceed in consideration with the priorities and resource consumption.

A UML-based Approach towards Test Case Generation and Optimization

  • Shahid Saleem;Saif U. R. Malik;Bilal Mehboob;Roobaea Alroobaea;Sultan Algarni;Abdullah M. Baqasah;Naveed Ahmad;Muhammad Hasnain
    • KSII Transactions on Internet and Information Systems (TIIS)
    • /
    • 제18권3호
    • /
    • pp.633-652
    • /
    • 2024
  • Software testing is an important phase as it ensures the software quality. The software testing process comprises of three steps: generation, execution, and evaluation of test cases. Literature claims the usage of single and multiple 'Unified Modeling Language' (UML) diagrams to generate test cases. Using multiple UML diagrams increases test case coverage. However, the existing approaches show limitations in test case generation from UML diagrams. Therefore, in this research study, we propose an approach to generate the test cases using UML State Chart Diagram (SCD), Activity Diagram (AD), and Sequence Diagram (SD). The proposed approach transforms UML diagrams into intermediate forms: SCD Graph, AD Graph, and SD Graph respectively. Furthermore, by integrating these three graphs, a System Testing Graph (STG) is formed. Finally, test cases are identified from STG by using a traversal algorithm such as Depth First Search (DFS) that is an optimization method. The results show that the proposed approach is better compared to existing approaches in terms of coverage and performance. Moreover, the generated test cases have the ability to detect faults at the unit level, integration, and system level testing.

A study on Software Maintenance of Domestic Weapon System by using the Automatic Test Equipment

  • Chae, Il-Kwon
    • 한국컴퓨터정보학회논문지
    • /
    • 제27권1호
    • /
    • pp.51-59
    • /
    • 2022
  • 무기체계의 소프트웨어 기능 의존성이 높아짐에 따라 소프트웨어는 무기체계를 제어하는 핵심요인으로 자리매김하였다. 또한 국내/외적으로 소프트웨어 개발이 중요해지면서 소프트웨어에 대한 검증이 쟁점이 되고 있다. 최근 방산시장에서 이러한 점을 인식하고 무기체계 소프트웨어 유지보수를 위한 방안을 요구하고 있다. 본 논문에서는 자동화시험장비(Automatic Test Equipment, ATE)를 이용하여 무기체계 소프트웨어 유지보수 방안을 제시한다. 그 구체적인 방안은 시뮬레이터를 활용하여 소프트웨어 기능을 확인하고 고장 케이스를 식별하는 것이다. 이는 개발업체가 고장 케이스를 식별하는 시간을 줄임으로써 무기체계 총 고장정비시간(Total Corrective Maintenance Time, TCM)을 감소시킬 수 있는 효과적인 방법이다. 제안된 소프트웨어 유지보수 기능 추가된 자동화시험장비(ATE)는 기존 대비 정비도 및 운용가용도(OA)가 개선됨을 입증하였다.