Avenue to Jane Seventh chapter eighth chapter

IBM's ability to improve its software engineering system acquired Rational, which has greatly increased IBM's strength.

A software implementation can not be separated from the efforts of the team, a person again genius also have a place to think, a person even if useless, but also with his good place, no matter when the team should be engraved in every one of our software worker's heart. Just as we write annotations during programming, it's for the sake of clarity and for the convenience of other people on the team to read. This is what the team said on the boulevard to Jane.

Ant's team is always very well organized by instinct. However, if a colony of ants has a pandemic disease, the ant is dying, and the newborn ant can't keep up with the speed of its death, then soon the team is scattered. This is because ants are used to maintain the "capital" of team operations in the drain. If there is no capital, there is no operation, there is no necessity and possibility of the existence of the team. The project is dead. This shows the importance of the team.

Making a software The first thing we want to be sure of is the goal, so that the strength of the team can unite together to achieve greater value.

In the demand phase, we will face the "goal" problem. On the contrary, we will meet the customer's quality complaints when the project is delivered and tested. The demand staff will blame the developers for all the blame, and the developers are constantly complaining about the need to be unclear or the endless changes. And if demand and development happen to be the same person or group, then they will start complaining about the client's rigor and the stress of the schedule. Because the goal may be established in the balance, but the quality is controlled in the process. Even with the balance of time, resources and functionality, even if customers, project groups and companies are equally satisfied with this balanced "goal", it may still be "impossible". If the whole of the original target itself is too large, the result of balancing the three relationships in any case is still not guaranteeing quality. When it comes to the question of objectives and quality, it refers to "the relationship between balance of time, resources and function". This is actually a detail in the implementation process. Or, it is a concrete method, not an end. So the details that we usually say are actually some limited descriptions of the implementation methods. For example, the concept of "software technology" itself, is to elaborate "details of the problem." From this point of view, I am not against the "details determine success or failure" view. But notice a premise: This is the detail of the technique or method. The first concern of software engineering is customer-based, the whole project's success or failure and quality. Fundamentally, technical, reusability, etc., is only the means to ensure the success and quality of the project.

Every software is a programmer's child, hate can not be the best of all to him, in the continuous modification of the perfect, finally let everyone satisfied. Now for the software engineering we have only seen the tip of the iceberg, in the future study we will be "Boulevard to Jane" This book must have a deeper understanding. To keep beginner's mind, what is beginner's mind? To keep a constant learning heart, always remember to learn.

Avenue to Jane Seventh chapter eighth chapter