Iot A Req

This deliverable presents the final list of requirements that were gathered in the process of developing the IoT Architectural Reference Model (IoT ARM). The requirements presented in this deliverable are potentially relevant for any concrete architecture derived from the IoT ARM, as they are based both on stakeholder requirements representing a typical mixture of relevant industrial domains and on internal requirements that were derived based on technical constraints.
# Iot Id Description Rationale Bussiness Scen Req Type
1 UNI.092 Remote services shall be accessible by human users The mobile phone of the consumer can and should be used for interacting with product centric services Retail NFR View
2 UNI.089 The system shall support reliable time synchronization Services which depend on a precise time need a guarantee that the devices they are communicating to have the right time. e-Health FR View
3 UNI.087 The system shall support service lifecycle management Road users want to use one service over a service life cycle e-Mobility FR View
4 UNI.073 The system shall allow the semantic description of physical entities and services by a user I would like a way to create and exchange semantics between objects in order to design new applications Smart City FR View
5 UNI.071 The system shall provide standardized and semantic communication between services Standard communications between objects, from a communication channel point of view but also from a semantic point of view. (Standardization of object semantic is somehow similar to the standardization of MIB (Management Information Base) of telecommunication equipments). Smart city DC View
6 UNI.070 The system shall handle semantic interoperability between different semantic levels I would like a way to create and exchange semantics between objects in order to design new applications Smart city FR View
7 UNI.067 The system shall provide different access permissions to information Sensitive data of patients must be kept secure in order to assure trust between the patients and to allow access to certain people e-Health FR View
8 UNI.066 The system shall provide integrity validation of virtual entities, devices, resources, and services In certain life-critical applications the device may be required to perform a secure start-up procedure that includes integrity checking. e-Health FR View
9 UNI.065 The system shall provide reliable services In order to accommodate certain scenarios, support of a certain degree of reliability might be necessary Smart city NFR View
10 UNI.064 The system shall provide security through resilience Security, why? Simply because the IoT - I am sure you will demonstrate it - is a kind of critical information infrastructure which means that if ever for whatever reason there is a failure somewhere on the IoT the impact will be so high that it would be a social loss, like if we do not have more electricity. Transportati on/Logistics NFR View
11 UNI.062 The system shall provide trusted and secure communication and information management A method for clarification whether the Cold/Hot Chain has been violated or not is required. To be able to do this, the detailed context information (e.g., temperature) of the things, which have been collected in some database need to be easily made available. This is for example of major importance to avoid any damage to the pharmaceutics during the transport and storage process. Transportati on/Logistics DC View
12 UNI.060 The system shall support different SLA Communication blackouts are not accepted from client side and particularly if they are paying for premium services e-Health NFR View
13 UNI.058 The system shall provide high availability Communication blackouts are not accepted from client side and particularly if they are paying for premium services e-Health NFR View
14 UNI.051 The system shall support mobility of the human user Citizens want to access all areas of a city Smart city FR View
15 UNI.050 The system shall support mobility of the physical entity The use of M2M Devices for monitoring health related information is not confined to the residence of the patient. e-Health FR View
16 UNI.049 Any system shall provide interoperability with other systems, including legacy ones Citizens do not want to use several city systems Smart city NFR View
17 UNI.048 The system shall provide interoperable naming and addressing IoT-A will play a role in terms of providing a kind of novel resolution infrastructure. We need to understand how best IoT could be served by scheme regarding the naming of objects, the addressing and assigning problems. (none specific) FR View
18 UNI.047 The system must ensure interoperability between objects or between applications As an example, CCTV system could inform traffic management of the length of the waiting queue at a crossroad. Having smart traffic lights receiving such input from the CCTV system could, could help changing the schedule of green/red light to optimize the traffic. Smart city NFR View
19 UNI.046 The system shall support storage of user data The mobile phone of the consumer can and should be used for assisting the user in all purchase relevant aspects Retail FR View
20 UNI.045 Services shall be accessible through semantic interfaces The mobile phone of the consumer can and should be used for interacting with product centric services Retail FR View
21 UNI.043 The system shall enable the composition of entity-related services The costs for complex logistics and healthcare processes need to be kept on a low level. A modular setup of the applications and services is one important ingredient to achieve this. Therefore it should be very easy to integrate things together with their atomic services into other services, and it should be easy for things to use services provided by others. Transportati on/Logistics FR View
22 UNI.042 Both user and device must be able to exchange information about their state Both the M2M server and the M2M device must be able to provide information about the current state e-Mobility NFR View
23 UNI.041 The system shall provide historical information about the physical entity A method for clarification whether the Cold/Hot Chain has been violated or not is required. To be able to do this, the continuous context information (e.g., temperature) of the things needs to be collected. This is for example of major importance to avoid any damage to the pharmaceutics during the transport and storage process. Transportati on/Logistics FR View
24 UNI.040 The system shall provide ways to ensure security and resilience Road users and energy providers want to avoid shortages/ blackouts Smart city NFR View
25 UNI.036 The system shall enable the retrieval of the self-description of things My wish is to retrieve the capacity of a thing. Thus, I can plan a change maintenance of all my bulbs if they can said when they should be changed Smart city FR View
26 UNI.032 The system shall enable the planning of automated tasks Today, due to sub-optimal processes, a lot of time and money is wasted. This situation could be improved a lot by tracking all the items/things, providing context data on them at any time and location, allowing for automated evaluation of the collected data and reacting immediately on a dangerous situation to protect against the break down of items. Transportati on/Logistics FR View
27 UNI.031 The system shall enable centralized or decentralized automated activities (control loops) Today, due to sub-optimal processes, a lot of time and money is wasted. This situation could be improved a lot by tracking all the items/things, providing context data on them at any time and location, allowing for automated evaluation of the collected data and reacting immediately on a dangerous situation to protect against the break down of items. Transportati on/Logistics TBD View
28 UNI.030 The system shall provide a resolution infrastructure for naming, addressing and assignment of virtual entities and services A system may be provided which is operable to determine a routing node for a data object. The system can comprise an identifier generator operable to generate an identifier for the data object on the basis of data content thereof, and a lookup engine operable to compare the identifier for the data object to a routing table to determine a routing node for the data element. e-Health FR View
29 UNI.029 The system shall provide a support for routing of data based on content A system may be provided which is operable to determine a routing node for a data object. The system can comprise an identifier generator operable to generate an identifier for the data object on the basis of data content thereof, and a lookup engine operable to compare the identifier for the data object to a routing table to determine a routing node for the data element. e-Health FR View
30 UNI.028 The system shall provide a message-priorisation mechanism Not every message has the same priority e-Health FR View
31 UNI.027 The system shall support prioritization of services In case of time-sensitive services the system needs to assure that important services are prioritized e-Health FR View
32 UNI.026 The system shall support timecritical message handling and delivery In case of emergency the RMD has to send or receive time critical messages e-Health FR View
33 UNI.023 The system shall provide access to external information sources, e.g. health databases Patients are able to initiate communication to the providers Electronic Medical Record (EMR) or health database application using the secure messaging tool for a variety of purposes. Examples include providing manually gathered information on existing selfmonitoring and/or chronic care regiments. e-Health FR View
34 UNI.022 The system shall support secure communication Patients are able to initiate communication to the providers Electronic Medical Record (EMR) or health database application using the secure messaging tool for a variety of purposes. Examples include providing manually gathered information on existing selfmonitoring and/or chronic care regiments. e-Health FR View
35 UNI.020 The system shall support realtime monitoring of radio usage of devices and gateways The application knows the current radio transmission activity of the M2M device e-Health FR View
36 UNI.019 The system shall support userinitiated communication Providers can initiate communication with the patients health monitoring device for a number of reasons. Examples of this include a provider querying the device for a reading or for configuring such a device e-Health FR View
37 UNI.018 The system shall support data processing (filtering, aggregation/fusion, ...) on different IoT-system levels (for instance device level) The remote monitoring device gathers patient measurements, data and or events. Data may be communicated each time the device gathers the data, accumulated measurements may be communicated periodically (e.g., hourly, daily), or data may be delivered upon request or upon certain events e-Health FR View
38 UNI.016 The system shall support physical entity location tracking (geo spatial and/or logical location) High value assets need to be tracked in order to avoid theft and also to know where they are currently located e-Mobility FR View
39 UNI.015 Devices shall have the possibility to be remotely controlled and configured The remote monitoring device may be configured by via the M2M network by the M2M application entities. The configuration capability could span simple parametric changes, such as, reporting rates, event or alarm trigger levels, and dosing levels to downloading and securely restarting new operating software e-Health FR View
40 UNI.014 The system shall support devices to activate themselves into a collaboration The remote monitoring device is prepared for use and communication by the action of the patient or clinician. This may involve physically attaching or placing the device, registering the device, setting up the communications channels to M2M application entities, setting up the communications capabilities of the device and providing for secure communications. e-Mobility FR View
41 UNI.012 The system shall be able to handle interference between IoT devices (avoidance and detection) In order to achieve a reliable eHealth service the system must be interference-free e-Health NFR View
42 UNI.010 The system shall enable autonomous goal-driven (taskdriven) collaboration between devices or services Smart objects should collaborate in order to realize a common goal (such as traffic lights in order to reduce traffic or pollution). Smart city NFR View
43 UNI.008 The system shall be able to run applications and services in and interoperable manner The problem is to provide a framework, a set of scenarios where these applications could be developed in harmony, in an interoperable way and in a way that responses to the real needs of organization and people (none specific) NFR View
44 UNI.005 The system shall support eventbased, periodic, and/or autonomous communication between devices The remote monitoring device gathers patient measurements, data and or events. Data may be communicated each time the device gathers the data, accumulated measurements may be communicated periodically (e.g., hourly, daily), or data may be delivered upon request or upon certain events e-Health FR View
45 UNI.004 The system shall enable the semantic description of physical entities I would like a way to create and exchange semantics between objects in order to design new applications Smart city NFR View
46 UNI.003 The system shall enable the provision and exchange of semantics between services in order to support the design of new applications I would like a way to create and exchange semantics between objects in order to design new applications Smart city NFR View
47 UNI.002 Human users have control how their data is exposed to other users Citizens want to protect their private data Smart city NFR View
48 UNI.001 The system shall provide a means to allow people to use Internet of Things services anonymously Citizens want to protect their private data Smart city NFR View
49 STW.331 The system should take into account external computing resources, e.g. 'the cloud'. Maybe there should be some part of processing information in the cloud. (none specific) DC View
50 STW.328 The system should include means to manage the energy consumption of devices. We must look out for a highly energy efficient system. (none specific) NFR View
51 STW.327 The system should include means to wake-up sleepy devices. We must look out also for some way to wake up sleepy communications in order to manage energy consume. (none specific) FR View
52 STW.321 The system shall guarantee correctness of resolutions (data). When searching for a certain object you need an implemented system that actually gives you the correct result. (none specific) FR View
53 STW.319 The system shall have a semantic understanding of distance and location. It is necessary to make the system know what defines a distance. (none specific) FR View
54 STW.311 The system shall support information (data) lifecycle management. Deal with the lifecycle of information (how to distinguish, if information (tag) is temporary not available or not valid any more?) (none specific) FR View
55 STW.042 The system shall support the autonomous and dynamic selection of protocols without human intervention. Future systems implementing the reference architecture shall allow for a dynamic selection of protocols and layers without any human intervention. (none specific) FR View
56 STW.036 The system shall include an interface to IP communication protocols. The reference architecture shall consider that we have gateways to IP everywhere, so we must have a global addressing system with protocol and so on. That would be an evolution of IPv6. Or we need an integration package for existing addressing systems. (none specific) DC View
57 STW.029 The system composition shall be driven by business scenarios. The reference architecture shall provide the building blocks in a creative way coming from a business perspective. (none specific) NFR View
58 STW.027 The system shall be extendible for future technologies. The reference architecture shall provide an integral approach that combines legacy aspects as well as an imaginating vision on the Internet of Things. (none specific) NFR View
59 IR5.9 Object capabilities may be universally defined at HW-level Enable plug n'play operations at user services level NFR View
60 IR5.8 Each object should have a universal ID, part of it read-only and part of it read/write Enable object recognition and setup/configuration in the context of particular applications development NFR View
61 IR5.7 Communication with the objects must be intermittent and commandbased Avoid traffic overhead NFR View
62 IR5.6 Data security & privacy should be enabled at atomic level NFR View
63 IR5.5 Connected objects shall be able to communicate with each other through the network via standard communication interfaces Enhance wide use potential FR View
64 IR5.4 Connected objects shall be able to do energy harvesting Maintain operation in harsh environments FR View
65 IR5.3 The identifier of the device (ID of an RFID tag for example) must not be tracked by unauthorized entities The tracking of items and then people raise the problem of privacy NFR View
66 IR5.2 The device (contactless card for example) must not be activated without the consent of the owner To avoid unsolicited scanning of people NFR View
67 IR5.10 Atomic-level protocols must implement only functions related to data acquisition (e.g. DSP-level), crypto and security Avoid overlap with user-level communication protocols (WP3) NFR View
68 IR5.1 The communicated messages must not be spied by an unauthorized person or device Confidentiality must be ensured NFR View
69 IR4.9 The Digital Entity History Storage should allow for storage of aggregation changes This is a main functionality of the BRIDGE system which applies to RFID/assets tracked in the EPCGlobal framework FR View
70 IR4.8 Services (and information providing services) connected with the IoT system can indicate what information can be found by a Discovery/Look-up service Opting out of being found in a data search was indicated in the BRIDGE requirement and also in the IoT-A stakeholders. The BRIDGE requirement was "Data that companies are willing to provide to the Discovery Services are mainly URL addresses of databases / EPCIS repositories" FR View
71 IR4.7 The look-up service of IoT-A shall withhold or grant information depending on context such as application involved, requesting entity, and security permissions Needed for fulfilling security requests of stakeholders. Derived from BRIDGE requirement: "A broad set of data from enterprise applications MAY be requested depending on context, industry, application, etc" FR View
72 IR4.6 The location model shall enable the implementation of the following Derived from SP requirement: "The location model shall support the following common location queries: position queries, nearest neighbor queries, navigational queries, and range queries" FR View
73 IR4.5 The location model shall allow programmers to add new coordinate reference systems and shall support the transformation of coordinates among them Derived from SP requirement: The location model shall allow programmers to add new coordinate reference systems and shall support the transformation of coordinates among them FR View
74 IR4.4 IoT-A shall support a hybrid location model, that is, it shall support symbolic coordinates as well as local and global Derived from SP requirement "Smart products shall support a hybrid location model, that is, it shall support symbolic coordinates as well as local and global FR View
75 IR4.32 IoT system should define a common virtual identification system (virtual-ID) An universal identifier should be defined as standard ID in order to map it to the specific ID used in every type of system (TCP/IP, RFID, ...) FR View
76 IR4.31 A VE that is associated with a PE that changes geolocation shall update coordinates/address/locator through IoT system service IoT Service Monitoring is a service that manages the coordinates/address/locator and uses for the Resolution Service by return the last address/locator FR View
77 IR4.30 The IoT system shall have a service to register the proper URI and the locator of the new registered resource/service To managed by dynamic linker, uses for the Resolution Service by return the last address/locator FR View
78 IR4.3 IoT-A shall support a standardized location model and locationinformation representation. Derived from SP requirement "Smart products shall support a standardized location model and location-information representation." FR View
79 IR4.29 The IoT system shall have a service to insert the operational specifications of the new registered resource/service VE Service Specification manage the association ID(VID) to the operational specification for the LookUp Service FR View
80 IR4.28 The IoT system shall have a service to obtain a new identifier to the new VE registered resource/service and to save the description of its services VE Service Identifier manages the ID (VID) and the semantic description, for the Global Discovery Search. FR View
81 IR4.27 The Discovery Service in local search, is required to find service/resource based on (rough) semantic description Because the discovery service in local search combine the peer to peer discovery with the white search (no semantic filter) in the geolocalization context. FR View
82 IR4.26 The IoT System shall be able to accept and manage semantic queries from the user and return Resources/Services Necessary for the match in the VE Semantic Retrieval FR View
83 IR4.25 The IoT Service Identifier shall use the service/resource description for retrieval The IoT System must consider the description of a service/resource for the semantic indexing on which the search will be performed FR View
84 IR4.24 The IoT system must provide privacy protection for users accessing information about physical entities or services For acceptance of the Internet of Things privacy during usage must be guaranteed DC View
85 IR4.23 The IoT system must respect the privacy aspects when performing discovery, resolution and lookup Privacy is a key aspect for the IoT. DC View
86 IR4.22 The IoT system shall enable the discovery and lookup of associations across multiple administrative domains. The Internet of Things will consist of multiple administrative domains with different owners. To develop its full potential interactions, including lookup and discovery, across domain boundaries must be possible. DC View
87 IR4.21 The IoT system must be able to track dynamic associations between an virtual entity and services based on geographic location to determine whether they are still valid. Mobility is one of the key aspects for changing associations. By monitoring the location of physical entities, e.g., using location services, it can be determined when associations become invalid due to the geographic distance of physical entities and possibly other aspects. FR View
88 IR4.20 The IoT system must be able to discover dynamic associations based on geographic location and other context information. Mobility is one of the key aspects for changing associations. By monitoring the location of physical entities and area for which resources can provide information, possibly in combination with other context information, dynamic associations between physical entities and services providing access to resources can be discovered. FR View
89 IR4.2 A geographical location attribute shall exist for virtual entities Confirms our present plan of having some geographical representation. Derived from SP requirement "A SmartProduct should be able to access the location information of other SmartProducts" FR View
90 IR4.19 The IoT system must be able to track dynamic associations between an augmented entity and services related to the augmented entity to determine whether they are still valid. Due to the mobility of augmented entities as well as devices whose resources are accessible through services, changing services may provide information, allow actuation or enable interaction with augmented entities. In order to provide the currently relevant services for an augmented entity, the dynamic associations must be tracked to determine whether they are still valid. FR View
91 IR4.18 The IoT system must be able to discover dynamic associations between an virtual entities and services related to the virtual entities Due to the mobility of physical entities as well as devices whose resources are accessible through services, changing services may provide information, allow actuation or enable interaction with physical entities. In order to provide the currently relevant services for a corresponding virtual entity, the dynamic associations must be discovered FR View
92 IR4.17 The IoT system must enable the resolution of service identifiers to service locators. Due to the heterogeneity, dynamicity and mobility in the Internet of Things, the communication endpoint may change or different endpoints may be suitable for different applications. Therefore, services should be uniquely identified by a service identifier, but this identifier should not be used for locating the service, so a resolution step is necessary. FR View
93 IR4.16 The IoT system must enable the lookup of service descriptions of specified services for an augmented entity with the augmented entity identifier as key for the lookup. It is important to find the services related to an augmented entity that may provide information about it, allow to actuate the augmented entity or enable interaction with the augmented entity. FR View
94 IR4.15 The IoT system must enable the dynamic discovery of relevant physical entities and their related services based on a geographical location scope. Geographic location is one of the most important aspects for finding relevant physical entities. Spatial relations are of prime importance in the physical world. FR View
95 IR4.14 The IoT system must enable the dynamic discovery of relevant virtual entities and their related services based on respective specifications. Augmented entities are the core concept proposed for IoT and to enable applications that do not have to be a-priori configured for a fixed set of augmented entities, discovery at runtime must be possible. FR View
96 IR4.13 Access-control rights/ policies (set up by data owners) shall not be published publicly. Access control policies themselves, if known, can give away information. DC View
97 IR4.12 Data owners should be able to set access-control rights/ policies (set up by data owners) to their data stored on resources This addresses privacy by putting the control in the hands of the data owners (or certain external groups) FR View
98 IR4.11 Clients requesting data via the Discovery/Lookup services shall be uniquely identifiable BRIDGE mentioned that the unique client identification at the DS is required to control access to data stored on the DS (particularly EPC number and link). FR View
99 IR4.10 The Digital Entity History Storage shall be restricted in who can call delete and update functions The integrity and trust in the history storage block depends on how "unaltered" it is. The BRIDGE SoTA justifies the present use of the "history storage" component. They expressed it as "Discovery Service security policies may be set to restrict update and delete actions on DS records to provide a journal functionality" FR View
100 IR4.1 Discovery and lookup service of IoT systems shall allow the locating physical entities based on geographical parameters Confirms our present plan of having some geographical representation. This requirement is derived from SmartProducts (SP) requirement "A SmartProduct should be able to locate another SmartProduct in the same environment w.r.t. their environment" FR View
101 IR2.9 The process editor must be interoperable with developments of other WPs and Tasks. The projects results should be combinable to reach the common project goals. FR View
102 IR2.8 The process editor has to provide an attractive graphical user interface. The project results need to be representable in a research review. NFR View
103 IR2.7 The process editor must be "easily and fastly" extendable. First project results should be presentable in a small time frame. NFR View
104 IR2.6 The process editor must be able to verify the syntax of the process model. The technical user needs information about the correctness of the syntax before the execution. FR View
105 IR2.53 The orchestration engines shall support setting preferences for selecting services involved in composition Users can have the possibility to prefer one service over another for any reason FR View
106 IR2.52 The orchestration engine shall provide feedback within a reasonable amount of time (<5sec) A time out must be set for request/response loops NFR View
107 IR2.51 The orchestration shall provide a feedback to the user who sent a composition request The feedback should contain a message about the success of the requested composition FR View
108 IR2.50 The orchestration shall access service resolution Orchestration depends on service descriptions provided by discovery FR View
109 IR2.5 The process editor has to be enduser-friendly. A business user needs to be able to model a process. NFR View
110 IR2.49 The orchestration engine shall increase quality of information by service composition QoI can be increased by using additional information as reference FR View
111 IR2.48 The orchestration engine shall handle scopes for selecting services for composition Scopes selected for composed service must be applied to the atomic services as well FR View
112 IR2.47 The orchestration engine shall support flexible composition Services involved in compositions can fail and need to be replaced by some serving equal needs FR View
113 IR2.46 The orchestration engine shall create new service descriptions The newly created service must be registered with service discovery FR View
114 IR2.45 The orchestration engine shall support creation of new applications Higher level services should create new functionality FR View
115 IR2.44 The orchestration engine shall interpret service descriptions service orchestration is done based on service descriptions FR View
116 IR2.43 The IoT-A architecture shall provide mechanisms to publish and present the resource/entity/service description meta data as linked-data This will enable linking the published description to other domain knowledge and also location models described by third party ontologies or open linked data concepts and will also support reasoning the data based on high-level concepts and entities defined in domain ontologies FR View
117 IR2.42 The IoT-A architecture shall provide standard query end-points and generic reasoning mechanisms to infer the emerging data and to process the stored meta-data related to resources/entities This will provide generic interface to query the stored meta-data and to enable high-level applications/services to perform query and reasoning upon the existing/emerging data FR View
118 IR2.41 The IoT-A architecture shall provide unified interfaces to access and query the observation and measurement data emerging from resources This will enable integration of IoT data into business layer and high-level applications; this will be also related to requirement IR2.39 FR View
119 IR2.40 The IoT-A architecture shall provide unified interfaces to access and query the resource/entity meta data This will enable WP4 discovery and identification and also reasoning mechanisms to access the required descriptions FR View
120 IR2.4 The process editor must provide facilities to model on technical level. A technical user is not able to specify the business frame of a process. FR View
121 IR2.39 The IoT-A architecture shall provide a shared memory of the observable phenomenon Due to services could not be online all the time it could be necessary to incorporate a shared memory in order to store this information. FR View
122 IR2.38 The IoT-A reference architecture shall provide event templates that can be related to types of augmented entities Events can be defined for a class of augmented entities at design time, but evaluated for every augmented entities of the same type at runtime. Otherwise Events must be defined for every particular augmented entity. FR View
123 IR2.37 The IoT-A reference architecture shall provide events that can be related to augmented entities Augmented entities are the key concepts in IoTA with which the applications will deal with. FR View
124 IR2.36 Quality of information related to virtual entities can be retrieved from the system Different devices provide information with varying quality. An application may have certain quality requirements. FR View
125 IR2.35 Processing of events must take quality of information (QoI) into account QoI may have an impact on applied processing and varies processing steps (e.g. mean calculation), FR View
126 IR2.34 Events are processed on a set of distributed nodes A distributed architecture provides more flexibility in the way events are processed, saves energy and allows minimal functionality if there is no network connectivity NFR View
127 IR2.33 Mobile entities must be able to provide events to the platform Many physical entities such as mobile phones, products in a retail store, etc. are mobile and IoT-A must be able to detect changes related to those entities FR View
128 IR2.32 The process execution engine must support the integration with a Complex Event Processing (CEP) component. One WP central process execution engine including the CEP enables a bigger research contribution. FR View
129 IR2.31 The process execution engine must support BPMN 2.0 completely. The development effort should focus on the BPMN IoT extension. FR View
130 IR2.30 The process execution engine must be interoperable with the results and development of the other WP task. The projects results should be combinable to reach the common project goals. FR View
131 IR2.3 The process editor must provide facilities to model on business level. A business user is not able to specify an executable process model. FR View
132 IR2.29 The process execution engine must be "easily and fastly" extendable. The development should focus on the IoT related extension. NFR View
133 IR2.28 The process execution engine must be able to execute defined BPMN 2.0 extensions. The execution demonstrates the benefit of the graphical extension. FR View
134 IR2.27 The process execution engine must be able to execute processes described in BPMN 2.0 format. The graphically defined BPMN 2.0 process model can be executed without mapping the process model to another notation. FR View
135 IR2.26 The BPMN extension must provide means for expressing real-time constraints. As the process interact with augmented entities real-time constraints apply to these processes FR View
136 IR2.25 The BPMN extension must provide means for expressing the uncertainty of process components. The uncertainty of individual process components can influence the process creation on model and execution time. FR View
137 IR2.24 The BPMN extension must provide means for designing context-aware business processes. Depending on occurring events the IoT processes need to be highly flexible. FR View
138 IR2.23 The BPMN extension must provide means to express the tolerable error rate of a process. Depending on the process, a process result is still acceptable as far it stays under a tolerable error rate. FR View
139 IR2.22 The BPMN extension must support means to express the availability of a process component. Due to the mobile nature that physical entities, devices and its services and data often have, a business process can have a different availability depending on its involved components. FR View
140 IR2.21 The BPMN extension must support the abstraction of individual process components. In the IoT multiple devices, resources and services can appear. The accuracy and availability of accumulated data can be of much higher importance for the process than the data of individual components. The extension shall provide abstractive individual process components. FR View
141 IR2.20 The BPMN extension must provide means to scalably model and execute processes independently of the number of involved process components. In IoT processes multiple physical entities, devices, resources and services can appear, which could negatively effect the performance of the execution. FR View
142 IR2.2 The process editor must be extendable. The reuse of a comprehensive tool allows to focus the effort. FR View
143 IR2.19 The BPMN extension must support to arrange data distribution over several data storages (resources) of devices. Business Processes in the IoT distribute data objects in resources of many devices. FR View
144 IR2.18 The BPMN extension must support the modelling of different IoT specific interaction types. The interaction between different devices, the integration of information about physical entities, and the interaction between services characterizes the IoT. FR View
145 IR2.17 The BPMN extension must support the process execution distributed over several devices. In the IoT the execution of process steps can be distributed over several devices. FR View
146 IR2.16 The BPMN extension must support an entity based approach defined by the domain model of WP1. The domain model is one key result by WP1 and should fit to the business modeling approach of WP2. FR View
147 IR2.15 The process modeling notation has to be a standard. A common standard maximizes the potential application of industrial stakeholders. NFR View
148 IR2.14 The process modeling notation has to offer a graphical representation. A graphical process notation offers a symbolism to easily model and document business processes. FR View
149 IR2.13 The process modeling notation has to be IoT-aware. Due to the DOW the project focuses on IoT processes. NFR View
150 IR2.12 The process modeling notation has to be executable. The projects task 2.2 and 2.3 should closely work together and represent a hand in hand solution. FR View
151 IR2.11 The process modeling notation has to be extensible in terms of the definition of new stencils, the specification of new syntax, the definition of serialisation and execution semantics. The reuse of an existing process modeling notation allows to focus the effort on the IoTextension. FR View
152 IR2.10 The process editor must support BPMN 2.0 completely (in particular the IoT-aware parts) The development effort should focus on the BPMN IoT extension. DC View
153 IR2.1 The process editor must be able to create BPMN 2.0.D25 BPMN 2.0 was evaluated to be the most IoTaware process notation. FR View
Records : 153 of 153 | Page : of 1 | Limit