Archive for category Design
App Feature: Safety and Reliability Rating of an Area
Posted by Po Ting Tse in Contextual Factors and Research, Design, Engineering on 25/03/2015
Introduction
Safety and reliability rating of an area will be the feature to prevent illegal operators, illegal taxis or users being overcharged. Users can verify legal operators and services from the application database, such as the nearest taxis, tour guides, hotels, shops, restaurants, police stations. This article will investigate the feature and discuss its benefits and limitations.
Related Work and limitations
Safety Rating
Global travel warnings and recommendations are publicly available online, such as foreign travel advice from the UK Government (UK Government Digital Service, 2015), and country travel advice and advisories from the government of Canada (Government of Canada, 2015). Figure 1 is the visualisation graph of dangerous destinations and safer spots, which classify destinations with 5 safety levels.
Figure 1 Visualisation graph of dangerous destinations and safer spots, which the data is provided by the government of Canada (CBC News, 2014)
In addition the information provides data in open data format, which the application may subscribe to the feed, and therefore receive updates automatically. Existing apps may provide a limited source of information and functions, like SmartTraveler (US Dept of State, 2014) which only displays US government data, and contains road traffic reporting data in York (The Regional Municipality of York, 2014).
On the other hand, crime Information in the UK is available in Open Data format and free to download from direct.gov.uk. In the Police API (Home Office, 2015) as shown in Figure 2, provides a rich data source of information, such as street-level crime, outcome data, and nearest police stations.
Figure 2 Police API Documentation, providing instant crime data and details of police stations (Home Office, 2015)
However, current apps may cover a limited amount of information. For example, in the Road Buddy app (Warman, 2013), it only provides walking route to users based on the publicly available police data.
Rating of areas
Since current travel recommendation and review websites have already provided rich travel information, it seems that there is a lack of applications for verifying legal operators, hotels, guesthouse, restaurants, etc. Among popular tourist sites, there are several restrictions on the API usage. For example, in TripAdvisor, the popular travel review website, it only allows up to “10,000 calls per-day” (TripAdvisor LLC, 2014).
The Feature Proposal
In the application, both safety and reliability ratings will be contributed by reliable open data sources and users’ ratings. For safety rating of an area, the app will rely on the open crime data sources, including UK Crime information. It will also adjust its ratings according to user inputs who will be able to rate the safety of a route (after using the route generator), and rate the reliability of other user reviews. Rating will take the format of a short question, such as ‘How safe did you feel using this suggested route? Answer out of 10’. Users’ geographic location will be tracked anonymously, in order to verify the rating.
For reliability rating, like verifying official buildings, such as police stations, embassies and hospitals, the application will preload their information to the users’ devices. For other places, like attractions and accommodation, the application will access other sites APIs like TripAdvisor for obtaining reviews and recommendations. It will also import open data like license hotels list and food business list for verifying legal operators.
Conclusion
Based on the above research, and lack of similar applications at the moment, the group believes that showing safety and reliability rating of area to users is essential for the application. In addition to this it provides some in depth context for the other features of the app which will aid their usability.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements a specific app feature has. This is based on market analysis, evaluation, and expert opinions. There is evidence that questions that the app feature has been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
This post additionally represents Engineering and Design decisions. These are based on the Contextual Factors and literature review which the group have tailored the product to incorporate. This means that the app feature has considerable research, fluent design and well planned out engineering steps. All of which are apparent in this post, and are also illustrated with media. This app feature dictates future engineering steps, illustrates how and why the product has been influenced in its design, and shows how engineering this app feature will solve problems.
References
CBC News, 2014. World travel map: dangerous destinations and safer spots. [Online]
Available at: http://www.cbc.ca/news2/interactives/travel-warnings/
[Accessed 10 March 2015].
Government of Canada, 2015. Country travel advice and advisories. [Online]
Available at: http://travel.gc.ca/travelling/advisories
[Accessed 10 March 2015].
Home Office, 2015. Police API Documentation. [Online]
Available at: http://data.police.uk/docs/
[Accessed 7 March 2015].
The Regional Municipality of York, 2014. York Travel Alert – Android Apps on Google Play. [Online]
Available at: https://play.google.com/store/apps/details?id=com.greenowl.yorkregion.android
[Accessed 10 March 2015].
TripAdvisor LLC, 2014. Request API Access – TripAdvisor Developer Portal. [Online]
Available at: https://developer-tripadvisor.com/content-api/request-api-access/
[Accessed 3 March 2015].
UK Government Digital Service, 2015. Foreign travel advice. [Online]
Available at: https://www.gov.uk/foreign-travel-advice
[Accessed 10 March 2015].
US Dept of State, 2014. SmartTraveler – Android Apps on Google Play. [Online]
Available at: https://play.google.com/store/apps/details?id=gov.state.apps.smarttraveler&hl=en
[Accessed 10 March 2015].
Warman, M., 2013. Road Buddy mobile app plots safe routes to walk home. [Online]
Available at: http://www.telegraph.co.uk/technology/news/10047029/Road-Buddy-mobile-app-plots-safe-routes-to-walk-home.html
App Feature: Download Pack for Offline Use
Posted by Emily Pearce in Contextual Factors and Research, Design, Engineering on 24/03/2015
It can be suggested that one of the key problems when people travel abroad is the huge cost of data roaming – no-one wants to come home from a holiday or months travelling to be confronted by a huge bill! Because of this, TravelSafe will provide a feature that enables the user to choose a location and download a summary pack of information, which can be accessed offline once they get to their destination.
The pack will contain:
- Map(s) of the area
- Travel information – public transport stations and times
- Key cultural customs incorporated with tips on staying safe
- Key phrases in the local language
- Helpful numbers, such as emergency services
- The user’s information such as holiday insurance, lost credit card, passport number and itinerary
To access it, a user will open the application at home or work, connected to WiFi, search or select a location and chooses what information they would like to be included in the pack. This will then be downloaded and then stored in the device storage in an application specific folder, where it can be accessed alongside previously downloaded packs. The application will be able to store packs for multiple locations, dependent on the amount of memory available on the user’s smartphone.
The other feature posts in this blog describe where each set of information will come from and how it will be used, as the purpose of this feature is to collate that information for use offline.
Written by Emily.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements a specific app feature has. This is based on market analysis, evaluation, and expert opinions. There is evidence that questions that the app feature has been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
This post additionally represents Engineering and Design decisions. These are based on the Contextual Factors and literature review which the group have tailored the product to incorporate. This means that the app feature has considerable research, fluent design and well planned out engineering steps. All of which are apparent in this post, and are also illustrated with media. This app feature dictates future engineering steps, illustrates how and why the product has been influenced in its design, and shows how engineering this app feature will solve problems.
App Feature: Travel Safety Information
Posted by Taekyun Kim in Contextual Factors and Research, Design, Engineering on 24/03/2015
Another important aspect of both travel apps and safety apps is the ability to have easy access to public transport and other information updates. The table below illustrates and explains the different services offered by existing travel apps on the market.
App Name | Explanation | Platform |
Safety Map Worldwide | Flagged by locals as a high-crime area of drugs, prostitution etc | Apple |
World Wide Safety | This programme included: health and safety programme development and implementation, safety leadership training, job-site safety inspections; regulatory compliance, emergency management, fall protection, construction safety, respiratory protection, forklift training, Hazardous Materials and Waste clean-up operations, health and safety management OSHA required training, and design and implementation of loss prevention initiatives |
Android |
Travel Safe | User make emergency calls and texts anywhere in the world | Apple Android |
iPatrol Travel Advice | Put in user’s current destination this app will warn you about nearby reported scams and pickpocket schemes. | Apple |
Safer Travel | Safety tips and potential risks for the destination as well as giving the security of emergency numbers and locations in case they were ever needed |
Apple |
Smart Traveler App | Offered by US government. travel warnings and alerts for countries around the world | Apple Android |
SafetiPin | Gps Tracking,Emergency, directions to safe locations, pins showing safe and unsafe area with score. | Apple Android |
XXX Travel guide with me(Maps.me) | Offered through different countries. Guides,warnings how to stay safe and healthy, road rules etc.. | Apple Android |
looked for the app for the world not for one countrys’ safety information and not in English. |
In light of the market research presented above, The group have decided that our app “TravelSafe” will offer combination of travel and emergency information services. These include maps that identify the safest route (please see post of Safest Route Generator), live travel updates information from locational RSS feeds for national bus and rail services, the option to add your emergency contact information, downloadable resource packs (please see Safety pack post), tips and advice for travelling based on GPS location, easily translatable maps and services (provided freely and easily by Google translate), and finally contact information for local taxi services based on GPS location.
The combination of the travel information features can be used both offline and online making it by far the most accessible and safest app in the current market based on research. The use of these services make it a social network between the user, and the companies updating information.
Written by Taekyun.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements a specific app feature has. This is based on market analysis, evaluation, and expert opinions. There is evidence that questions that the app feature has been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
This post additionally represents Engineering and Design decisions. These are based on the Contextual Factors and literature review which the group have tailored the product to incorporate. This means that the app feature has considerable research, fluent design and well planned out engineering steps. All of which are apparent in this post, and are also illustrated with media. This app feature dictates future engineering steps, illustrates how and why the product has been influenced in its design, and shows how engineering this app feature will solve problems.
App Feature: Safest Route Generator
Posted by Briony Gray in Contextual Factors and Research, Design, Engineering on 23/03/2015
During the initial designing phases for the TravelSafe app we came up with the idea of a ‘Safest Route Generator’ as a prominent feature which no other safety apps on the market offer. The idea is for a map routing algorithm to take into account other data sets, such as crime statistics of an area, before generating a suggested route path from A to B. It would then use social networking to generate it’s own data using a user’s experience to rate the routes, thus generating a ‘safety’ rating that could be incorporated into the algorithm. However, for this feature to work comprehensively there are a number of considerations to take into account which this blog post will explain and evaluate. These include a literature review to understand the mapping market in greater detail, what limitations exist for mapping algorithms and networks, existing examples of route generators, how routes may be ranked, a proposed methodology for our Safest Route Generator and finally a discussion of the network and predicted outcome of the feature based on all of the above.
1.0 Map Routing Algorithms
During the ‘Information Age’ the functionality of mapping Applications (apps) has increased dramatically (Pascalau, 2011). The range of uses that computing is applicable to is largely responsible for this, which extends to logistics planning, traffic simulations and shortest-path queries (Pascalau, 2011). Route generators were originally based on adapted simplified algorithms, such as Dijkstra’s algorithm in 1956, which finds the shortest path between two nodes in a graph (Jasika et al., 2012). As technology evolved along with our understanding of the more complex aspects that may shape a route, such as traffic or vehicle type, so did the algorithms used to calculate them (Jasika et al., 2012).
Modern algorithms take into account huge volumes of data and metadata (Sander and Schultes, 2007). Unlike Dijkstra’s basic algorithm they aren’t looking simply for the shortest route anymore – they’re looking for the best route available (Sanders and Schultes, 2007). This allows for companies and individuals to tailor their mapping software and route generators to a specific use or cause by placing a higher priority on the influencing aspects that they consider essential to their own project (Quercia et al., 2014). As mapping is a vast industry there is a multitude of factors that may potentially be considered for any one project, these include:
- Length of route
- Geographical features
- Understanding what the target audience needs from the map
- Ease of use from the platform
- Type and quality of supporting datasets
- Form and complexity of route instructions
- Type of vehicle/on foot options and impacts
- Off-limits or privately owned land taken into consideration
In addition to routing, networks play a key role in the generation of map routes in mapping apps (Bishop et al., 1998). Networks are the connections of nodes and links that form graphs, and similarly they have developed over-time to incorporate the evolution of algorithms, consumer need and technology (Bishop et al., 1998). Nodes specify which links connect to them and vice versa, which then creates a graph to traverse (Bishop et al., 1998). Particularly in the mapping industry, geographic Face Routing is commonly used, shown in figure 1 below.
Figure 1.
In this example, a message is routed along the interior of the faces of the graph, with face changes at the edges crossing the S-D line (shortest distance). The final path is shown in blue, illustrating how the network deciphers the shortest route based on that particular network (Finn, 1987).
2.0 Problems and Limitations
Despite a number of general and more specific routing methods currently employed in the mapping market, it is important to note that the dominating players, such Tomtom, do not publish the intricacies of their software or methodologies (reference). As such a majority of companies who wish to produce a similar product or app are forced into three main categories: They can either buy the research and information from an existing company or product, invest large amounts of money and man-power into researching and building a network for themselves (which holds no guarantee of being better than the existing ones), or utilise free open data and open access software such as OpenStreetMap (reference). In addition to this problems also arise from the inconsistencies of geographical data that are being used (Kray et al., 2003). This may due to a number of issues, such as:
- Maps are very complex, diverse and sometimes full of geometrical inconsistencies.
- It is difficult to define what a “relevant manoeuvre” is. Some users might want to hear a “Go straight” instruction at each crossing, whereas other would not.
- Lack of consistent network data
- Lack of interoperable networks between countries
- Lack of off-road networks which makes some transport methods difficult to create
Despite a number of these problems being applicable to a large number of mapping applications, there are projects that are continuously working to solve these limitations (Kray et al., 2003).
3.0 Existing Examples on the Market
There is a plethora of existing apps and sites that create, use and demonstrate route generation in a mapping software. They do this through varying methodologies, datasets, networks and algorithms, which all aim to tailor their own service for a specific task (Kray et al., 2003). In order to understand how the TravelSafe app can compete in this market, three contrasting products or services have been chosen to evaluate with regards to the previous literature review. These are, TeleAtlas (TomTom), HappyPaths (Yahoo) and OpenStreetMap (Google).
3.1 TeleAtlas (TomTom)
TeleAtlas is a patented software that was bought by TomTom, the satellite navigation company, in 2008. They have released a diagram illustrating the process of data collection from multiple sources that is shown below in figure 2 (www.tomtom.com/en_gb/licensing/).
Figure 2
As shown above the company generated the data for TeleAtlas themselves using significant investment and man-hours in a diverse range of methods. This generated the basis for a wide selection of maps and services that the company offers on their site, of which a majority are pay-for-access only. TomTom specialise in simplifying travel for vehicles, which ranges from everyday use for the public to larger cliental who use the software and technology for shipping goods. This model works well for TomTom, as they rely on selling technology, such as SatNav’s, with their software pre-installed on devices. In contrast, TravelSafe is not intended to be installed on devices before they are to be bought, rendering this business model insufficient for our needs.
3.2 HappyPaths (Yahoo)
Yahoo’s new project, HappyPaths, is designed to build on the development of shortest route maps, as they believe routes with the option of highly extensive tailoring will be the future of the mapping market (Quercia et al., 2014). The goal of HappyPaths is to automatically suggest routes that are not only short but also emotionally pleasant. To achieve this they have used data from a crowd-sourced platform that shows street scenes in London (as the example city). A user then votes on which route looks more visually appealing, turning these votes into quantitative measures of locations in the network. The locations are then arranged on a graph which highlights the most visually pleasing routes.
Although this methodology places highest priority on route aesthetics rather than the shortest distance, Yahoo found that the recommended routes are only marginally longer than the shortest ones on average. This corresponds to similar study by Duckham and Kulik (2003), who discovered that placing the highest importance on path simplicity rather than shortest route produced routes that were on average only 10-16% longer than the shortest route available. This would be a valuable and applicable methodology for the Safest Route Generator for the TravelSafe app, and would allow for the aspect of Safety Rating to be the prioritised influencing factor in the route generations.
3.3 OpenStreetMap (Google)
Arguably Google are the dominant player when it comes to mapping in the modern age. Unlike a majority of the mapping market, Google’s OpenStreetMap is a collaborative project to create free editable maps in order to combat the dominance of closed, licenced or patented data and data processing (Haklay and Webber, 2008). It does not seek a profit, but does not however offer a tailored service for a specific target audience. Rather than the map itself, the data generated by the OpenStreetMap project is considered its primary output. This data is then available for use in both traditional applications, such as Craiglist, OsmAnd, Geocaching, MapQuest, Open JMP, and in uncommon uses such as to replace Google Maps, and to replace default data included with GPS receivers. For software in order to generate the Safest Route Maps, OpenStreetMap is the most viable solution to the problem of funding.
If the project were to use one of the two other options for mapping (either buying the research and information from an existing company or product, or investing large amounts of money and man-power into researching and building a network for oneself) we would severely impair the reach and commercialisation of app. By utilising open data and software the app would be virtually cost-free, and in a market where the majority of mapping apps are free this would be an extremely important aspect to the target audience.
4.0 Our Feature Proposal
Taking into account the literature and existing examples in the market, the TravelSafe Safest Route Generator is not only a plausible idea, but represents a transition from shortest-route mapping to the innovative trend of tailored routes and networked data. In order to keep the app free it will utilise OpenStreetMap software from Google, which will then be tailored using methods employed by Yahoo’s HappyPaths. The tailored routes will take into consideration safety rating as the highest priority, which will initially be generated from existing open data such as Direct.Gov.UK’s locational crime statistics. At the end of a route, a user will be prompted to answer the question ‘How safe did you feel while travelling along this route?’ answerable by a score out of 10. This data can then be anonymously collected, generating more accurate networks for the route generator to incorporate.
The Safest Route Generator will take into consideration ethical aspects regarding the use of the app, as it is possible that an individual may use the app to pinpoint locations where travellers are being directed, making it easier to commit a crime. Consequently, the generator will produce three possible routes for the user to take, making safety tips and warnings clear, such as ‘Do not always select the shortest route of the three calculated routes’. Further ethical aspects have been considered regarding the cost of the app, which will be free for use. Not only does this fit in with a majority of the mapping market, but also promotes good company and individual ethics which does not charge and individual for wanting to feel safe.
It is important to bear in mind that the platform specifications, clarifications of external data sets, and how user-generated data sets will update in real time are to be discussed in future posts, after further research.
5.0 The Networked Aspect
By encouraging a user to input data regarding the safety of a route, TravelSafe is incorporating a social networking solution to the problem of static and basic route generation in apps – this is something which no other mapping app on the market offers. Furthermore, the database generated by user input will form an intricate socially influenced network, allowing for a more complex and tailored route generation system that takes into consideration specific user needs. This will improve the nature of social network infrastructures in both travel and mapping apps in an innovative way, and encourage the shaping of technology by social need.
The generation of user input will develop aspects of trust associated with social media and human/computer networking, which is becoming an increasingly prominent feature of apps and websites (Gligor and Wing, 2011). The formation of user trust (also emotional trust, and similarities to yhprum’s law covered in the lecture materials) in knowledge transfer within the network of the app will cultivate a strong image of reliability, which studies argue is a necessity for the creation of viable and reliable knowledge, and the transfer of this (Levin and Cross, 2004).
In keeping with the findings of Duckham and Kulik (2003), user interaction will be in the simplest format thus warranting a larger number of participants. Once the generated data set regarding safety ratings has reached a reasonable size, the app may potentially offer a more in depth review process in a similar format to TripAdvisor in future developments. We anticipate the more in depth review process to be an aspect offered between 9 and 18 months after the launch of the app, as Kray (2003) suggests this is the optimal time for mobile-based apps to generate enough usability and social networking connections.
Written by Briony.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements a specific app feature has. This is based on market analysis, evaluation, and expert opinions. There is evidence that questions that the app feature has been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
This post additionally represents Engineering and Design decisions. These are based on the Contextual Factors and literature review which the group have tailored the product to incorporate. This means that the app feature has considerable research, fluent design and well planned out engineering steps. All of which are apparent in this post, and are also illustrated with media. This app feature dictates future engineering steps, illustrates how and why the product has been influenced in its design, and shows how engineering this app feature will solve problems.
References
Bishop, C. M., Svensén, M., & Williams, C. K. (1998). GTM: The generative topographic mapping. Neural computation, 10(1), 215-234.
Duckham, M., & Kulik, L. (2003). “Simplest” Paths: Automated Route Selection for Navigation. In Spatial information theory. Foundations of geographic information science (pp. 169-185). Springer Berlin Heidelberg.
Finn, G. (1987). Routing and Addressing Problems in Large Metropolitan-Scale Internetworks. University of Southern California, ISI/RR-87-180.
Gilgor, V., Wing, J., (2011) Towards a Theory of Trust in Networks of Humans and Computers. 19th International Workshop on Security Protocols, Cambridge, UK
Haklay, M., & Weber, P. (2008). Openstreetmap: User-generated street maps.Pervasive Computing, IEEE, 7(4), 12-18.
HappyPaths (2014) [online] available at http://arxiv.org/abs/1407.1031
Jasika, N., Alispahic, N., Elma, A., Ilvana, K., Elma, L., & Nosovic, N. (2012, May). Dijkstra’s shortest path algorithm serial and parallel execution performance analysis. In MIPRO, 2012 Proceedings of the 35th International Convention (pp. 1811-1815). IEEE.
Kray, C., Elting, C., Laakso, K., & Coors, V. (2003, January). Presenting route instructions on mobile devices. In Proceedings of the 8th international conference on Intelligent user interfaces (pp. 117-124). ACM.
Levin, D. Z., & Cross, R. (2004). The strength of weak ties you can trust: The mediating role of trust in effective knowledge transfer. Management science,50(11), 1477-1490.
Pascalau, E. (2011). Towards TomTom like systems for the web: a novel architecture for browser-based mashups. In Proceedings of the 2nd International Workshop on Business intelligencE and the WEB (pp. 44-47). ACM.
Quercia, D., Schifanella, R., Aiello, L. (2014) Social and Information Networks (cs.SI). Computers and Society (cs.CY); Physics and Society
Sanders, P., Schultes. (2007) Engineering Fast Route Planning Algorithms. Universitat Karlsruhe, Germany.
TomTom satellite navigation company website (2014) [online] available at http://www.tomtom.com/en_gb/licensing/
Determining the TravelSafe App Features
Posted by Briony Gray in Contextual Factors and Research, Design, Engineering on 18/03/2015
Based upon the literature review, expert opinions and advice, and group consensus we have made a shortlist of the features the App will have. The list below represents the features that are deemed to be the most important and useful for a travel safety app:
- Safest route generator (with an option for an individual to rate the route)
- A safety rating of the area (used to calculate the safest route)
- Travel information updates from other services (e.g. bus timetables)
- Safety tips for travelling based on location (e.g. taking into account cultural differences)
- A downloadable travel pack for offline use
- Web and Mobile based application
Consequently, each member of the group has selected a feature that they are interested in, or have knowledge about, and will write a literature outlining the current market of the App, its functionality, and how it will be utilised to best effect in the TravelSafe App. It is important to bear in mind that each of us have deadlines for other modules during this period, and so posts to the blog may be staggered.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements the product will have in terms of useful app features. These are based on market analysis, evaluation of existing app features, and identification of useful app features. These have been presented to experts to ensure further guidance and feedback for contextual factors. There is evidence that questions and the short-list of app features have been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
Based on the Contextual Factors and Expert Opinions the group have tailored the product to incorporate app features which have been identified as being useful, innovative and original. This dictates future engineering steps, and illustrates how and why the product has been influenced in its design.
Written by Briony
Scope of the App
Posted by Taekyun Kim in Contextual Factors and Research, Design, Structure and Story on 17/03/2015
Introduction
An important consideration for the TravelSafe app is the scope of the intended area for its use. Although we fully intend for the app to be used on a global scale, this is not possible for a small group project with limited time. Therefore, we have decided to use the UK as a case study in which to test the app before its launch for use world wide.
Why the UK?
We have selected the UK primarily because all of the group work and live here, which makes tailoring the app and planning its stages easier for us. Also, we know the area very well, which will mean that app can be planned out very well. Along the same lines Miluzzo et al., (2008) reccommend that for apps which need testing in a smaller situation before expanding, a familiar area for the designers should be used which may then be scaled up.
Kangas and Kinnunen (2005) go on to further explain that user testing for an app should be tested in a single cultural and language zone first. Bigger areas should then be used so that easily identification of social, cultural and language barrier issues can be more easily identified and tackled (Kangas and Kinnunen, 2005). Therefore, this advice makes the UK the perfect area to demonstrate the usability of the TravelSafe app, as the area is small and the app can be adjusted before further use.
Limitations
By using the UK as a case study there will be limitations. One limitation is that in the UK there may be different demographics who may use the app, for example maybe more English people will use it when travelling to a different city rather than a different country. This should be fully considered in the qualitative testing in the future. Another limitation is that because of the previously mentioned one, the app may not be fully tested in different countries, therefore it may be difficult to know whether it works correctly. This will be addressed when the app is tested on a bigger scale. We suggest that future testing should begin in the UK, then expand to some other selected countries for example in Europe, and then if this works well, it should be scaled up once again. Finally this will be on a global scale.
Conclusions
The TravelSafe app should use a small area for extensive testing to make sure that any social issues can be addressed on a wider scale (Kangas and Kinnunen, 2005). The UK is the perfect starting point for the testing app as it is small, and the designers/engineers are english-speakers (Miluzzo et al., 2008). The aim of the project is to develop an idea that is at the stage of being able to be tested commercially and extensively, therefore the TravelSafe app at the end of this project will list future testing and technological considerations which may discuss how the app may be release on a global scale.
References
Kangas, E., & Kinnunen, T. (2005). Applying user-centered design to mobile application development. Communications of the ACM, 48(7), 55-59.
Miluzzo, E., Lane, N. D., Fodor, K., Peterson, R., Lu, H., Musolesi, M., … & Campbell, A. T. (2008, November). Sensing meets mobile social networks: the design, implementation and evaluation of the cenceme application. InProceedings of the 6th ACM conference on Embedded network sensor systems(pp. 337-350). ACM.
Determning a Project Methodology
Posted by Po Ting Tse in Contextual Factors and Research, Design, Structure and Story on 13/03/2015
Introduction
The group are currently using Scrum (Schwaber,1997) for the software development process. This post is going to explain the group’s choice among existing methodologies, the advantages, and the possible issues the group may have with this approach. Determining a methodology that a group should follow is a vital part of producing a project that will fulfill the success criteria. This is due to the project requiring many steps and many contributions from different members. This means that in order for this to occur to a high standard the group must all follow the same method, understand that method, and be able to work as a group to achieve the same goals. Therefore choosing a methodology that suits both the group, the project, and the success criteria is important.
Traditional waterfall model
Traditionally Software Development Life Cycle, or commonly known as the waterfall model, has been adopted in software development. It is well known of its cascading development stages, in which the stages are be followed in sequential order, as shown in Figure 1 below. These include feasibility study, systems investigation, analysis, design, development, implementation, and maintenance ( E. Avison & Fitzgerald, 2003).
Figure 1 The waterfall lifecycle for software development (Vidgen, 2002).
Before starting the next phase previous phases have to be completed (hence the term waterfall), and each phase has a set of defined outputs or deliverables to be produced before it could be deemed complete ( E. Avison & Fitzgerald, 2003). As the world became fast-paced and technological requirements changed frequently, people soon discovered the weaknesses of this approach and start to embrace the agile methodology.
Weaknesses of the Waterfall model
Firstly, the waterfall model fails to meet the real needs of the business world (Avison & Fitzgerald, 2003) as the technological efficiency improvements are at the operational level, detracting from the business needs. Consequently the project sponsors also focus on the project investment, as well as the return and benefits through the system.
Secondly, over conservative systems design is an apparent limitation ( E. Avison & Fitzgerald, 2003). Since the model emphasises the existing system as a basis of the new system, there is limited creativity for developers to implement the new one. Thirdly, instability is apparent as the modeling of processes could be unstable due to changing businesses and markets. Subsequently it is difficult to develop a suitable and stable model. It becomes a burden for developer to implement the program as the modeling is varied.
In addition, inflexibility of the model, the inability to change requirements, leads to further limitation (Vidgen, 2002). The methodology makes a number of simplifying yet invalid assumptions (such as a stable environment, a well-documented business strategy, users knowledgeable about their own requirements, or that a consensus of requirements can be achieved). However, such conditions rarely exist in practice.
Next, user dissatisfaction ( E. Avison & Fitzgerald, 2003). According to problems with computer-oriented documentation, users are not allowed to browse the prototype of the system before it is completed. The user involvement is limited and they may feel uncertain since nothing could be seen when the system is incomplete. In addition to this the problems with documentation produce further limitations ( E. Avison & Fitzgerald, 2003) since the document is full of information, developers have to assume they understand what they need, instead of referring users’ needs.
Finally, application backlog is a tangible limitation ( E. Avison & Fitzgerald, 2003) as the maintenance workload can be large. As a result attempts are made to change the system in order to reflect the change of user needs. The above weaknesses raise the urge of methodology evolution. In order to fit in the fast paced environment, the group decides to adopt the agile methodology. The next paragraph will explain why the group choose agile for software development.
Agile’s advantages and limitation (Cohen, et al., 2003)
Unlike traditional waterfall model, agile software development is known as its rapid and iterative approach (Highsmith & Cockburn, 2002). It highlights the most important parts, which the crucial parts will be accomplished first. This can gain confidence to the team, and project sponsor will be easily satisfied with the project in the early stage.
A strength of agile is embracing change and continuous development. As customers are the essential part in the team, they can come up with their ideas and thoughts immediately to the team. There is no communication lag between developers and customers. Time is saved and a prompt responded development can be performed. Next, agile software development enables the team to work effectively as a cohesive unit, which can improve productivity by several times. Team work is highlighted as cooperation enables greater productivity. Team members show their various expertise, understanding of the schedules and work cohesively, so the burden or difficulties can be solved together quickly..
Agile software development is a simple, elegant and correct solution found by true domain expertise and experience. Under this aspect, software can be maintained efficiently,as everything is simple and intuitive. The new comer can easily come up with ideas of the development, which we think is better for maintenance than the waterfall model.
Why the group will use Scrum for the project
Among popular agile approaches, the group decided to use Scrum due to its substantial benefits in comparison to other methodologies. Scrum is an incremental, time-based development (Rising & Janoff, 2002) with frequent meetings (i.e. Sprint). It embraces requirement changes, and is suitable for small team that working individually. This methodology works the best for the group as group members prefer to discuss and contribute ideas and research, rather than one person focusing on a large part. The group will have one to two meetings each week. In each week, the group will decide the next parts and corresponding job division, similar to the basic questions required in every Scrum meeting. The group meetings will last between 30 and 45 minutes each, one of which the mentor will join the group.
Conclusion
After a comparison of different methodologies the group has adopted the Scrum methodology because of its advantages. Since the application is user-oriented, user involvement in the whole development process is crucial. The group hope the project can achieve success with Scrum.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding how best the group works towards a joint goal. These are based on a literature review which explains why the outcome was chosen and how the group will implement it. There is evidence that the methodology has been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
It is also evident that based upon the Contextual Considerations, literature review and analysis that appropriate Design steps for the product have been chosen intelligently. This is shown by the conclusion of picking a suitable methodology for the group and explaining its choice and how it will shape product development. This choice further represents the Structure and Story of the portfolio by dictating the methodology used.
References
Avison, D. & Fitzgerald, G., 2003. Information systems development: methodologies, techniques and tools. 3rd ed. s.l.:McGraw Hill.
Cohen, D., Lindvall, M. & Costa, P., 2003. Agile software development. DACS SOAR Report, Issue 11.
E. Avison, D. & Fitzgerald, G., 2003. Where now for development methodologies?. Communications of the ACM, 46(1), pp. 78-82.
Highsmith, J. & Cockburn, A., 2002. Agile Software Development:The Business of Innovation. Computer, 34(9), pp. 120-127.
Rising, L. & Janoff, N. S., 2002. The Scrum software development process for small teams. IEEE software, Volume 17, pp. 26-32.
Schwaber, Ken. “Scrum development process.” Business Object Design and Implementation. Springer London, 1997. 117-134.
Vidgen, R., 2002. Developing Web Information Systems: From Strategy to Implementation. s.l.:Butterworth-Heinemann.
By Po Ting Tse
Shortlist for App Features
Posted by Briony Gray in Design, Engineering, Structure and Story on 07/03/2015
The group is now in position where a wide range of background research has been conducted. This takes the form of Similar Applications, Market Research and Literature reviews for specific features. Consequently, determining a short-list of features which the TravelSafe app will utilise is the next design and engineering step of the project. As the project has the final objective of producing a fully researched and designed idea which is then ready to be subjected to qualitative and quantitative testing (which will require more funding and time than a group project is able to), we have enlisted the help of individuals who are considered experts in their field. In order to objectively evaluate the short-list of app features we have used purposive sampling to select a number of experts from ranging backgrounds. These include Engineering, Web Applications and Solutions, Web Master, and Senior Technical Advisor. This is a guidance solution regarding how we should structure and decide on the features of the TravelSafe app without breaching extensive qualitative and quantitative testing.
The experts were identified as being useful or relevant to our project interests, and then were contacted via email. This provided an easy medium for conversation without being formal. Initial contact with the expert explained our project scenario and requested that, if they were willing, should read the short-list of TravelSafe feature apps and answer 4 short questions regarding these. In addition we strongly encouraged any other thoughts or guidance throughout. Each expert gave permission to use their name, job title, expertise and answers in our portfolio. The feedback received can be found in the Expert Opinions post.
The short-list which the experts were presented can be found below:
1. Safest Route Generator – This generates three safest routes from point to point in real-time
2. Area Information Safety Rating – This is used for areas using open data crime statistics and social media
3. Local Travel Information Updates – This provides local bus and train times, locations of these, and weather information Weather updates.
4. Safety Information – This is generated from locational based RSS feeds from embassies, social media and news feeds.
5. Emergency Contact Information – This is done through user input which an individual stores travel information such as flight numbers, travel insurance, credit card numbers, and emergency contact details.
6. Downloadable Resource Pack – This allows the user to choose a location and download above features (such as travel information or safety information) which can be accessed while offline. This combats roaming charges while travelling.
7. Blogging Features – e.g. photo and video with GPS location – Links to social media e.g. photo and video
post uploads, blog posts.
8. Family Alerts – This features a danger button to send location to designated contacts, and/or emergency services or the police.
9. Flight Information – This provides information from airport/airlines with notifications for specified Pack offline.
This post also represents that the group has chosen appropriate design and engineering choices that directly link to the marking criteria, which are vital to understanding which features that the product will have. These are based on Contextual Factors such as market analysis, evaluation of existing products, and identification of app features. There is evidence that the design and engineering steps (app features) have been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
In addition there is evidence of Structure and Story, as the post explains why these were chosen, how they were chosen, and that these will shape the development of the project.
Written by Briony.
Project Requirements
Posted by Emily Pearce in Contextual Factors and Research, Design, Structure and Story on 04/03/2015
Requirements Gathering
As the group has undertaken the research and design aspects of this project first, with the aim of completing market research and expert opinions before implementation, requirements gathering was undertaken in group meetings by developing ideas about the potential users of our application and the functionality that would be included in the TravelSafe application. Due to the way that this project has been undertaken, these requirements are to provide an idea of the functionality and limitations of our application and may change during the market research stages. This has been influenced by background research that includes the evaluation of Similar Applications. This lead the group to conclude the most important functional and non-functional requirements for the project, which are stated below.
Functional Requirements
The system shall be able to:
- allow a user to search and select a location based on GPS data
- allow a user to select a location from a list of saved locations
- For each location, it must be able to:
- generate three point to point safe routes using area safety ratings
- provide a safety rating of a user’s surrounding area based on publicly available crime data
- provide travel information from publicly available times and map
- provide safety tips using open data from Government and police service
- provide an updated news feed from RSS feeds of news source
- download a pack of the above data that can be accessed and used offline from on-device storage
- allow users to access and search through a list of Frequently Asked Questions (FAQs)
- provide translation functionality through use of Google Translate API
- have a section dedicated to user-input information as free text
Non-Functional Requirements
The system should:
- be a web-based application
- provide a comprehensive list of help and instructions for use
- use a consistent style, layout and colour scheme throughout the application
- take all reasonable steps to improve accessibility
- be intuitive for use
- be compatible with Internet Explorer, Google Chrome, Mozilla Firefox and Apple Safari to ensure compatibility with mobile browsers
Constraints
The application will be limited by/not be able to:
- the accuracy of the GPS hardware within a mobile device
- provide external backup of data
This set of finalised criteria were chosen from the extensive discussion of the merits and drawbacks of the potential features, combined with the research into similar applications as well as project constraints such as the time available and the skillsets of the developers within the group. The group feels that the finalised requirement are representative of the type of application that is being suggested, with the quantity of features providing the unique selling point to allow the group to target a niche in the market identified during research utilising both development and time management skills of the group as a whole.
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.
This post also represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements the product will have. There is evidence that these have been chosen intelligently (by reference to literature and analysis) to produce a specification of professional quality, leading to a successful product.
In addition design considerations for the project have been addressed in this post. This is evident through the layout of steps that the project should include, how these have been decided, and how this will be implemented to solve a problem.
Written by Emily.
Project Planning
Posted by Ayoub Elgassier in Design, Media Use, Structure and Story on 03/03/2015
Project management tools are vital for a successful project (Bakouros, Dr. Yannis, 2000). Likelihood of proportion of occurrence of mistakes would be reduced by implementation of these tools (Bakouros, Dr. Yannis, 2000). The project environment has a high chance that unexpected conditions might occur. For example, unpredictable results might be found. These might be a reason for failing the project, or it might reduce the quality of the project. Therefore, utilizing the techniques and tools of project management could be a key to overcoming these issues. Advantageously, the former offers a project team the chance to identify uncontrollable tasks as well as controllable ones (Bakouros, Dr. Yannis, 2000). Consequently, The One Percent team decided to choose a Gantt Chart as a suitable project management tool, as it provides features (discussed later) in addition to ease of usability.
The Gantt chart is a “project planning tool” offering chance of tracking tasks and activities of the project(Durfee, 2008). The reason behind chosen this tool is the simplicity of construct the tasks and tracking tasks and sub-tasks (Durfee, 2008). Gantt chart can be used to order and schedule tasks and activities of a project, each of which is pictured in horizontal bar over time (Durfee, 2008). each task takes a place in a row where Date takes a place in a column (Durfee, 2008). Start date as well as end date are recorded in order to compare whether goal is achieved or in a risk. To implement Gantt Chart, the online Smartsheet application is used. This smartsheet offers features as follows:
- Simplicity of use in terms of tackling icons, drop and drag, and also import and expert features. In addition, it can be incorporated with google sheet.
- It allows you to have a cooperation with other participants. It provides, for example, alert feature which it can send over an email to them for reminding.
- Completion feature, which is calculate the proportion of accomplishments out of 100 and also number of days that have been spent, is useful.
- It can be also set a rule in order to specify each member’s tasks with using a certain color.
There are three main phases in TravelSafe project plan, each of has sub tasks assigned to a team member. The phases are:
- Planning phase consists of six task each of which has sub-tasks.
- Design phase consists of six task as well.
- The final phase is future works which are survey, focus group and testing the application.
The following pictures illustrate a part of planning stage of our project using Gantt chart. To read full plan online visit the following link: (Full project plan) and to download PDF version click on Full Project Plan PDF.
In conclusion, this blog aims to show the importance of project management tools to improve project time management. Therefore, this project lists the Smart sheet named Gantt chart which is being used in The One Percent project.
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 Media Use by incorporating a gantt chart as a method for time and resource management.
This post also represents that the group has chosen appropriate project steps that directly link to the marking criteria. The project steps were chosen intelligently to produce a project of professional quality, leading to a successful product.
References
Bakouros, Dr. Yannis, D. V. K. (2000). Project Management, 0–32.
W. Durfee, Oct 2008, Project Planning and Gantt Chart