Tenth chapter (typical users and scenes) (Goddess of God with Community Dating network)
- Name: Onion
- Gender: Male
- Date of birth: 19940404
- Age: 21
- Blood type: AB
- Occupation: Student in school
- User preferences: like to make friends
- Motivation, purpose, difficulty: Want to take off a single, because always single, so eager to seek true love, the other half of life, difficulty: fear of not meeting true love;
- Typical scenario: On social networking sites, you can encounter true love among a large number of people;
- Typical description: The more people you register, the greater the opportunity to find true love.
- name: Sybin teacher
- Gender: Male
- Age:
- blood type: AB
- user preferences: likes to make friends, music loyal to the computer application base
- motive, purpose, difficulty: Want to use this network platform, to meet more music loyal to the application of the basis of the Youdao, hope to communicate together. Difficulty: fear that if there is a similar interest in the students, because the identity is a teacher, and do not want to communicate with themselves in depth
- Typical scenario: If one day, can meet in this platform one or two fellow human, in the classroom is the teacher-student relations, after class each other becomes the friend, the elder sister
- typical description: The more people you register, the greater the chance of encountering such a person in a sense
11th chapter (Software Design and implementation)
- In the software development phase of the daily management, to minimize non-development time , do not have to open the "plenary", because team members of the self-time management is also important. Like our team, the first to hear that every day to open a regular meeting, I think this is not practical, because when the meeting, I must be forced to say progress. If every day to open a regular session, their own research and development of the time is limited, there is no big jump progress, every day to open the meaning of the regular meeting is not very small. Some good teams, such as some of Google's teams, stipulate that one day a week is not a meeting. But at the same time we do not encourage "closed development", we should have more freedom of communication, so that team members will be more willing to ask and share in an unfettered environment.
- For Daily builds , once the work is busy, we do not have the time to control the problem of construction. Our team sometimes collective meeting time is in the evening, generally we discuss the fiery will forget the time, until the outside world suddenly disturb (teaching building off the lights lock door) only to remember that should be adjourned, and back to the dormitory and because of the network (broken network) can not update the progress of our team discussion in time, This may result in the second day after forgetting that there are other things to deal with and that the discussion is not updated in the end. So, as in the book "Chiu" said:"in theory, theory and practice is one thing, and in practice, theory and practice aretwo different things."
- We have to understand and be familiar with the construction process, because the building is the core , like a handyman to understand and familiar with scaffolding construction, players in the game to understand and familiar with the dribble.
- Work to understand the balance of progress and quality . I have always had a problem: like our team this time to do the male goddess with community Dating Network, I am responsible for the homepage design and content module, there is a teammate responsible for the site registration and login module, a teammate is responsible for the search module, a teammate responsible for the Activity view module. But a project is a whole, each person responsible for each module must be linked to become a whole, for example, my home page completed 50%, in order to see the overall effect, to the team to connect with his module, if the other side in my program to modify the section, At the same time I also continue to write the rest of my content, both sides in my original completed 50% of the progress of the module has been modified, the next job, in the end with whose? In fact, both sides of the modification must be used, but I can not wait for the other party to modify and then continue to do the next work, and the other side will not be able to wait until I complete 100% of the module I am responsible for viewing the modification or connection, because this will lead to a significant decrease in productivity. I think this is a bit like when we learn the operating system of the ticketing system , several windows at the same time to the customer ticketing, there must be a mechanism to manage the remaining number of votes, because it is not possible to successfully sell the same ticket several windows.
12th chapter (User experience)
The method of construction--typical user and scene + software design and implementation + user experience
