Supporting the Standardization Process of Smart City Systems

Marion Gottschalk


The continuous development in information and communication technologies (ICT) and the resulting research area Internet of Things (IoT) enable the connection of more and more hardware and software systems. IoT describes a global infrastructure for the information society to enable interconnecting physical and virtual things based on existing and evolving ICT. Regarding the development of smart cities that constitutes a system of systems concept using ICT, a defined, or, better still, a standardized way to define and to link various systems is necessary. Smart cities are innovative cities that use ICT to make urban operations and services more efficient for improving the quality of life. Smart cities are difficult to realize because they are complex based on their system of systems concept. It starts with the specification process. Each smart city system has many requirements – functional and non-functional requirements – which have to be matched with each other and have to be complemented with further requirements to connect systems – interface requirements. For supporting the requirements specification process, the IEC adapts the use case methodology to offer a standardized template for describing all functional requirements of a complex systems in the same way and for detecting standardization gaps (IEC 62559-2). On the basis of these requirements, complex systems are implemented. If errors are occurred or rather detected during the implementation process of smart cities, it can be very time consuming and expensive to correct these errors. Thus, it is important and sensible to invest time and money in the specification process of future smart cities to get consistent requirements and to prevent errors. Aim of the PhD project is to create and to evaluate an approach to support the standardization and the management of requirements for complex systems by automated consistency checks.


  1. Apfelbacher, R. (2007). Tolerierbare Inkonsistenzen in Konzeptbeschreibungen. PhD thesis, University of Postdam.
  2. Berry, M. W. and Castellanos, M., editors (2007). Survey of Text Mining: Clustering, Classication, and Retrieval, volume 2. Springer.
  3. CISCO and AGT International (2014). AGT and Cisco Traffic Incident Management Solution: Improving Traffic Safety and Efficiency. Technical report, CISCO and AGT International.
  4. Cockburn, A. (2000). Wrting Effective Use Cases. AddisonWesley Professional.
  5. DaCosta, F. (2013). Rethinking the Internet of Things: a scalable approach to connecting everything. Apress.
  6. Discern (2016). Discern - Distributed Intelligence for Cost-effective and Reliable Solutions. last visit on 28th January 2016.
  7. DKE (2014). The German Standardization Roadmap Smart City. Technical Report 1, DKE.
  8. DKE (2015). The German Standardization Roadmap Smart City. Technical Report 1.1, DKE.
  9. Evans, C., Brodie, L., and Augusto, J. C. (2014). Requirements Engineering for Intelligent Environments. In International Conference on Intelligent Environments.
  10. Heim, P., Lohmann, S., Lauenroth, K., and Ziegler, J. (2008). Graph-based Visualization of Requirements Relationships. In Requirements Engineering Visualization, pages 51-55. IEEE.
  11. Heitmeyer, C., Jeffords, R., and Labaw, B. (1996). Automated consistency checking of requirements specications. In ACM Transactions on Software Engineering and Methodology (TOSEM).
  12. Hevner, A. and Chatterjee, S. (2010). Design Research in Information Systems. In Integrated Series in Information Systems 22, pages 9-21. Springer Science+Business Media.
  13. IEC (2015). IEC 62559-2:2015 Use case methodology - Part 2: Definition of the templates for use cases, actor list and requirements list.
  14. IEEE (1990). Standard: IEEE Std 610 - IEEE Standard Glossary of Software Engineering Terminology.
  15. IEEE (1998). IEEE Recommended Practice for Software Requirements Specification.
  16. ITU-T (2012). Overview of the Internet of things. Technical Report Y.2060, ITU.
  17. ITU-T FG-SSC (2014). Smart sustainable cities: An analysis of definitions . Technical report, ITU-T.
  18. Johnson, C. (2011). Achieving Systems Safety, chapter CyberSafety: On the Interactions between CyberSecurity and the Software Engineering of Safety-Critical Systems, pages 85-95. Springer.
  19. Khairuddin, N. N. and Hashim, K. (2008). Requirements Visualization Techniques: A Comparative Analysis. In Proceedings of the 8th Conference on Applied Computer Science, ACS08.
  20. Kibble, R. (2013). Introduction to natural language processing. Technical report, University of London.
  21. Lamsweerde, A. v. (2009). Requirements Engineering: From System Goals to UML Models to Software Specifications . Wiley.
  22. Ludewig, J. (2007). Software Engineering. dpunkt Verlag.
  23. OMG (2011). Unified Modeling Language. Technical report, OMG.
  24. Parnas, D. L. and Clements, P. C. (1986). A Rational Design Process: How and Why to Fake It. IEEE Transactions on Software Engineering, (2):251-257.
  25. Peffers, K., Tuunanen, T., Gengler, C. E., Rossi, M., Hui, W., Virtanen, V., and Bragge, J. (2006). The Design Science Research Process: A Model for Producing and Presenting Information System Research. In DESRIST, pages 83-106.
  26. Port, D., Nikora, A., Hayes, J. H., and Huang, L. (2011). Text Mining Support for Software Requirements: Traceability Assurance. In System Sciences (HICSS).
  27. Rittel, H. W. and Webber, M. M. (1973). Dilemmas in a general theory of planning. Policy sciences.
  28. Robertson, S. and Robertson, J. (2012). Mastering the Requirements Process - Getting Requirements Right. Addison-Wesley.
  29. Rupp, C. and die SOPHISTen, editor (2014). RequirementsEngineering und -Management. Hanser Verlag.
  30. Smart Software (2016). Spell Checker for Chrome.
  31. Sommerville, I. (2009). Software Engineering, volume 9, chapter Formal Specification. Addison Wesley.
  32. Sommerville, I., Cliff, D., Calinescu, R., Keen, J., Kelly, T., Kwiatkowska, M., McDermid, J., and Paige, R. (2011). Large-scale complex IT systems. Communications of the ACM, 55(7):71-77.
  33. Sutcliffe, A., Fickas, S., and Sohlber, M. M. (2006). PC-RE: a method for personal and contextual requirements engineering with some experience. Requirements Eng.
  34. Systems and Software Engineering Directorate (2008). Systems Engineering Guide for Systems of Systems. Technical report, Office to the Deputy Under Secretary of Defense for Acquisition and Technology, Washington, DC.
  35. Tan, A.-H. (1999). Text Mining: Promises and Challenges. In South East Asia Regional Computer Confederation.
  36. Tragos, E. Z., Angelakis, V., Fragkiadakis, A., Gundlegard, D., Nechifor, C., Oikonomou, G., Pöhls, H. C., and Gavras, A. (2014). Enabling Reliable and Secure IoTbased Smart City Applications. In The First Internation Workshop on Pervasive Systems for Smart Cities.
  37. Wagner, S. (2014). Verkehrssteuerung über die Siemens private cloud”. Technical report, Siemens.
  38. Wiesner, S., Baalsrud Hauge, J., and Thoben, K.-D. (2015). Challenges for Requirements Engineering of CyberPhysical Systems in Distributed Environments. In

Paper Citation

in Harvard Style

Gottschalk M. (2016). Supporting the Standardization Process of Smart City Systems . In Doctoral Consortium - DCSMARTGREENS, (SMARTGREENS 2016) ISBN , pages 17-27

in Bibtex Style

author={Marion Gottschalk},
title={Supporting the Standardization Process of Smart City Systems},
booktitle={Doctoral Consortium - DCSMARTGREENS, (SMARTGREENS 2016)},

in EndNote Style

JO - Doctoral Consortium - DCSMARTGREENS, (SMARTGREENS 2016)
TI - Supporting the Standardization Process of Smart City Systems
SN -
AU - Gottschalk M.
PY - 2016
SP - 17
EP - 27
DO -