SYSTEM RELIABILITY OF TWO NON-IDENTICAL UNITS SYSTEM WITH COMMON CAUSE SHOCK FAILURE AND STATE DEPENDENT RATES
Madhu Jain* and Ashish Mishra*
Abstract
The presence of common cause shock failure in the reliability analysis of a two units system is analyzed. This paper takes care of states dependent rates in case of statistically independent and noniidentical two components system. Formulae have been developed for both time dependent and stady state availability and frequency of lethal common cause shock (LCCS) failure as well as non-lethal common cause (NLCCS) failure in addition to individual failure. The Markov model is explored to steady the impact of lethal and non-lethal common cause shock failure on availability and system failure. An inverse Laplace transform is used to solve the simultaneous differential difference equations governing the model. The performances LCCS for both time dependent and steady state availability are obtained. Numerical experiments have also been performed to validate the analytical results and examine the sensitivity parameters.
Index-terms - System reliability, two non-identical components. Availability, Frequency, LCCS and NLCCS failure State dependent rates.
SOME OBSERVATIONS ON RELATIONSHIP BETWEEN MAINTAINABILITY AND OBJECT-ORIENTED ANALYSIS
Anil Kumar Tripathi*, Sanjay K. Gupta** and Manjari Gupta*
Abstract
the object oriented analysis (OOA) gives emphasis only on conceptual picture of the system to be built as objects. Complexity in expressing requirements during analysis modeling is a prime cause for maintenance. This paper carries out the 'don'ts" dos of the analysis process to enhance the maintainability of the object oriented system. We try to define relationship among all the four maintenance activities (corrective, adaptive, preventive, and perfective maintenance) and nine elements (noise, silence, overspecification, contradiction, ambiguous, forward reference, dilemma, inconsistentvocabulary and non-clearly) that are generally drawbacks attached to use of natural language during analysis phase. This relationship will help an analyst to perform analysis in such a way that would result in enhanced maintainability of the software system.
key words: Object-oriented Analysis, Natural Language, Software Maintainability.
NEED TO REDEFINE THE TESTING PROCESS FOR COMPONENT BASED SOFTWARE
A. K. Tripathi*, Ratneshwer*, and Manjari Gupta*
Abstract
The importance of software testing and its implications with respect to software quality can not be over emphasized. Testing process of Component Based Software has its own challenge, because its development process, system life cycle, coding style etc. are very different from traditi8onal software development. The testing methods must be looked into a fresh to consider problems and possibilities of their applicability may call for redefinition. In CBSE, there will be parallel testing process; one for testing an individual component and other is testing of a Component Based System. Adding of components in system are runtime, unavailability of components source code, modification affect of component on whole system etc. leads the requirement of new testing requirements. These newer issue needs to be addressed for any testing methodology of CBSE. The proposed research work aims at identifying software testing process and concepts that need redefinition in the context of CBSE. The idea is to evaluate whether the t5esting methodologies for conventional software development can be used for CBSE or there is a need to propose and develop newer methodologies for the purpose. The issue related to software testing is important because the slow rate of the practice of CBSE may be result of the use of the software testing practice meant for non CBSE base software development.
Key Words: Software testing, Component Based Software, Compensability.
Introduction
Software testing is an important and resource demanding activity. Traditional Software Testing methodologies have been developed keeping in mind the traditional software development methodologies. Component Based Software Engineering is different from traditional software engineering in many ways. This focus us to consider the requirement of redefinition of testing processes for Component Based Software. Here, first of all, the software testing itself and then the Component Software Based Engineering has been a scribed, in sections 1.1 and 1.2 and then section 2, an attempt has been made to show the difference between traditional software testing process and Component Based Software testing process, by comparing the test cases, the unit testing, the integration testing, and the system testing. In section 2.5, it is shown that only integration of components is not sufficient, one also have to think that whether the unit “component“is composable into any new system or not? In last subsection 2.6, some comparison between testability of these two testing process are described. The concluding section summaries the idea and its influences.
Conclusion
The discussion above clearly suggests the need for fresh look at the testing process for Component Based Software Engineering. Component Based Software is developed using methodology that does not match with the general software development methodology and hence the need for considering the testing process a fresh. The very fact that a component testing philosophy and methodology. The integration of components in a system also has to be considered very carefully. This work considers these peculiar requirements elaborating the specific needs for redefining the testing process for component based software systems.
|
