Les termes client Web riche ou interface riche sont utilisés pour désigner l'interface utilisateur d'une application Web qui comprend des fonctionnalités et des méthodes d'interactions similaires à celles des interfaces utilisateurs conventionnelles. Un client Web riche assure une part du traitement de l'application. Cela peut aller de la validation de saisies jusqu'à la prise en charge complète des interactions avec l'utilisateur. Il doit donc être doté d'une certaine intelligence, c'est-à-dire que du code, décrivant son comportement ainsi qu'une part de la logique d'affaire de l'application, doit pouvoir y être exécuté. L'utilisation de méthodes d'interactions avancées (comme le glisser-déplacer, la saisie semi-automatique ou l'utilisation de contrôles « widgets ») implique aussi des capacités de traitement plus poussées que pour les clients Web standards. Il existe une multitude de technologies pouvant êtres utilisées pour le développement d'un client Web riche. Le principal problème relié à cette situation est que les projets basés sur une technologie de présentation deviennent dépendants de cette dernière. Un changement de technologie implique alors la perte des investissements relatifs au développement de la partie client. Le fait d'avoir à supporter plusieurs plateformes de présentation implique aussi généralement d'avoir à maintenir plusieurs versions distinctes du client de l'application. Ces travaux couvrent les approches existantes et la conceptualisation d'une nouvelle approche permettant de définir, indépendamment d'une technologie de présentation, le volet client d'une application. Celle-ci a été expérimentée à l'intérieur de trois projets concrets présentés sous forme d'étude de cas. Une revue des plateformes d'exécution contemporaines pour les clients Web riches y est effectuée, suivi d'un état de l'art couvrant les méthodes existantes pour la définition d'interfaces utilisateur. Les travaux s'intéressant à la définition d'interfaces utilisateurs à l'aide de dialectes XML sont également couverts, de même que les architectures couramment utilisées pour la définition d'un client Web riche. Les résultats obtenus à l'intérieur des études de cas auront permis de montrer la faisabilité de l'approche ainsi que de mesurer certains avantages de celle-ci selon différents critères de qualité.

Allant des simples pages Web aux systèmes transactionnels sophistiqués, les applications Web ont beaucoup évolué et continuent de l'être. On parle même d'une nouvelle ingénierie logicielle à savoir l'ingénierie Web [pressman2005]. La mise en marché rapide et l'hétérogénéité de l'équipe de développement sont parmi les principales spécificités des applications et projets Web. Ces spécificités lancent de nouveaux défis aux modèles d'estimation actuels même pour les plus matures d'entre eux comme COCOMO II. Dans ce travail nous avons analysé la fiabilité d'un nouveau modèle d'estimation à savoir: WebMo. Ce dernier est une adaptation de la version COCOMO II avant projet au contexte du Web. L'instigateur de WebMo est Donald Reifer qui est aussi un membre très actif dans la communauté de COCOMO. Reifer a présenté son nouveau modèle comme une alternative viable à COCOMO II si on le dote en plus d'une nouvelle métrique qui tient compte des spécificités des applications Web. Dans cette étude visant l'analyse de fiabilité de WebMo, nous avons développé un outil d'estimation qui permet d'estimer et comparer les efforts de développement pour des projets Web selon les modèles COCOMO II et WebMo. En suivant un processus de sélection de projet bien défini, nous avons choisi cinq projets Web de la banque de projets ISBSG. Malgré l'immaturité du modèle WebMo et son caractère prévisionnel, les résultats générés par l'outil étaient conformes à nos attentes. En effet, WebMo fournit des estimations de l'effort plus proches de la réalité en comparaison avec son modèle de base (COCOMO II version avant projet). Ceci est dû essentiellement à la prise en compte des objets multimédias et autres objets spécifiques aux applications Web par la nouvelle métrique de Reifer à savoir: les 'Web Objects'. Un autre facteur important de succès est la calibration du modèle qui est basée uniquement sur des projets Web. Finalement, on suggère certaines recommandations telles qu'une version WebMo post-architecture pour des phases plus avancées du cycle de développement et aussi tenir compte de la diversité des langages de programmation, caractéristique typique des applications Web. Nous recommandons aussi d'alimenter la base de données du modèle avec plus de projets pour une meilleure calibration et ramener sa conception à une forme plus standard comme celle de COCOMO II. ______________________________________________________________________________ MOTS-CLÉS DE L’AUTEUR : Estimation, Projet Web, WebMo, COCOMO II, ISBSG, Ingénierie Web.

