Essay: Kids World Play Fun Learn – application evaluation

1. INTRODUCTION
1.1 PROJECT SUMMARY
“Kids World – Play Fun Learn”, this application is like a game which consist of various interesting tasks to perform by kids. It includes graphics and sound effects that are attractive enough to keep children playing.
While they are playing, they are learning things unknowingly like mathematics, alphabets, it includes word puzzle and many things which can help children to improve their skills.
This application includes different scenario and each option consists of various levels. All the different levels contain different tasks. When the solution is given by kids it is checked whether the answer is wrong or right at each level.
The main modules included in this application are like Math, Words, Alphabet and Drawing.
1.2 PURPOSE
‘ Purpose:
This application entitles “Kids World – Play Learn Fun’, now a day’s children are getting spoiled by mobile phones in their early childhood so, we are making something innovative that helps kids to improve their basic knowledge skills and develop their concentration and memory skills.
‘ Objectives:
‘ Provides easy user interface.
‘ Provide basic knowledge to kids.
‘ Provide attractive graphical view.
‘ Provide functions like switching application music ONOFF.
‘ Provide select player option for user.
‘ Provide individual player score card.
‘ Provide images to fill it with different colors.
1.3 SCOPE
This application uses a very simple GUI that can be easily interacted by the kids without getting any help by adults.
We already mentioned that it improves basic knowledge skills, which includes:
Mathematics – Addition, subtraction, multiplication, etc.
Alphabets ‘ To learn alphabets and its use.
Words – To understand how the English alphabets are arranged & recognition of English words.
Drawing ‘ To get in touch with art.
1.4 TECHNOLOGY AND LITERATURE REVIEW
It is found that in this type application the UI is used at very complicated level. When small kids do try to use this application they are not able to do on their own they need guidance by elder to open it and let them explain the use of application function.
To overcome this mentioned problem, we are developing a new android application ‘Kids World – Play Fun Learn’, which provides easy and understandable user interaction method that kids can understand and operate this application on their own.
The outcome of this application is a very simple to understand and operate able application that kids can easily use.
2. System Requirement Study
2.1 User Characteristics
‘ User :
User can create their own individual user profile up to 9 different users. Each different user can give their name as input for their profile. Each profile contains a different icon for their profile. This application provides services for the user like:
‘ User profile creation as player
‘ Player icon selection from given options
‘ Player icon with their name as input for different user
‘ Player score card for selected user
‘ Change player at any time
‘ Player profile contains level and score information for individual Task.
2.2 Hardware and Software Requirement
The details below shows the minimum requirement that must be is required to run this application:
‘ Hardware Requirements :
Processor : 800MHz
RAM : 256Mb
Screen Size : 240 X 120 dpi
Device : Android base device
‘ Software Requirements :
Operating System : Android 2.3.1(API 9)
‘ Supported Device :
This application developed by us supports all types of Android platform devices like Mobiles, Tablets, etc. which meets the minimum hardware and software requirements.
NOTE: The given requirements of system are minimum. So to run this application on any device this is minimum required to execute application efficiently.
2.3 Constraints
2.3.1 Hardware Limitation
It must be required minimum 256Mb Ram and processor with 800MHz and Android 2.3.1(API 9).This application will requires at least 10 to 20 Mb of phone storage or SD card.
2.3.2 Interface to other Applications
This application does not integrate with any other different application. It is a small application that stands and operate individually it does not depends or a component of any other larger application. Also it is not a replacement for any other application.
2.3.3 Parallel Operations
This application is parallel processing so, application is parallel to update player information for each level with its score. E.g. if user creates a player and reach to next level it stores level information and score for completed level.
2.3.4 Higher Order Language Requirement
In development it uses JAVA as higher order language. JAVA is a concurrent, class-based, object oriented programming language.
2.3.5 Assumptions
‘ The Android device that is used is meeting minimum requirement in terms of hardware and software.
‘ The database is correct and up-to-date every time.
2.3.6 Dependencies
The entire application task and processes are depended on end-users operations. They should possess basic knowledge to work with the application. The application is easy to interact but always depended on the input given by the user.
2.3.7 Criticality of the Application
When the available RAM goes it may possible this application may crash or in the case of low processor availability.
2.3.8 Safety Security Consideration
This application provides basic security like when only the player complete its level then only they are authorized to go to next level. Also completed level cannot be deleted by any other player.
2.4 Timeline Chart And Process Model
‘ Process model
Here, we have decided to take ‘WATERFALL MODEL’ as our process model for developing the application. Because we find it more suitable for our application development.
The waterfall model is often called as ‘Linear-sequential model’ or ‘classic life cycle’. It is oldest software paradigm. This model suggests a systematic, sequential approach to software development.
The development process starts with requirement analysis, system design, implementation, testing, deployment, maintenance.
‘ Framework Type:
In our Application we use Linear Framework because of
a. Project under control
b. Milestones are known and tracked
c. Resource requirements are know
d. Work distribution
e. Work well with inexperienced developers
This model is mainly divided into six phases as mentioned below:
1. Requirement analysis
2. System design
3. Implementation
4. Testing
5. Deployment
6. Maintenance
Fig. 2.2 Waterfall process model
The sequential phases in model are:
‘ Requirements specification:
The first step of waterfall model is analysis of requirements in the beginning and to check whether the project is actually feasible with the technologies available in present or not. Requirements are gathered, analyzed and then proper documentation is prepared which is useful further in the development process of the project. Here all the requirements of the application ‘Kid’s World ‘ Play Learn Fun’ are gathered from the user. Gathered requirements are clear and will be used by the other software phases.
‘ Design:
The requirements collected in the above phase are analyzed and a proper implementation strategy is created according to the software developing environment. The design phase is sub categorized into two sections, i.e. system design and component design. The system design contains details and specifications of the whole system and explains how each component of the system will interact with others. The component design contains specifications as to how each component will work separately and how results from one component will travel to another. Coders are individually assigned to develop each component. So, on the base of the client’s requirements collected by us will be used by the next phase to implement the functionality of the application.
‘ Implementation:
Now is the time to actually start making the components. The information gathered in the first two phases is applied in this step to create the real working components of the system. The design generated in the above phase is converted into machine language that the computers can actually understand and process.
‘ Testing:
The testing phase is a very important phase. In this phase the software is checked for any errors or compatibility or other issues. When the implementation phase is in its ending stage and codes are prepared that’s where testing phase starts. In order to make sure that the system is error free various tools, software and strategies are used for testing the solution. The individual program unit or programs are integrated and tested as a complete system to finalize that the software requirements have been met. After testing, the software system is ready to be delivered to the customer. Implemented coding of ‘Kid’s World ‘ Play Fun Learn’ is now tested against user’s requirements so that it is delivered to the intended user.
‘ Deployment:
The deployment phase go smoothly if all the above phases are completed carefully. Once software is tested it needs to be assembled as a whole system and installed on the computer or required device.
‘ Maintenance:
As the time passes requirement of users will change so modifications or upgrade is required for the system. Here where the maintenance phase comes in the picture. Maintenance is an upcoming process after deployment it may last for weeks months or years. No matter how carefully the software is made there is always possibility of occurrence of bugs in the tested software.
‘ Advantages of Waterfall Iterative Model
1) Waterfall model is simple to implement and also the amount of resources required for it are minimal.
2) In this model, output is generated after each stage (as seen before), therefore it has high visibility. The client and project manager gets a feel that there is considerable progress. Here it is important to note that in any project psychological factors also play an important role.
3) Project management, both at internal level and client’s level, is easy again because of visible outputs after each phase. Deadlines can be set for the completion of each phase and evaluation can be done from time to time, to check if project is going as per milestones.
4) This methodology is significantly better than the haphazard approach to develop software. It provides a template into which methods of analysis, design, coding, testing and maintenance can be placed.
5) This methodology is preferred in projects where quality is more important as compared to schedule or cost.
‘ Limitations of the waterfall model
1) The model implies that you should attempt to complete a give stage before moving on to the next stage
‘ Does not account for the fact that requirements constantly change.
‘ It also means that customers cannot use anything until the entire system is complete.
2) The model makes no allowances for prototyping.
3) It implies that you can get the requirements right by simple writing them down and reviewing them.
4) The model implies that once the product is finished, everything else is maintenance.
‘ Why we use waterfall model’? Situations where waterfall model is appropriate:
Clear, Fixed and Well documented requirements.
Stable product definition.
Understandable technology and not dynamic.
Unambiguous requirements.
3. SYSTEM ANALYSIS
3.1 STUDY OF CURRENT SYSTEM
Now a days, Mobile working on android based operating system are used by the number of user. On those phone there are many applications are being developed for different purposes of use. In those different types of applications for small children are also covered as well.
Currently there many application that share the purpose of growing children mind power abilities that make children active and intelligent at their knowledge level.
Some examples can be taken as Kids Slide Puzzle, Kids Connects animals, maze for kids. This applications uses functionality currently like sliding puzzles solutions for an image, connecting dots and making animals figure, some low level solution mazes that can be solve by kids.
3.2 PROBLEM AND WEEKNESS OF CURRENT SYSTEM
‘ Problems faced in current system:
‘ UI is hard to handle by the kids.
‘ Scores are stored in total only.
‘ Required space for installation is higher sometimes.
‘ Sometimes application purchase costs are higher.
‘ Sometimes the instruction specified are so complicated that the kids face difficulty to move the game ahead.
3.3 REQUIREMENT OF NEW SYSTEM
After studying the current system that are available in the market we can see there are many problems should be found.
The new application is required to enhance the features to overcome those problems. It is properly taken care the current system problem and tried to overcome it as much as possible.
It is required to build an app that is available in the market at very low cost. Application should work in stable conditions and User interface must be easy to intractable.
‘ User requirements:
User requirements not include many things because the most user uses this game is small children. The only thing we have to take care is that it can be used by children very easily.
‘ Should have easy user interface.
‘ Simple GUI support.
‘ Scorecards in detail.
‘ Easy to operate.
‘ System Requirements:
The application required space for installation should be smaller in size. Easily available to user and installed very easily. Should have functionality like background music and sound effects to attract the user and keep them to stay playing without getting bored.
3.4 FEASIBILITY STUDY
The feasibility study is an evaluation and detailed analysis of the proposed project that we are building which is based on extensive investigation and research to support the process of decision making processes that comes in the project.
‘ Economic feasibility:
The Proposed system is economically feasible, because this application have benefits like:
‘ It save money, because it can be available at low cost.
‘ It requires internet but in less usage.
‘ Relatively low cost and less internet usage make it affordable in low budget.
‘ No special designers needed because GUI is used simple.
‘ Technical Feasibility :
Here “Kid’s World- Play Learn Fun” application it needs less storage, stability, simple GUI support, less hardware requirements to give an user friendly application output.
To achieve this goal and to design this application we need following hardware and software:
‘ Hardware tools :
‘ Processor : Pentium Dual core, 1.5GHz
‘ RAM : 512 MB RAM
‘ Hard Disk : 40 GB HDD
‘ Mouse : Optical or compatible pointing device
‘ Keyboard : Any keyboard
‘ Monitor : Any display monitor with 1024*768 Resolution
‘ Software tools :
‘ Operating System : Microsoft Windows 7
‘ IDE : Eclipse
‘ Plugins : ADT (Android development kit) Plugin
‘ Database tools :
‘ SQLite (SQL Database Engine) is the database used to store the data of the system.
‘ Android tools :
‘ Operating System : Android 2.3.1
‘ Processor : 800MHz
‘ RAM : 256 Mb RAM
‘ Storage Space : < 20 Mb The proposed system is technically feasible, because: ' The platform we used in our system is easily available in the market. ' All the tools we needed for development are already available in the market at very low cost. ' The system does not need any new resources. ' Behavioral Feasibility : In this application, easy interaction, navigation, attractive look and music are provided so it makes the application user friendly. Also because of user friendly application it can be used by the user that does not have technical programming awareness. 3.5 REQUIREMENTS VALIDATIONS a. Player must select an icon for profile. b. Player must input user name in profile. c. Player name should have maximum 10 characters. 3.6 FUNCTIONS OF NEW SYSTEM 3.6.1 Use Case Model In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be human or external system. There is basically one actor of my application: 1. User/Player 3.7 DATA MODELING 3.7.1 E-R Diagram 3.7.2 Class Diagram 3.7.3 Activity Diagram 3.7.3.1 Player creation 3.7.3.2 Player selection 3.7.3.3 Task interaction 3.7.3.4 Problem solution 3.7.3.5 Settings 3.7.1 Data Dictionary 1. Table name: CharactersTable Primary Key: id Field Name Data Type Constraints id Integer Primary key Character Text Not null Name Text Not null MathsScore Numeric Not null WordScore Numeric Not null MathsLevel Numeric Not null WordsLevel Numeric Not null Table 3.1 Characterstable 2. Table Name: WordsTable Primary Key: id Field Name Data Type Constraints id Integer Primary key Word Text Not null Options Text Not null Score Numeric Not null Level Numeric Not null Table 3.2 Wordstable 3. Table Name: MathsTable Primary Key: id Field Name Data Type Constraints id Integer Primary key Operator Text Not null FirstValue Numeric Not null SecondValue Numeric Not null Answer Numeric Not null Options Text Not null Score Numeric Not null level Numeric Not null Table 3.3 MathsTable 4. Table Name: android_metadata Field Name Data Type Constraints Locale Text en_US Table 3.4 android_metadata 3.8 Control Flow Diagram 3.9 MAIN MODULE OF NEW SYSTEM ' Detailed scorecard ' Profile management ' Tasks ' Settings 4. SYSTEM DESIGN 4.1 DATABASE RELATIONSHIP 4.1.1 Relationship of Database Tables Figure 4.1 Database tables relationship 4.2 INPUT/OUTPUT AND INTERFACE DESIGN 4.2.1 State Diagram Figure 4.2 Kid's World state diagram Figure 4.3 Player creation state diagram Figure 4.4 Scorecard state diagram Figure 4.5 Settings state diagram Figure 4.6 Tasks state diagram 4.2.2 Sequence Diagram Figure 4.7 Player creation and details sequence diagram Figure 4.8 Problem solution sequence diagram Figure 4.9 Update level sequence diagram Figure 4.10 Application Sequence diagram 5. IMPLEMENTATION PLANNING AND DETAILS 5.1 IMPLEMENTATION ENVIRONMENT ' Operating System : Windows 7 ' Version : Ultimate ' OS Manufacturer : Microsoft Corporation ' System Name : TRANSFORMERZ-PC ' System Type : 64-bit operating system ' BIOS Version : 02.09 ' Processor : AMD Phenom(tm) II X4 970 Processor (4 CPUs), ~3.5GHz ' Windows Directory : c :Windows ' System Directory : c :WindowsSystem32 ' BOOT Device : DeviceHard diskDisk1Volume1 ' HDD : 4192 GB ' Language : English (Regional Setting: English) ' User Name : TRANSFORMERZ ' Time Zone : (GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi ' Memory(RAM) : 8.00 GB ' Graphics Card : NVIDIA GeForce GTX 550 Ti ' Memory(Graphics) : 4.00 GB ' Sound Device : Realtek High Definition Audio 5.2 MODULE SPECIFICATION Following Modules are included in Application: ' Player profile ' Alphabets ' Drawing ' Maths ' Words ' Scorecard PLAYER PROFILE: ' Each player can create its own profile. ' Profile is created with icon and name. ' Maximum 9 profiles can be created. ALPHABETS: ' Each alphabets are given with example. ' While clicked it is highlighted. ' Audio is played of given alphabet and example. ' After audio is played highlight is removed. DRAWING: ' Fill colors on canvas. ' Canvas can be blank image or blank space. ' Change brush style. ' Change color of brush. ' Change size of brush. ' Erase filled color. ' Save on SD card. ' See saved images. MATHS: ' Have 10 levels. ' After completion of first level next level is unlocked. ' Answer is checked correct or not. ' Score and level are updated as answers given. WORDS: ' Have 10 levels. ' After completion of first level next level is unlocked. ' Answer is checked correct or not. ' Score and level are updated as answers given. SCORECARD: ' Each player profile have an individual scorecard. ' Score card maintain individual score and level of word and maths. ' While clicked on profile icon or name scorecard is displayed. 5.3 SECURITY FEATURES This Application 'Kid's World ' Play Fun Learn' is specially made for small kids of age 3 to 12. So not authentication security is included but user profiles are provided instead. To make different profile for different user. And all details are stored separately for users. 5.4 CODING STANDARDS 6. TESTING Testing ' Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design, and code generation. ' It tests the software for quality, result and accuracy. There are many strategies that can be used to test software. ' The testing strategy that is chosen by our software team falls in between the individual program units, moving to tests designed to facilitate the integration of the units and culminating(ending) with test that exercise the constructed system. Testing Objectives: ' Testing is a process of executing a program with the intent of finding an error. ' A good test case is one that has a high probability of finding undiscovered error. ' A successful test is one that uncovers yet undiscovered error. 6.1 Type of testing: There are two types of testing :- 1. Structural testing 2. Functional testing 6.1.1 Structural testing:- Structural tests verify the structure of the software itself and require complete access to the source code. This is known as 'White-Box' or transparent testing because you see into the internal workings of the code. Structural testing phase make sure that the software structure itself contributes to proper and efficient program execution. Complicated loop structures, common data areas, 100,000 lines of complex code and nests of ifs are evil. Well-designed control structures, sub-routines and reusable modular programs are good. Large software systems have the execution path as defined by the program calls, their input and output and the structure of common files that is important. This gets into a hybrid kind of testing that is often employed in intermediate or integration stages of testing. Structural testing's strength is also its weakness. The code needs to be examined by highly skilled technicians. That means that tools and skills are highly specialized to the particular language and environment. Also, large or distributed system execution goes beyond one program, so a correct procedure might call another program that provides bad data. 6.1.2 Functional testing:- Functional tests examine the behavior of software as evidenced by its outputs without reference to internal functions. Hence it is also called 'Black-Box' testing. If the program consistently provides the desired features with acceptable performance, then specific source code features are irrelevant. It's a pragmatic and down-to-earth assessment of software. Black box tests have a basis in the scientific method. Like the process of science, Black box tests must have a hypothesis (specifications), a defined method or procedure (test plan), reproducible components (test data), and a standard notation to record the results. One can re-run black box tests after a change to make sure the change only produced intended results with no inadvertent effects. The Third method is called as 'Grey-Box' Testing as it is the combination of Black-Box and White-Box Testing. But hereby we use the Functional Testing on our Application. InputOutput 6.2 Level of testing: There are several types of testing in a comprehensive software test process, many of which occur simultaneously. ' Integration Testing ' Regression Testing ' System Testing ' User Acceptance Testing 6.2.2 Integration Testing: The individual components are combined with other components to make sure that necessary communications, links and data sharing occur properly. It is not truly system testing because the components are not implemented in the operating environment. The integration phase requires more planning and some reasonable sub-set of production-type data. Larger systems often require several integration steps. It is a more intuitive approach to testing that also usually finds errors in critical routines earlier than the top-down method. However, in a new system many modules must be integrated to produce system-level behavior, thus interface errors surface late in the process. 6.3.2 Regression Testing: Regression tests confirms that implementation of changes have not adversely affected other functions. Regression testing is a type of test as opposed to a phase in testing. Regression tests apply at all phases whenever a change is made. So basically it deals with the affects to be generated if we change the one part of the Application and other parts are working or not. 6.4.2 System Testing: The system test phase begins once modules are integrated enough to perform tests in a whole system environment. System testing can occur in parallel with integration test, especially with the top-down method. System testing tests not only the design, but also the behavior and even the believed expectations of the customer. a) Performance Testing: The actual performance of the application is considered as main point in this testing. The minimum hardware configurations are needed to run the applications are as follows. o CPU : 400MHz or Above ' RAM : 256 MB or Higher o Storage : <20Mb (As per usage) If the device doesn't have minimum amount of specifications then application might not work smoothly. b) System Load: A System Load testing is it confirms that the system can handle heavy loads, but cannot so easily determine if the system is producing the correct information. If the system load is heavy then there might be chances to crash the application or hang the application. To overcome this drawback we made this application to consume very less amount as possible of system resources. There are also chances of restarting the device or headset if the overall background applications and other abnormal services are running, c) Stress Test: An important phase of the system testing, often-called load or volume or performance test, stress tests tries to determine the failure point of a system under extreme pressure. Stress tests are most useful when systems are being scaled up to larger environments or being implemented for the first time. Web sites, like any other large-scale system that requires multiple accesses and processing, contain vulnerable nodes that should be tested before deployment. Unfortunately, most stress testing can only simulate loads on various points of the system and cannot truly stress the entire network, as the users would experience it. Fortunately, once stress and load factors have been successfully overcome, it is only necessary to stress test again if major changes take place. A drawback of performance testing is it confirms the system can handle heavy loads, but cannot so easily determine if the system is producing the correct information. d) Security Testing: Security testing is a process intended to reveal flaws in the security mechanisms of an information system that protect data and maintain functionality as intended. Actual security requirements tested depend on the security requirements implemented by the system. Security testing as a term has a number of different meanings and can be completed in a number of different ways. The application itself has an advantage of secure the entire app data in the android file system, if any user has to access the database the phone must be rooted to access internal file system. The application made in android itself also checks the duplication of data in SQLite database as certain circumstances like username or email, so no more duplicate accounts possible of same data. As an enhancement in security of internal data, the feature called as 'ProGuard' is integrated into the Android build system. The ProGuard tool shrinks, optimizes, and obfuscates your code by removing unused code and renaming classes, fields, and methods with semantically obscure names. 6.5.2 User Acceptance Testing: User Acceptance Testing (UAT) consists of a process of verifying that a solution works for the end user or not. It is not system testing (ensuring software does not crash and meets documented requirements), but rather is there to ensure that the solution will work for the user i.e. test the user accepts the solution. Alpha Testing conducted internally by the manufacturer, alpha testing takes a new product through a protocol of testing procedures to verify product functionality and capability. This application is used by us, so we are conduction Alpha Testing for our application, because the developer does know the complete code and knows about the bugs and other enhancements possible. Here we are testing the application, so we can implement the limitations and vulnerabilities in final completion of the application. 9.2 Testing Life Cycle: Software Testing Life Cycle (STLC) is the testing process which is executed in systematic and planned manner. In STLC process, all different activities are carried out to improve the quality of the software. Following steps are involved in Software Testing Life Cycle (STLC). Each step is having its own Entry Criteria and deliverable. ' Test Strategy ' Test Plan ' Testing Process ' Generate Test Case ' Execution 6.2.2 Test Strategy: The test strategy describes the approach that the test team will use to test the software both overall and in each phase. Deciding on the strategy is a complex task- one that needs to be made by very experienced testers because it can determine the successes or failure of the test effort. 6.3.2 Test Plan: Test Plan is the primary step of testing phase by which software testers communicate to the product development team what they intend to do. The purpose of the software test plan is to prescribe the scope, approach, resource, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with the plan. We test software process activities such as Design, Implementation. Because design cost error are costly to repair once the system has started to operate. Hence it is important to repair them at initial stage of implementation. Test plan needs to identify the people working on the project, what they do, and how to contact them. The test team will likely work with all of them and knowing who they are and how to contact them is very important. 6.4.2 Testing Process: Testing process can have different types of tests and the ability of software to survive the tests are verified by the testing professionals or the developer. ' The various tests done on application are as follows. ' Startup Test ' Load/Performance Test ' Connection Test ' Registration Test ' Chatting Test ' Sharing Test ' Display Images,Video,Audio,Install Appsproperly in application Test ' The results of various tests done on device are shown in next Test Case generated by us. 8.3.4 Test cases: The test cases are designed to check the system functionality to ensure the software quality. Here we have designed test cases for android application that consist the resultant output and errors to be corrected. No. Test Input Expected O/P Actual O/P Action 1 Startup Starting App Splash Screen Splash Screen Success 2 Load/Performance Starting Main Activity Start Page Start Page Success 3 Connection Test Establish Connection to Network No Error Connection available Success 4 Registration User Details Submit user information into database and open Home Activity blank User Name Do not insert blank User Name 5 Chatting To write text Sent and Receive textual message both side Completely sent and receive message both side Success 6 Sharing All media data, installed apps Completely share media data and install apps Completely share media data and install apps Success 7 DisplayImage,Video,Audio and install app properly in application Swapping page one by one Completely display all content and done swapping page Completely display all content and done swapping page . Success Table 8.3.4.1 Test cases 8.3.5 Execution: After all the test phases completed, The execution of the Applications on various devices are performed. The Compatibility of the execution on the different devices is the most important for the application. Our application can supported by the Latest Android KitKat 4.4.2 version and as least as Android API level 14 IceCreamSandwich 4.0 version also. 7. SCREEN SHOTS 8. LIMITATIONS AND FUTURE ENHANCEMENT 8.1 LIMITATIONS ' Can only create 9 profiles for player. ' This application can run on android platform only. ' The limitation of this application is that no two player can select the same character at a time. ' In drawing, Images that are saved can be seen but cannot edit it. ' Only four tasks are included in present. 8.2 FUTURE ENHANCEMENT ' More player profile can be possible to create. ' Along with the module defined in the project, we can also include new modules like puzzles, fast quiz, etc. ' By adding new more complex modules, even kids who are more than 12 years can also play this game. ' More levels can be implemented. ' Different music that can be changed while playing for application. ' ' 9. CONCLUSION ' ' 'Kid's World ' Play Fun Learn' is an application developed for android platform. This application is a quiz game built for learning purpose of small age group of kids varies from 3 to 12.This application has main purpose of providing small kids with the knowledge of various basic learning practices that is helpful to them at studies. ' ' This application is used as a method to analyze kid's growth in different fields of learning by parents. This application is played by kids with fun and their learning achievements are analyzed by parents as a track of their scores in each task is stored individually in the scorecard as they solve the question at different levels in each task. This application have different tasks like mathematics, Words, Alphabets, Picture recognition. And the main feature of this application is its scorecard built to store each task details separately. REFERENCES Website references: ' http://en.wikipedia.org/wiki/Android_(operating_system)
‘ http://source.android.com/devices/index.html
‘ http://developer.android.com/about/index.html
‘ http://en.wikipedia.org/wiki/Project_management
‘ http://stackoverflow.com/questions
‘ http://www.github.com
‘ http://www.androidhive.info
‘ http://www.tutorialspoint.com/android/
Books:
‘ Java Complete Reference
‘ Android Programmer Guide
‘ Learning Android
‘ Professional Android Application Development