The concept and role of the mobile app scene in singapore

The role of the user is fixed, static, and only put it into a certain scene, will be alive and interact with the product.
Scenarios are "idealized" scenarios in which personas interact with the product. It tells the story of how each persona interacts with the product. Each person character will correspond to a scene, or even more, in order to cover various situations in which the user uses the scene.

Use personas for contextual mining in scenarios: Designing a sensible scenario for each personas, then brainstorming with staff (not just interaction and visual designers) of app design. At this stage everyone should have a deep empathy, and at every point of the joint he can put aside what he can think of, say it completely, and record the atmosphere at this time is also unconstrained and non-critical.
In this time axis "life day" as an example, to use mobile phone browser product character to carry out demand mining. for example:
In the morning, just get up: Will see the weather forecast, the calendar may be involved in the function: weather, calendar.
When eating breakfast: may look at the news, mail, and your own blog. This will be designed to news, microblogging and email.
And the traffic on the way: Morning Office: Noon Lunch: Afternoon Office: Before get off work: on the way: in the restaurant: home: blanket and so on a variety of state down to tap the possible functions.
Each person character through the mining of one or more scenes, to be listed on the functions involved, and according to each person's role in the importance of defining the weight of each function, and create excel file.

1.4 user demand for the promotion of product demand, resulting product demand list
The user needs obtained above, and can not be directly transferred to product demand, need to go through a certain evaluation and handsome election to examine the feasibility and necessity.
Feasibility: Is current technology and enterprise resources capable of mobile app developing that fully meet the needs of users under realistic conditions, such as current conditions and schedule.
Necessity: Whether or not these needs of users need to be met to meet the needs of enterprises to pay the price, and whether there is sufficient corporate effectiveness to support the operation of the market.

After the above verification, and combined with the aforementioned stakeholders described above, competing products, benchmarking market and internal seminars and other user needs obtained, so as to get a complete list of user needs.
All product requirements here are translated into product features. Staff can incorporate functional requirements collected during previous user research phases into a list of requirements that they later tap into the scene using the task's role. They essentially correspond to different personas.
Here, the product of the weight of the character (which can be divided into 3-point scale or 5-point scale according to the primary persona, the secondary persona, the unimportant persona, etc.) and the weight of the corresponding task is the overall degree of importance of the function.