Archive for February, 2015

Choosing an Idea with an Analysis matrix

After our initial meeting we decided to go away and individually research a possible idea for our group project. We wrote out 15 criteria that these would be marked against by using the assessment criteria listed in the moduleā€™s resource specification. In the next meeting we pitched each idea to the rest of the group, and discussed our thoughts and considerations on a number of topics. For instance, if there was a limitation to someoneā€™s idea we discussed a way in which it could be improved or changed to better meet our deciding criteria before deciding on a project. Once each idea had been pitched and discussed we wrote an analysis matrix, plotting each of the ideas against the criteria and one another. This allowed us to clearly identify stronger ideas based on the assessment criteria, and is shown in the table below. Taking each score into account we also held a group vote so that each memberā€™s concerns and preferences could be taken into account. The list of our 6 ideas are explained below:

 

  1. Meeting scheduler

The number of back and forth emails that have to be sent to decide on a convenient date for both people, with tools and technologies available to us, planning a meeting should be a lot easier than it is. Existing technologies like Google, Apple and Microsoft calendars havenā€™t made this easy on a large scale, however smaller versions and applications exist. Therefore I propose a single page app that that allows users manage and schedule meetings; including meeting places and times. The main Technologies is will use are HTML 5 geolocation, Email API, Google MAP and Places API, and a Calendar. Useful features may include the use of common types of meeting Templates, frequently used days, time and places, meeting with multiple people, a Mobile app version and a possible business case. It would benefit members of a business, friends, family, and institutional staff.

 

  1. StudnetLinks

Although this idea is widely known and fairly popular it still poses a problem for students. This idea addresses the limitations in the article “Can social network improve project management”, and can be tailored specifically for group coursework for university students. The key areas it addresses are students complain that “group coursework” assessment is not fair sometime, despite of distribution of marks, and international students facing social and communication problems because of originating from a different education system. The focus therefore is workgroup assignments and final projects, aiding all types of students from different backgrounds in order for them to feel like the work has been fairly distributed. The features of this are as follows:
– All modules have their own page each of which can allow students share their profiles. This is in order to help students get each other and each one knows others’ skills.

– Each student posts their skills, his/her background and area interested in.
– After students grouped up a close and secrete should be created.

– Each group page should provide area for update codes, Q&A as well as enables students to schedule tasks and alert them at the deadline for each one.

– At the end of coursework, a report on proportion of student’s contribution should be issued (AS GITHUP)

– An area for posting stuff related to the modules (AS A DISSCUTION AREA IN BLACKBOARD)

– With regard to subject of dissertation, some of projects are varied. For example, the final project would be on disabilities, so I do need writing about laws of disabilities and I don’t have any idea about. Thus, I need to contact with laws’ students to explain some critical points and where I can find that. This is just an example.

– Search for students in particular department would be easily.

 

  1. Travel Safety app

This idea is a travel safety app which alerts travellers about tourist black-spots and suggests detour routes to avoid going unsafe areas The information is contributed from the social network and other reliable media. The app may have the features as follows:
– It can suggest the most safe route, and give useful guidance/tips (ie. be careful to the pickpocket before taking the train in Paris)
– It will make use of social networks to connect travellers and its news
– Verification of taxis/ tour guides/ hotels/shops/restaurants/police office (prevent illegal operators, black taxis or being overcharged)
– Alert travel updates
– Detect user’s current GPS location and provide suitable emergency contact.
– Provide corresponding embassy details, credit card lost emergency call, insurance company details and claiming procedure

 

  1. Tool to improve existing group sites in academia

Based on the literature I have been reading it suggests that group study for university students in particular could greatly be improved by better management tools, as in most cases students prefer to use social media asĀ a lack of any other competitive options. Specifically I think it should target existing student-based sites that aim to help project management, such as Medeley, and identify how they could be improved. Often this will be something along the lines of ‘it doesnt have an option to invite others to meetings’, or ‘for a project papers that the group are reading can’t easily be stored in the same place for all to have access to’. We can then propose key changes (or a new site entirely) that improves the weak areas, I.e. a group discussion area in blackboard, paper sharing, meeting planning, and personal deadlines all in the same space.

 

  1. Online Memorials

This idea is based upon the collection and presentation of personal information after someone has died. In many cases when someone dies their social networking profiles remain, but act as a place for friends and family to visit to remember them or leave comments. However, a majority of people actually have more than one profile on social media sites, and these arenā€™t linked up. For example if you gave a family member permission to change your account if you have died, they would not have the same permission on another social networking platform, so your profile on one site may be a cut-off memorial that not everyone can access. This idea is for a tool that scrapes information from each of these platforms (once a family or friend has permission to do so) and displays it on one profile/site, thus making it easier for everyone to see.

 

  1. Charity Crowdsourcing

My suggestion for our social network was something that combines crowdfunding and charity donation sites like JustGiving. This idea is that people can have a profile, show interest in charities/causes etc, create events for fundraisers that people can join in with or do at the same time elsewhere (for example, how Macmillan coffee morning takes place in lots of different places, run by lots of different people but all on the same day) – basically a platform for allowing this.

