Team Orion has now designed and implemented a prototype of Leapin.it. This post will conclude the project by describing the process we have been through, followed by the future possibilities of LeapIn.it. Overview LeapIn.it was not one of our original ideas – it formed from the development of an idea on gaming, and a focus on virtual worlds within gaming…. Read more →
LeapIn.it uses a REST endpoint for access to the database. This is a design pattern for hypermedia systems, which advocates providing individual resources (e.g., people) with unique URLs, and using those URLs to exchange structured information. HTTP requests can be made to these URLs, where HTTP methods are used to instruct what should happen with attached data, and status codes… Read more →
The code for the prototype is available to download from our GitHub repository.
Throughout implementing the prototypes, we’ve employed a number of testing methodologies to ensure that the product is of a high quality. In this post, we’ll discuss four methodologies we have used: regression testing, code modularity, code quality checking and code metric monitoring. Regression testing After each significant change was made to the code, the prototype would be compiled into an… Read more →
During our development of the LeapIn.it prototype, we have used a number of design patterns, libraries and API’s. This post will give an overview of the most crucial of these. Server The server is responsible for creating a REST interface for database access. As mentioned in our post on architecture, we have chosen to use RedBeanPHP to communicate with the… Read more →
In this post, we will design an ontology to describe LeapIn.it with the Semantic Web technology. Through building an ontology, we can provide mechanisms for other people to interrogate the dataset in meaningful ways. Additionally, annotating the data will be helpful when using SPARQL to do some queries later on. We are using the ontology editing environment, Protege 4.3. Class Hierarchy There are… Read more →
In planning how we would implement a LeapIn.it prototype, we agree that we should use similar development environments to prevent any mistakes or unforeseen incompatibilities. We agreed that we would use the following tools: Git – allows us to collaborate and manage versions of code GitHub – a website where Git repositories can be stored centrally. This ensures our code is… Read more →