Table of Contents
Logical design of IoT:
- The Logical design of IoT is however too abstract to be used for building directly concrete architectures. In order to implement compliant IoT solutions, Reference Architectures must be defined, describing essential building blocks as well as design choices able to select specific constructs able to deal with converging requirements regarding functionality, performance, deployment, and security, to name a few. Interfaces among different technological functional blocks should be standardized; best practices in terms of functionality and information usage need to be provided.
- Existing literature provides methodologies for dealing with system architectures (hereafter called Concrete Architectures) based on Views and Perspectives. The way that the IoT-A project illustrates the Reference Architecture (RA) is through a matrix that provides clear technological choices in order to develop concrete architectures.
- To establish the contents of this matrix we need to analyze all possible functionalities, mechanisms and protocols that can be used for building any concrete IoT-related architecture and to show how interconnections could take place between selected design and technological choices. A system architect should then have a tool to make a rational selection of protocols, functional components, and architectural options needed to build specific IoT systems.
- The IoT-A project is viewed as a representation of one or more structural aspects of an architecture that illustrates how the architecture addresses one or more concerns held by one or more of its stakeholders. Some typical examples of viewpoints are Functional, Information, Concurrency, Development, Deployment, and Operational viewpoints. However, architectural decisions often address concerns that are common to more than one view. These concerns are often related to non-functional or quality properties.
- The approach that the project is following is to define special perspectives to address these aspects of concrete architecture, emphasizing the importance of stakeholder requirements. Therefore we define a perspective as a collection of activities, tactics, and guidelines that are used to ensure that a system exhibits a particular set of related quality properties that require consideration across a number of the system’s architectural views, where a quality property is defined as an externally visible, non-functional property of a system such as performance, security, or scalability.
Find more Related Post >>