Consensus Building and In-operation Assurance for Service Dependability

  • Yutaka Matsuno
  • Shuichiro Yamamoto
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7465)


Recent information systems have become large and complex by interacting with each other via networks. This makes assuring dependability of systems much more difficult than ever before. For this problem, we observe that requirement elicitation and risk analysis methods should be tightly connected with assurance methods. Furthermore, requirements should be ensured also in operation in such open environment where several interdependency may exist. This paper describes our initial research result and preliminary implementation toward consensus building and in-operation assurance for service dependability. We propose a process cycle for consensus building among stakeholders with assurance cases. We extend conventional assurance cases for ensuring that stakeholders’ requirements are satisfied during operation. The extended assurance case is called D-Case[16]. We also describe how D-Case is used for in-operation assurance.


Consensus Building Dependability Requirement Requirement Elicitation External Node Fault Tree Analysis 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
  2. 2.
  3. 3.
  4. 4.
    Workshop on Assurance Cases: Best Practices,Possible Obstacles, and Future Opportunities, DSN 2004 (2004)Google Scholar
  5. 5.
    Aurum, A., Wohlin, C. (eds.): Engineering and Managing Software Requirements Engineering and Managing Software Requirements. Springer (2010)Google Scholar
  6. 6.
    Berenbach, B., Paulish, D., Kazmeier, J., Dudorfeer, A.: Software and Systems Requirements Engineering In Practice. McGraw-Hill (2009)Google Scholar
  7. 7.
    Davis, A.M.: Just Enough Requiremtns Management- Where Software Development Meets Marketing. Dorset House Publishing (2005)Google Scholar
  8. 8.
    Despotou, G.: Managing the Evolution of Dependability Cases for Systems of Systems. PhD thesis, Department of Computer Science, University of York (2007)Google Scholar
  9. 9.
    Ericson, C.A.: Hazard Analysis Techniques for System Safety. John Wiley and Sons, Inc. (2005)Google Scholar
  10. 10.
    European Organisation for the Safety of Air Navigation. Safety case development manual. European Air Traffic Management, 2006.Google Scholar
  11. 11.
    IIBA. BABOK 2.0 (2009)Google Scholar
  12. 12.
    Kelly, T., Weaver, R.: The goal structuring notation - a safety argument notation. In: Proc. of the Dependable Systems and Networks 2004, Workshop on Assurance Cases (2004)Google Scholar
  13. 13.
    Kotonya, G., Sommerville, I.: Requirements Engineering-Process and Techniqeus. John Wiley and Sons (2002)Google Scholar
  14. 14.
    Leffingwel, D., Widrig, D.: Managing Software Requirements A Unified Approach. Addison-Wesley Professional (2000)Google Scholar
  15. 15.
    Leveson, N.G.: Safeware: System Safety and Computers. Addison-Wesley (1995)Google Scholar
  16. 16.
    Matsuno, Y., Nakazawa, J., Takeyama, M., Sugaya, M., Ishikawa, Y.: Toward a language for communication among stakeholders. In: Proc. of the 16th IEEE Pacific Rim International Symposium on Dependable Computing, PRDC 2010 (2010)Google Scholar
  17. 17.
    Pohl, K.: Requirements Enginerring Fundamentals, Principles, and Techniques. Springer (2010)Google Scholar
  18. 18.
    Sasaki, R., Ishii, S., Hidaka, Y., Yajima, H., Yoshiura, H., Murayama, Y.: Development Concept for and Trial Application of a “Multiple Risk Communicator”. In: Funabashi, M., Grzech, A. (eds.) Challenges of Expanding e-Commerce, e-Business, and e-Government. IFIP, vol. 189, pp. 203–217. Springer, Boston (2005)CrossRefGoogle Scholar
  19. 19.
    Sommerville, I., Sawyer, P.: Requirements Engineering: A Good Practice Guide. John Wiley and Sons (1997)Google Scholar
  20. 20.
    Taniyama, M., Hidaka, Y., Arai, M., Kai, S., Igawa, H., Yajima, H., Sasaki, R.: Application of Multiple Risk Communicator to the Personal Information Leakage Problem, pp. 284–289. World Academy of Science (2008)Google Scholar
  21. 21.
    Tokoro, M.: White paper: Dependable embedded operating system for practical use (DEOS) project, version 3 (2011)Google Scholar
  22. 22.
    Troubitsyna, E.: Elicitation and specification of safety requirements. In: ICONS 2008, pp. 202–207 (2008)Google Scholar
  23. 23.
    Wiegers, K.: Software Requirements- Practical techniques for gathering and managing requirements through the product development cycle. Microsoft Corporation (2003)Google Scholar
  24. 24.
    Zowghi, D., Couling, C.: Requirements Elicitation: A survey of Techniques, Approaches, and Tools. Springer (2010)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2012

Authors and Affiliations

  • Yutaka Matsuno
    • 1
  • Shuichiro Yamamoto
    • 1
  1. 1.Strategy Office, Information and Communication HeadquartersNagoya UniversityJapan

Personalised recommendations