Answered You can hire a professional tutor to get the answer.
I will pay for the following article Second question to complete the project. The work is to be 2 pages with three to five sources, with in-text citations and a reference page.
I will pay for the following article Second question to complete the project. The work is to be 2 pages with three to five sources, with in-text citations and a reference page. Number: Lecturer: Activity Design scenarios and claims The activity design scenario has two actors ly Android users and programmers. The two actors have divergent understanding of the Android phone. While the user does not understand the cause of the problem in the Android programs, the developer or programmer can rectify the problem. Both actors have been provided with distinct activities. therefore, problem discovery and recovery will take place at different levels.
Actor
Problem Scenario
Actor1: Android phones users
Background: Users have no technical knowhow on how to correct bugs in Android programs since most of them are not programmers.
The programs in this phone close by issuing forceclose error. This means that the applications, had bugs. Users have lost data resulting from this application error. hence, the need to rectify this error.
Actor 2: Programmers
Background: The programmers understand the problem. They can provide a remedy to the problems experienced while using Android applications.
The programmers have to come up with the most effective and efficient applications to use with the Android phone to avert forceclose error.
Claim Analysis
In claim analysis, the activity design includes,
Discussing the issue at xda-developers.com
Discussing the issue at androidcentral.com
Popularizing Android phones on androidcentral.com and xda-developers.com
These activities aim at improving Android usability, program efficiency, and recoverability of the programs. In the activity design, both advantages and disadvantages have been hypothesized as indicated in the table below.
Activity Design
Hypothesized Advantages and disadvantages
Discussing the issue at xda-developers.com
Advantages:
It will enable programmers to access and share information about the forceclose error.
It will be convenient for developers to get immediate feedback
It will help the developers to improve on the usability of the and efficiency of the Android phone
It will provide recoverability of the forceclose error
Disadvantages:
The non-technical Android users will not understand how the information will help them
Non-technical users may not contribute to the discovery of the problem
Discussing the issue at androidcentral.com
Advantages:
It will be convenient for Android users to get immediate feedback
It will improve the usability of the Android phones
Disadvantages:
Android users will have to wait for other users to experience similar problems for an issue to be popular.
Non-technical users may not contribute to the discovery of the problem if they are yet to experience it.
Popularizing Android phones on androidcentral.com and xda-developers.com
Advantages:
There will be more users of the phone
More users will be aware of the applications used in Android phones
Disadvantages:
More non-users will know of the problems associated with the Android phones.
Metaphors for activities in Android phone:
Activity
Metaphor
Implications
Discussing the issue at xda-developers.com
Discussing the issue at xda-developers.com is something like a forum of experts in a boardroom
Interpretation of the problem
discovery of the source of the bug
bug elimination
Discussing the issue at androidcentral.com
Discussing the issue at androidcentral.com is something like a driver helping another driver to change a tire
Immediate identification of bugs
Identification of more issues
Identification of alternative programs
Popularizing Android phones on androidcentral.com and xda-developers.com
Popularizing Android phones on androidcentral.com and xda-developers.com is something like blowing a trumpet for all people to hear
Buying of the Android phone
Identification of alternative programs
Works cited
Darses, Françoise. Cooperative systems design scenario-based design of collaborative systems. Amsterdam Washington, DC: IOS Press, 2004. Print
DoCoMo. "Mobile Phones Increasingly Popular Among the Elderly." Computing Journal (2001): 65. Print
Jacko, Julie and Sears, Andrew. The human-computer interaction handbook : fundamentals, evolving technologies, and emerging applications. Mahwah, N.J: Lawrence Erlbaum Associates, 2003. Print
Martin, Richard. and Hoover, Nicholas. "Mobile Computing." Information Week Journal 3.23 (2008): 21-23. Print
Rosson, Mary. Usability engineering : scenario-based development of human-computer interaction. San Fancisco: Academic Press, 2002.