Mobile devices must deal with limited and dynamically varying resources, in particular, the network quality of service (QoS). In addition, wireless devices have other constraints such as limited memory, battery power, and physical dimensions. Applications that execute in such environments need to adapt to the dynamic operating conditions in order to preserve an acceptable level of service as close to 100% of the time as possible. Viewing and downloading digital spatial data on mobile devices has become more popular, especially with the availability of <i>location-aware</i> applications that exploit GPS (Global Positioning System) receivers integrated in many of today's mobile devices. Map client applications face many challenges in accessing data across a wireless network. Vector spatial data files tend to be large, and file sizes tend to increase unpredictably depending on the complexity of feature geometry. Due to the limited size of the mobile device display, viewing all the details of the map could cause unreasonable clutter and render the map useless. Even if it is feasible to transmit all the details from a QoS standpoint, this could pose a problem from a usability standpoint. This research effort aims to tackle the issues of QoS and usability on mobile devices through a client-proxy-server model where clients are on mobile devices. The proxy performs two functions. First, it supplies the client with vital data about the status of the system that allows the client to take adaptive decisions aimed at maintaining the QoS. Second, it performs the adaptive actions requested by the client. There are two types of adaptive actions performed by the proxy, activating and deactivating filters. When filters are activated, the amount of data transmitted from the server to the client is reduced. The client may decide to activate one or more filters either to maintain QoS or to limit clutter on the screen and enhance usability. The map client-server application and the proxy were developed in Java (tm), and a number of experiments and real-life scenarios were designed to determine the effectiveness and feasibility of the proposed adaptation model and to evaluate the performance of the proxy.

The aim of this thesis project was to migrate an existing excel-based application, used to analyze energy use and carbon dioxide emission of companies, to a web-based application. Special development questions were put around which software development process, solution stack and user interface to be used according to the company needs. The spiral lifecycle model has been chosen because it provides a clear view of the process and has the concept of early prototypes. A solution stack based on Linux, Apache, PHP and MySQL has been chosen because such approach has met the company requirements in terms of cost, security, support, and maintenance. As a result, the developed web-based system overcomes the problems normally found in excel-based applications, such as application deployment and maintenance, and provides a more usable and richer user interface.

The aim of this thesis project was to migrate an existing excel-based application, used to analyze energy use and carbon dioxide emission of companies, to a web-based application. Special development questions were put around which software development process, solution stack and user interface to be used according to the company needs. The spiral lifecycle model has been chosen because it provides a clear view of the process and has the concept of early prototypes. A solution stack based on Linux, Apache, PHP and MySQL has been chosen because such approach has met the company requirements in terms of cost, security, support, and maintenance. As a result, the developed web-based system overcomes the problems normally found in excel-based applications, such as application deployment and maintenance, and provides a more usable and richer user interface.

This research aims at analysing how the usage of Facebook differs on mobile phones and computers from the view of an end user. 10 people were consulted in semistructured interviews about their individual usage. Topics of the interviews included the amount of time they spend on Facebook on their mobile phones and how often, why they are using it on this device and when they rather use a computer. The results of the interviews indicate that people mostly use their mobile phone on their every-day journeys, esp. while they use public transport and they are bored waiting for or beeing on the means of transport. Often they just check the Newsfeed to see what their friends are doing. They mainly want to be informed about the activities of their friends, therefore, produce less content themselves on Facebook Mobile rather than on their computer. The questioned users do not have the feeling they need to log in on Facebook, instead they do it subconsciously all the time. The small screen and keypad on the mobile phone are still the main reasons why the usage of Facebook on the computer is more convenient. Nevertheless, because Facebook on the mobile phone is limited in its features it also offers a good overview. The non-available features on mobile devices are simply not missed and for this reason not even used on the Facebook computer version. However, if a function should be executed, which does not exist on the mobile phone the users are waiting until they can access a computer but possibly they forget about it by then and the importance of the accomplishment disappears.

