Volume 18, Number 3, November 2015
An Architecture Based Approach To Assess The Reliability And Performance Of Naval Platforms
- 1 Institute for Systems Studies and Analyses, Metcalfe House, Delhi 110054, India.
- 2 Reliability Engineering Center, Indian Institute for Technology, Kharagpur, West Bengal, India.
Abstract
With rapid advances in technology, there is an ever increasing need for deploying increasingly complex defence systems to be fielded in operation within costs, time and acceptable end-use functionality. The design of such large-scale military systems are done by integrating off-the-shelf sub-systems, and component-based systems along with indigenously developed systems, ensuring interoperability, functionality and performance. As the size and complexity of systems increases, the design problem goes beyond component and subsystem design or the design of algorithms and data structures of the computation in the sub-systems. The proliferation of software systems have triggered a transition from the hardware oriented military systems to systems that are controlled by software and more so towards embedded systems. In this paper, we extend and apply a framework based reliability assessment approach for a naval system architecture based on a scenario analysis. This approach enables us to infer the system reliability from aspect reliabilities based on the composition methods, allowing the application specific aspects to be added dynamically or upgraded at a later stage. The design of a system as a framework that can support plug-in application specific aspects is an effective way of simplifying the system and assuring high quality by making the specification of each aspect as well as composition component more amenable to rigorous analysis. In order to assess the performance of these systems in various real time warfare scenarios, a Discrete Time Markov Chain is constructed. This methodology can be applied in early design stages to allow the designer to understand the effect of operational degradation factors and their effects that occur over the days of war. The methodology has been effectively applied to carry out the sensitivity analysis of the sub-systems with respect to the scenario based operations and compute mission reliability.
I. Introduction
With rapid advances in technology, there is an ever increasing need for deploying increasingly complex defence systems to be fielded in operation within costs, time and acceptable end-use functionality. The design of such large-scale military systems are done by integrating off-the-shelf sub-systems, and component-based systems engineering along with indigenously developed systems, ensuring interoperability, functionality and performance. The proliferation of software systems have triggered a transition from the hardware oriented military systems to systems that are controlled by software and more so towards embedded systems. Military systems such as naval platforms, which are naval warships configured with advanced sensors, data processing units, weapons and features like stealth, high speed, full-sensor fusion systems necessitate the usage of hardware and software based system architectures. The complexity of such systems, such as a typical naval system is very high because of factors like real time operations, interconnections of many subsystems, interdependency of various subsystems and their interfaces. Specifying the reliability and assessing the performance of the overall system of systems structure is emerging as a new kind of a problem for such complex systems.
Prevalent approaches to characterize the behaviour of monolithic applications are inappropriate to model complex real time cyber-physical systems which are heterogeneous, and are built using a combination of components picked off the shelf, those developed in-house and those developed contractually which are interwoven as a system architecture. The existing approaches to predict the reliability of systems are applicable very late in the life-cycle and ignore information about testing and reliabilities of the components of which the system is made and do not take into consideration the architecture of the system. Earlier efforts in the area of architecture-based analysis have focused on the development of composite models which are quite cumbersome due to their inherent largeness and stiffness.
In this paper a methodology has been proposed to predict the performance and reliability of component-based large scale naval systems based on their architecture. The effect of sensitivity of the performance and reliability predictions to the changes in the parameters of individual modules is considered. The performance and reliability prediction as well as sensitivity analysis techniques have been illustrated taking a case study of naval systems.
II. ARCHITECTURE BASED APPROACH TO RELIABILITY ANALYSIS
As the size and complexity of systems increases, the design problem goes beyond component and subsystem design or the design of algorithms and data structures of the computation in the sub-systems. Military architectural frameworks are powerful tools for enabling system architects to define, design, plan and implement architectures. The application of architecture based methodology at the design stage of complex, real time defence systems has been well documented [1]. An effective approach for designing systems is by application oriented frameworks where each framework has common core components that are reused over all applications in a product-line and plug-in aspects that can be added, upgraded or removed dynamically to meet the varying requirements of missions. Each plug in aspect is designed to be certifiable independently of other aspects or the framework. A framework consists of two sets of independent aspects and one composition component donated by {S, A, C}. Here S = {s1, s2, s3, s4 ……. sn} denotes the set of fixed or static framework aspects that address functional as well as non-functional requirements. Requirement imposed on these aspects is that they are independent of each other. A = { a1, a2, a3, a4 ……. an } denotes set of plug-and-play application components that can be dynamically added to or removed from the framework. These aspects implement specific features or functional aspects of the application. Component C denotes the composition component [2].
The quality Q of the aspect is the value provided to the user by correct operation of that aspect. The term quality or quality of service provided by the system is analogous to performance, composition can take several forms such as montage, selection, filter, nesting and fusion.
Montage. Here, the output of each component is evident in the final system output which forms a specified montage of the outputs of all the aspects. This composition makes the success or failure of each aspect directly visible in the final output. Reliability and quality are given as:
R(t) = { r1(t), r2(t), r3(t), r4(t) … rn(t) } – Reliability vector of Application Aspects
Q = { q1, q2, q3, q4 … qn } – Quality Vector
C(Q) – Composition Expression for System Quality
C[QR(t)] – Average Quality of the system output
QR(t) = { q1 x r1(t), q2 x r2(t), q3 x r3(t), q4 x r4(t) ... qn x rn(t) }
Selection. Here, all the aspects process the same set of inputs and the output of one of the aspects is selected to be the output of the system.
P = { p1, p2, p3, p4….. pn} – Probability vector of Application Aspects that a particular aspect is selected
Ri – Reliability of the Aspect Ai
Fusion. In this case, the composition component processes all the outputs and generates the final system output.
Nesting. This occurs in pipeline processing where an aspect has an inverse aspect, such as coder and decoder aspects, encryption and decryption routines, compression and decompression routines.
Filtering. This also occurs in pipeline processing where each aspect processes the output of the previous stage and removes or adds some information while preserving other information.
The methodology gives the system output in the form of Quality in addition to Reliability. Quality is similar to a reward function similar to performance of the system which is added provided the aspect is doing a correct operation. In case the aspect fails to perform correct operation, the Quality of the aspect will be given a value of 0. This will in turn result in the degraded performance which is reflected in the mission reliability calculation.
IV. Conclusions and Discussion
In this paper, we explored the techniques for reliability and performance based design of architectures for military systems. Prevalent approaches to characterize the behaviour of monolithic applications are inappropriate to model complex real time systems which are heterogeneous, and are built using a combination of components picked off the shelf, those developed in-house and those developed contractually which are interwoven as architecture. These approaches to predict the reliability of systems are applicable very late in the life-cycle and ignore information about testing and reliabilities of the components of which the system is made, and do not take into consideration the architecture of the system. Development of techniques to characterize the behaviour of such component-based systems based on their architecture is then absolutely essential. Earlier efforts in the area of architecture-based analysis have focused on the development of composite models which are quite cumbersome due to their inherent largeness and stiffness. A methodology has been proposed to predict the performance and reliability of component-based large scale naval systems based on their architecture. The effect of sensitivity of the performance and reliability predictions to the changes in the parameters of individual modules is considered. The performance and reliability prediction as well as sensitivity analysis techniques have been illustrated taking a case study of naval systems.
In the proposed methodology, a framework based reliability assessment approach for decomposing and implementing a naval system based on a particular scenario is presented and evaluation of the same in form of architectures carried out. The main constructs for evaluating the reliability of architectures represented by unified modelling language are montage, filtering, selection and fusion. Using these constructs, the architecture based reliability models are assessed and this methodology is illustrated using a naval platform system as a case study. The approach enables the system reliability to be rigorously inferred from aspect reliabilities based on the composition methods, allowing the application specific aspects to be added dynamically or upgraded at a later stage. The design of a system as a framework that can support plug-in application specific aspects is an effective way of simplifying the system and assuring high quality by making the specification of each aspect as well as composition component more amenable to rigorous analysis. It helps the designer to carry out reliability apportionment if the desired reliability for the mission is not met at the design stage itself. The methodology also helps in defining the reliability goals for the system designer.
In order to assess the performability of these systems in various real time scenarios, a Discrete Time Markov Chain is constructed. This methodology can be applied in early design stages to allow the designer to understand the effect of operational degradation factors due to the usage profile of the entire system in a particular scenario during actual usage. Such a scenario based operational analysis can be carried out keeping the reliability constraints of the sub-systems in mind by the application of Markov chain. The methodology can be effectively applied to carry out the sensitivity analysis of the sub-systems with respect to the scenario based operation. The criticality of a particular subsystem in respect to the system functioning goes a long way in giving the designer an insight into how effective the system has been designed. This also helps the designer to identify the weak subsystems, wherein measures can be taken to improve the reliability of the sub-system at the design stage itself. The methodology proposed can be effectively used to carry out the what-if reliability and performance analysis and aid in apportionment for the subsystems.
(b) The study carried out takes in to consideration the reliability and performance of the system for carrying out the architecture based evaluation. Some of the other criteria which can be explored are safety, availability, maintainability and sustainability.
(c) The study presents one of the possible techniques for modelling of architecture based systems for calculation of reliability and performance of the system. Other possible techniques for such evaluations can be explored and their applications for architecture based assessment can be evaluated.
(d) Another notable feature for which the study can be utilised is the application of modelling and simulation techniques for reliability and performance evaluation based acquisition.
Appendix A
Description of various states of the DTMC
| State No | State abcde | Description of the State |
|---|---|---|
| 1 | 00000 | Sonar, CIC, ASWFCS, Torpedo and ASW Rocket in Idle State. |
| 2 | 10000 | Sonar in Functional State ie Sonar is transmitting and detecting all available targets. |
| 3 | 11000 | Sonar in Functional State. On detection of Target, the target details are sent to CIC and CIC comes to Functional state. |
| 4 | 20000 | Sonar in degraded state, the Sonar will not be able to track all the targets completely. |
| 5 | 30000 | Sonar is in failed state. It is not able to transmit. |
| 6 | 21000 | Sonar in Degraded state. On detection of Target, the target details are sent to CIC and CIC comes to Functional state. |
| 7 | 22000 | Sonar is in Degraded State. The target is detected but on receiving the target details, the CIC goes to failed state. |
| 8 | 12000 | Sonar in Functional State. On detection of target, the details are sent to the CIC but CIC goes to failed state and is unable to process the targets. |
| 9 | 11100 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. |
| 10 | 21100 | Sonar is in degraded state. The detected target details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. |
| 11 | 11110 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is Torpedo and firing data is fed to it. |
| 12 | 11101 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is ASW Rocket and firing data is fed to it. |
| 13 | 21110 | Sonar is in degraded state. The detected target details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is Torpedo and firing data is fed to it. |
| 14 | 21101 | Sonar is in degraded state. The detected target details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is ASW Rocket and firing data is fed to it. |
| State No | State abcde | Description of the State |
| 15 | 11120 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is Torpedo, firing data is fed to it and Torpedo is fired. |
| 16 | 11102 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is ASW Rocket, firing data is fed to it and ASW Rocket is fired. |
| 17 | 11111 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to ASW rockets and Torpedo. |
| 18 | 11121 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to both the weapons and torpedo is fired. |
| 19 | 11112 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to both the weapons and ASW rocket is fired. |
| 20 | 11122 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to both the weapons and both the weapons are fired. |
| 21 | 21120 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is Torpedo, firing data is fed to it and Torpedo is fired. |
| 22 | 21102 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the weapon selected is ASW Rocket, firing data is fed to it and ASW Rocket is fired. |
| 23 | 21111 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to the weapons. |
| State No | State | Description of the State |
| 24 | 21121 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to both the weapons and torpedo is fired. |
| 25 | 21112 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to both the weapons and ASW rocket is fired. |
| 26 | 21122 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS which comes to Functional state and does the Firing data calculation. After processing by ASWFCS, the firing data is fed to both the weapons and both the weapons are fired. |
| 27 | 11200 | Sonar in Functional State. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS. The ASWFCS being in failed state, no firing data calculation is done and weapon cannot be fired on the target. |
| 28 | 21200 | Sonar in degraded state. On detection of targets, details are sent to CIC which is in functional state and starts processing the targets and sends the data to the ASWFCS. The ASWFCS being in failed state, no firing data calculation is done and weapon cannot be fired on the target. |
| 29 | MC | Mission Complete. Target is destroyed. |
| 30 | MF | Mission Fail. Target is not destroyed. |
References
[1] F. Bastani, S. Kim, “Systematic Reliability Analysis of a Class of Application-Specific Embedded Software Frameworks”, IEEE transactions on Software Engineering, Vol. 30, No. 4, April 2004.
[2] J. Voas, A. Ghosh, G. McGraw, and K. Miller. “Glueing together software components: How good is your glue?”, Proc. of Pacific Northwest Software Quality Conference, Portland, OR, October 1996.
[3] S.S. Gokhale, K.S. Trivedi, “Reliability Prediction and Sensitivity Analysis Based on Software Architecture”, Proceedings of the 13th International Symposium on Software Reliability Engineering (ISSRE’02), 2002. Fundamentals of Naval Weapon Systems, Weapons and System Engg Department, United States Naval Academy.
[4] F. Bastani, S. Kim, “Reliability Assessment of Framework-Based Distributed Embedded Software Systems”, Proceedings of the 13th International Symposium on Software Reliability Engineering (ISSRE’02), 2002.
[5] B. Littlewood, "Theories of software reliability: How good are they and how can they be improved?" IEEE Transactions on Software Eng., vol.SE-6, pp. 489-500, 1980.
[6] J. Voas, A. Ghosh, G. McGraw, and K. Miller. “Glueing together software components: How good is your glue?”, Proc. of Pacific Northwest Software Quality Conference, Portland, OR, October 1996.
[7] S. Gokhale, P. Kishor, “Reliability Prediction and Sensitivity Analysis Based on Software Architecture of CSE CACC”, Proceedings of the 13th International Symposium on Software Reliability Engineering (ISSRE’02), 2002.
[8] Katerina Goeva P., Kishore Trivedi, “Architecture Based Software Reliability”, Department of Electrical & Computer Engineering, Duke University, (IPDS'98), 13-22, 1998.
[9] S Gokhale, K. Trivedi, “Structure based software reliability prediction”, Proc 5th International Conference in Advanced Computing (ADCOMP 97), 447-452, 1997.
[10] B. Littlewood, “Software reliability model for modular program structure”, IEEE Transactions on Reliability, 28 (3), 241-246 (1979).
[11] R.C. Cheung, “A user oriented software reliability model”, IEEE Transactions on Software Engineering, 6 (2), 118-125 (1980).
[12] J.C. Laprie, “Dependability evaluation of software systems in operation”, IEEE Transactions on Software Engineering, 10(6), 701-714, (1984).
[13] P. Kubat, “Assessing reliability of modular software”, Operation Research Letters, 8 35- 41, (1989).
[14] S. Gokhale, W.E. Wong, K. Trivedi, J.R. Horgan, “An analytical approach to architecture based software reliability prediction”, Proc. 3rd International Computer Performance & Dependability Symposium, (IPDS 98), 13-22, 1998.
[15] S.M. Yacoub, B. Cukic, H.H. Ammar, “Scenario based reliability analysis of component based software”, Proc. 10th International Symp. on Software Reliability Engineering, ISSRE- 99, 22-31, 1999.
[16] F. Bastani, S. Kim, “Systematic Reliability Analysis of a Class ofApplication-Specific Embedded Software Frameworks”, IEEE Transactions on Software Engineering, Vol. 30, No. 4, April 2004.
[17] C. Hofmeister, R.L. Nord, D. Soni, “Describing Software Architecture with UML”, Proceedings of the First Working IFIP Conference on Software Architecture, 1999.
[18] C. Dabrowski, F. Hunt, “Using Markov chain and graph theory concepts to analyze behavior in complex distributed systems”, US National Institute of Standards & Technology, 2003.
[19] M. Karri, An architecture based approach to assess the reliability and performance of naval platforms, Masters Thesis, Indian Institute of Technology, Kharagpur, 2015.









