Change of Functional Requirements For Information Systems Integration With Internet of Things

Nowadays there are some concepts that indicate a new revolution in information technology and systems. Internet of Things (IoT) is one of those which produce significant changes at information systems level. In this context, information systems developers are challenged with numerous practical and theoretical controversial topics on the adaptation of information systems to the IoT characteristics. Most studies approach the new issue from the architecture perspective and the infrastructure required for communication. But, there are few approaches about functional requirements, data streaming and data processing to be adapted to the Internet of Things. This is the aim of our paper. In that regard, we proceed to identify the state-of-the-arts in this field, based on literature review, and we use the modelling methods and field of expertise. Next, we will highlight the key features that should be mastered in order to integrate the IoT into information systems for the new synchronized enterprises. Moreover, this paper will emphasize the changes related to the functional requirements based on the general framework proposed. Most functional requirements aim to change the method of data gathering, processing and communication, recording information generated by business transactions and include data that have not been considered before by business systems as they were viewed as being the main elements of technical and engineer systems.

seemed to be developing in the coming years, it did not happen in terms of applicability.Even if the RFID technology had been used on well-defined segments of business, it could not be applied on a large scale due to difficulties related to broad band communications, standardization of communication languages, web platforms and interoperability of systems, especially of the embedded systems.In addition, there also was the high cost of RFID tags, lack of devices, embedded software products for gathering, processing and communication of data in different formats, structured or unstructured.Also, there were difficulties due to the high volume of collected data.Therefore, from the wallmart symphony, things did not develop, as quickly as we had expected.So, starting with 2008-2010, together with the explosion of cloud technologies, platforms based on semantic web and ontology, the presence of the big data concept and large scale use of data analytics, business intelligence, pervasive computing, augmented reality, the Internet of Things became the Internet of Everything, even though the expression IoT has been kept.This is the reason why topics such as the impact, influence, advantages, disadvantages and challenges of the IoT on business information systems have been reactivated.
Most literature, as it has also been noted by other authors, investigates data communication, interoperability, security, system architecture (Zambonelli 2016), (Chen et al. 2014), (Matos et al. 2015), (Lee and Lee 2015), (Dar et al. 2015), but less the last layer of architecture, that of information systems and the integration of the IoT into company architecture.
So, we will move from a general architecture of the IoT to data processing, the new requirements by which information systems may use the IoT.The architecture from which we start our study is based on views of (Oprea 1999), (Cretu 2006), (Dospinescu and Perca 2011), (Fotache and Cogean 2013), (Dospinescu and Perca 2013), (Pavaloaia 2013), (Greavu-Serban 2015).Considering the changes generated by the integration of the IoT into the architecture of a company, new terms have been used, such as sensing enterprises (Boza et al. 2016), generic enablers (Barmpounakisa 2015), smart enterprises (Fang et al. 2015), and we suggest the term connected and synchronized enterprises.These terms underline the challenges faced by enterprises through the IoT, data now attract objects and objects generate data requiring an integration and perfect synchronization of systems, objects and companies.New business models that companies have to adopt, the use of the IoT in different fields, the impact of the IoT upon information systems ask for proper solutions, so that data created benefits to users and not even bigger problems if they would not have adopted the IoT.
Studies by (Boza 2015), (Zambonelli 2016), (Chen et al. 2014), (Dar et al. 2015), (Fang et al. 2015), (Verdouw et al. 2015), (Meroni 2015) suggest that the focus has been mostly on the physical layer of connected equipment and objects, the integration of the IoT not being well-researched from the methodological and systematic perspective of information systems and business data and applications.
Therefore, we will identify, by means of use case diagrams, the requirements of the systems that ask for the attention of those involved in the development/adaptation of systems to the IoT.This will be done starting from the framework suggested for the interaction of the information system with external entities by means of its integration with the IoT.So, we approach information systems in the context of the IoT from the following perspectives: • Functional requirements induced by the IoT, starting from the features that the new systems should have; To interpret these two perspectives, we will shortly present the features of systems in the context of the IoT.Then, we will suggest the general framework of system interaction with external entities.It will be the support for the identification of functional requirements of information systems in the context of the IoT.

Features of information systems integrated with IoT
Most authors believe that we can find the applicability of the IoT in the following fields: construction, agriculture, health, electricity, transportation, and logistics (Mazhelis and Warma 2013), (Xu et al. 2014), (Houyou et al. 2012), (Vicente et al. 2015), (Havis 2014).Some examples of IoT used in information systems are: Based on the above, the authors agree that to exploit the facilities offered by the IoT, the information systems must have at least the following features: Interoperability and compatibility (Fersi 2015), (Xu et al. 2014), (Zambonelli 2016), (Ebersold and Glass 2015) Taking into account the heterogeneity of various data sources, from RFID sensors to embedded software devices, the systems have to ensure data interaction, gathering, processing and communication, so that there do not appear problems in the running of processing procedures.Moreover, system development should take into account that other objects will connect to it that have not been identified yet.It means that communication protocols and data representations schemes are needed to identify objects connected to the system and that could be used to gather, process and transmit data irrespective of their type.The systems should be able to learn specific stereotypes as to ensure using self-adaptation and autoconfiguration that they can take over dynamically the data they need, send the data required by objects with which it can connect, synchronize all interconnected components.This may be done only if we ensure the standardization of protocols and platforms to manage data.Also, it is important to have common semantics for concepts with which the IoT will operate to make possible the cooperation and communication among objects.(Fersi 2015), (Xu et al. 2014), (Zambonelli 2016), (Houyou et al. 2012).Functionality must be provided to systems, irrespective of the number of connected objects.Globally, it is stated that there will be over 50 billion devices connected to the Internet and communicating among them.Clearly, an information system will not be interacting with all these devices but it is essential to ensure its stability and functionality so that it works efficiently regardless of the number of connected objects.It ensures and provides another feature of the system, effective operation on a global scale.Reliability (Xu et al. 2014), (Ahmad 2014).The systems must work without interruptions, except the scheduled ones.The more connected devices receiving and sending data, signals, information by many network structures, the harder it is to provide this feature.All connected elements become potential sources of interruptions in the system functionality.Traditional systems work in predictable environments, with stable networks, relational data bases, planned software updates and announced well in advance.They were not developed to function under unpredictable conditions, where various devices may be connected or disconnected at different times and the network may function at its highest capacity at one time and the signal may be very weak at another time.These aspects have a critical impact on non-functional requirements of the system that should be given special attention by developers.(Fersi 2015), (Ahmad 2014), (Ruiz-Lopez et.al 2013), (Namirimu 2015), (Xiao et al. 2014) are new features for traditional systems and basic for the systems of pervasive computing.In other words, the systems must be able to identify, analyze and react to changes in work environment, namely, have the ability to add, eliminate, replace services, procedures and processing processes, so as to be able to cope with the dynamic context and reach their goals.These features place developers into critical situations as these are nonfunctional requirements changing depending on the state of interconnected objects, being transversal complex requirements.(Fersi 2015), (Popescul and Georgescu 2013), (Rudy 2015), (Leister and Schultz 2012), (Sicari et al. 2015), taking into account that many software modules interacting among them have been developed by different teams, companies, having their own methodologies and interests.It is both a security feature and trust that the system functions as expected providing required information.Also, it can filter and send data depending on interconnections among objects.

System trust
Starting from these features, we believe that attention should be focused mainly on the self-notion (Haller et al., 2008) including: self-configuration, self-healing (automatic discovery and correction of faults), self-optimization (monitoring and automated control of resources to ensure optimal functioning of the defined requirements), and self-protection.In other words, we may state that we enter in the age of system selfies that go beyond picture-making.System features must be assessed taking into account the types of connected objects to business and technical operations based on the following typology.
RFID is the initial technology of the IoT allowing automatic identification and gather of data using radio waves, tags and readers.There are three types of tags (Lee and Lee 2015) influencing communication with systems.Passive tags containing data about the tagged product or object are often used in supply, logistics, transportation and stock management operations.Active tags have been incorporated with external sensors by means of which various features of the environment may be measured, such as deposit temperature, atmospheric pressure, precipitation and humidity or the level of toxicity.Such tags are used in production processes, stocking and depositing operations, long-distance assets management.The third category is made of semi-passive tags containing microchips used to communicate data to readers.In terms of their relationship with the information system, tags can only send data to processing processes and cannot take over information from the system to activate specific actions or reconfigurations depending on the state of the system.It will be reflected in the context diagram by a single flow between the system and the RFID.2016a).Sensors communicate openly with several systems and the most important problem is to find a common language in order to take over data regardless the platform on which run the applications.Sensors, as well as RFID, send data to the system.

Sensors extend the boundaries of IT infrastructure to integrate devices, computers and machines with information
Actuators are used to activate and deactivate other devices or equipment based on information received from sensors or other systems.Consequently, we do not witness only data transmission depending on what tags and sensors identify but also the initiation of device or business operations functioning depending on the dynamics of recorded data.This is the reason why, in the context diagram, the relation with system is drawn by two flows, as to specifically emphasize the process of data communication and gather them.The actuators are one of the most complex objects having a direct impact on system functionality.Actuators together with sensors are the backbone of the IoT (Kithion 2016b).
Embedded software equipment with immediate access to sensed data and processed by the system (Mazhelis and Warma 2013).Having already incorporated the software solutions, the developers of information systems have to find the most efficient methods to ensure the compatibility and the interoperability of these equipments.Furthermore, it is important to focus on the ability to auto configure and self-adapt depending on the flows of data sent in both directions.
Recently, the objects/things have attained new features and this is the reason why they are called smart objects, including smart dust, viewed as autonomous elements able to communicate with external entities that may require information on the state of a smart object and may inform the smart object about the processes in which they are involved (Meroni 2015).These aspects also influence the system requirements.
Based on the above mentioned features and the typology of interconnected objects, we formulate the following two hypotheses of our research: Apart from these two hypotheses, there is another one closely linked with the development of systems, the hypothesis related to data management.Therefore, the cycle of data processing undergoes big changes, especially related to data collection and making them ready for the processing.The aim is to assure the information system can cope with the big volume of data and ensure processing both business, operational transaction and data analytics type.However, this is the topic of a future research that must be approached in close connection with database management systems, Big Data and Data Analytics.

General framework for the interaction of the IoT information system with external entities
In the establishment of functional requirements presented in the next section, we started from the creation of a general framework of relations of the IoT with external entities.For this purpose, we used modelling methods for a generalized context diagram shown in Figure 1.The diagram has been built based on Yourdon&DeMarco methodology.Besides the conventional symbols, to show specific features of new relations, especially of external entities with other components outside of system borders, we suggest an additional symbol (dotted line with an arrow at the end).Thus, we may easily observe the way in which the information system integrated with the IoT communicates with external entities, regardless whether these are traditional entities (departments, people, systems) or RFID, sensors, equipment belonging to a company or an environment outside it.To make the framework clearer, we used the parallel presentation of relations in the traditional system and the relations in the system integrated with the IoT.
A few explanations on external entities and relations in figure 1 For the traditional system, we decided that the category "Subunits" includes departments, production units, deposits and stores etc., namely the departments ensuring company operations.Under "Partners", we included both business partners, especially suppliers and customers, and the banks, public institutions and any other organization interacting with the company.
In what regards the IoT system, we kept those entities whose role does not change, whether because they interact in the same way with the system (Employees and the Management), or they lack the IoT, named Non-IoT.On the right side of the context diagram for information systems with IoT, we may observe connections only with the IoT entities that mainly send data and information both to the system and to entities owning the objects.These are RFIDs, sensors, actuators, software embedded machines owned by the company and partners.In this context, we may note on the two diagrams some aspects influencing the development of information system.
For the IoT environment, relations appear more often among systems with devices and objects interconnected within the company than among departments (we named them subunits), other applications and with traditional partners.
Non-IoT external entities are kept to ensure the interoperability of systems if partners or some subunits fail to integrate the IoT that grows the complexity of system development as the attention should be given to two directions, the IoT and non-IoT with data and information conversion Systems users are not only people but also equipment, sensors which almost always send data to systems and other entities.Therefore, new requirements are not collected only from users-individuals and we should identify potential types of objects that will enter in contact with the system, the incorporated technology, used language, object's owner, types of sent data etc.As most objects are not known when systems and applications are developed, it is vital that self-configuration, selfidentification and self-adaptation features be provided.
When the system is designed, the focus will be put more on the design of system interface (Oprea, Dumitriu and Mesnita 2006) and less on user interface due to minimal human intervention in the relationship with the system.Many data flows are not visible any more to human users, nor data collection or the information sent as the interaction among  Most processing operations will be initiated automatically being mainly oriented towards external and state events (Oprea, Mesnita, and Dumitriu 2005).
Processing operations begin to no longer be considered in real time, involving a lag time until the update is made, but they are dynamics with a visible immediate effect both on data and other objects.
Until now most information systems had interfaces for RFID, sensors, devices that existed in the company and only for specific conditions with those of business partners.So, most relations of systems with objects were set internally and for external relations there was an intermediary application to converse received or sent data through RFID, sensors and other devices.
Now, with the new IoT, things have changed as objects may connect among them or with people or machines with or without any internal restrictions, even automatically, without notification depending on system configuration.In this context, how the systems should react?How these should be developed so as, on the one hand, they benefit from the multitude of data needed for operations that in other conditions were difficult to collect, and, on the other hand, security risks and useless informational overload be limited?These are just a few questions that system developers should answer and then identify new requirements.
Based on these views, we may identify which components in the structure of system are affected by the integration with the IoT, establish data and information flows, method of data gathering, processing and communication by type of interconnected objects, operations and subunits that may be integrated with the IoT.This way, the existent applications may be assessed whether they may handle new flows of data and processing procedures or just need extensions or should be replaced.Finally, it should be checked if the security policy, business contracts and development strategies still meet the challenges of the IoT.

New functional requirement for information systems in IoT
As we have mentioned, the aim of our research was to identify the main functional requirements of information systems by the integration with the IoT based on literature, previous experience and the general suggested framework of information system interaction with external entities in the context of the IoT.
Depending on the area of applicability and the architecture of the IoT, there should be found a solution by means of which any interconnected object, regardless whether it is human-to-human, human-to-object, object-to-object, (Vicente et.al 2015), may be allowed to reflect in the information system the results of its interactions.To use fully the capacities of systems based on the IoT, a software infrastructure is needed supporting not only the connection of objects among them, but also providing to stakeholders and users the means to access data generated by the IoT and benefit from its advantages.
The development of new systems should be designed using a decentralized data processing strategy considering all objects connected to business operations, services and data processing, so that data sources be retained, from classical business operations to operations generated by sensors or the ones that have already been processed by smart objects (Haller et al. 2008).
To meet these needs, the systems must incorporate new requirements, the nonfunctional requirements being more researched in literature compared to the functional ones.In our research, we started from the definitions of requirements provided by Oprea, Mesnita and Dumitriu (2005).Functional requirements are operations performed by the system, namely, functions, processes and processing procedures as a response to business operations of a company.Nonfunctional requirements follow aspects related to hardware and software environment in which the system will be From the most important non-functional requirements, we list the following: In what regards functional requirements, these may be differentiated by type of company activity, adopted development strategy, degree of integration of the IoT in business operations.However, some of them are common to all companies wishing to move to new technologies and others are similar to those identified in web-based systems.Out of them, we believe the most important are: There have appeared new processing operations and those performed by traditional transaction processing systems are changing, some of them not requiring special attention as they had been implemented by moving to first systems • Coordinating triggering devices for gathering and sending data using RFID, sensors, actuators, software embedded equipment; • Filtering and aggregating data so that only really needed data will be processed; • Routing and integrating data into information systems so all activities will be efficient; • Monitoring and aggregating data to support decision-making.
For a more analytical view, table 1 presents a short list of the main requirements that should be considered in developing/adapting transactions processing systems through the IoT.The list was made using the grouping of systems around the main business functions of a company, according to (Oprea 1999), (Oprea and Mesnita 2002), (Airinei et al. 2014), (Fotache et.al. 2010): production, supply, logistics, inventory and transportation, sales and customers, human resources, accounting.For a better view, we will model the requirements with the use of case diagrams, providing examples for production that is probably mostly influenced by the IoT and supply and logistics as it reflects reversely the relation with customers and sales.As it may be noted, the most important changes in the nature of functional requirements appear in transaction recordings and in their auditing and reporting.Manual collection of primary data will be almost entirely eliminated leading to reduction of errors due to data manual recording.At first sight, the changes seem to be similar to those observed in the first forms of product automation and robotization and forms of data and money electronic transfer (EDI and EFT).However, it is more complex as now data source and their nature are different, as well as their format.
Cao and Zhu (Cao and Zhu, 2012) state most applications of the IoT are not in the area of finance, namely, business operations, quantifiable in money and affecting the assets, so three important questions appear for information systems: • How the information will be stored on the IoT hardware?• How technical information will be integrated into information from accounting? • How the applications of the chain value will be managed centrally?
The business sector must be able to collect information through the IoT, especially using tags placed on inventory objects, on tangible assets, on certificates and bonds circulating on the bank and stock market, so that any time these items move, there will be no need to collect data manually.Data transfer may be done using XBRL by allocating a unique identification number for each asset and its transactions (Cao and Zhu 2012).
In conclusion, the information system in order to cope with changes and the need for self-adaptability should be organized in modules with highly reduced interdependence.In other words, the focus will be placed on the development of systems and applications with a reduced level of coupling and the SOA (Service Oriented Architecture) (Haller et al. 2008) linked with ROA (Resource Oriented Architecture) (Dar et al. 2015) seems to be an ideal model for such a need.

Conclusions
This study presents a general framework of information system interaction with external entities in the context of the IoT in order to establish new functional requirements.To define this framework and the new requirements, we reviewed the literature, used modelling methods and our previous experience in the analysis and design of information systems.The identified aspects, the discovered requirements and the provided argument may provide support to experts developing/adapting information systems integrated with the IoT.
Most functional requirements aim to change the method of data gathering, processing and communication, recording information generated by business transactions and include data that have not been considered before by business systems as they were viewed as being the main elements of technical and engineer systems.
With the appearance of the IoT, things have seriously changed so that we will need to talk about information systems without using the term business or technical as they need to be integrated without any separation borders.The main challenge remains the collection and quantification of non-monetary data, a possible solution being to have an events based-accounting management and the integration of block chain on a large scale.Also, the teams developing systems will not be made up only of experts in business applications or engineers, but will be mixed teams as many interfaces of business applications will be interacting directly with objects, sensors, equipment for recording and sending data as it has been noted in use case diagrams in section 4.Moreover, system requirements will no longer be identified just by talking to system users as individuals who require and send information due to the fact that the notion of user has now a new meaning reflected by objects and devices connected to the world of business.
The main limitation of the study lies in the lack of a quantitative and qualitative research validating of the newly identified requirements, on the one hand, and the general framework of system interaction with external entities on the other hand.These limitations are new lines of research that have been already announced in the previous section, namely, the influence of the IoT on data processing cycle.
2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662 2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662 2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662systems based on communication standards (Mayberry 2005).The most common sensors are GPS, bar code sensors, sensors embedded in mobile devices, sensors calculating distances between two landmarks, proximity sensors, light-based and image-based sensors etc. (Che et al. 2014), ( _________________________________________________________________________________ ______________ Gabriela Mesnita (2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662 2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662 the objects allows running operations automatically, the result visible to an individual being a delivered product, the initiation of device functioning, change of an environmental condition, a notification of a specific state etc.

Figure 1 :
Figure 1: Context diagram for traditional information systems versus context diagram for information system with the IoT 2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662operating.They specify the system features, such as implementation restrictions, performance, reliance on a specific development platform, safety of exploitation etc.
2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662connected to RFID and architectures based on web-services.So, according to Chen (Chen et al. 2014), middleware in the context of the IoT should have at least the following functionalities:

Fig. 2 :
Fig. 2: Use case diagram of production system for new functional requirements

Fig. 3 :
Fig. 3: Use case diagram of supply and logistic system for new functional requirements 2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662

Table 1 : Summary of requirements to change or add new processing operations into transactions processing systems using the IoT Transaction processing systems
______________ Gabriela Mesnita (2017), Journal of Software & Systems Development, DOI: 10.5171/2017.361662