• Journal of Information Processing Systems
• /
• v.8 no.1
• /
• pp.21-54
• /
• 2012

As we know every software development process is pretty large and consists of different modules. This raises the idea of prioritizing different software modules so that important modules can be tested by preference. In the software testing process, it is not possible to test each and every module regressively, which is due to time and cost constraints. To deal with these constraints, this paper proposes an approach that is based on the fuzzy multi-criteria approach for prioritizing several software modules and calculates optimal time and cost for software testing by using fuzzy logic and the fault tolerance approach.

• Journal of Information Processing Systems
• /
• v.7 no.3
• /
• pp.473-518
• /
• 2011

Software measurement is a key factor in managing, controlling, and improving the software development processes. Software quality is one of the most important factors for assessing the global competitive position of any software company. Thus the quantification of quality parameters and integrating them into quality models is very essential. Software quality criteria are not very easily measured and quantified. Many attempts have been made to exactly quantify the software quality parameters using various models such as ISO/IEC 9126 Quality Model, Boehm's Model, McCall's model, etc. In this paper an attempt has been made to provide a tool for precisely quantifying software quality factors with the help of quality factors stated in ISO/IEC 9126 model. Due to the unpredictable nature of the software quality attributes, the fuzzy multi criteria approach has been used to evolve the quality of the software.

• Journal of the Institute of Electronics Engineers of Korea TC
• /
• v.41 no.8
• /
• pp.69-78
• /
• 2004

In this paper, we estimated the exact software defect density to build up a suitable model that is closely related to the size of module in the probability model proposed by MD (Malaiya and Denton). To put it concretely, we predict that the software defect density using some practical data sets that are the outcomes from the system test performed our three projects for the types of distribution (exponential and geometric), per a unit of module, and the size of source line that have been recommended by KLOC(kilo-line-of-code). Then, we make comparison between our proposed defect density model and those examined real data.

• Proceedings of the Korean Powder Metallurgy Institute Conference
• /
• 2006.09a
• /
• pp.589-590
• /
• 2006

Based on the comparison of structures and properties of the HS6-5-2 high speed steels made with the powder injection moulding method, pressureless forming, compacting and sintering, and commercial steels made with the ASEA-STORA method, fine carbides spread evenly in the steel matrix were found in the structure of all tested high-speed steels in the sintered state. The steels made with the pressureless forming method are characteristic of the lowest sintering temperature and the highest density, resulting from the high carbon concentration coming from the binding agent degradation.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.590-606
• /
• 2009

We present a static analyzer that detects memory leaks in C programs. It achieves relatively high accuracy at a relatively low cost on SPEC2000 benchmarks and several open-source software packages, demonstrating its practicality and competitive edge against other reported analyzers: for a set of benchmarks totaling 1,777 KLOCs, it found 332 bugs with 47 additional false positives (a 12.4% false-positive ratio), and the average analysis speed was 720 LOC/sec. We separately analyze each procedure's memory behavior into a summary that is used in analyzing its call sites. Each procedural summary is parameterized by the procedure's call context so that it can be instantiated at different call sites. What information to capture in each procedural summary has been carefully tuned so that the summary should not lose any common memory-leak-related behaviors in real-world C program. Because each procedure is summarized by conventional fixpoint iteration over the abstract semantics ('a la abstract interpretation), the analyzer naturally handles arbitrary call cycles from direct or indirect recursive calls.