Thesis (M.S.)--California State University, Chico. / Includes abstract. "Located in the Chico Digital Repository." Includes bibliographical references (p. 44-45).

Thesis (M.S. in Information Technology Management and M.S. in Computer Science)--Naval Postgraduate School, September 2002. / Thesis advisor(s): Alexander Bordetsky, Richard S. Coté. Michael P. Hadley received M.S. degrees in Information Technology Management and in Computer Science. James A. Wiest received a M.S. degree in Information Technology Management. Also available online.

Thesis (M.S.)--University of Florida, 2003. / Title from title page of source document. Includes vita. Includes bibliographical references.

Aim of this thesis is the description of the Microsoft .NET Framework, its different versions, architecture, and its assembly, used for its simplistic architecture, and ease of use with the assembly it is the ideal environment for creating modular applications. The work describes the C# programming language and its versions. It includes a description of the different stages and evolution of the web application framework ASP.NET. It includes a short description of the ADO.NET and LINQ technologies, used to access data from databases. It describes different databases, they structure and classification. At the end there is a layout for a database structure, blogging system, aim and structure of the files, the different system parts and functions.

Graphic user interface has become the mainstream of today¡¦s web-based systems. The object oriented technique and the diagrams from the Unified Modeling Language (UML) are becoming the major tools for modeling the platform independent model (PIM) of a web-based system. Once the PIM is constructed, the results can then be transformed into its platform specific model and template code based on the model driven architecture (MDA) approach. However, the detailed guideline for the transformation from PIM to the Microsoft .Net platform is lacking. Therefore, this study presents a methodology which provides guidelines for the transformation from PIM to Microsoft .Net platform for a web-based system. The research methodology is articulated using the design science research methodology. A usability evaluation with a real-world web-based system case is performed to demonstrate its applicability. The results indicated that with this proposed method, the system developer can effectively transform the PIM of a web-based system into its Microsoft .Net platform and template code.

One of the main aims of Component adaptation [Szy97] is to help application developers reuse components so that they can plug-in third party components into their application. This research concentrates on this type of adaptation but in the context of Web Services. Web Services are becoming increasingly popular. Web Services often fit the requirements of being a component, and can be reused in a very similar manner. Hence there is a requirement for adaptation of Web Services just as there is the need for adaptation of software components. There are now quite a few adaptation techniques, but few of them have identified adaptation techniques for Web Services. This approach to adaptation allows for the modification of data and behaviour of existing Web Services. The approach to adaptation uses eXtensible Stylesheet Language (XSL) transformation applied to the message passed between Web Services. These messages are commonly in XML format, hence XSL can be used to modify them. The application of the transformation is guided by a specification written in XML. The adaptation is executed by a generic runtime system that uses these specifications which are referred to as Guiding Specifications. This has been demonstrated by way of a motivating real world example implemented on the .Net platform. It is shown how an adapter can be specified using a simplistic Guiding Specification and related XSLT documents. This allows the implementation to work more efficiently than hand coding each adapter. It is the underlying generic runtime support that provides much of this benefit. Component based software engineering (CBSE) constructs applications by assembling components together, CBSE has been of great help to application developers due to the very fact that tailor made components can be purchased from third party vendors and can be plugged-in to a system to form a working application. But in practice 'as-is' reuse is very unlikely to occur, and most components need to be changed in some way to match the requirements of the application architecture and other components. The process of changing thecomponent for use in a particular application is often referred to as Component Adaptation.

Abstract not available

Publicación a texto completo no autorizada por el autor / Presenta una definición de arquitectura de referencia para soluciones empresariales móviles que sea reutilizable y que considere también una guía de decisión basada principalmente en el Framework de decisiones móviles de Gartner y otros estudios relacionados. El tipo de soluciones móviles sobre el cual se concentra la arquitectura de referencia es el de mejora de servicios al consumidor y se usará el enfoque centrado en la arquitectura del software Engineering Institute para la definición y validación de la arquitectura de referencia. También se detalla su integración con las metodologías tradicionales (dirigidas por planes) y agiles de desarrollo de software. Como resultado de esta tesina, la Arquitectura de referencia ayudara a las empresas en la definición de la arquitectura de sus soluciones móviles de una forma eficaz y eficiente. / Trabajo de suficiencia profesional

With the rapid development of wireless technologies, traditional mobile devices, such as pagers and cellular phones, have evolved from a purely communications and messaging-oriented medium to one that supports mobile data communication in general and acts as an application platform. As shown in a recent survey conducted by MDA, easy access to the present-day wireless Internet has resulted in mobile devices gaining more and more attention and popularity. The growth of and demand for mobile Web applications is expected to increase rapidly in the near future, as a range of software companies and mobile device manufacturers release increasingly accessible tools for creating mobile Web application and services. From a variety of possible development environments of this kind, the author has selected and examined two leading contenders, the J2ME and the Microsoft .NET mobile Web application development environments. This document reports the product life cycle of pilot mobile web applications, designed and implemented in each host environment in tum. A feature-by-feature investigation and comparison of the J2ME and .NET environments was carried out, covering the range of issues necessary for a complete mobile Web application development life cycle. The resulting analysis addresses features and efficiencies of the application development environment and the target deployment environment, the degree to which the resultant services are compatible on a variety of platforms, and the ease with which applications can be designed to be extensible. The thesis offers an objective evaluation of the J2ME and the .NET mobile development environments, which highlights their strengths and weaknesses, and suggests guidelines for designing, creating, and deploying high quality mobile Web applications. The research uncovers no clear winner across all categories assessed. J2ME currently favours situations in which bandwidth is limited and client side processing power is relatively sufficient, it exerts the processing power of mobile devices over distributed network environments. .NET requires a less constrained network throughput, but performs adequately on clients with more limited processing power, supports a more diverse target platform range, and offers a more efficient, in terms of development time, development environment. Both technologies are likely to receive significant user support for some time. / KMBT_363 / Adobe Acrobat 9.54 Paper Capture Plug-in

Since the early eighties researchers have been studying the use of technology that supports collaboration amongst co-workers and group members. This field of computer science became known as Computer Supported Cooperative Work (CSCW). With the advent of wireless and mobile Internet communication technologies research in the CSCW field has been focused on providing “access, anytime and anywhere”. The main contribution of this study is to introduce and analyze the technology required to support casually connected collaboration. Firstly, we define casually connected collaboration as having “access, anytime and anywhere” to collaborators and resources without having explicit control or knowledge over the environment and its technical abilities. In order to distinguish between connected, mobile, and casually connected collaboration we introduce a conceptual model of collaboration that extrapolates the term “access, anytime and anywhere”. We then aim to prove the soundness of our model by using it to classify some well known collaboration scenarios. Furthermore, by evaluating the functional and non-functional requirements for a casually connected collaboration solution, we argue that current commercial and CSCW research implementations do not sufficiently meet these demands. We then present Nomad: a Peer-to-Peer framework specifically designed to overcome the challenges encountered in casually connected collaboration. We study the technology requirements and highlight the implementation details that enabled us to successfully conform to the requirements set by casually connected collaboration. Finally, we pave the road for future work by investigating new features introduced into the Microsoft .NET Framework version 4.0, Visual Studio 2010 and language enhancements made to C# version 4.0. / Dissertation (MSc)--University of Pretoria, 2009. / Computer Science / unrestricted