The main aim of the thesis is to compare two web development technologies. For this purpose, a real estate application is developed using Active Server Pages (ASP.NET) with C-Sharp (C#) and Hypertext Preprocessor (PHP) as languages. The platforms used are Microsoft Visual Studio 2010 for ASP.NET and Eclipse Helios 2010 for PHP developers.  Two different servers implemented in these platforms comprising the Sql server 2008 for ASP.NET and MySQL for PHP. A real estate web application is developed with three main panels which are the user panel, advertiser panel and admin panel. The same functional requirements are used in two web technologies. When comparing two technologies, ASP. NET is found to be more efficient and reliable than PHP. During the development process it was found that, PHP is a simple scripting language in comparison to the .NET language C#. However, ASP.NET provides built in tools, function and controls which helps in faster development of code as compared to PHP.

Mobile devices must deal with limited and dynamically varying resources, in particular, the network quality of service (QoS). In addition, wireless devices have other constraints such as limited memory, battery power, and physical dimensions. Applications that execute in such environments need to adapt to the dynamic operating conditions in order to preserve an acceptable level of service as close to 100% of the time as possible. Viewing and downloading digital spatial data on mobile devices has become more popular, especially with the availability of <i>location-aware</i> applications that exploit GPS (Global Positioning System) receivers integrated in many of today's mobile devices. Map client applications face many challenges in accessing data across a wireless network. Vector spatial data files tend to be large, and file sizes tend to increase unpredictably depending on the complexity of feature geometry. Due to the limited size of the mobile device display, viewing all the details of the map could cause unreasonable clutter and render the map useless. Even if it is feasible to transmit all the details from a QoS standpoint, this could pose a problem from a usability standpoint. This research effort aims to tackle the issues of QoS and usability on mobile devices through a client-proxy-server model where clients are on mobile devices. The proxy performs two functions. First, it supplies the client with vital data about the status of the system that allows the client to take adaptive decisions aimed at maintaining the QoS. Second, it performs the adaptive actions requested by the client. There are two types of adaptive actions performed by the proxy, activating and deactivating filters. When filters are activated, the amount of data transmitted from the server to the client is reduced. The client may decide to activate one or more filters either to maintain QoS or to limit clutter on the screen and enhance usability. The map client-server application and the proxy were developed in Java (tm), and a number of experiments and real-life scenarios were designed to determine the effectiveness and feasibility of the proposed adaptation model and to evaluate the performance of the proxy.

Web servers that generate dynamic content are widely used in the development of Internet applications. With the Internet highly connected to people’s lifestyles, the service requirements of Internet applications have increased significantly. This increasing trend intensifies the need to improve server performance in dynamic content generation. In this thesis, we describe the opportunity to improve server performance by co-locating the web server and the application server on the same machine. We identify related work and discuss their respective advantages and deficiencies. We then introduce and explain our technique that passes the client socket’s file descriptor from the web server process to the application server. This allows the application server to reply to the client directly, reducing the amount of data copied and improving server performance. Experiments were designed to evaluate the performance of this technique and provide a detailed analysis of processor time and data copying during response delivery. A performance comparison against alternative approaches has been performed. We analyze the results to understand factors in data copying efficiency and determine that cache misses are an important factor in server performance. There are four major contributions in this thesis. First, we show that in multiprocessor environments, co-locating web servers and application servers can take advantage of faster communication. Second, we introduce a new technique that reduces the amount of data copied by two-thirds. This technique requires no modifications to the application server code (other existing techniques do), and it is also applicable in a variety of systems, allowing easy adoption in production environments. Third, we provide a performance comparison against other approaches and raise questions regarding data copying efficiency. Our technique attains an average peak throughput of 1.27 times the FastCGI with Unix domain sockets in both uniprocessor and multiprocessor environments. Finally, our analysis on the effect of cache misses on server performance provides valuable insights into why these benefits are obtained.

The rise of mobile phones as the number one leading personal communication device make mobile phones very attractive for marketers, as they are always on, always with the consumer and always connected. Smartphones has the ability to update their location (thus the location of the consumer) by themselves. Through this an automatic location-dependent advertisement, triggered by the location of the mobile device, may be sent to any customer in a predetermined area. However, a current problem is how to not misuse this opportunity. For example, even though a consumer is in the nearby area of a store it does not mean that they are interested in receiving an offer. Consumers are also very keen on feeling in control of the access to their personal information. The purpose of this bachelor thesis is thus to investigate what attributes a location-based application may have to increase customer usage by enhancing, facilitating and developing the customers shopping behaviour. Theories used as a basis for investigation are marketing strategy, marketing innovation, direct marketing, mobile marketing (location-based marketing and permission-based marketing), consumer behaviour (customer value, attitudes and monetary- and non-monetary promotion). A deductive, qualitative research approach was chosen, semi-structured interviews and focus groups were conducted among students at the Linnaeus University in Växjö. The interviews regarded application attributes; the results obtained were used as a base for the focus group studies. In the analysis, the findings from the focus groups linked with theory outlined the attributes and how such an application should be designed. The most important categories are customisation and value, followed in descending order by functional, external, registration and privacy. Also concluded is how the customers shopping experience may be enhanced, facilitated and developed on the basis of these attributes. In the conclusion similarities and differences between the two focus groups were discussed and theoretical and managerial implications were outlined.