I would take this opportunity to thank my research supervisor, family and friends for their support and guidance without which this research would not have been possible.
DECLARATION
I, [type your full first names and surname here], declare that the contents of this dissertation/thesis represent my own unaided work, and that the dissertation/thesis has not previously been submitted for academic examination towards any qualification. Furthermore, it represents my own opinions and not necessarily those of the University.
Signed __________________ Date _________________
CHAPTER 1: INTRODUCTION
Background of the Study
The software industry is currently experiencing a paradigm shift towards web-based software. Applications that used to be written for specific computer architectures, CPUs, operating systems and devices are now increasingly written for the Web, to be executed inside a web browser or a compatible web runtime environment. In the future, the majority of end user software, including applications for both personal and business use, will be web-based. For the average computer user, the web browser will be the primary software environment for most purposes, effectively displacing conventional operating systems from the central role that they used to have in the past.
We believe that the transition towards web-based end user software will have a significant impact not only on desktop computing but on mobile devices as well. Although as of this writing there is considerable momentum behind native, web-connected mobile “apps” that have been written for specific devices or operating systems, it is clear that web-based software will play a critical role also in the mobile device space. In fact, we anticipate a major “battle of the decade” between native apps and pure HTML5 Open Web applications [1]. In this paper we provide an overview of Cloudberry - a novel HTML5-based “cloud phone” software platform developed at Nokia Research Center. One of the most central benefits of a cloud phone is that nearly any customer-facing application or feature in such a device can be changed from the server side, possibly to millions of devices all over the world almost instantly.
This will shorten application and service deployment and update lifecycles, and make it easier to customize devices to different users and purposes. Another key benefit is multiple device ownership, i.e., the ability to access the same applications and data to be accessed effortlessly from different devices. RBAC has its roots in the enterprise, where each individual has a well-defined function (or role), which, in turn, defines the resources the individual is author-ized to access. As reports, NIST first began studying access control in both commercial and government organizations in 1992 and concluded that access control needs had not been met by the products on the market. They specifically found that there was no implementation support for subject-based security policies and access based on the concept of least privilege.
There were other limitations as well. At the time, access control to resources (files and input/output devices) was maintained through eponymous access control lists (ACLs) associated with the respective resources. With that, a list of authorized users was ...