Soft work - the last team work: Summary
| This work belongs courses |
https://edu.cnblogs.com/campus/xnsy/Autumn2019SoftwareEngineeringFoundation/ |
| Where the job requires |
https://edu.cnblogs.com/campus/xnsy/Autumn2019SoftwareEngineeringFoundation/homework/10119 |
| Team Name |
typhoon |
| The target job |
The contrast between the first blog of the curriculum summary and reflection and vision; A semester to reflect on their learning process and make the future of learning programs; |
| Github Address |
<Given link> |
| The first job |
https://www.cnblogs.com/ayanotc/p/11509618.html |
Reflection
(Attempt to answer the questions you raise, and to clarify, is how to read, practical, or figure out the discussion.)
- How to get better user needs / new ways to improve the user experience
A: In this course just the beginning I have raised these two issues, through the development of practical experience of our team, I have some questions to these two simple views. When the target program is not too large, we can first take the traditional surveys and other methods to get its basic functional requirements, then when the project first edition publication, first through continuous experiment internal testers, constant use and then found the problem and found after the re-release is insufficient, and optimize subsequent editions repeat the process until it perfect to near perfect launch user-oriented, the purpose of doing so is to use the program through user roles they play, to imagine the user through empathy needs and feelings may experience effect, this method can greatly improve the user experience of feeling the first time, the product leaving a good impression.
- Task allocation method
A: This problem is not fixed answer, because every team in the division one team in the role is different, but in general we can not accurately determine the content and complete needed to complete a project, so at the beginning of the beginning of the task is still to be good at their respective portions of the task assigned, but as the project, the task has become increasingly cumbersome and complex, each person will no longer be limited to those initially planned distribution, which requires at the beginning of the task allocation should be simple and plain, it does not have to work out the details and specific content of each stage, but continue to fine-tune each individual task in the task in progress, so as to ensure maximum efficiency of the task fair assigned to each individual.
reward
(After this semester, you have mastered the skills which were not there before, how you grasp.)
- Use Github
- Prototyping
- Pair Programming
In this course through a time of major assignments and team projects I learned skills is to learn to use Github, prototyping as well as pair programming, first learned how to use Github great help to me, like a freshman at the beginning CSDN aware of the existence of its importance even more than this, though I use Github is not yet skilled enough, failed to play a full role in its own, but I believe in the future of learning in Github It will continue to play a role; prototyping Society may be followed by a big harvest this semester I, the benefits of prototyping in the development process before it is too big for a white programming is simply an epoch-making turning point , making prototyping and then programming it a lot easier and a more visible to their own pace; the last knot in the current program can only be regarded just whom contact has not been able to play to their strengths role of stage right, but also I have a basic understanding of this new development model, after all, better than nothing.