Abstract
The new generation of smart systems require processing a vast amount of information from distributed data sources, while fulfilling non-functional properties related to real-time, energy-efficiency, communication quality and security. The ELASTIC software architecture is being developed to tackle this challenge, considering the complete continuum from the edge to the cloud. This paper provides a brief analysis of the smart application considered in the project, and the requirements emanating from their non-functional properties. The paper then identifies some of the technical constrains imposed to the ELASTIC software architecture to allow guaranteeing the non-functional requirements of the systems.
- ELASTIC Consortium, Deliverable D4.2: "Nonfunctional properties analysis and constraints specification", May 2019Google Scholar
- ELASTIC Consortium, Deliverable D1.1: "Use case requirement specification and definition", May 2019Google Scholar
- Definition of a Research and Innovation Policy Leveraging Cloud Computing and IoT Combination, European Commission DG Communications Networks, Content & Technology, 2014 ISBN 978--92--79--47760--7 DOI:10.2759/38400.Google Scholar
- Henning Butz, Open integrated modular avionic (IMA): State of the art and future development road, Technical report, Department of Avionic Systems, Airbus Deutschland GmbH, 2010.Google Scholar
- ITU-T, Focus Group on Aviation Applications of Cloud Computing for Flight Data MonitoringGoogle Scholar
- ITU-T, Existing and emerging technologies of cloud computing and data analytics, 2016Google Scholar
- EASA, Flight Data Monitoring on ATR Aircraft, 2016Google Scholar
- Rajeev Thakur. "Infrared Sensors for Autonomous Vehicles". Recent Development in Optoelectronic Devices, IntechOpen, 2017. DOI: 10.5772/intechopen.70577Google Scholar
- M. Campbell, M. Egerstedt, J.P. How, R.M. Murray. "Autonomous driving in urban environments: approaches, lessons and challenges". Philosophical Transactions of the Royal Society of London A: Mathematical, Physical and Engineering Sciences, 368:4649--4672, 2010. DOI: 10.1098/rsta.2010.0110Google Scholar
Cross Ref
- Liu, S.; Tang, J.; Wang, C.; Wang, Q.; Gaudiot, J.L. "A Unified Cloud Platform for Autonomous Driving". Computer, 50: 42--49, 2017 Google Scholar
Digital Library
- Andy Greenberg. "The Jeep Hackers are Back to Prove Car Hacking Can Get Much Worse", Wired, January 2018. Available at: https://www.wired.com/2016/08/jeep-hackers-returnhigh- speed-steering-acceleration-hacks/Google Scholar
- Jared Gall. "Can a Connected Car Ever Be Safe from hacking?", Car and Driver, October 2017. Available at: https://www.caranddriver.com/features/a15079914/ cana- connected-car-ever-be-safe-from-hacking-feature/Google Scholar
- Gabrielle Coppola, Esha Dey. "Driverless Cars Are Giving Engineers a Fuel Economy Headache". Bloomberg, October 2017. Available at: https://www.bloomberg.com/ news/articles/2017--10- 11/driverless-cars-are-giving-engineers-a-fuel-economyheadacheGoogle Scholar
- CENELEC, EN 50159 : Railway applications - Communication, signalling and processing systems - Safety-related communication in transmission systems, 2011Google Scholar
- P.Toillon, P.B.Champeaux, D.Faura, W.Terroy, M.Gatti, An optimized answer toward a Switchless Avionics Communication Network, DASC 2015Google Scholar
- EU General Data Protection Regulation, https://ec.europa.eu/commission/priorities/justice-andfundamental- rights/data-protection/2018-reform-eu-dataprotection- rules_enGoogle Scholar
Recommendations
Are "non-functional" requirements really non-functional?: an investigation of non-functional requirements in practice
ICSE '16: Proceedings of the 38th International Conference on Software EngineeringNon-functional requirements (NFRs) are commonly distinguished from functional requirements by differentiating how the system shall do something in contrast to what the system shall do. This distinction is not only prevalent in research, but also ...
Toward improved traceability of non-functional requirements
TEFSE '05: Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineeringThis position paper examines current practices and challenges for tracing non-functional requirements (NFRs). Anecdotal evidence suggests that many organizations do not effectively trace NFRs and that functional changes are often implemented with very ...
An Ontological Approach to Specify Conflicts among Non-Functional Requirements
ICGDA 2019: Proceedings of the 2019 2nd International Conference on Geoinformatics and Data AnalysisIt is a usual practice for a user to narrate the Non-Functional Requirements (NFRs) in natural language and the requirements engineers manually try to express the same, using semi-formal or formal language notations. However, inaccurate and the ...






Comments