Michael Vierhauser
ABSTRACT
An increasing number of software systems today are systems of systems (SoS) that have been developed by diverse teams over many years. Such systems emerge gradually and it is hard to analyze or predict their behavior due to their scale, complexity, and heterogeneity. In particular, certain behavior only emerges at runtime due to complex interactions between the involved systems and their environment. Requirements monitoring has been proposed as a solution for checking at runtime whether systems adhere to their requirements. However, existing requirements monitoring approaches have been designed for single systems and therefore do not adequately consider the characteristics of SoS. More specifically, requirements in SoS exist at different levels, across different systems, and are owned by diverse stakeholders. Furthermore, requirements monitoring for SoS has to be flexible with respect to technologies and architectural patterns. This thesis will identify the capabilities required for requirements monitoring of SoS. It will further provide a flexible and tailorable infrastructure to support engineers and maintenance staff in observing and analyzing the behavior of a SoS at runtime. We plan to evaluate our work by assessing its usefulness in the context of an industrial SoS.
- L. Baresi, S. Guinea, O. Nano, and G. Spanoudakis. Comprehensive monitoring of BPEL processes. IEEE Internet Computing, 14(3):50--57, 2010. Google Scholar
Digital Library
- N. Bencomo, J. Whittle, P. Sawyer, A. Finkelstein, and E. Letier. Requirements reflection: requirements as runtime entities. In Proc. 32nd Int'l Conf. on Software Engineering (vol. 2), pages 199--202, 2010. Google ScholarDigital Library
- D. S. Caffall and J. B. Michael. Architectural framework for a system-of-systems. In Proceedings of the IEEE International Conference on Systems, Man and Cybernetics, pages 1876--1881. IEEE, 2005.Google ScholarCross Ref
- J. Cleland-Huang, C. K. Chang, and M. Christensen. Event-based traceability for managing evolutionary change. IEEE Transactions on Software Engineering, 29(9):796--810, 2003. Google ScholarDigital Library
- J. S. Dahmann and K. J. Baldwin. Understanding the current state of us defense systems of systems and the implications for systems engineering. In 2nd Annual IEEE Systems Conference, pages 1--7, 2008.Google ScholarCross Ref
- M. Jamshidi. Systems of systems engineering: principles and applications. CRC press, 2008.Google Scholar
- G. Kaiser, J. Parekh, P. Gross, and G. Valetto. Kinesthetics extreme: An external infrastructure for monitoring distributed legacy systems. In Proc. Autonomic Computing Workshop, pages 22--30. IEEE, 2003.Google ScholarCross Ref
- B. A. Kitchenham and S. Charters. Guidelines for performing systematic literature reviews in software engineering. Technical report, EBSE Technical Report EBSE-2007-01, 2007.Google Scholar
- N. Maiden. Monitoring our requirements. IEEE Software, 30(1):16--17, 2013. Google ScholarDigital Library
- M. W. Maier. Architecting principles for systems-of-systems. Systems Engineering, 1(4):267--284, 1998.Google ScholarCross Ref
- H. Muccini, A. Polini, F. Ricci, and A. Bertolino. Monitoring architectural properties in dynamic component-based systems. In Component-Based Software Engineering, LNCS 4608, pages 124--139. Springer, 2007. Google ScholarDigital Library
- W. Robinson. Extended OCL for goal monitoring. Electronic Communication of the European Association of Software Science and Technology, 9(1):1--12, 2008.Google Scholar
- P. Runeson and M. Höst. Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering, 14(2):131--164, 2009. Google ScholarDigital Library
- A. van Hoorn, J. Waller, and W. Hasselbring. Kieker: A framework for application performance monitoring and dynamic software analysis. In Proc. 3rd Joint Int'l Conference on Performance Engineering, pages 247--248, 2012. Google ScholarDigital Library
- M. Vierhauser, R. Rabiser, and P. Grünbacher. A case study on testing, commissioning, and operation of very-large-scale software systems. In Proceedings 36th Int'l Conference on Software Engineering (ICSE 2014), Hyderabad, India, 2014. Google ScholarDigital Library
- M. Vierhauser, R. Rabiser, and P. Grünbacher. A requirements monitoring infrastructure for very-large-scale software systems. In Proceedings 20th Int'l Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2014), Essen, Germany, 2014.Google ScholarDigital Library
- M. Vierhauser, R. Rabiser, P. Grünbacher, C. Danner, S. Wallner, and H. Zeisel. A flexible framework for runtime monitoring of system-of-systems architectures. In 11th Working IEEE/IFIP Conference on Software Architecture (WICSA 2014), Sydney, Australia, 2014. IEEE. Google ScholarDigital Library
- M. Vierhauser, R. Rabiser, P. Grünbacher, C. Danner, and S. Wallner. Evolving systems of systems: industrial challenges and research perspectives. In Proceedings of the First International Workshop on Software Engineering for Systems-of-Systems, pages 1--4. ACM, 2013. Google ScholarDigital Library
Index Terms
- A requirements monitoring infrastructure for systems of systems
Recommendations
Towards a Comprehensive Survey of the Requirements Elicitation Process Improvements
IPAC '15: Proceedings of the International Conference on Intelligent Information Processing, Security and Advanced CommunicationGood quality of requirements is considered as one of the most critical parts of software development projects. The main objective of any project is to get the right requirements in order to be successful. Requirements elicitation is the process of ...
User requirements modeling and analysis of software-intensive systems
The increasing complexity of software systems makes Requirements Engineering activities both more important and more difficult. This article is about user requirements development, mainly the activities of documenting and analyzing user requirements for ...
(Requirement) evolution requirements for adaptive systems
SEAMS '12: Proceedings of the 7th International Symposium on Software Engineering for Adaptive and Self-Managing SystemsIt is often the case that stakeholders want to strengthen/weaken or otherwise change their requirements for a system-to-be when certain conditions apply at runtime. For example, stakeholders may decide that if requirement R is violated more than N times ...
Comments