In conclusion we have picked idea number 3, the travel safety application, as it fits both the most criteria in the matrix, and each member was happy with the idea. Further research and a gantt chart mapping out the stages of our project will follow shortly.

 

A table to show the analysis matrix conducted in selecting a project idea.

A table to show the analysis matrix conducted in selecting a project idea.

 


This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.Ā 

In addition this post represents Innovation and Creativity by identifying a project idea in a novel and well-informed manner.Ā 

This post also represents that the group has chosen appropriate criteria for the comparison of ideas that directly link to the marking criteria. The analysis matrix criteria were chosen intelligently to produce a project of professional quality, leading to a successful product.Ā 


 

Written by Briony.

, , ,

No Comments

Introduction to Our Project

Welcome to the blog of Group 4 in The Science of Online Social Networks!

As our introductory post we would like to explain how the first few weeks of the course have shaped and produced an intriguing project idea, and the future steps we plan to take to develop it further. We would also like to introduce our ā€˜company nameā€™, based on the internet culture and lecture topic of the 90 – 9 – 1 percent rule (Hargettatai and Walejko, 2008):

We are ā€˜The One Percentā€™.

The purpose of this blog is to have a professional digital narrative of our project, which includes all of the choices and decisions that we have made, and the outcomes these have produced to our idea. Consequently this is a great resource for the members of the group who can access data and information quickly and easily. It is also a great tool for understanding our project – it allows the reader to follow the process of our project at each and every stage. Not only does this include all of our research, designs and engineering development: it also shows you the aspects that rarely cross over into fortfolios. For example, the problems that we faced throughout, a sense of the group dynamic and productivity, and the human discussions that were present in meetings throughout.

Over the previous few weeks we have been brainstorming thoughts, producing innovative ideas and addressing the existing weaknesses of social networking websites and Appā€™s. These include the expectations vs reality of online privacy (Gilbert et al., 2011), a limited number of app features per project (Gavalas, 2011), and language barriers for a an increasingly global technological trend (Godwin-Jones, 2011). Our ideas covered a wide spectrum of potential projects: ranging from sites for improved group project management for university students, a site for arranging meetings using personal preferences of local areas, charity fundraising combined with crowdsourcing, to the scraping and storing ofĀ  personal data across platforms to create an ā€˜online memorialā€™ for those who have deceased.

Despite many promising propositions, we have selected our final project idea which takes the form of an app designed for safer travel. This was done by creating an analysis matrix, which compared each idea to a number of criteria, which included the marking criteria of the project and what we personally felt the idea must incorporate in order to be innovative and successful. You can find the analysis matrix here. But what use is an idea without any in depth background research?

The next week was spent researching a number of aspects regarding the app, which included:

  • Identifying a set list of features it was going to have based on a market evaluation of similar travel apps. The features we have selected, although a majority of which already exist, do not feature in one single app for easier use (Gavalas, 2011). Fully researching and designing how they may work and interact with one another is therefore extremely important for the production of an app which is original in the safety market by having multiple features.
  • Our target audience, a vital consideration for much of the design-work. Both surrounding literature and market evaluation suggests that there is not an age group most likely to travel, and so our app must be user-friendly and easy to use for a wide range of ages.Ā This represents vital market information from which we may learn a lot, and in turn tailor our own application for greater success. For example, through this we may identify a target audience for safety applications, and in response we may incorporate this audience into our own project projections.
  • Economic and social factors that require consideration, for example should we charge money for our app? This may be vital market research as knowing the economic background of the market may dictate whether the public perceives charging to feel safer as morally viable or not. This would ensure that our pricing choice coincides with the trends in the market we aim to be a part of.
  • Identifying potential datasets we could use for certain features, for example the use of governmental open data crime statistics to generate a ā€˜safestā€™ route for a traveller. This again represents vital background knowledge which will contribute to a smoother running application. In addition to this, it may further help determine the pricing of our app as open sets may keep set-up costs low, allowing us to reduce app cost should we feel this ties in with our market analysis.

This research has produced an initial framework for our app, and a themed name which is ā€˜TravelSafeā€™:

TravelSafe is a mobile application for anyone travelling anywhere in the world, whether at home or abroad. The application will consist of a safest route generator, which generates three safe routes from point to point, as well as a safety rating of areas within a given city which are both generated using open data and crime statistics. It will also provide travel information, such as bus and train times, locations and maps as well as weather information including severe weather updates and safety tips compiled from embassies, the World Health Organisation and social media and news feeds. Other functions will be the ability for the user to input information such as their travel insurance, flight details and important numbers, such as a lost credit card and incorporation of translation functionality. Finally, there will be a resource pack available to download which will provide a summary of the information and can be accessed offline to avoid roaming costs. The app features will be developed and researched later in the portfolio. You can skip to determining app feature research, expert opinions regarding features, and specific feature posts beginning with the Safest Route Generator onwards.

