Search

Issues such as test case revalidation, test execution failure identification, fault identification, modification dependency, fault mitigation and test case dependency are essential for an industrial environment in applying regression testing. […]

Authors in this special section describe knowledge gained from applying object-oriented techniques, tools, and environments to a variety of software development projects. The stakes are increasing every day as more […]

The article presents a transition plan based on lessons learned from real-world experience and recommends several effective managerial practices. Object oriented software engineering (OOSE) introduces a software development model based upon the way human think. OOSE promises remarkable benefits. It allows software components to be readily reused, potentially saving substantial development costs. Also, OOSE reduces the scope and side effects of software changes, potentially saving substantial maintenance costs. In spite of these potential benefits, many software development groups still hesitate to use OOSE. Many of these groups are fully occupied by their current software development work and fear being overwhelmed if they introduce a new development paradigm. Other groups, interested in OOSE, do not know where to begin. To make matters worse, these groups had additional problems such as their most recent development efforts were in most cases inconsistent and usually behind schedule. Fixing one problem frequently created others.

This article presents expert system testing as the comparison between by-products by each life-cycle phase and implementation. An expert life system life cycle consists of the problem-specification phase, solution-specification phase, high-level design phase and testing phase. Problem specification is a description of the problem being solved. Black-box testing methods have been shown to be effective in identifying faults for programs with large fault-prone regions. Therefore, random testing should be effective in detecting problem-specification faults. Solutions specification describes how to satisfy requirements specified in problem specification. Design specifies the structure, control and data-flow information of different modules and the interactions between different modules in the design of the system. Implementation faults are due to simple mistakes made during implementation, such as initializing with wrong values, using an incorrect attribute or typographical mistakes. To evaluate these propositions, life-cycle mutation testing is used.