Research Papers - Dept of Information Technology
Permanent URI for this collectionhttps://rda.sliit.lk/handle/123456789/593
Browse
17 results
Search Results
Publication Open Access Annotation Based Build Process Automation for Cyber Foraging Frameworks(KDU IRC, 2016) Vekneswaran, P; Dissanayake, N. RCyber Foraging is a technique introduced to utilize the computing resources in the vicinity to improve the performance and the standby of the portable mobile devices. There have been various attempts to enable Cyber Foraging in smartphones, and they require lots of developer effort to offload the work from the applications in the mobile device, where the developers are required to do lots of code modifications or additions. We introduce an annotation based approach to automate the work offloading in a Cyber Foraging system to a greater extent, which requires minimal developer workload, through flexible technique. This can be refined in the future and be automated using machine learning algorithms, reducing developer effort furthermore.Publication Open Access Conceptual Approach Towards Stateful Computation Offloading in Resource Constraint Android Devices(KDU IRC, 2017) Vekneswaran, P; Dissanayake, N. RCyber Foraging is an approach to resolve the performance and resource limitations of small portable hand-held devices, through offloading heavy processes to nearby stationary devices called Surrogate Devices, which have more computation capabilities. The way the Cyber Foraging is mostly tackled by invoking a remote method in the Surrogate Device – which contains the application related information as a pre-requisite – at the time of local invocation, in a state-less manner. This limits the possibilities where the Cyber Foraging can be used in statefull context, which can provide maintenance of state which will help the developer to transmit state of objects used inside the offload candidate so it won’t differ from local execution and remote execution. In order to use in a stateful manner, researchers have used a virtualisation approach, which is a resource consuming approach. As an alternative, we propose a conceptual solution to transmit state from mobile platform to the surrogate platform, without having to deploy a mobile OS virtual machine into the surrogate environment. The concept will address all the drawbacks of virtualisation and provide the similar benefits at a lower resource cost in the Surrogate endPublication Open Access Towards ICT based Solution for Stuttering(2017) Withanage, K. N; Dissanayake, N. RStuttering is speech disorder that has affected a large group of people in the world population. ICT based solutions for stuttering treatments are not well known. Information about the existing ICT based solutions, their effectiveness, and the user satisfaction of the currently available solutions are not studied thoroughly. Therefore, present day researchers have fell into greater trouble in delivering the best possible solution to the masses. This paper provides the results of a cross sectional survey conducted towards identifying the differentiation of age groups, duration of existence of stuttering, use and experience of existing solutions, and the effectiveness of their performance. This paper will be an initial step towards engineering an ICT based solution to assist stuttering treatments.Publication Open Access Towards Understanding the need for a Comprehensive Design Methodology for Rich Web-based Applications(2018 FST Doctoral Conference, 2018-04-19) Dissanayake, N. RSoftware design has marked a distinctive space within the software development life cycle, since the early stages of the timeline of software engineering, bridging between requirements phase and development. In this setting, dedicated design methods such as Interaction Flow Modeling Language (IFML) have been introduced for modeling the new breed of software systems called Rich Web-based Applications (RiWAs), which deliver rich user experience via the combination of rich Graphical User Interfaces (GUIs) and a special communication model named Delta-Communication (DC). We have identified the incompleteness and high complexity of these available design methods for RiWAs and we are proposing to introduce a comprehensive design methodology, dedicated to RiWAs. However, due to many reasons – including the need for early software releases – agile software engineering methodologies like Rapid Application Development (RAD) and Scrum have become popular, which drastically cut down the design and documentation activities. They focus more on iteratively releasing working software versions, over comprehensive designs and documentation. In this environment, the necessity for a dedicated comprehensive design methodology for RiWAs can be questioned. Conducting an in-depth literature survey, we noted that the actual setting of the aforesaid environment in the context of RiWAs engineering is not much clear. Therefore, we decided to conduct a data survey to identify the contemporary state of the RiWAs engineering industry, towards understanding the need for a comprehensive design methodology for RiWAs. Rather than only examining the design practices in the industry, we also expect to find facts to verify the importance of learning design methodologies in the direction of increased realization, which can support the development activities. We plan to use an online questionnaire for gathering initial facts to gain a structured understanding of the environment, and based on the knowledge gained by it, we expect to conduct deep discussions with the domain experts to identify more in-depth aspects. Based on the facts identified through the data survey, we expect to identify the dimensions of the contribution of the design methodologies in the contemporary RiWAs engineering industry, by the means of cognitive aspects of the developers. Through the results, we expect to verify the need for a dedicated design methodology for RiWAs.Publication Embargo RiWAArch Style: An Architectural Style for Rich Web-Based Applications(Springer, Cham, 2020-11-05) Dissanayake, N. R; Dias, G. K. APush Communication is an integral requirement in modern Rich Web-based Applications, to implement the features like push notifications or real-time updates. Aspects like push-communication related concepts and their development technologies – focusing on the roots of them and the rationale behind their advancements – are not collectively discussed in any available forum. An intensive literature survey was conducted on identifying the very roots of the push-communication and its evolution towards understanding the abstract architectural formalism of the push-communication in Rich Web-based Applications, also focusing on the aforementioned aspects. We collected and documented the literature regarding the evolution of the push-communication, for archiving and also for reviewing and comparing the reasoning behind the improvements of them over time. We also tried to capture the knowledge to answer some important questions like is push-communication important and how difficult to integrate push-communication into the Rich Web-based Applications? We expect to study the artefacts identified through the survey to identify the abstract characteristics of the push-communication to realize the integration of the push-communication into the Rich Web-based Applications in the form of Delta-Communication.Publication Embargo Evolution of Push-Communication Towards the Rich Web-Based Applications(Springer, Cham, 2020-11-05) Dissanayake, N. R; Kasthurirathna, D; Jayalal, SPush Communication is an integral requirement in modern RichWebbased Applications, to implement the features like push notifications or real-time updates. Aspects like push-communication related concepts and their development technologies – focusing on the roots of them and the rationale behind their advancements – are not collectively discussed in any available forum. An intensive literature survey was conducted on identifying the very roots of the push-communication and its evolution towards understanding the abstract architectural formalism of the push-communication in Rich Web-based Applications, also focusing on the aforementioned aspects. We collected and documented the literature regarding the evolution of the push-communication, for archiving and also for reviewing and comparing the reasoning behind the improvements of them over time. We also tried to capture the knowledge to answer some important questions like is push-communication important and how difficult to integrate push-communication into the Rich Web-based Applications? We expect to study the artefacts identified through the survey to identify the abstract characteristics of the push-communication to realize the integration of the push-communication into the Rich Web-based Applications in the form of Delta-Communication.Publication Open Access Annotation based Offload Automation Approach for Cyber Foraging Frameworks(General Sir John Kotelawala Defence University, 2016) Vekneswaran, P; Dissanayake, N. RCyber Foraging is a technique introduced to utilize the computing resources in the vicinity to improve the performance and the standby of the portable mobile devices. There have been various attempts to enable Cyber Foraging in smartphones, and they require lots of developer effort to offload the work from the applications in the mobile device, where the developers are required to do lots of code modifications or additions. We introduce an annotation based approach to automate the work offloading in a Cyber Foraging system to a greater extent, which requires minimal developer workload, through flexible technique. This can be refined in the future and be automated using machine learning algorithms, reducing developer effort furthermore.Publication Embargo A CONCEPT OF BALANCED-CLIENT FOR RICH INTERNET APPLICATIONS(SAITM, Malabe, 2015-04-25) Dissanayake, N. R; Liyanage, G. U; Dias, G. K. AThe Rich Internet Applications engineering is marked as complex and difficult, since they lack of architectural formalism. If we can identify the separation of the modules clearly and generalize the architectural structure in Rich Internet Applications, it might increase the realization of the system, hence reduce the complexities and speed up the development too. We propose an architectural structure based on Model-View-Controller pattern, which describes the separation of the logic; and the distribution of the modules and related components; between the client and the server, which we expect to specify as a standard and balanced layout, we name it the “Balanced-client”, referred to the concepts of Thin-client and Thick-client. We expect to incorporate this concept to design a general architectural model for Rich Internet Applications, to provide a good realization, which can addresses the complexities in Rich Internet Applications engineering.Publication Open Access A comparison of delta-communication technologies and techniques(2017) Dissanayake, N. R; Dias, G. K. ADelta-Communication can be seen as the power of Rich Internet Applications, and there are different Techniques and Technologies available for the development of Delta-Communication, which should be selected carefully into the Rich Internet Application development. Enough discussions are not available, which compare and contrast these Delta-Communication development Techniques and Technologies towards supporting decision making of selecting them. This paper provides an overview of the contemporary Techniques and Technologies available for the Delta-Communication development, contextually compares them aligning to some selected criteria, and finally discusses some facts to be considered when selecting them for the Rich Internet Application development. A literature survey on the Delta-Communication development Technologies and Techniques was conducted, which was followed by a series of experiments towards getting the empirical evidence for the comparison. During the contextual comparison, the Simple Pull Delta-Communication was identified as the least complex technique and the Websocket was noted as the highest complex technology.Publication Open Access RIA-Bus: A conceptual technique to facilitate the AJAX-based rich Internet application development(Uva Wellassa University of Sri Lanka, 2015-01-29) Dissanayake, N. R; Dias, G. K. ARich Internet Applications (RIAs) have become quite popular in this era of Web2 (Lawton, 2008). Compared to the traditional Web Applications, RIAs are faster, responsive and they have rich Graphical User Interfaces (GUIs) (Paulson, 2005). Among plugin-based approach and script-based approach, Asynchronous Javascript And Xml (AJAX) – which is a script-based technique to develop RIAs – grabbed the demand of the engineers due to many good features of AJAX. AJAX uses stable languages HTML, CSS, JavaScript; it is free; and do not need third party plugins (Farrell & Nezlek, 2007). However the complexity of the AJAX based RIAs are considered high due to various reasons (Li & Peng, 2012) (Mesbah & Deursen, 2007). Hence, the application of Rapid Application Development (RAD) practices are not supported adequate in AJAX based RIAs engineering (Dissanayake & Dias, The Significance of Importance of an Architectural Pattern for AJAX Based Rich Internet Applications, 2014). To maintain the sustainability of both the developed RIA and the engineering project – not only in the initial development life cycle, but also in post deployment stages – it is important to identify the main cause of these complexities and address it. Methodology We conducted a literature survey to gain the background knowledge of the RIAs, AJAX, RAD, architectural patterns and the relationship between these areas. The main intention was to identify and understand the complexities and difficulties of enabling RAD in AJAX based RIA engineering. As we gain the knowledge and identify some facts related to the complexities in AJAX based RIA engineering, we conducted a cross-sectional survey to verify the facts identified in literature survey. Also understanding of the up to date nature of the AJAX based RIA development was gained by analyzing the data gathered in the cross-sectional survey. The targeted crowed was the individuals engaged in AJAX based RIA engineering; specifically in the design and development phases. Data were gathered using a structured questionnaire with closed end questions and analyzed using statistical methods. Parallel to the surveys, a series of experiments were conducted to understand and get the experience of AJAX based RIA designing and development techniques, tools, and complexities. This series of experiments was conducted as a prototype based incremental development. In each and every incremental complexities were identified, and some techniques to address the identified complexities were tested. The knowledge gained in the early iterations was applied to the later iterations. We used HTML5 and CSS3 for GUI development, JavaScript for client-side development along with jQuery library, and PHP as the server-side development language. Apache server was used to host the web application and for databases MySQL serer was used. Results and Discussion The key finding of the literature survey is, that the main reason for the complexities engaged in AJAX based RIAs engineering is, the lack of availability of architectural formalism for AJAX based RIAs engineering (Dissanayake, Dias, & Jayawardena, 2013). In the analysis of the cross-sectional survey, we derived and highlighted the following results. The understanding of the general AJAX architecture is not difficult, and there is a good usage of Computer Aided Software Engineering (CASE) tools in AJAX RIA development. However, the difficulty level of implementing AJAX features in the same page increases, with the number of AJAX features in the page (Dissanayake & Dias, 2014). One of the complexities we noted throughout the series of experiments is that the difficulties engaged in the file management of the project. Referring to the AJAX general architecture, standard practice when implementing an AJAX feature is, pointing the AJAX request to a dedicated PHP script file in the server. This dedicated script file contains the code for the logic, to provide the complete respond for the particular request. Usually these script files contain few lines of codes, needed to handle the single request. When the number of AJAX requests increases, the number of the script files also increase parallel. To provide more rich features in the application, the need for more AJAX features grows, and as more AJAX features implemented, probably the AJAX request handling script files will be piled up in the server. As the number of script files increases, the logic could be scattered and it may create a complex environment, where the management of the server-side implementation is difficult. This setting will lower the realization of the architectural structure of the system too. Furthermore – due to the aforementioned facts – in the needs of modifications of the RIA, the effort needed will be higher, and this environment may affect the sustainability of the project too. To control this situation we propose a conceptual technique, we name it as the RIA-Bus (Dissanayake & Dias, 2014). Instead of maintaining numerous small script files in the server to handle the AJAX requests, we advise to keep a single script file – what we call the RIA-Bus – which contains the code to receive all the AJAX requests; direct the processing of the request to the necessary scripts or functions; and respond back the client, with the results returned from the functions in the other script files. Figure 01 illustrates the architectural structure of the RIA-Bus. A parameter will be sent to the RIA-Bus along with the request by the AJAX engine, to indicate the type of the AJAX feature, which requests the service. Based on the type of the feature, the RIA-Bus can decide, to where the processing should be passed. RIA-Bus is responsible for reading all the data sent by the AJAX engine – using either GET or POST method – and pass the data to the function dedicated for processing the data. Figure 02 shows a sample PHP code of a RIA-Bus. The script files may contain code for all the logic of the application and organized in a way easy to manage. For an example all the user related functions may be written in one file and products related function may be written in another file. These files can be included into the RIA-Bus as needed and the functions in them can be called according to the type of the feature of the AJAX request.