Case study of the Microsoft Cortana app

Personal Blog Job Three: Microsoft Cortana Case Study of the APP

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 ticket site, contact with each other, QQ, and so on 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?

through various case analysis, evaluation, debate, summary, we can see the principles of software engineering in the practice of all kinds of embodiment, learn software engineering, help us to do better in practice.

Products

please download Microsoft Cortana - Smart Assistant ,win10,iOS or Android clients all have!

First Part Research, Reviews

( bugof software,functional evaluation, black box test, Chapter 8 User Survey, user experience of software)

1. Download and use to describe the simplest and most intuitive personal first-time experience.

in freshness and curiosity, I downloaded the Microsoft Cortana smart Assistant. When opened, she gets most of the user's information, including some privacy information. So the construction of information security and maintenance is very important, so that users can use it with peace of mind. The user interface is simple and can be used to design multiple themes in layout. In the menu bar has a variety of functions, is more common, widely used.

Figure 1-1

1. In accordance with the definition of Bugs described in the 13.1 section of The Building Act , we found a few functional, more serious bugs. Minimum of 2 .

(1) There are sometimes errors in language recognition (i.e., human-computer interaction).

(2) in the information query will be irrelevantly replying.

(3) of course, its simulated artificial intelligence, is still more vivid.

(4) Excessive collection of user personal information.

1. describe in a professional language ( each bug is not less than the number of words ) , if necessary , can be fitted with diagrams.

First, a brief description is given by the definition of the Bug in chapter VII of The law of construction .

1. believe that each classmate's friends must be someone who needs to use such software , choose a friend (user) to conduct interviews, and to record.

I interviewed my classmates, and he also downloaded the software out of a sense of freshness.

At the beginning, the use of artificial intelligence to query information, or to make some things, found that its efficiency is still relatively high. Feel that she knows her cell phone better than herself. After another period of time, the collection of too much privacy information has some trouble, but also the details of the software processing services for the praise.　

　 He said that this piece of the interface layout is somewhat lacking, menu options in the function is too few , not enough to meet the majority of applications, so after the use of less.

5. Tip : Interview Summary

5.1. Introduction to the background and needs of the interviewee (why they use the software)

Meet some needs, liberate labor, improve work efficiency.

5.2. let the interviewee use The function of the APP (please upload a photo to prove that the user is actually using it, Remote interview Students please let others help take photos)

Figure 2-1

5.3. describe the user's use of this product process, the user's problem solved it? what are the advantages and disadvantages of the software in data volume / interface / function / accuracy? Is there a problem with the user experience?

5.4. what are the user's suggestions for improving the product?

(1) The theme of the interface is diversified.

(2) function close to life, and diversified.

(3) Human-computer interaction can be more perfect.

5.5. conclusion: After so much work, you must have a good reason to give this software the next rating :

Also good, in a way of artificial intelligence, to meet the needs of most users, it is worth using.

? very not recommended

? Not recommended

? General

? yes, good.

? very recommended

Part II Analysis

(Refer to the work estimate of the 8.6 section of the building law , and the quality of 14.1 Software Engineering )

1. using all the features of this software , it is estimated that this project will take approximately how long it takes ( team size is around 6 people , Computer University Graduates , and have professional UI support ).

As a college student, our technical level is not high enough. There is no specific answer to the exact time of completion of the software.

in the process of completing this software, it is divided into 3 stages - definition, development and maintenance. Definition of problematic definition, feasibility analysis, and requirements analysis. The development phase is divided into design and coding tests. Finally, maintenance is required.

How long does it take to implement a module, and what parts are involved in the specific coding? Server to build, database to design.

in the project implementation phase, it can be divided into several modules to complete. Follow the features in the Software menu bar to divide the module. The focus of the software is on the implementation of artificial intelligence, so the time spent in this area will be relative to the length of the teaching. There are also related to database interaction, as well as some of the areas of attention, coupled with the final test acceptance phase, as well as on-line repair BUG, the total will take about 1 years or so. Then is the version of the update, in the actual use of gradually improved.

1. analyze the current merits of the software ( at least 2 software comparisons compared to similar software ) , and deduce the important aspects that the software team can improve in software engineering. ( specific recommendations ) . The results of the comparison are asked to List a table comparing the advantages and disadvantages of each software.

Advantages: Easy to use, more functions.

Disadvantage: human-computer interaction needs to be improved.

1. [ Additional questions ] according to the understanding and experience, draw the whole software all functional logical block diagram, according to the importance of the module to identify the importance of the degree, completion, starting point and effect;
2. [ Additional questions ] For different dimension ratings, the user experience, UI interface Aesthetics, core functions, scoring separately (can give more detailed score better)

Part III recommendations and Planning

(Refer to the position and priority of function in chapter 8 of The law of construction ; Chapter 9 project manager )

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

If I am the project manager of the team, I think the improvement is UI design aspects. First of all, consider making the market, or a crowd-oriented, to make the necessary work. After all, relying on software design is for people to use, the liberation of labor, to provide users with convenience.

and does not say that the current mobile phone prevalence, artificial intelligence has become the trend of this era. So the market's concerns are not that big. Next down is the function, what kind of function satisfies what kind of crowd. The first is the student community, which is the publisher of this software. Then there are the working groups, which provide some Office applications. There is also the mass community, providing the most common and useful application of life to meet the daily needs.

after users use the software, the need to consider is how to retain users, how to attract new users, how to stand out from the competition, which requires innovation, to explore more more demand. improved in interface, function, interaction efficiency.

1. What kind of products are there in the market now?

similar products, Siri.

1. What kind of features do you want to design?

in the improvements on the UI.

1. Why do you want to do this instead of other features?

It is important to be first impressions and feel that the interface of this software is not good looking. Because it is also just beginning to use, so some features are not very familiar with Ha, in the future of interaction to explore it.

1. Why does the user use your product / feature?

The user chooses a model software, sometimes very simple, in the case of others and the basic satisfaction of your function, he will rely on the first impression of this product to choose. The interface is the most advanced part of the user's ability to reach the software . So take the time to refactor the UI design, and you can reap more users .

6. where is your innovation ? Please use NABCD Analysis

( http://www.cnblogs.com/xinz/archive/2010/12/01/1893323.html ).

1. If you were to lead the team, what would be different?

if I were to lead the team, a competent Assistant There is no less. . In addition, I want to be involved, whether it's a requirement analysis, UI design, or code implementation . Careful questions do not need to be involved, but there are some important decisions that need to be made. In order to have a clear understanding of the process and function of the project, we can grasp the general direction. To better understand the work of each role of the team, to facilitate future work arrangements.

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

　because this time the focus is on UI design aspect, so I need to have 1 artists,3 Development,1 tests. Developers and artists need to communicate in a timely manner to design a satisfying UI interface .

After that, you can assign one person to test in development.

1. describe what your team will do every week during the week to release software, size milestone settings as scheduled in week one .

Week 1 : The problem is clear and a sexual plan is developed. Through the Network survey, user research and other ways to understand the needs of users, so that the art of designing a preliminary set of UI interface.

The first and third weeks : Demand Analysis is the development of the general direction, is crucial. It is necessary to spend enough time on the so-called sharpening of firewood. Organize user feedback, the artist continues to improve the UI design, continue to investigate, continue to get feedback, and form a preliminary final version.

Week 4~8 : The developer completes the on-the-inside version and the tester makes the test feedback.

9~10 week : put some market, receive the feedback of the official user, organize immediately, revise the BUG.

Week 11~12 : According to the collated feedback, the developer changes, completes the public beta version, the tester carries on the test feedback. Test pass, release the product.

Case study of the Microsoft Cortana app