In the upcoming weeks we have a planned out a number of stages that will develop our project further, these take the form of:

  • Designing interface and graphics of the app
  • Demonstrating examples of code that are linked to certain features of the app
  • Examples of the datasets that will be used to produce personalised information within the app
  • Platform considerations

 


This post represents that coherent Structure and Story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.

In addition this post represents Innovation and Creativity by demonstrating ideas that are original and beyond the expected thinking for this assignment – this is clear by the niche product design that is commercially viable in its target market.

This post also represents Contextual Considerations that take the form of background research, social and economic considerations, technological considerations, and most importantly using the research learnt to shape the development and outcome of the product. Ā 

This post lays the foundations for strong design and engineering steps later on in the project.Ā 


References
Gavalas, D., & Economou, D. (2011). Development platforms for mobile applications: Status and trends. Software, IEEE, 28(1), 77-86.

Gilbert, P., Chun, B. G., Cox, L. P., & Jung, J. (2011, June). Vision: automated security validation of mobile apps at app markets. In Proceedings of the second international workshop on Mobile cloud computing and services (pp. 21-26). ACM.

Godwin-Jones, R. (2011). Emerging technologies: Mobile apps for language learning. Language Learning & Technology, 15(2), 2-11.

Hargittai, E., & Walejko, G. (2008). The participation divide: content creation and sharing in the digital age 1. Information, Community and Society, 11(2), 239-256.

, , , ,

No Comments

Meeting Summary 26/02/15

Meeting Summary 26/02/2015

During this meeting we addresses the ethical issues of the app’s pricing that were raised during the previous meeting. This meant considering whether it was morally right to charge people in order to feel safe. Each member conducted market analysis of similar applications, and came to the conclusion that a majority of app’s within the safety market do not charge, and therefore we should not either. This is an important consideration for our product, as it may determine how many users user our product over others.

Furthermore based on this market analysis the team have identified features of app’s on the market and the potential weaknesses that these have. During the meeting this was discussed in further detail, and the group came to the conclusion that our product should build upon the weaknesses of existing apps which would therefore create a niche market for our product. This has allowed the group to scope out a short-list of app features which were lacking or inconsistent in other existing app’s.

For the next meeting

The group decided that as the success criteria dictates that extensive testing will not be included in our project, we should decide the app features by acquiring expert opinions, group discussion, and literature reviews. Alongside this the group will research engineering choices in order to decide whether the app should be mobile based or web based, as choice of platform may dictate the usability of the app, the technologies involved to create it, and what different means of testing it may require in the future.

 


 

This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.


 

Minutes byĀ Briony Gray

, , , ,

No Comments

Meeting Summary 23/02/15

Summary of first meeting 23/02/15

This meeting was the first in which all members of the group had been present. As a result, much of the discussion was based around discussing some initial project ideas, reading through the marking criteria, and deliberating which group names would convey the message we wanted to put across throughout our portfolio.

Deciding on a group name

The group decided that the name should be based upon several lectures that the group had received during the course of module, thus tying the group in strongly with the themes discussed and presented which would ultimately shape the course of our project. Each member suggested several names, and a group vote was taken to ascertain which was the most appropriate. Categories which dictated the appropriateness of a group name included: whether the name was broad and general enough to cover any idea that we later chose for a product, whether the name had positive connotations, whether the name was easily memorable or not, whether the name was applicable to all members of the group, and whether the name related to the subject material from the module lectures.

Suggestions for the name included Deliberate, Spiel, Prototype, Theory of Trust and The One Percent. The group came to the conclusion that the name The One Percent fit the majority of the categories previously mentioned, and this was decided as the group name.

Deciding on a group project

In the same manner as choosing a group name, a group project idea was decided by the democratic voting of all of the group members. Each member personally researched and presented an idea to the rest of the group, with some initial background research. An analysis matrix was drawn up which pitched the ideas against the marking criteria, and a score for each idea was tallied at the end. The idea which fit the most criteria, and which all members of the group were happy with, was a travel safety app put forward by Kaley.

For the next meeting

In order to proceed with the project development each member will read around the project area and find any applicationsĀ that offer one or two similar aspects to our proposal. A post regarding similar applications on the market will be produced to illustrate common trends in the market area, and to highlight potential weaknesses that our app may seek to rectify.

Each member will also consider what aspects would contribute to making this app, for example what are the easiest types of map to read, what safety concerns people are the most worried about, what datasets can be used in the app etc. These will be vital in the shaping and success of the design and engineering of the project.

Finally each member should consider whether we think the app should generate a profit or whether it should be free (ethical issues), based on the market research we have conducted. This should fit in with the target audience and pricing range highlighted to ensure that our app will be successful.

During the next meeting

During the next meeting the group will write the 200 word abstract that summarises our project ideas and the considerations we have thought about in selecting it. This will include the background research we have collected throughout the week stated above.

 


This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.


 

Minutes byĀ Briony Gray

, , , ,

No Comments