Abstract
Aspect-Oriented Programming (AOP) provides new constructs and concepts to handle secondary requirements in applications. Secondary requirements, i.e. crosscutting concerns, of the Internet of things (IoT) applications is inherited from the nature of the complexity of interactions, and implementation crosscutting concerns over core IoT architecture. Realizing the full potential of the IoT application requires a new abstraction design technique. This paper proposes an abstract class element toward a design approach to providing better means better separation of concerns. The proposed approach is accompanied by gathering relevant contextual properties pertaining to the environment of IoT interactions. A new architectural aspect-aware definition is proposed for tracking the logic of interaction characteristics on the IoT components being designed.
Highlights
Internet of Things (IoT) is a modern technology evolved throughout the years
This section explains a little bit of background and essential major related studies and works that focused on managing IoT application complexity and portability either using Aspect Orientation (AO) or non-AO methods
Atomic-context components obtained by pulling a set of interactions among low-level components occur when execution of one component modifies the behaviour of another one. Such interactions may cause by modification or extension aspects to any state that is accessible by high-level glue-aspect components, including the state of the core IoT application, communications, protocols, and network
Summary
Internet of Things (IoT) is a modern technology evolved throughout the years. IoT has turned into the most crucial and prevalent system that empowers everybody to make, create, offer, utilize the data to produce information. With IoT real word and digital words are interacting through various kinds of technologies such as internet protocols, sensors types and communication [4] Having all these issues in mind, there will be so many crosscutting concerns that spread across different components of IoT architecture [15]. The proposed model presents BIP-AOP as an IoT-aware interaction design through introducing a set of intercepted invoke/execution points These points represent IoTrelated context information, which are encapsulated into a high-level abstract aspect. IoT layer represents systems interactions between components; AOP layer represents a mediator on the IoT infrastructure to glue the IoT-related components with needed application concerns; and Application layer allows developer to customize the IoT behaviors without prior implementation knowledge All those layers are mapped into BIP components to address the design of an eventbased interaction components as a solution for pulling all relevant context information from IoT components.
Sign-in/Register to view highlights & summary 
Published Version (
Free)
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 call