/library/oar/handle/123456789/30221 Sat, 08 Nov 2025 03:58:16 GMT 2025-11-08T03:58:16Z /library/oar/handle/123456789/95686 Title: Tatja : a test automation tool for Java applets. Abstract: Although there are some very good tools to test Web Applications, such tools neglect the facility to test Java Applets. With existing technologies, Java Applets can only be tested either by using Swing/ A WT GUI Testing Tools or else by using tools that makes use of image recognition in order to capture and playback events. Such tools are not tailor made to test Java Applets and cannot be used to test Java Applets in their actual running environment, that is, in web browsers. The implemented tool allows software testers to test Java Applets in their actual running environments. The tool is platform and browser independent and does make use of any third party scripting language. Tests cases are generated directly in Java. Description: B.Sc. IT (Hons)(Melit.) Tue, 01 Jan 2008 00:00:00 GMT /library/oar/handle/123456789/95686 2008-01-01T00:00:00Z /library/oar/handle/123456789/94960 Title: Across the web : a collaborative approach to web page recommendation, classification, and automatic web directory building Abstract: Two problems that web users sometimes have whilst navigating a web containing billions of documents are "lost in hyperspace" and "cognitive overload". Bookmarks are a way of tackling "lost in hyperspace" but tools are needed to help users manage their bookmarks. Web page recommender systems tackle "cognitive overload" by presenting the user with a number of pages that are highly relevant to the user's interest. AcrossTheWeb is a collaborative-based system that provides automatic bookmark classification and web page recommendation facilities. Topic segmentation techniques are used to identify page topics. Page segments are compared with user categories having matching topics. Similar categories are recommended as potentially good destinations for the incoming bookmark. Alternatively, when no similar categories are found, a new category is created and possible category names are proposed by analysing how other users have bookmarked similar pages. Web page recommendation is also topic based. AcrossTheWeb recommends pages from other users having similar interests. Comparison between users is done at the interest level, rather than at the user level. Thus, user categories are compared and the system recommends unseen pages from categories which are similar enough. Description: B.Sc. IT (Hons)(Melit.) Tue, 01 Jan 2008 00:00:00 GMT /library/oar/handle/123456789/94960 2008-01-01T00:00:00Z /library/oar/handle/123456789/94945 Title: A P2P Personal Productivity Suite Abstract: The main goal behind this Final Year Project is to develop a Personal ¸£ÀûÔÚÏßÃâ·Ñ Management (PIM) application called P2P Productivity Suite. This will permit its users to access and modify their personal data stored in the PIM' s underlying data source from a number of diverse devices. Additionally, this system offers offline functionality. The P2P Productivity Suite will support four different modes which include Mail, Contacts, Calendar and Tasks. Whenever a peer running the P2P Productivity Suite connects to a network such as the Internet, it will discover other peers belonging to the same user with whom s/he can connect directly, thus forming a peer-to-peer architecture. All the peers connected over a P2P structure are of equal importance and therefore any one of them can initiate a synchronization session. Peers participating in a synchronization session will synchronize their underlying data source with each other. In other words, any modifications such as update, deletion or creation of a data item performed while a peer was offline will be synchronized to the other user peers as soon as the peer gets online and connects directly to other user peers that are currently online. Description: B.Sc. IT (Hons)(Melit.) Tue, 01 Jan 2008 00:00:00 GMT /library/oar/handle/123456789/94945 2008-01-01T00:00:00Z /library/oar/handle/123456789/94590 Title: Model checking user interfaces Abstract: Complex user interfaces are prone to bugs which might be difficult to find by means of testing. To ensure correctness, one would have to develop and run test cases for all possible execution paths within a system. Model checking provides a way to automatically check whether a property holds within all possible execution paths of the system. The model checking process involves modelling the system to be verified using the input language of the model checker being used, formally specifying the properties which are to be verified, then input both formalisms to the model checker. The model checker will then automatically determine whether the properties hold or not, and if not, possibly provide a counterexample to show a countertrace to the property. The problem with model checking is that the process is exponential, however this does not make it unusable. Depending on the nature of the properties we want to verify, we may abstract the system to obtain a relevantly small state space which is model checkable. In this work we look at how we can model check a number of properties which are relevant to the user interface of a system by abstracting a model of the user interface. Since user interfaces are classified as reactive systems, a temporal logic is used to describe the properties we want to verify. Temporal logic is ideal since models contain several states and it has a dynamic notion of truth, allowing a formula to be true in some states and false in others. Thus, the static notion of truth is replaced by a dynamic one, in which a formula may change its truth value as the system evolves from state to state. The aim of this project is to help the automation of model checking a system's user interface and show how a system's user interface may be model checked. The first task is to provide a means of automatically abstracting the user interface of a system. Secondly, a mechanism is to be built to translate the abstracted model into the model checker's input format. Thirdly, the properties we want to verify are to be formalized. Finally, both formalisms are used as input to the model checker. If the model checker provides a counterexample, we shall use this to obtain a visualization of the counterexample to help the system developer trace the possible bug. This project was successful at demonstrating how user interfaces may be automatically abstracted to be model checked for correctness. A case study was carried out to show how the project can be used where a number of properties were verified and a demonstration of how counterexamples are visualized is found in the report. Description: B.Sc. IT (Hons)(Melit.) Tue, 01 Jan 2008 00:00:00 GMT /library/oar/handle/123456789/94590 2008-01-01T00:00:00Z