[1] J.-C., Laprie, “Dependable computing and fault-tolerance,” in Proc. 15th Int. Symp. on Fault-Tolerant Computing (FTCS-15), 1985, pp. 2–11.Google Scholar

[2] A., Avizienis, J., Laprie, B., Randell, and C., Landwehr, “Basic concepts and taxonomy of dependable and secure computing,” IEEE Transactions on Dependable and Secure Computing, vol. 1, no. 1, pp. 11–33, 2004.Google Scholar

[3] K. S., Trivedi, D. S., Kim, A., Roy, and D., Medhi, “Dependability and security models,” in Proc. 7th Int. Workshop on Design of Reliable Communication Networks (DRCN 2009), 2009, pp. 11–20.Google Scholar

[4] IEC 60050, International Electrotechnical Vocabulary: Chapter 191: Dependability and Quality of Service. IEC Standard No. 60050-191, 2nd edn., 2001.

[5] A., Avizienis and J.-C., Laprie, “Dependable computing: From concepts to design diversity,” Proceedings of the IEEE, vol. 74, no. 5, pp. 629–638, 1986.Google Scholar

[6] B., Parhami, “From defects to failures: A view of dependable computing,” SIGARCH Comput. Archit. News, vol. 16, no. 4, pp. 157–168, Sep. 1988.Google Scholar

[7] D. P., Siewiorek and R. S., Swarz, Reliable Computer Systems: Design and Evaluation, 3rd edn. A K Peters/CRC Press, 1998.

[8] M., Grottke and K., Trivedi, “Fighting bugs: Remove, retry, replicate, and rejuvenate,” Computer, vol. 40, no. 2, pp. 107–109, 2007.Google Scholar

[9] D., Chen, S., Garg, and K. S., Trivedi, “Network survivability performance evaluation: A quantitative approach with applications in wireless ad-hoc networks,” in Proc. 5th ACM Int. Workshop on Modeling Analysis and Simulation of Wireless and Mobile Systems, 2002, pp. 61–68.Google Scholar

[10] F., Cristian, “Understanding fault-tolerant distributed systems,” Commun. ACM, vol. 34, no. 2, pp. 56–78, Feb. 1991.Google Scholar

[11] M., Grottke, A., Nikora, and K., Trivedi, “An empirical investigation of fault types in space mission system software,” in IEEE/IFIP Int. Conference on Dependable Systems and Networks (DSN), 2010, pp. 447–456.Google Scholar

[12] J., Musa, “Software reliability-engineered testing,” Computer, vol. 29, no. 11, pp. 61–68, 1996.Google Scholar

[13] B. B., Madan, K., Goševa-Popstojanova, K., Vaidyanathan, and K. S., Trivedi, “A method for modeling and quantifying the security attributes of intrusion tolerant systems,” Performance Evaluation, vol. 56, pp. 167–186, 2004.Google Scholar

[14] F. B., Schneider, “Blueprint for a science of cybersecurity,” The Next Wave, vol. 19, no. 2, pp. 47–57, 2012.Google Scholar

[15] M., Tortorella, “Service reliability theory and engineering I: Foundations,” Quality Technology & Quantitative Management, vol. 2, no. 1, pp. 1–16, 2005.Google Scholar

[16] E., Bauer and R., Adams, Reliability and Availability of Cloud Computing. Wiley-IEEE Press, 2012.

[17] K. S., Trivedi, D., Wang, and J., Hunt, “Computing the number of calls dropped due to failures,” in Proc. IEEE 21st Int. Symp. Software Reliability Engineering (ISSRE), 2010, pp. 11–20.Google Scholar

[18] FAA, Certification Maintenance Requirements, Advisory Circular num 25-19, Nov. 28, 1994.

[19] FAA, System Design and Analysis, Advisory Circular/Advisory Material Joint 25.1309, May 24, 1996.

[20] A., Ramesh, D., Twigg, U., Sandadi, and T., Sharma, “Reliability analysis of systems with operation-time management,” IEEE Transactions on Reliability, vol. 51, no. 1, pp. 39–48, 2002.Google Scholar

[21] K., Hjelmgren, S., Svensson, and O., Hannius, “Reliability analysis of a single-engine aircraft FADEC,” in Proc. Annual Reliability and Maintainability Symposium, 1998, pp. 401–407.Google Scholar

[22] A., Bobbio, D., Codetta-Raiteri, L., Portinale, A., Guiotto, and Y., Yushtein, “A unified modelling and operational framework for fault detection, identification, and recovery in autonomous spacecrafts,” in Theory and Application of Multi-Formalism Modeling, eds. M., Gribaudo and M., Iacono. IGI-Global, 2014, ch. 11, pp. 239–258.

