This post will detail the basic components and architecture of the planned system. Web as a platform LeapIn.it is aimed primarily at mobile devices. A major issue with developing for mobiles is the proliferation of mobile devices – to reach 90% of active mobile users, more that 330 devices must be considered. The differences between these devices include screen-size, inputs, programming language… Read more →
The class diagram below illustrates the data structures which will be used on the client and server. These models will be made available over REST, which is discussed here. The Enhanced Entity Relationship diagram below shows the schema of the database. The tables and relationships between the tables are illustrated.
This post will illustrate two user scenarios of LeapIn.it. The first scenario illustrates how a new user can register to Leap in it! social network, customizes his/her own avatar and choosing which rooms that match his/her interest from the public room. The second scenario shows how the user is taken from the real world to… Read more →
The name of our social network is LeapIn.it. There are several motivations behind this name: It describes our social network. Our social network allows people to go to virtual rooms to discuss real life things. Using a smartphone camera, a person can scan something they’re interested and “leap in it” to interact with others about it. It’s a short and… Read more →
A context-level data flow diagram is used to identify the data flows between the system and its external entities. The data contained in our system comes from two external entities, which are the regular users and the subscribed organizations. Therefore, the system is shown as a single process (or a black box) that exchanges information from its external actors. Figure… Read more →
The following use case diagram is used to illustrate the functions that will be implemented in our social network. This diagram demonstrates who the stakeholders are and what they can do. There are two main stakeholders/actors who can use our project: The regular user who might be a regular viewer/visitor or a room administrator (the first to scan a particular… Read more →
This post gives an overview of the potential business opportunities of LeapIn.it. Five models are discussed: social capital, online advertising, sponsored rooms, check-ins and freemium. Social capital The nature of online social networks is different from other types of websites or search engines because of the social aspects that are involved. In online social networks, people might join a network… Read more →
The following slideshow shows our current mockups for the LeapIn.it mobile app. [portfolio_slideshow size=large] Editor’s note: revised mockups can be found here.
This post describes the non-functional requirements of LeapIn.it. 1. Performance Performance is the speed at which content is delivered to users, and how responsive the system is. 1.1. Processing time Interactions with the server which require processing, such as login and requesting thumbnails of images, should take less that three seconds. 1.2. Response time Over reasonably common internet connection speeds,… Read more →
The purpose of this post is to list the basic functions of the system that will be considered later in the design and implementation stage. These requirements are listed below: Req.1 The system must allow the user to scan QR codes and Barcodes. Req.2 The system must decode the scanned QR codes and Barcodes to references. Req.3 The system must… Read more →
