OntoArch reliability-aware software architecture design and experience

Modern Software Engineering Concepts and Practices: Advanced Approaches

Volumn , Issue , 2010, Pages 48-74

  Zhou, Jiehan ^a   Ovaska, Eila ^a   Evesti, Antti ^a   Immonen, Anne ^a  

^a UNIVERSITY OF OULU   (Finland)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84898554996     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-60960-215-4.ch003     Document Type: Chapter

References (88)

1. W3C-WSA. (2004). Web services architecture. Retrieved May 25, 2010, from http://www.w3.org/TR/ws-rch/#whatis
2. AgenaRisk. (2006). Bayesian network and simulation software for risk analysis and decision support. Retrieved May 25, 2010, from http://www.Agenarisk.Com/
3. AT&T. (2006). SRE toolkit. Retrieved May 25, 2010, from http://www.Cse.Cuhk.Edu.hk/~lyu/book/reliability/sretools.Html
4. Bachmann, F., Bass, L., Chastek, G., Donohoe, P., & Peruzzi, F. (2000). The architecture-based design method. Unpublished Technical Report 2000-TR-001, CMU/SEI.
5. Barry, D. K. (2003). Web services and service-oriented architectures: The savvy manager's guide. San Francisco: Morgan Kaufmann Publishers.
6. Bass, L., Clements, P., & Kazman, R. (1998). Software architecture in practice. Boston: Addison-Wesley.
7. Bengtsson, P. O., & Bosch, J. (1998). Scenariobased architecture reengineering. Proceedings Fifth International Conference on Software Reuse (ICSR 5). (pp. 308).
8. Bengtsson, P. O., & Bosch, J. (1999). Architecture level prediction of software maintenance. Third European Conference on Software Maintenance and Reengineering, (pp. 139-147).
9. Boer, R. C. D., Lago, P., Telea, R., & Vliet, H. V. (2009). Ontology-driven visualization of architectural design decisions (pp. 51-60). Cambridge, UK: WICSA/ECSA.
10. Bosch, J. (2000). Design & use of software architectures-adopting and evolving a product line approach. Addison-Wesley.
11. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., & Stal, M. (1996). Pattern-oriented software architecture: A system of patterns. New York: Wiley.
12. Cheung, R. C. (1980). A user-oriented software reliability model. IEEE Transactions on Software Engineering, 6(2), 118-125. doi:10.1109/TSE.1980.234477
13. Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000). Non-functional requirements in software engineering. Kluwer Academic Publishing.
14. Cortellessa, V., Singh, H., & Cukic, B. (2002). Early reliability assessment of UML-based software models. Paper presented at the Third International Workshop on Software and Performance, (pp. 302-309).
15. Dali. (2006). The Dali workbench. Retrieved May 25, 2010, from http://www.Cs.Cmu.edu/afs/cs/project/tinkerrch/www/html/1998/Lectures/25.RevEng/base.007.Html
16. Delamaro, M., Maldonado, J., & Mathur, A. P. (1996). Integration testing using interface mutations. Paper presented at The Seventh International Symposium on Software Reliability Engineering (ISSRE'96), (pp. 112-121).
17. Dobrica, L., & Niemelä, E. (2002). A survey on software architecture analysis methods. IEEE Transactions on Software Engineering, 28(7), 638-653. doi:10.1109/TSE.2002.1019479
18. Duenas, J. C., Oliveira, W. L. D., & de la Puente, J. A. (1998). A software architecture evaluation model. Paper presented at the Second Int'l ESPRIT ARES Workshop, (pp. 148-157).
19. Eclipse. (2005). Home page. Retrieved May 25, 2010, from http://www.eclipse.org/
20. Everett, W. (1999). Software component reliability analysis. Paper presented at the Symposium on Application-Specific Systems and Software Engineering Technology (ASSET'99), (pp. 204-211).
21. Evesti, A. (2007). Quality-oriented software architecture development (p. 79). Espoo: VTT Publications.
22. Gennari, J. H. (2003). The evolution of protégé: An environment for knowledge-based systems development. International Journal of HumanComputer Studies, 58, 89-123. doi:10.1016/S1071-5819(02)00127-1
23. GNU. (2006). The GNU profiler. Retrieved 25 May, 2010, from http://www.Cs.Utah.edu/dept/old/texinfo/as/gprof_toc.html
24. Gokhale, S., Wong, W. E., Trivedi, K., & Horgan, J. R. (1998). An analytical approach to architecture based software reliability prediction. Paper presented at the Third International Computer Performance and Dependability Symposium (IPDS'98), (pp. 13-22).
25. Goseva-Popstojanova, K., Mathur, A. P., & Trivedi, K. S. (2001). Comparison of architecturebased software reliability models. Paper presented at the 12th International Symposium on Software Reliability Engineering, (p. 22).
26. Hofmeister, C., Nord, R., & Soni, D. (2000). Applied software architecture. Addison-Wesley.
27. Horgan, J. R., & London, S. (1992). ATAC: A data flow coverage testing tool for C. Paper presented at the Second Symposium on Assessment of Quality Software Development Tools, (pp. 2-10).
28. IEEE. (2000). IEEE recommended practice for architectural description of software-intensive systems. IEEE Std-1471-2000.
29. Immonen, A. (2006). A method for predicting reliability and availability at the architectural level. In Kakola, T., & Duenas, J. C. (Eds.), Research issues in software product-lines-engineering and management (pp. 373-422). Berlin, Heidelberg: Springer Verlag.
30. Immonen, A., & Niemelä, E. (2007). Survey of reliability and availability prediction methods from the viewpoint of software architecture. Software and Systems Modeling, 7(1), 49-65. doi:10.1007/s10270-006-0040-x
31. Immonen, A., & Niskanen, A. (2005). A tool for reliability and availability prediction. Paper presented at the 31st Euromicro Conference on Software Engineering and Advanced Applications, (p. 416).
32. ISO/IEC. (1997). ISO/IEC CD 9126-1: Software quality characteristics and metrics, part 1: Quality characteristics and sub-characteristics.
33. Jaaksi, A., Aalto, J., Aalto, A., & Vatto, K. (1999). Tried & true object development, industry-proven approaches with UML. Cambridge University Press.
34. Kanoun, K., Kaaniche, M., Laprie, J., & Metge, S. (1993). SoRel: A tool for reliability growth analysis and prediction from statistical failure data. Paper presented at The Twenty-Third International Symposium on Fault-Tolerant Computing, (p. 654).
35. Kanoun, K., & Sabourin, T. (1987). Software dependability of a telephone switching system. Paper presented at the 17th International Symposium on Fault-Tolerant Computing (FTCS'17), (pp. 236-241).
36. Kantorovitch, J., & Niemelä, E. (2008). Service description ontologies. Encyclopedia of information science and technology, second edition, (pp. 3445-3451).
37. Kazman, R., Abowd, G., Bass, L., & Clements, P. (1996). Scenario-based analysis of software architecture. IEEE Software, 13(6), 47-55. doi:10.1109/52.542294
38. Kazman, R., Klein, M., Barbacci, M., Lipson, H., Longstaff, T., & Carriere, S. J. (1998). The architecture tradeoff analysis method. Paper presented at the Fourth International Conference Eng. of Complex Computer Systems (ICECCS '98).
39. Keller, A., & Ludwig, H. (2002). The WSLA framework: Specifying and monitoring of service level agreements for web services. Journal of Network and Systems Management, 11(1), 57-81. doi:10.1023/A:1022445108617
40. Krishnamurthy, S., & Mathur, A. P. (1997). On the estimation of reliability of a software system using reliabilities of its components. Proceedings of the Eighth International Symposium on Software Reliability Engineering, (pp. 146-155).
41. Kruchten, P. B. (1995). The 4+1 view model of architecture. IEEE Software, 12(6), 42-50. doi:10.1109/52.469759
42. Kubat, P. (1989). Assessing reliability of modular software. Operations Research Letters, 8(1), 35-41. doi:10.1016/0167-6377(89)90031-X
43. Lahteenmaki, J., Leppanen, J., & Kaijanranta, H. (2007). Document-based service architecture for communication between health and wellness service providers and customers. (pp. 275-278). ICHIT2007.
44. Laprie, J. C. (1984). Dependability evaluation of software systems in operation. IEEE Transactions on Software Engineering, 10(6), 701-714. doi:10.1109/TSE.1984.5010299
45. Lassing, N., Rijsenbrij, D., & Vliet, H. v. (1999). On software architecture analysis of flexibility, complexity of changes: Size isn't everything. Paper presented at the Second Nordic Software Architecture Workshop (NOSA '99), (pp. 1103-1581).
46. Ledoux, J. (1999). Availability modeling of modular software. IEEE Transactions on Reliability, 48(2), 159-168. doi:10.1109/24.784274
47. Littlewood, B. (1979). Software reliability model for modular program structure. IEEE Transactions on Reliability, 28(3), 241-246. doi:10.1109/TR.1979.5220576
48. Lung, C., Bot, S., Kalaichelvan, K., & Kazman, R. (1997). An approach to software architecture analysis for evolution and reusability. Proceedings of CASCON '97, (pp.15).
49. Lyu, M. R. (1995). Handbook of software reliability engineering. McGraw-Hill.
50. Lyu, M. R., & Nikora, A. (1992). CASRE: A computer-aided software reliability estimation tool. Paper presented at the Fifth International Workshop on Computer-Aided Software Engineering, (pp. 264-275).
51. Marks, E., & Michael, B. (2006). Service oriented architecture: A planning and implementation guide for business and technology. Hoboken, NJ: John Wiley & Sons.
52. Matinlassi, M. (2006). Quality driven software architecture model transformation towards automation. Espoo, Finland: VTT Publications.
53. Matinlassi, M., Niemelä, E., & Dobrica, L. (2002). Quality-driven architecture design and quality analysis method: A revolutionary initiation approach to a product line architecture. Espoo, Finland: VTT Publications.
54. Medvidovic, N., Dashofy, E. M., & Taylor, R. N. (2007). Moving architectural description from under the technology lamppost. Information and Software Technology, 49(1), 12-31. doi:10.1016/j.infsof.2006.08.006
55. Merilinna, J., & Niemelä, E. (2005). A stylebase as a tool for modelling of quality-driven software architecture. Proceedings of the Estonia Academy of Sciences Engineering, Special Issue on Programming Languages and Software Tools, 11(4), 296-312.
56. Molter, G. (1999). Integrating SAAM in domaincentric and reuse-based development processes. Proceedings of the Second Nordic Workshop on Software Architecture (NOSA '99), (pp. 1103-1581).
57. Musa, J. (1998). Software reliability engineering, more reliable software faster development and testing. McGraw-Hill.
58. Musa, J. D., Iannino, A., & Okumoto, K. (1987). Software reliability: Measurement, prediction, application. McGraw-Hill.
59. Nakagawa, E. Y., Barbosa, E. F., & Maldonado, J. C. (2009). Exploring ontologies to support the establishment of reference architectures: An example on software testing (pp. 249-252). Cambridge, UK: WICSA/ECSA.
60. Niemelä, E., & Immonen, A. (2006). Capturing quality requirements of product family architecture. Information and Software Technology, 49(1112), 1107-1120. doi:10.1016/j.infsof.2006.11.003
61. Niemelä, E., Kalaoja, J., & Lago, P. (2005). Toward an architectural knowledge base for wireless service engineering. IEEE Transactions on Software Engineering, 31(5), 361-379. doi:10.1109/TSE.2005.60
62. Noy, N. F., & McGuinness, D. L. (2006). Ontology development 101: A guide to creating your first ontology. Retrieved May 25, 2010, from http://ksl.Stanford.edu/people/dlm/papers/ontology101/ontology101-Noy-Mcguinness.Html
63. Oreizy, L. P., Taylor, R. N., Heimbigner, D., Johnson, G., Medvidovic, N., & Quilici, A. (1999). Self-adaptive software: An architecture-based approach. IEEE Intelligent Systems, 14(3), 54-62. doi:10.1109/5254.769885
64. Ovaska, E., Evesti, A., Henttonen, K., Palviainen, M., & Aho, P. (2010). Knowledge based qualitydriven architecture design and evaluation. Information and Software Technology, 52(6), 577-601. doi:10.1016/j.infsof.2009.11.008
65. Popstojanova, K. G., & Trivedi, K. S. (2001). Architecture-based approach to reliability assessment of software systems. Performance Evaluation, 45(2), 179-204. doi:10.1016/S01665316(01)00034-7
66. Purhonen, A., Niemelä, E., & Matinlassi, M. (2004). Viewpoints of DSP software and service architectures. Journal of Systems and Software, 69(1), 57-73. doi:10.1016/S01641212(03)00050-5
67. Reussner, R., Schmidt, H., & Poernomo, I. (2003). Reliability prediction for component-based software architectures. Journal of Systems and Software, 66(3), 241-252. doi:10.1016/S01641212(02)00080-8
68. Rodrigues, G., Rosenblum, D., Uchitel, S., Bt, W., & Rh, S. (2005). Using scenarios to predict the reliability of concurrent component-based software systems. FASE 2005 - LNCS 3442, (pp. 111-126).
69. Roshandel, R., & Medvidovic, N. (2004). Toward architecture-based reliability estimation. Proceedings from The International Conference on Dependable Systems and Networks.
70. Sandia, N. L. (2005). Java expert system shell (JESS). Retrieved May 25, 2010, from http://herzberg.ca.sandia.gov/jess/
71. Shooman, M. (1976). Structural models for software reliability prediction, (pp. 268-280). Paper presented at the Second International Conference on Software Engineering.
72. Standard. (1991). Standard glossary of software engineering terminology.
73. Szyperski, C. (1997). Component software, beyond object-oriented programming. New York: Addison Wesley Longman Ltd.
74. Thomason, M. G., & Whittaker, J. A. (1999). Rare failure-state in a Markov chain model for software reliability, (pp. 12-19). Paper presented at the 10th International Symposium on Software Reliability Engineering.
75. TOPCASED. (2007). Home page. Retrieved May 25, 2010, from http://topcased-mm.Gforge.Enseeiht.fr/website/index.Html
76. UML2. (2006). Home page. Retrieved May 25, 2010, from http://www.Eclipse.org/uml2/
77. Unified. (2006). Unified modeling language. Retrieved May 25, 2010, from http://en.Wikipedia.org/wiki/Unified_Modeling_Language.
78. Voas, J., Charron, F., & Miller, K. (1996). Robust software interfaces: Can COTS-based systems be trusted without them? (pp. 126-135). Paper presented at the 15th International Conference on Computer Safety.
79. Voas, J. M. (1998). Certifying off-the-shelf software components. IEEE Comput., 31(6), 53-59.
80. Wada, H., & Suzuki, J. (2006). Modeling nonfunctional aspects in service oriented architecture, (pp. 222-229). Paper presented at the IEEE International Conference on Service Computing.
81. Wang, W., Pan, D., & Chen, M. (1999). An architecture-based software reliability model. In Proceedings of the Pacific Rim International Symposium on Dependable Computing (PRDC'99), (pp. 143-150).
82. Wang, W., Pan, D., & Chen, M. (2006). Architecture-based software reliability modeling. Journal of Systems and Software, 79(1), 132-146. doi:10.1016/j.jss.2005.09.004
83. Wongthongtham, P., Chang, E., & Dillon, T. (2006). Software design process ontology development. In On the move to meaningful internet systems (pp. 1806-1813). Berlin, Heidelberg: Springer.
84. Wright. (2006). The Wright architecture description language. Retrieved May 25, 2010, from http://www.Cs.Cmu.edu/afs/cs/project/able/www/wright/index.Html
85. Yacoub, S., Cukic, B., & Ammar, H. (1999). Scenario-based reliability analysis of componentbased software, (pp. 22-31). Paper presented at the 10th International Symposium on Software Reliability Engineering (ISSRE'99).
86. Zhou, J., & Dieng, R. (2004). A semantic knowledge management system for knowledge-intensive manufacturing, (pp. 114-122). Paper presented at the 2004 IADIS International Conference of e-Commerce.
87. Zhou, J., & Niemelä, E. (2006). Toward semantic QoS-aware web services: Issues, related studies and experience. Paper presented at the IEEE/WIC/ACM International Conference on Web Intelligence.
88. Zhou, J., Niemelä, E., Evesti, A., Immonen, A., & Savolainen, P. (2008). OntoArch approach for reliability-aware software architecture development (pp. 1228-1233). Turku, Finland.