This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.
This should be an approximately one page summary of the whole project from start to finish, typically including a statement of the problem to be solved, how the problem was addressed, how the project was evaluated and what conclusions could be drawn from the work. The abstract should be left to last because it is a summary of what you actually did.
Construct and build an interactive language learning aid and supplement and gaming application that can be used by both children and adults.
Table of Contents
Project Specification 2
Table of Contents 3
Should include a brief introduction to the project, a clear definition of the problem to be addressed, and guide to rest of the report.
In this brief introduction, I will explore building an Android application and using it to learn a new language.
The main problem in this project is to design and build an application that can help a user to start learning a language. I've explored a lot of the language learning applications on Google Play and they usually employ fairly similar methods of learning a new language such as flashcards and audio of native French speakers. Some of the more high quality applications have other, better ways of helping an unmotivated user to learn French.
For example; some offer vocabulary words with images, pronunciation and sentence examples, speech recognition for pronunciation exercises, offline mode, a vocabulary trainer for beginners, vibrant background themes, extra courses and extra features on the developer website.
Of course, my application will not need an internet connection. There are superfluous features that I cannot offer such as storing frequently used phrases in a favourite folder or optimisation for tablets. Also, I don't want to build an application that lets a user learn a language the wrong way and mangle the language (the French are notorious for their dedication to their language), leading him or her to embarrass themselves in front of other people.
Background and literature review.
This should describe the context of the project and should attempt to establish the state of the art in the project area. This should show evidence of scholarly activity in demonstrating the ability to research, collate and integrate information into a coherent document that uses referencing and quotations correctly such that an intelligent computer literate person should be able to quickly understand the background to the project.
The Android platform is the result of an open source enterprise led by Google under Open Handset Alliance's umbrella. The main purpose of the Android platform was to provide an open source operating system to improve the overall experience of mobile users.
Android is currently the first totally open-source and free operating system for mobile phones.
All-inclusive: The Android platform is a secure, comprehensively frame-worked and well-defined interfaced mobile platform that is very easy to upgrade. Application developers can build and integrate their applications completely into the platform. Android also comes with compatibility and certification programs, so device manufacturers can design devices that are extremely compliant.
Open-source: Every element of the Android platform has been built and provided under the open-source Apache licensing terms. There is no distinction between preloaded applications and third-party applications on the Android platform. Android application builders have complete control over device features and services while they are creating applications.
Free of cost: A developer does not have to pay any licensing, royalty, membership or certification fees to develop applications on the Android platform. All Android platform source codes and software development kits are free to use by application builders. If however, an application developer wants to upload their finished application to the Android marketplace, they must pay a one-time developer fee of twenty five dollars.
Android is one of the most important platforms for mobile phone applications development nowadays. Recent market analysis reveals that approximately several hundred thousand Android devices are being activated daily, and more than two hundred million devices already use the Android platform. Android forty eight percent of the mobile phone market share is quickly growing.
Android version recap
The first beta version for the Android platform was released in November 5, 2007. There have been a number of updates and bug fixes since then. Bug fixes are usually quite obvious from a developer's perspective; more updates generally means that changes and additions have to be made to the framework API. So other than the Android platform version numbers, a secondary version number which is known as the API level, is used to classify the supported framework API. From April 2009 onwards, every Android version codename has been named after desserts such as Éclair, Froyo and Gingerbread. All of this meant that yet a third versioning format had to be added to the Android platform, making things even more confusing for beginner Android application developers. In Android application development, people will often talk about their application requiring Gingerbread and above, a method requires API level 9 at least, and their phones getting the latest Android 3.1 update. Trying to figure out what version and what API level they are talking about, and what latest APIs are included in various Android platform version can become very frustrating and tiresome very fast.
Paranoid Network Security
Network security is one of the most important requirements of any mobile platform. In order to provide an extensive level of security, Android handles this requirement at the lowest possible layer as a kernel modification. Through this implementation, Android restricts access by the group of the calling process.
Applications should request the necessary permissions in advance, in order to be part of these network groups. Otherwise, the network access of these applications will be blocked within the kernel.
This should be as detailed as possible a specification of the requirements for the development of your program. In some cases the requirements may come from tutors or users outside of academia and more formal techniques for requirements elicitation may be needed. In other cases the student will define these requirements. This may include a test plan.
This is a list of required software, materials, and equipment that I'll be using:
The good thing about Java, Android and Eclipse is that this software available in both 32-bit and 64- bit versions on the three main operating systems currently in use today:
I'll be using Windows Vista in 32-bit, the 7.0 version of Java, the current Android SDK and Eclipse. The Java, Android and Eclipse software are free. I downloaded the Android SDK at http://developer.android.com/sdk/index.html. For hardware equipment, I'll be using a Toshiba Satellite Pro.
Operating System and IDE
While Android can be used on various platforms, many developers prefer to use the Eclipse IDE (integrated development environment) to build Android applications either on a Windows or Linux operating system. The Eclipse IDE is totally free and can be obtained at the www.eclipse.org website. As my operating system will be Windows Vista it will be able to run Eclipse efficiently.
The SDK tools I will download
In this section, I will demonstrate how I learnt how to set up an entire Android development environment. I'll be doing this on Windows, because this is the only operating system available to me and because many people use this operating system to develop for the Android platform, but Android applications development on Mac or Linux systems is almost the same. I will do a step-by-step demo on how I go about downloading the tools I will need, when the time comes to install and configure them I won't be unprepared to document this. Each of these development tools has more than a hundred megabytes in file size, and because my connection speed is inconsistent, this may take more than half-an-hour to download.
Analysis and Design
This chapter should document your analysis of the requirements and the design using an appropriate method. Usually this will be UML (e.g. class diagrams, sequence diagrams etc), but other methods can be used if appropriate. It should include a commentary on how design decisions are made.
Implementation and Testing
This section should give details of how your design is actually implemented and how testing has been planned and conducted. For real world applications testing can be very detailed, but in student projects it is often fairly brief. You can choose to make this a feature of the project if you wish (for example you could use the Test Driven Development methodology). Software performance could also be measured against an test plan. (e.g. acceptance testing for the given stakeholder) developed at the requirements stage.
In this chapter you have the opportunity to show off your program in action and evaluate how well it fulfils the requirements specification. The reader should be able to get a clear idea of what the program does and looks like without having to run the code. Some indication of program performance is expected her (e.g. screen shots, results, collated results or other output, analysis of performance, graphs etc as appropriate) are expected here in order to demonstrate and evaluate the work. However a detailed users guide to the software (if the work warranted it) or lengthy numeric analysis would usually appear as an appendix. The management of the project should also be discussed with reference to the Gantt chart/s produced, and variances from the proposed milestones and deliverables should be accounted for.
The project should conclude with a critical and reflective evaluation of both the process and outcomes of the work. It should detail the lessons learned, how the project would be conducted if it was started over, and what future work could be done to improve the project.
Appendices should include your references and cover some standard entries such as a guide to the materials on the submitted CD, and the log of meetings with the supervisor, but also any other materials too detailed to be included in the main text (up to a maximum of twenty pages). A guide to how to compile, configure and run the software is essential. Note than references from un-validated sources such as Wikipedia and similar sites are not acceptable.