[23] W. E., Smith, K. S., Trivedi, L., Tomek, and J., Ackaret, “Availability analysis of blade server systems,” IBM Systems Journal, vol. 47, no. 4, pp. 621–640, 2008.Google Scholar

[24] K., Vaidyanathan and K. S., Trivedi, “A comprehensive model for software rejuvenation,” IEEE Transactions Dependable and Secure Computing, vol. 2, no. 2, pp. 124–137, Apr. 2005.Google Scholar

[25] IBM'sWebSphere Application Server (WAS). [Online]. Available: www.ibm.com/software/ webservers/appserv/was/

[26] BEA's Web Logic Server. [Online]. Available: www.bea.com/content/products/weblogic/ server/

[27] S., Mondal, X., Yin, J., Muppala, J. Alonso, Lopez, and K. S., Trivedi, “Defects per million computation in service-oriented environments,” IEEE Transactions on Services Computing, vol. 8, no. 1, pp. 32–46, Jan. 2015.Google Scholar

[28] Back-To-Back User Agent (B2BUA) SIP Servers Powering Next Generation Networks – A Functional and Architectural Look At Back-To-Back User Agent (B2BUA) SIP Servers. RADVISION – an Avaya Company. [Online]. Available: www.radvision.com

[29] V., Kulkarni, V., Nicola, and K., Trivedi, “The completion time of a job on a multi-mode system,” Advances in Applied Probability, vol. 19, pp. 932–954, 1987.Google Scholar

[30] P., Chimento and K., Trivedi, “The completion time of programs on processors subject to failure and repair,” IEEE Transactions on Computers, vol. 42, pp. 1184–1194, 1993.Google Scholar

[31] A., Bobbio and M., Telek, “Task completion time in degradable systems,” in Performability Modelling: Techniques and Tools, eds. B. R., Haverkort, R., Marie, G., Rubino, and K. S., Trivedi. Wiley, 2001, ch. 7, pp. 139–161.

[32] E., Zio, “Challenges in the vulnerability and risk analysis of critical infrastructures,” Reliability Engineering & System Safety, vol. 152, pp. 137–150, 2016.Google Scholar

[33] E., Henley and H., Kumamoto, Reliability Engineering and Risk Assessment. Prentice Hall, 1981.

[34] IEC 61508, Functional Safety of Electrical/Electronic/Programmable Electronic Safety-Related Systems. IEC Standard No. 61508, 2011.

[35] D. G., Nguyen and D. N. P., Murthy, “Optimal preventive maintenance policies for repairable systems,” Operations Research, vol. 29, no. 6, pp. 1181–1194, 1981.Google Scholar

[36] D., Chen and K., Trivedi, “Analysis of periodic preventive maintenance with general system failure distribution,” in Proc. Pacific Rim Int. Symp. on Dependable Computing (PRDC), 2001, pp. 103–107.Google Scholar

[37] D., Chen and K. S., Trivedi, “Closed-form analytical results for condition-based maintenance,” Reliability Engineering & System Safety, vol. 76, no. 1, pp. 43–51, 2002.Google Scholar

[38] Y., Huang, C. M. R., Kintala, N., Kolettis, and N. D., Fultoni, “Software rejuvenation: Analysis, module and applications,” in Proc. Int. Symp. on Fault-Tolerant Computing (FTCS), 1995, pp. 381–390.Google Scholar

[39] R., Pietrantuono, S., Russo, and K., Trivedi, “Software reliability and testing time allocation: An architecture-based approach,” IEEE Transactions on Software Engineering, vol. 36, no. 3, pp. 323–337, 2010.Google Scholar

[40] K. B., Misra, New Trends in System Reliability Evaluation. Elsevier, 1993.

[41] K. B., Misra, Handbook of Performability Engineering. Springer-Verlag, 2008.

[42] M. R., Lyu, Software Fault Tolerance. John Wiley & Sons, 1995.

[43] N., Leveson, Safeware: System Safety and Computers. Addison-Wesley, 1995.

[44] M., Grottke, D. S., Kim, R. K., Mansharamani, M. K., Nambiar, R., Natella, and K. S., Trivedi, “Recovery from software failures caused by Mandelbugs,” IEEE Trans. Reliability, vol. 65, no. 1, pp. 70–87, 2016.Google Scholar

[45] D., Wang and K. S., Trivedi, “Modeling user-perceived reliability based on user behavior graphs,” International Journal of Reliability, Quality and Safety Engineering, vol. 16, no. 04, pp. 303–329, 2009.Google Scholar

[46] H., Kumamoto and E., Henley, Probabilistic Risk Assessment and Management for Engineers and Scientists. IEEE Press, 1996.