[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to main content

A Method for Predicting Reliability and Availability at the Architecture Level

  • Chapter
Software Product Lines

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
£29.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
GBP 19.95
Price includes VAT (United Kingdom)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
GBP 71.50
Price includes VAT (United Kingdom)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
GBP 88.00
Price includes VAT (United Kingdom)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
GBP 89.99
Price includes VAT (United Kingdom)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. America, P., Obbink, H., van Ommering, R., van der Linden, F.: CoPAM: a component-oriented platform ar-chitecting method family for product family engineering. In: Software Product Lines, Experience and Re-search Directions, ed by Donohoe, P., Proceedings of the 1st Software Product Lines Conference (Kluwer, Dordrecht 2000) pp 167-180

    Google Scholar 

  2. Barry, D.K.: Web Services and Service-Oriented Architectures: The Savvy Manager’s Guide (Morgan Kaufmann, Los Altos, CA 2003)

    Google Scholar 

  3. Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice (Addison-Wesley, Reading, MA 1998)

    Google Scholar 

  4. Bennett, K., Layzell, P.J., Budgen, D., Brereton, L., Munro, M.: Service-based software: the future of flexi-ble software. In: Proceedings of the Asia-Pacific Software Engineering Conference (IEEE Computer Society, Los Alamitos, CA 2000) pp 214-221

    Google Scholar 

  5. Bondavalli, A., Majzik, I., Mura, I.: Automatic dependability analysis for supporting design decisions in UML. In: Proceedings of the 4th IEEE High Assurance System Engineering Symposium. (IEEE Computer Society, Los Alamitos, CA 1999) pp 64-71

    Chapter  Google Scholar 

  6. Bosch, J.: Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach (Addison-Wesley, Reading, MA 2000)

    Google Scholar 

  7. Buschmann, F., Meunier, R., Rohnert, H., Sommerland, P., Stal, M.: Pattern Oriented Software Architecture. A System of Patterns (Wiley, New York 1996)

    Google Scholar 

  8. Chung, L., Gross, D., Yu, E.: Architectural design to meet stakeholders requirements. In: The 1st Working IFIP Conference on Software Architecture (Kluwer, Dordrecht 1999)

    Google Scholar 

  9. Chung, L., Nixon, B., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering (Kluwer, Dordrecht 2000)

    MATH  Google Scholar 

  10. Clements, P., Northrop, L.: Software Product Lines: Practices and Patterns (Addison-Wesley, Reading, MA 2002)

    Google Scholar 

  11. Clements, P., Kazman, R., Klein, M.: Evaluating Software Architecture: Methods and Case Studies, 1st edn (Addison-Wesley, Reading, MA 2002)

    Google Scholar 

  12. Cortellessa, V., Singh, H., Cukic, B.: Early reliability assessment of UML based software models. In: 3rd Inter-national Workshop on Software and Performance (Association for Computing Machinery 2002) pp 302-309

    Google Scholar 

  13. Dobrica, L., Niemelä, E.: Using UML notation extensions to model variability in product line architectures. In: ICSE, International workshop on Software Variability Management (2003) pp 8-13

    Google Scholar 

  14. Douglass, B.P.: Doing Hard Time: Developing Real-Time Systems with UML, Objects, Frameworks, and Patterns (Addison-Wesley, Reading, MA 1999)

    Google Scholar 

  15. Dugan, J.B.: Software system analysis using fault trees. In: Handbook of Software Reliability Engineering, ed by Lyu, M.R. (McGraw-Hill, New York 1995) pp 615-659

    Google Scholar 

  16. Everett, W.: Software component reliability analysis. In: IEEE Symposium on Application - Specific Systems and Software Engineering and Technology (IEEE Computer Society, Los Alamitos, CA 1999) pp 204-211

    Google Scholar 

  17. Frankel, D.: Model Driven Architecture, Applying MDA to Enterprise Computing (Wiley, New York 2003)

    Google Scholar 

  18. Garlan, D., Shaw, M.: An introduction to software architecture. In: Advances in Software Engineering and Knowledge Engineering (World Scientific, Singapore 1993) pp 1-39

    Google Scholar 

  19. Gokhale, S.S., Trivedi, K.S.: Dependency characterization in path-based approaches to architecture-based software reliability prediction. In: Proceedings of the IEEE Workshop on Application-Specific Software En-gineering Technology, ASSET-98 (IEEE Computer Society, Los Alamitos, CA 1998) pp 86-89

    Chapter  Google Scholar 

  20. Goseva-Popstojanova, K, Trivedi, K.S. Architecture-based approach to reliability assessment of software systems. Perform. Eval. 45: 179-204 (2001)

    Article  MATH  Google Scholar 

  21. Rational Software Corp.: UML Profile for EJB. In: Public Review Draft JSR-000026, ed by Greenfield, J. (2001)

    Google Scholar 

  22. Grünbacher, P., Egyed, A., Medvidovic, N.: Reconciling software requirements and architectures with inter-mediate models. Softw. Syst. Model. 3: 235-253 (2003)

    Google Scholar 

  23. Hevner, A.R., March, S.T., Park, J., Ram, S.: Design science in information system research. MIS Q. 28: 75-105 (2004)

    Google Scholar 

  24. Hofmeister, C., Nord, R., Soni, D.: Applied Software Architecture (Addison-Wesley, Reading, MA 1999)

    Google Scholar 

  25. IEEE: IEEE Std 1471-2000. Recommended Practice for Architectural Description of Software-Intensive Sys-tems (Institute of Electrical and Electronics Engineers, New York 2000)

    Google Scholar 

  26. Immonen, A., Niskanen, A.: A tool for reliability and availability prediction. In: Proceedings of the 31st Eu-romicro Conference on Software Engineering and Advanced Applications (IEEE Computer Society, Los Alamitos, CA 2005) pp 416-423

    Google Scholar 

  27. Immonen, A., Holappa, J., Kallio, P., Kalaoja, J.: Towards interoperability of wireless services - a descrip-tion model of service interfaces. In: Proceedings of the IADIS International Conference WWW/Internet 2004 (2004) pp 983-988

    Google Scholar 

  28. ISO/IEC: ISO/IEC 9126-1 International Standard: Software Engineering - Product Quality. Part 1: Quality Model (2001)

    Google Scholar 

  29. Jaaksi, A., Aalto, J.-M., Aalto, A., Vättö, K.: Tried & True Object Development: Industry-Proven Approaches with UML (Cambridge University Press, Cambridge 1999)

    Google Scholar 

  30. Jazayeri, M., Ran, A., van der Linden, F. Software Architecture for Product Families (Addison-Wesley, Reading, MA 2000)

    Google Scholar 

  31. Kazman, R., Abowd, G., Bass, L., Clements, P.: Scenario-based analysis of software architecture. IEEE Softw. 47-55 (1996)

    Google Scholar 

  32. Kazman, R., Klein, M., Barbacci, M., Longstaff, T., Lipson, H., Carriere, J.: The architecture tradeoff analy-sis method. In: The 4th IEEE International Conference on Engineering of Complex Computer Systems (IEEE Computer Society, Los Alamitos, CA 1998)

    Google Scholar 

  33. Klein, M., Kazman, R., Bass, L., Carriere, J., Barbacci, M., Lipson, H.: Attribute-based architecture styles. In: The 1st Working IFIP Conference on Software Architecture (Kluwer, Dordrecht 1999)

    Google Scholar 

  34. Koistinen, J.: Dimensions for reliability contracts in distributed object systems. Technical report HPL-97-119, October 3, Hewlett-Packard (1997)

    Google Scholar 

  35. Krishnamurthy, S., Mathur, A.P.: On the estimation of reliability of a software system using reliabilities of its components. In: Proceedings of the 8th International Symposium in Software Reliability Engineering (IEEE Computer Society, Los Alamitos, CA 1997) pp 146-155

    Google Scholar 

  36. Kruchten, P.: The 4+1 view model of architecture. IEEE Softw. 12: 42-50 (1995)

    Article  Google Scholar 

  37. Leangsuksun, C., Song, H., Shen, L.: Reliability modeling using UML. In: Proceedings of the International Conference on Software Engineering Research and Practice, vol 1 (CSREA, Athens, GA 2003) pp 259-262

    Google Scholar 

  38. Matinlassi, M.: Quality-driven software architecture model transformation. In: Proceedings of the 5th Work-ing IEEE/IFIP Conference on Software Architecture (IEEE Computer Society, Los Alamitos, CA 2004)

    Google Scholar 

  39. Matinlassi, M., Kalaoja, J.: Requirements for Service Architecture Modeling in Workshop of Software Mod-eling Engineering of UML2002, Dresden, Germany (2002)

    Google Scholar 

  40. Matinlassi, M., Niemelä, E., Dobrica, L.: Quality-Driven Architecture Design and Quality Analysis Method, A Revolutionary Initiation Approach to a Product Line Achitecture, VTT Publication 456 (VTT Technical Research Centre of Finland, Espoo 2002)

    Google Scholar 

  41. Matinlassi, M., Pantsar-Syväniemi, S., Niemelä, E.: Towards service-oriented development in base station modules. In: Service-Oriented Software System Engineering: Challenges and Practices, ed by Zoran, S., Ajantha, D., vol 2 (Austrian Society for Cybernetic Studies, Vienna 2004) pp 440-444

    Google Scholar 

  42. Merilinna, J.: A Tool for Quality-Driven Architecture Model Transformation. VTT Publication 561 (VTT Technical Research Centre of Finland, Espoo 2005)

    Google Scholar 

  43. Miller, J., Mukerji, J.: MDA Guide, version 1.0.1 (Object Management Group 2003)

    Google Scholar 

  44. Ncube, C., Maiden, N.: COTS software selection: the need to make tradeoffs between system requirements, architectures and COTS/components. In: Proceedings of 2nd International COTS Workshop: Continuing Collaborations for Successful COTS Development, ICSE-2000, Limerick, Ireland (2000)

    Google Scholar 

  45. Niemelä, E., Kalaoja, J., Lago, P.: Towards an architectural knowledge base for wireless service engineering. IEEE Trans. Softw. Eng. 31: 361-379 (2005)

    Article  Google Scholar 

  46. Object Management Group: Unified modeling language (UML), version 1.5 (2002)

    Google Scholar 

  47. Object Management Group: UML profile for schedulability, performance, and time specification (2003)

    Google Scholar 

  48. Object Management Group: UML profile for modeling quality of service and fault tolerance characteristics and mechanisms. Revised submission (2003)

    Google Scholar 

  49. Object Management Group: Unified modeling language (UML), 2.0 Specification (2003)

    Google Scholar 

  50. Papoulis, A.: Probability, Random Variables, and Stochastic Processes, 2nd edn (McGraw-Hill, New York 1984)

    MATH  Google Scholar 

  51. Purhonen, A., Niemelä, E., Matinlassi, M.: Viewpoints of DSP software and service architectures. J. Syst. Softw. 69: 57-73 (2004)

    Article  Google Scholar 

  52. Reussner, R.H., Schmidt, H.W., Poernomo, I.H.: Reliability prediction for component-based software architec- tures. J. Syst. and Software 66: 241-252 (2003)

    Article  Google Scholar 

  53. Rodrigues, G.N., Roberts, G., Emmerich, W., Skene, J.: Reliability support for the model driven architecture. In: Proceedings of Workshop on Software Architecture for Dependable Systems, ICSE-2003 (2003) pp 7-12

    Google Scholar 

  54. Shaw, M., Garlan, D.: Software Architecture: Perspectives on an Emerging Discipline (Prentice-Hall, Englewood Cliffs, NJ 1996)

    MATH  Google Scholar 

  55. Shooman, M.: Structural models for software reliability prediction. In: Proceedings of the 2nd International Conference on Software Engineering (1976) pp 268-280

    Google Scholar 

  56. Taulavuori, A., Niemelä, E., Kallio, P.: Component documentation - a key issue in software product lines. Inform. Softw. Technol.46: 535-546 (2004)

    Article  Google Scholar 

  57. Thomason, M.G., Whittaker, J.A.: Rare failure-state in a Markov chain model for software reliability. In: Proceedings of the 10th International Symposium on Software Reliability Engineering (IEEE Computer So-ciety, Los Alamitos, CA 1999) pp 12-19

    Google Scholar 

  58. van der Linden, F.: Software product families in Europe: the ESAPS & CAF É projects. IEEE Softw. 19: 41-49 (2002)

    Article  Google Scholar 

  59. Voas, J.M.: Certifying off-the-shelf software components. Computer 31: 53-59 (1998)

    Article  Google Scholar 

  60. Yacoub, S., Cukic, B., Ammar, H.: Scenario-based reliability analysis of component-based software. In: Pro-ceedings of the 10th International Symposium on Software Reliability Engineering (IEEE Computer Society, Los Alamitos, CA 1999) pp 22-31

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2006 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Immonen, A. (2006). A Method for Predicting Reliability and Availability at the Architecture Level. In: Käköla, T., Duenas, J.C. (eds) Software Product Lines. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-33253-4_10

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-33253-4_10

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-33252-7

  • Online ISBN: 978-3-540-33253-4

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics