**2. Overview: From the monolith to the clouds (Le roi s'amuse)**

Meaningful usage of computers requires certain programme backup that considers existence of data. Data is being processed according to these programmes respectively algorithms applied in the programmes. Besides programme solutions one requires appropriate communication between user and computer. Realisation of monolith application assumes that programmes and data are physically at the same place – computer, accompanied by user. Although this shape of application is considered to be a beginning of computer backup, the monolith applications are not purely historic since even today specific systems can request such a solution. Specific system has specific users so their position is bonded to special characteristics of system's functions. Legal regulations in such environment are strongly defined since those needs are monolithically connected to such relationship.

Usually, though wrongly, monolithic organisation of application is considered a historical form of organising the information systems (fig 1). Though the majority of monolithic organised systems are historically basic form, that form of organisation exists even today, if system and user are organised in that manner, out of any reason possible. Monolithic assumes coexistence of systems and users in same environment, without more significant

The Requirements for the Legal Regulation of Commercial Relations in Cloud Computing 165

Importance of data and need to manage data and to preserve them has led to double and triple-layer organisation of applicative solutions. Indirectly it led to layering a category of users, information scientists and narrower specialization of certain cadres. Specialization of cadres has at the same time meant a diversification of rights derived from obligations given to them. Final or key user of system has in this architecture been extracted, while his approach has been enabled through defined interface. Responsibility for data base has been shifted to skilled and prepared workers, usually information science experts residential to that specific business system. Legal aspects of information system in these architectures have been solved as accompanying problems at level of managerial structures of business systems. Separation of data bases into a special tier has demanded regulation of security mechanisms that necessarily included legal regulation and protection of same. Layering of systems into tiers has more

Separation of data bases into special tier put users' obligations towards data into frames of concern for accuracy and correctness while organisational and security aspects have resumed in authorisation of IT department. Necessity to manage data and to preserve them led to double-layer and triple-layer organisation of applicative solutions (fig. 3). Indirectly, layering has been made between class of users-information scientists and narrower specialisation of certain cadre. This happened regardless to saving data in a simple file or organising them as more complex form – data basis. When possibility of physical dislocation of users beyond business environment emerged, a need for relationship's organisation known as client-server organisation also emerged. As consequence a need for specialised users who will maintain dataware appeared in line with users who will concern computer networks or working stations – personal computers used by clients. Narrower specialisation of Information Scientists together with increase of consummation possibilities of system led to a need for adjusting system to final user. Graphic interface as solution to communication demands brings more possibilities to user but it imposes need for introduction of the third layer (known as middle tier) which includes logics of applicative solutions. Still, the relationship service user – Information Scientist service provider causes a legal regulation to be solved in general level, usually managerial, by leaving it to personnel outside such a relationship. If the relationships in a prior mentioned architecture of information systems are analysed from time distance, one fact is indisputable and unavoidable. That is relatively low information science education of final users. It also indirectly puts user into inferior position and leaves possibility to information scientists, usually organised in IT department of business system, a freedom that

Though only few scientists have concretely analysed that problem, the author can, upon his own experience, confirm frequent conflict between users and information scientists. Sometimes and somewhere the supremacy of information scientist has led to problems in implementation of solutions and left an impression of compulsion by users, with complexes of ignorance and inadequacy to problems. Users' response to such situation was necessary and it was expressed through need for information education and a simpler usage and managing of computer products. Simplification suited to both groups, so it has led to innovation and improvement within area of hardware and software. That trend led to multitier architecture and consequently to stronger diversification of information science cadre. (Fig. 4) Data-tier is divided into data tier and data-access-tier. Necessity of implementing the business-tier more intensively includes final user into organisation, though his inclusion

precisely articulated rights that belong to users and information science experts.

realistically shouldn't be given to them since it can be misinterpreted.

into information science tasks remains at level of consummation.

Fig. 1. Monolithic Application. Source: //rubyonrailslink.blogspot.com/2010/09/singletier-architecture.html

need to communicate with environment. Regulation of rights and obligations in monolithic systems is strictly defined by organisational rules of system to which such information system belongs.

(Batini&Scannapieca, 2006) define area where all information systems are located according to their structure and architecture (fig. 2). Area is defined by coordinates: totally, heterogeneity and distribution. Considering these three characteristics according to measurable intensity, monolithic systems are located in the centre of coordinate system. That is, they are classified as homogenous, not distributive and specialised. Authors have located P2P information systems in a diagonal spot. Systems of type peer to peer are declared as autonomous and independent from computer providers. Such systems are different than usual client-provider architecture. Usually possibilities of all networkconnected computers are being used. Scalability is the strongest characteristic of such systems. When user is logged on a network, the complete capacity of a system grows.

Fig. 2. Type of Information Systems (Batini&Scannapieco, 2006)

Fig. 1. Monolithic Application. Source: //rubyonrailslink.blogspot.com/2010/09/single-

need to communicate with environment. Regulation of rights and obligations in monolithic systems is strictly defined by organisational rules of system to which such information

(Batini&Scannapieca, 2006) define area where all information systems are located according to their structure and architecture (fig. 2). Area is defined by coordinates: totally, heterogeneity and distribution. Considering these three characteristics according to measurable intensity, monolithic systems are located in the centre of coordinate system. That is, they are classified as homogenous, not distributive and specialised. Authors have located P2P information systems in a diagonal spot. Systems of type peer to peer are declared as autonomous and independent from computer providers. Such systems are different than usual client-provider architecture. Usually possibilities of all networkconnected computers are being used. Scalability is the strongest characteristic of such systems. When user is logged on a network, the complete capacity of a system grows.

Fig. 2. Type of Information Systems (Batini&Scannapieco, 2006)

tier-architecture.html

system belongs.

Importance of data and need to manage data and to preserve them has led to double and triple-layer organisation of applicative solutions. Indirectly it led to layering a category of users, information scientists and narrower specialization of certain cadres. Specialization of cadres has at the same time meant a diversification of rights derived from obligations given to them. Final or key user of system has in this architecture been extracted, while his approach has been enabled through defined interface. Responsibility for data base has been shifted to skilled and prepared workers, usually information science experts residential to that specific business system. Legal aspects of information system in these architectures have been solved as accompanying problems at level of managerial structures of business systems. Separation of data bases into a special tier has demanded regulation of security mechanisms that necessarily included legal regulation and protection of same. Layering of systems into tiers has more precisely articulated rights that belong to users and information science experts.

Separation of data bases into special tier put users' obligations towards data into frames of concern for accuracy and correctness while organisational and security aspects have resumed in authorisation of IT department. Necessity to manage data and to preserve them led to double-layer and triple-layer organisation of applicative solutions (fig. 3). Indirectly, layering has been made between class of users-information scientists and narrower specialisation of certain cadre. This happened regardless to saving data in a simple file or organising them as more complex form – data basis. When possibility of physical dislocation of users beyond business environment emerged, a need for relationship's organisation known as client-server organisation also emerged. As consequence a need for specialised users who will maintain dataware appeared in line with users who will concern computer networks or working stations – personal computers used by clients. Narrower specialisation of Information Scientists together with increase of consummation possibilities of system led to a need for adjusting system to final user. Graphic interface as solution to communication demands brings more possibilities to user but it imposes need for introduction of the third layer (known as middle tier) which includes logics of applicative solutions. Still, the relationship service user – Information Scientist service provider causes a legal regulation to be solved in general level, usually managerial, by leaving it to personnel outside such a relationship. If the relationships in a prior mentioned architecture of information systems are analysed from time distance, one fact is indisputable and unavoidable. That is relatively low information science education of final users. It also indirectly puts user into inferior position and leaves possibility to information scientists, usually organised in IT department of business system, a freedom that realistically shouldn't be given to them since it can be misinterpreted.

Though only few scientists have concretely analysed that problem, the author can, upon his own experience, confirm frequent conflict between users and information scientists. Sometimes and somewhere the supremacy of information scientist has led to problems in implementation of solutions and left an impression of compulsion by users, with complexes of ignorance and inadequacy to problems. Users' response to such situation was necessary and it was expressed through need for information education and a simpler usage and managing of computer products. Simplification suited to both groups, so it has led to innovation and improvement within area of hardware and software. That trend led to multitier architecture and consequently to stronger diversification of information science cadre. (Fig. 4) Data-tier is divided into data tier and data-access-tier. Necessity of implementing the business-tier more intensively includes final user into organisation, though his inclusion into information science tasks remains at level of consummation.

The Requirements for the Legal Regulation of Commercial Relations in Cloud Computing 167

Fig. 4. Multi tier Architecture (Source: http://www.15seconds.com/issue/011023.htm and

Simultaneously, Information Science education of system's users has increased while his demands are becoming broader, bigger and frequenter. Technical tools are becoming more sophisticated as technological solutions. Technological solutions as product undergo

**3. Elaboration: Paradigm shift (Mixing cards with the war for middle-earth)**  Necessity for separating computer solutions into layers or multi tier organisation has resulted in more detailed diversification of activities in their development. Changes in approach and consideration of the complete issue moved barycentre from structural system towards system's architecture as a new centre of gravity. Modifications in paradigms are most obvious in the approach to projecting and programming. Object oriented software is the cause and consequence of changes that will result in emergence of opened platforms and multiply usable software. In order to satisfy increased appetites of users, a proclaimed paradigm of inheritance within object oriented approach has provided multiple uses.

However, object oriented approach has also caused a "rearrangement" of role and position of user by regulating approaches to software through mechanisms of encapsulation. That way the system's structure can be observed as a method of its construction or compliance and combination of its parts. Possibility of organising the Information System within conditions of detachment of business system refers to organisation of computer network of different possibilities and purposes. Along with significant improvement and upraise of

http://www.codeproject.com/KB/aspnet/NTierApp\_UsingLINQ.aspx)

through all rights and regulations that accompany any other market product.

Fig. 3. Two and three tier Architecture (Source: http://www.iro.umontreal.ca/ ~pift1025/bigjava/Ch27/ch27.html, http://flylib.com/books/en/2.642.1.11/1/)


Fig. 3. Two and three tier Architecture (Source: http://www.iro.umontreal.ca/ ~pift1025/bigjava/Ch27/ch27.html, http://flylib.com/books/en/2.642.1.11/1/)

Fig. 4. Multi tier Architecture (Source: http://www.15seconds.com/issue/011023.htm and http://www.codeproject.com/KB/aspnet/NTierApp\_UsingLINQ.aspx)

Simultaneously, Information Science education of system's users has increased while his demands are becoming broader, bigger and frequenter. Technical tools are becoming more sophisticated as technological solutions. Technological solutions as product undergo through all rights and regulations that accompany any other market product.
