Abstract
The Internet of Things (IoT) is a paradigm that permits smart entities to be interconnected anywhere and anyhow. IoT opens new opportunities but also rises new issues. In this dynamic environment, trust is useful to mitigate these issues. In fact, it is important that the smart entities could know and trust the other smart entities in order to collaborate with them. So far, there is a lack of research when considering trust through the whole System Development Life Cycle (SDLC) of a smart IoT entity. In this paper, we suggest a new approach that considers trust not only at the end of the SDLC but also at the start of it. More precisely, we explore the modeling phase proposing a model-driven approach extending UML and SysML considering trust and its related domains, such as security and privacy. We propose stereotypes for each diagram in order to give developers a way to represent trust elements in an effective way. Moreover, we propose two new diagrams that are very important for the IoT: a traceability diagram and a context diagram. This model-driven approach will help developers to model the smart IoT entities according to the requirements elicited in the previous phases of the SDLC. These models will be a fundamental input for the following and final phases of the SDLC.
Highlights
The Internet of Things (IoT) is a paradigm that permits smart entities to be interconnected anywhere and anyhow [1]
We propose an extension of the class diagram (CD), which is widely used in UML and Software Engineering
We extend existing diagrams adding new features and stereotypes
Summary
The Internet of Things (IoT) is a paradigm that permits smart entities (i.e., smart things and humans) to be interconnected anywhere and anyhow [1]. Gartner forecasted that 20.4 billions of devices will be connected by 2020 and, in the same year, the IoT spending will reach almost 3 trillion US$.1 These numbers show how IoT can grow in the future. We have presented a framework that holistically considers trust during the SDLC of an IoT entity [8]. It is composed of a K-Model and transversal activities (i.e., Traceability, Risk Analysis). The first phase is about the need phase, where the purpose of the new IoT entity is presented and discussed among all the stakeholders They are all the actors having an interest in the new IoT entity that is going to be developed. It is important to understand where the new IoT entity will be used by the final customers and to know which kind of architecture will be considered in its working environment [37,38,39]
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
