Practice 4--Reading the law of Construction 5.5, 6-7 chapters

Fifth Chapter

5.3 Development process

For the software development process, in the current University of software development Learning, most of us are using the Swarm team model, generally several people or a person's state is no document class plan, directly to play code, write a change to write, sometimes even the mind is chaotic, hit the code, show the effect is correct, If it is not correct, change it again. If the teacher asks to write the project requirements, analysis, UML diagrams and other documents, then always after the project is completed, and then hastily write the document according to the completion of the project. For the development process, it is completely chaotic. Now learn this chapter, the software development process also have a certain understanding, the next development work can also try to apply it. However, before this, we also consider that, in fact, the work done now, the time limit is more urgent, if the stage really to follow a certain process, then spend a lot of time, it may be unable to deliver the job on time, so at this stage of software engineering work actually seems to rely on the swarm mode.

In China, most companies are still in accordance with the boss-driven process, in such a process, most of the software orders are mainly through personal relationships, the boss than the general technical staff to understand the market and competition, and the boss of the technology is not necessarily good, so in this process, the boss and team is the ability to complement each other. Some of the ability of software engineers are separated from the team on their own to talk about projects, write their own code, the income is considerable. Of course, this is a test of a person's ability, whether it is communication skills, technology, etc. are particularly important, after all, they have carried out the role of the boss and employees.

The sixth chapter Agile process

1. Agile processes are not omnipotent, like nature's plants, have the role of purifying air, but some suitable for living in the greenhouse, some suitable for living in the wild, some suitable for living in the land, some suitable for living in the water. We cannot say that the Lotus cannot live on land and says it is not a good flower, it only has to live in the place that is right for it to be meaningful. Agile programming is the same. Has its own scope of application, there are pros and cons. It is not omnipotent, it can be used for "frequent changes in demand or changes in demand, the project team and users to communicate more easily, the project development risk is relatively high, the size is small, the general project team members within 50 people; "Software development. (quoted content from Baidu). There are theories and tools, agile is a good theory, and other methodologies have certain uses. All say paddle, so the ability to use theory and application tools is a must.

2. What is scrum? Agile development?

Scrum is an iterative incremental software development process, often used for agile software development. Scrum includes a series of procedural skeletons that practice and pre-define roles. The main roles in scrum include the role of the scrum leader, similar to the project manager, responsible for maintaining processes and tasks, the product owner representing the benefit owner, and the development team including all developers. Although scrum is developed for managing software development projects, it can also be used to run software maintenance teams or as a plan management approach: Scrum of scrums. (from Baidu Encyclopedia)

Seventh MSF (Microsoft Solution Framework)

1. Microsoft recommends the method of doing software--msf. The 2nd principle of MSF, "Working for a common vision", is the vision of a software development product and the key to a project. If the team disagree, it is difficult to reach the consensus, then the software products made, it must be wrong. Although "100 readers will have 100 Harry Potter", everyone's opinions, ideas are different, but we must do our best to unity, have a common vision, yearning for the vision, not to undermine the principle, in order to make everything orderly. Principle 3 "Full empowerment and trust" includes mutual trust among members of the team, as well as customer trust in team commitment. But this trust is often difficult to achieve between leaders and leaders in the team.

2. In TFS, you can ensure that people are not exhausted by the rules. Because TFS can help us save all the information about the project, including some stupid, low-level bugs. All errors, changes are not allowed to delete, so as to facilitate our experience. Even great men make mistakes, so they don't have to worry about their mistakes being put in front of you, putting them out, just to experience the lessons, to do better next time, not to punish those who make mistakes.

3. For business value, indeed a lot of college students took part in such a competition, did a very cool project, then no matter take the prize is nothing, never in the actual run. So it's all about losing the business value of the project itself. The Yu Jiawen of the Chinese Soft school embodies the business value of software, he issued a "super curriculum" app, creating business value for "Super Curriculum", and achieved great success, became a "myth".

Practice 4--Reading the law of Construction 5.5, 6-7 chapters