Individual homework 2--English learning app case study

Title Requirements:

We have a lot of time in our lives to deal with the software, we have to play in class when the mobile games, buy train tickets website, contact with each other, QQ, and so are software, are worth analyzing. Why do you become their users? What did their team do right and what was wrong? Would you do better if you did it? Case study: Research, evaluate Bing dictionary .

The first part: research, evaluation.

1.1 First-time experience:

The interface is brief but not very beautiful. No ads are an added bonus to experience

1.2 BUG:

1.2.1 cannot translate words that are read internally daily in the word-taking mode.

1.2.2 The fixed window function fails when the mini-window mode is turned on. (WIN10)

1.3 Interview trial.

To better understand the user experience, I have invited a roommate who needs to take a level six exam. Usually the requirements of the dictionary are mainly to find Fast, less steps of operation.

1.3.1 Trial experience.

as Microsoft's own dictionary, Bing's promotion is not very good, in our college students of the group does not seem to be famous. Functional and interface aspects: simple interface basic functions are available, but there is no nearly just need to back word function.

1.4 Improvement opinions.

1, now everyone of English learning is very important, now English learning software generally not only contains the basic function of check words, most of them provide a certain interesting back word function, hope can be improved.

2, the interface of the software is simple and clear, but not beautiful enough. If the interface design can be more beautiful, it will improve the user's enjoyment of the degree.

1.5 conclusion.

General. For functional requirements are relatively simple to consider, no ads this is still very praise!

Part II: Analysis.

2.1 Team Collaboration analysis.

such as the team number of 6 people, computer university graduates, and have professional UI support, such as working 8 hours a day, estimated to take 12 weeks to complete software development debugging.

2.2 Software Market analysis.

I think this software is currently at a small disadvantage through a trial by myself and a small partner.

Part III: Recommendations and planning.

3.1 If you are a project manager, how can you improve and win in the competition?

Do market research to understand the real needs of the target users. At the same time the function of the product is strong, the user interface is good.

3.2 What kind of products are available on the market?

Powerful dictionaries, and a variety of back-word software.

3.3 What kind of features do you want to design?

Set up a leaderboard that can be organized as a class or as a personal invitation.

3.4 Why do you want to do this function, not other features?

A good learning partner can greatly improve our learning efficiency, there is such a chart can form a healthy competition. Improve our enthusiasm for learning. Many other features are available in our world, and we use a differentiated style so that users with this need can choose us.

3.5 Why does the user use your product/feature?

To form a healthy competition, improve user learning enthusiasm.

3.6 Where is your innovation?

Our products can solve the problem that many users cannot persist in the long-term boring back words. The way we use leaderboards has added some fun to the learning process, which is not available in many other software on the world. At the same time, if the user thinks that our function is interesting, it will also recommend to the people around to join this leaderboard to compete. Just as the movement pushes the number of steps a day, it also makes people more athletic.

3.7 What would be different if you were to lead the team?

Identify the basic functions and core points of contention that we need.

3.8 If your team has 5 people, 4 months of time, you as a project manager, how should you configure roles (development, testing, artwork, etc.)?

According to each person's expertise to allocate, the center of gravity is mainly in the development aspect.

3.9 Describe what your team does each week during the 16 week period in order to release the software, size milestone settings as scheduled in the 16th week.

1-7 weeks development.

4-8 weeks of UI beautification processing.

9-12 weeks debug, trial run modification, make Bata version.

13-14 weeks to open the small-scale beta, collect user feedback.

15 weeks modification, adjustment to make the final version.

Released on schedule 16 weeks.

Individual homework 2--English learning app case study