Requirements Engineering Aspects of a Geographically Distributed Architecture

Maria Spichkova, Heinz Schmidt

2015

Abstract

We present our ongoing work on requirements specification and analysis for the geographically distributed software and systems. Developing software and systems within/for different countries or states or even within/for different organisations means that the requirements to them can differ in each particular case. These aspects naturally impact on the software architecture and on the development process as a whole. The challenge is to deal with this diversity in a systematic way, avoiding contradictions and non-compliance. In this paper, we present a formal framework for the analysis of the requirements diversity, which comes from the differences in the regulations, laws and cultural aspects for different countries or organisations. The framework also provides the corresponding architectural view and the methods for requirements structuring and optimisation.

References

  1. Borchers, G. (2003). The software engineering impacts of cultural factors on multi-cultural software development teams. In International Conference on Software Engineering, pages 540-545. IEEE Computer Society.
  2. Braun, P., Broy, M., Houdek, F., Kirchmayr, M., Mller, M., Penzenstadler, B., Pohl, K., and Weyer, T. (2014). Guiding requirements engineering for software-intensive embedded systems in the automotive industry. Computer Science - Research and Development, 29(1):21-43.
  3. Breaux, T., Anton, A., Boucher, K., and Dorfman, M. (2008). Legal requirements, compliance and practice: An industry case study in accessibility. In IEEE Conf. on Requirements Engineering, pages 43-52.
  4. Breaux, T., Vail, M., and Anton, A. (2006). Towards regulatory compliance: Extracting rights and obligations to align requirements with regulations. In IEEE International Conf. on Requirements Engineering, pages 49- 58.
  5. Broy, M. and Slotosch, O. (2001). From requirements to validated embedded systems. In Henzinger, T. A. and Kirsch, C. M., editors, Embedded Software, volume 2211 of LNCS, pages 51-65. Springer.
  6. Broy, M. and Stølen, K. (2001). Specification and Development of Interactive Systems: FOCUS on Streams, Interfaces, and Refinement. Springer.
  7. Crnkovic, I., Schmidt, H., Stafford, J., Heineman, G., and Wallnau, K. (2007). Component-based software engineering of trustworthy embedded systems. Journal of Systems and Software, 80(5):641-642.
  8. Egyed, A., Grnbacher, P., and Medvidovic, N. (2001). Refinement and Evolution Issues in Bridging Requirements and Architecture - The CBSP Approach. In From Software Requirements to Architectures, pages 42-47.
  9. Ferrari, R. and Madhavji, N. (2007). The impact of requirements knowledge and experience on software architecting: An empirical study. In The Working IEEE/IFIP Conference on Software Architecture, pages 16-16.
  10. Glinz, M. (2007). On non-functional requirements. In IEEE Conf. on Requirements Engineering, pages 21-26.
  11. Hölzl, F., Spichkova, M., and Trachtenherz, D. (2010). AutoFocus Tool Chain. Technical Report TUM-I1021, TU München.
  12. In, H., Boehm, B., Rodger, T., and Deutsch, M. (2001). Applying winwin to quality requirements: a case study. In Int. Conf. on Software Engineering, pages 555-564.
  13. Kiyavitskaya, N., Krausova, A., and Zannone, N. (2008). Why eliciting and managing legal requirements is hard. In Workshop on Requirements Engineering and Law, pages 26-30.
  14. Maxwell, J. and Anton, A. (2009). Checking existing requirements for compliance with law using a production rule model. In Workshop on Requirements Engineering and Law, pages 1-6.
  15. Nekvi, R., Ferrari, R., Berenbach, B., and Madhavji, N. (2011). Towards a compliance meta-model for system requirements in contractual projects. In Workshop on Requirements Engineering and Law, pages 74-77.
  16. Nuseibeh, B. (2001). Weaving together requirements and architectures. Computer, 34(3):115-117.
  17. Otto, P. and Anton, A. (2007). Addressing legal requirements in requirements engineering. In IEEE Conf. on Requirements Engineering, pages 5-14.
  18. Paech, B., von Knethen, A., Drr, J., Bayer, J., Kerkow, D., Kolb, R., Trendowicz, A., Punter, T., and Dutoit, A. (2003). An experience-based approach for integrating architecture and requirements engineering. In Workshop on Software Requirements to Architectures, pages 142-149.
  19. Pohl, K. and Sikora, E. (2007). Structuring the co-design of requirements and architecture. In Requirements Engineering: Foundation for Software Quality, pages 48- 62. Springer.
  20. Pretschner, A., Broy, M., Kruger, I. H., and Stauner, T. (2007). Software engineering for automotive systems: A roadmap. In Future of Software Engineering, pages 55-71. IEEE Computer Society.
  21. Rinke, T. and Weyer, T. (2007). Defining reference models for modelling qualities: How requirements engineering techniques can help. In Sawyer, P., Paech, B., and Heymans, P., editors, Requirements Engineering: Foundation for Software Quality, pages 335-340. Springer.
  22. Siena, A., Perini, A., Susi, A., and Mylopoulos, J. (2009a). A meta-model for modelling law-compliant requirements. In Workshop on Requirements Engineering and Law, pages 45-51.
  23. Siena, A., Perini, A., Susi, A., and Mylopoulos, J. (2009b). Towards a framework for law-compliant software requirements. In International Conference on Software Engineering. Companion Volume, pages 251-254.
  24. Spichkova, M. (2008). Refinement-based verification of interactive real-time systems. ENTCS, 214(0):131 - 157. BAC-FACS Refinement Workshop.
  25. Spichkova, M. (2011). Architecture: Requirements + Decomposition + Refinement. Softwaretechnik-Trends, 31(4).
  26. Spichkova, M. (2012). Human Factors of Formal Methods. In IADIS Interfaces and Human Computer Interaction (IHCI 2012), pages 307-310. IADIS Press.
  27. Spichkova, M., Hölzl, F., and Trachtenherz, D. (2012). Verified system development with the autofocus tool chain. In Workshop on Formal Methods in the Development of Software, EPTCS, pages 17-24.
  28. Spichkova, M., Schmidt, H., and Peake, I. (2013). From abstract modelling to remote cyber-physical integration/interoperability testing. In Improving Systems and Software Engineering Conference.
  29. van Lamsweerde, A. (2008). Requirements engineering: From craft to discipline. In International Symposium on Foundations of Software Engineering, SIGSOFT 7808/FSE-16, pages 238-249. ACM.
  30. Yin, Q., Madhavji, N., and Pattani, M. (2013). Eros: an approach for ensuring regulatory compliance of process outcomes. In Workshop on Requirements Engineering and Law, pages 21-24.
Download


Paper Citation


in Harvard Style

Spichkova M. and Schmidt H. (2015). Requirements Engineering Aspects of a Geographically Distributed Architecture . In Proceedings of the 10th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE, ISBN 978-989-758-100-7, pages 276-281. DOI: 10.5220/0005465802760281


in Bibtex Style

@conference{enase15,
author={Maria Spichkova and Heinz Schmidt},
title={Requirements Engineering Aspects of a Geographically Distributed Architecture},
booktitle={Proceedings of the 10th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,},
year={2015},
pages={276-281},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0005465802760281},
isbn={978-989-758-100-7},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 10th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,
TI - Requirements Engineering Aspects of a Geographically Distributed Architecture
SN - 978-989-758-100-7
AU - Spichkova M.
AU - Schmidt H.
PY - 2015
SP - 276
EP - 281
DO - 10.5220/0005465802760281