• Journal of Advanced Navigation Technology
• /
• v.12 no.6
• /
• pp.681-690
• /
• 2008

The software reliability have to be improved as one major method to enhance the quality of developed software, and its defect is detected and modified through testing as a direct way to meet the purpose before releasing. Once its reliability grows up to the target and it is released to public. there may be operational reliability problem. The operational software reliability trend may be different depending on the condition whether it is universal or dedicated. And its reliability estimation is changed based on the condition if it follows uniform testing efforts or Weibull testing efforts. I study the operational reliability trend of dedicated software, applying two case testing efforts for the released item.

• Journal of Korea Multimedia Society
• /
• v.14 no.6
• /
• pp.766-774
• /
• 2011

We survey the software faults according to the software characteristics, so we can use it to make a software testcases. We divide the software fault according to six characteristics, functionality, usability, reliability, efficiency, maintainability, and portability. We analyze the software faults to find the common factors according to the software products, also we survey the number of faults according to six characteristics. We propose the method of weight application using the relative comparison of the number of faults.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2017.04a
• /
• pp.618-620
• /
• 2017

Currently, IoT mobile applications are growing fast in number and complexity. As a result, the applications quality issue became crucial, hence to ensure their quality a proper testing is highly required. Testing such mobile applications is always tedious, time-consuming and expensive. To cope with these issues, we propose a testing approach using activity diagram with data flow information. The main functionality of IoT applications is exposing the meaningful data obtained from the sensors to the users by doing a lot of analysis, comparison, and computation. Therefore, our focus is on identifying and selecting the most appropriate paths at which calculation is taking place and the paths at which predicate exists. In our case study, we have used a real-world IoT mobile application and identified a total of ten test paths with two predicate uses and two computation uses through an example. With applying only this four critical paths, we can adequately test the application's core functionalities while significantly reduce the testing effort and cost.

• Journal of KIISE:Software and Applications
• /
• v.34 no.3
• /
• pp.212-218
• /
• 2007

Not enough verification or enough design of test is not performing in many software developments organization as yet. Therefore, defects that can be detected and corrected during the beginning phases of development are usually found during dynamic testing, it is often observed that testing is inefficient compared to effort for testing. This study aims to suggest a method for effective testing through case study. It is useful in case of not verification and not enough design of test in the previous phase than coding. We show in a concrete way major activities that determine prioritization of testing and level of test case design through static testing, i.e. code review and analysis of code quality. And also we show role between test team and development team.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.18 no.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.

• Journal of KIISE:Software and Applications
• /
• v.36 no.5
• /
• pp.353-360
• /
• 2009

Software, once developed, has a long life and evolves through numerous additions and modifications because of the faults, the changes in user requirements, the changes in environments, and so forth. With the evolution of the software, assuring the quality of the software is getting more difficult because of numerous versions of the software. Meanwhile, regression testing has been used to support the software testing activities and assure acquiring appropriate quality through several versions of software. Regression testing, however, is too expensive because it requires lots of test cases executions and the number of test cases increases sharply as the software evolves. For this reason, several techniques are suggested to help conducting regression testing then test case prioritization technique is understood the most effective and efficient technique to support regression testing. In this paper, we propose an approach, Historical Value-Based Approach, which is based on the use of historical information to estimate the current cost and fault severity for cost-cognizant test case prioritization. As a result of the proposed approach, software testers who perform regression testing prioritize their test cases more effectively so that the test effectiveness of them can be improved in terms of APFDc.

• Journal of Power Electronics
• /
• v.12 no.5
• /
• pp.813-820
• /
• 2012

This paper presents the development of a software supported acquisition system for metrological verification and testing of the equipment for monitoring and analysis of the basic electrical power quality parameters. The described procedure consists of two functionally connected segments. The first segment involves generation of the reference three-phase voltage signals, including the possibility of simulation of the various power quality disturbances, typical for electrical power distribution networks. The second part of this procedure includes the real-time recording of power quality disturbances in three-phase distribution networks. The procedure is functionally supported by the virtual instrumentation concept, including a software application developed in LabVIEW environment and data acquisition boards NI 6713 and NI 9215A. The software support of this system performs graphical presentation of the previously generated and recorded signal waveforms. A number of the control functions and buttons, implemented on the virtual instrument front panels, are provided to adjust the basic signal acquisition, generation and recording parameters.

• Journal of Applied Reliability
• /
• v.2 no.1
• /
• pp.23-32
• /
• 2002

As the function of digital products gets diverse and complex, more than 30~40% job of software developing and testing group within its development cycle, concentrates on the software testing[1]. To cope with consumers'quickly changing needs, development cycle time gets short, and the number of model and test items increase steadily This is why automating software basic function and UI(User Interface) verification is needed [4][5][6]. This paper draws many strength and weakness defines Input/Output through integrating mobile phone, DVDP, PDA, and Black-Box (Intrusive (mobile) or Non-Intrusive(DVDP, PDA)) testing systematically, which brought above the 64% average of automation rate, and ensure 80% of test coverage [4][5][6].

• IEMEK Journal of Embedded Systems and Applications
• /
• v.9 no.6
• /
• pp.307-314
• /
• 2014

Recently, software reliability and safety issues are seriously considered since failures of embedded systems may cause the damages of human lifes. For verifying and testing embedded software, execution environment including sensors and actuators should be prepared in the actual plants or virtual forms on PC. In this paper, we provide the virtual prototype based code simulation techniques and testing framework on PC. Virtual prototypes are generated by combining the Adobe's Flash SWF images corresponding to the state machine of HW or environment components. Code simulation on PC is possible by replacing the device drivers into virtual drivers which connect to virtual prototypes. Also, testing is performed by controlling the states of virtual prototype and simulators. By using these tools, embedded software can be executed in the earlier development phase and the efficiency and SW quality can be enhanced.

• Journal of Korean Society for Quality Management
• /
• v.34 no.4
• /
• pp.133-138
• /
• 2006

In this paper, we propose a software reliability growth model (SRGM) based on the testing domain, which is isolated by the executed test cases. This model assumes an imperfect debugging environment in which new faults are introduced in the fault-correction process. We consider that the fault detection rate of NHPP model is changed in the proposed SRGM. We obtain the maximum likelihood estimate, and compare goodness-of-fit with another existing software reliability growth model.