Architecture-Based Approaches to Software Reliability Prediction

Computers and Mathematics with Applications

Volumn 46, Issue 7, 2003, Pages 1023-1036

  Goseva Popstojanova K ^a   Trivedi, K S ^b  

^a West Virginia University   (United States)

^b Duke University   (United States)

Author keywords

Additive models; Architecture based software reliability; Path based models; State based models

Indexed keywords

DATA REDUCTION; FAILURE ANALYSIS; PROBLEM SOLVING; RELIABILITY; SECURITY OF DATA;

SOFTWARE ARCHITECTURE; SOFTWARE RELIABILITY;

SOFTWARE ENGINEERING;

EID: 0242663286     PISSN: 08981221     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0898-1221(03)90116-7     Document Type: Conference Paper

References (41)

1. C.V. Ramamoorthy and F.B. Bastani, Software reliability - Status and perspectives, IEEE Trans. Software Eng. 8 (4), 354-371, (1982).
2. A.L. Goel, Software reliability models: Assumptions, limitations, and applicability, IEEE Trans. Software Eng. 11 (12), 1411-1423, (1985).
3. W. Farr, Software reliability modeling survey, In Handbook of Software Reliability Engineering, (Edited by M.R. Lyu), pp. 71-117, McGraw-Hill, (1996).
4. th Int. Conf. Advanced Computing (ADCOMP'97), pp. 447-452, (1997).
5. R.C. Cheung, A user-oriented software reliability model, IEEE Trans. Software Eng. 6 (2), 118-125, (1980).
6. W. Wang, Y. Wu and M. Chen, An architecture-based software reliability model, In Proc. Pacific Rim Int. Symp. on Dependable Computing, pp. 143-150, (1999).
7. J.H. Poore, H.D. Mills and D. Mutchler, Planning and certifying software system reliability, IEEE Software, 88-99, (1993).
8. P. Kubat, Assessing reliability of modular software, Operations Research Letters 8, 35-41, (1989).
9. rd Int. Computer Performance & Dependability Symp. (IPDS'98), pp. 13-22, (1998).
10. nd Symp. Assessment of Quality Software Development Tools, pp. 2-10, (1992).
11. B. Littlewood, A reliability model for systems with Markov structure, Applied Statistics 24 (2), 172-177, (1975).
12. J.C. Laprie, Dependability evaluation of software systems in operation, IEEE Trans. Software Eng. 10 (6), 701-714, (1984).
13. J.C. Laprie and K. Kanoun, X-ware reliability and availability modeling, IEEE Trans. Software Eng. 18 (2), 130-147, (1992).
14. J. Ledoux, Availability modeling of modular software, IEEE Trans. Rel. 48 (2), 159-168, (1999).
15. M.F. Neuts, A versatile Markovian point process, J. Applied Probability 16, 764-779, (1979).
16. D.M. Lucantoni, New results on the single server queue with a batch Markovian arrival process, Stochastic Models 7 (1), 1-46, (1991).
17. B. Littlewood, Software reliability model for modular program structure, IEEE Trans. Rel. 28 (3), 241-246, (1979).
18. V.G. Kulkarni, Modeling and Analysis of Stochastic Systems, Chapman & Hall, (1995).
19. nd Int. Con. Software Engineering, pp. 268-280, (1976).
20. th Int. Symp. Software Reliability Eng. (ISSRE'97), pp. 146-155, (1997).
21. S. Gokhale and K. Trivedi, Dependency characterization in path-based approaches to architecture based software reliability prediction, In Proc. Symp. Application-Specific Systems and Software Engineering Technology (ASSET'98); pp. 86-89, (1998).
22. th Int. Symp. Software Reliability Eng. (ISSRE'99), pp. 22-31, (1999).
23. J.D. Musa, Operational profiles in software reliability engineering, IEEE Software 10 (2), 14-32, (1993).
24. th Int. Symp. Software Reliability Eng. (ISSRE'95), pp. 188-194, (1995).
25. W. Everett, Software component reliability analysis, In Proc. Symp. Application-Specific Systems and Software Engineering Technology (ASSET'99), pp. 204-211, (1999).
26. th Int. Symp. on Fault-Tolerant Computing (FTCS 17), pp. 236-241, (1987).
27. R.A. Sahner, K.S. Trivedi and A. Puliaflto, Performance and Reliability Analysis of Computer Systems: An Example-Based Approach Using the SHARPE Software Package, Kluwer Academic, (1996).
28. K. GoŠeva-Popstojanova and K. Trivedi, Failure correlation in software reliability models, IEEE Trans. Rel. 49 (1), 37-48, (2000).
29. E. Nelson, A Statistical Basis for Software Reliability, TRW-SS-73-02, TRW Software Series, (1973).
30. K.W. Miller, L.J. Morell, R.E. Noonan, S.K, Park, D.M. Nicol, B.W. Murrill and J.M. Voas, Estimating the probability of failure when testing reveals no failures, IEEE Trans. Software Eng. 18 (1), 33-43, (1992).
31. B. Littlewood and D. Wright, Some conservative stopping rules for operational testing of safety-critical software, IEEE Trans. Software Eng. 23 (11), 673-683, (1997).
32. J.M, Voas, Certifying off-the-shelf software components, IEEE Computer 31 (6), 53-59, (1998).
33. th Int. Conf. Computer Safety, Reliability, and Security (SAFECOMP'96), pp. 126-135, (1996).
34. th Int. Symp. Software Reliability Eng. (ISSRE'96), pp. 112-121, (1996).
35. th Int. Conf. Software Engineering (ICSE 18), pp. 90-99, (1996).
36. http://www.gnu.org/manual/gprof-2.9.1/html-mono/gprof.html.
37. http//xsuds.argreenhouse.com.
38. http://www.unix.digital.com/faq/publications/base_doc/DOCUMENTATION/ V40F_HTML/APS30-ETE/TITLE.HTM.
39. R. Kazman and J. Carriere, Playing detective: Reconstructing software architecture from available evidence, J. Automated Software Engineering 6 (2), 107-138, (1999).
40. C. Smith and L. Williams, Software performance engineering; A case study including performance comparison with design alternatives, IEEE Trans. Software Eng. 19 (7), 720-741, (1993).
41. R. Kazman, M. Klein, M. Barbacci, T. Lingstaff, H. Lipson and J. Carriere, The architecture tradeoff analysis method, In Proc. IEEE Int. Conf. on Engineering of Complex Computer Systems (ICECCS'98), pp. 68-78, (1998).