Some discussions about the greatest truths to simplicity ~

Mr. Yan Xin, author of "The path to mountains", wrote an article about several issues in "the greatest truths to simplicity. Read related questions
I also often ask, so I picked up a reply to Mr. Chen, which is also a response to some common questions.

The original Article is posted on the official website of "mountain migration:
Http://yishan.cc/blogs/xin/archive/2007/09/15/693.aspx

= Reply abstract =

Q2.a
The requirements for process management are very different. In addition, "model and Model language" seem closer to "method ".
==========
An ehm diagram tries to remove engineering elements, rather than emphasizing the complex relationship between them. Therefore,
A noun is a narrow definition. For example, the model in a process mainly emphasizes the process model and the process gap for completion.
Common Model language. In fact, in a broader sense, processes, projects, organizations, and so on all have their own methods and methods.
Methods also have their own models or model-related tools. This complex relationship is not described in the ehm diagram.

The first part of chapter 10 is a supplementary description. In fact, the entire chapter 10 is missing, making up for some of the previous chapters
Hidden issues that are ignored or hidden due to extreme or focus on details. This is what the quotes mentioned earlier in this chapter mean.

The q2. B model is still useful. The author may explain what different people should be able to obtain from the model.
==========
Yes. However, this book does not elaborate on practical methods. I will explain this question in detail later.

Q2.c has already been found. Thank you for your correction.

Q3. why does "Project Manager" belong to the development team, but there is an independent "Quality Department" in the figure on the 30th page "?
I think the project participants of the "quality department" should belong to the development team.
==========
An independent "Quality Department" model is a model that companies that focus on project output may adopt. For example, Shanda
Such game companies have both specialized product testing departments and specialized user experience testing departments. These are for customers,
The final product. The establishment of such departments is the responsibility of the same department and the same supervisor for a large number of products of the same type.
Management, but it is easier to control quality. However, this quality department is not suitable for unit testing or module testing during the project process.
Try. The R model is a very simplified model and does not take into account the details of the project. In fact, it is mostly used
To distinguish roles.

Q6.90 page, figure 7-3: It seems that "method" should be on "tool. Methods are specific and abstract. Here we will talk about
ItemsProgramModule Design method or software engineering methodology?
==========
This figure is taken directly from software engineering-Practitioner's research methodology. I think it means that a tool is a specific implementation of a method.
Currently, tools rely on specific method theories. I just checked the original book. The original Article says, "The tool provides
Manual or semi-automatic support ".

Q7.94, boss question: Who is boss ?......
==========
This is an interesting question. I think you mean: the customer is boss. The answer is also correct. But among many domestic companies
The problem is not to provide services to customers, but to survive the company. In this situation, the boss is probably more urgent than the customer,
It is also more likely to roar to the programmers. The two problems are actually the same: Who the project team serves. From the project perspective
Look, serving customers; from the perspective of company operations, serving the strategic direction. I think for most teams in China
Urgent.

Finally, it is about the positioning of this book.

The book "The greatest truths to simplicity" was originally positioned as not a ready-to-use book. It talks about methods, but no method can be used directly.
It is used in practice. It talks about tools, but does not teach readers to keep pace. The methods and tools I have mentioned in my book are all critical.
To discuss their value. Basically, there are two points of view:
-Methods can be created and recreated, rather than used to die;
-Tools have application restrictions and application theories. Do not be superstitious about the power of tools.

This book discusses the relationship between methods, the nature of tools, engineering, teams, and roles. But none of them are centered around
A practical environment. Therefore, Mr. Zou hopes that this book will be able to explain the benefits, usefulness, or usage of a specific thing (for example
Model), which is not described in this book. In such a book that only talks about ideas, any real thing will be misleading.

In this book, I reviewed what I have seen, thought, and thought about, and organized these things clearly in the ehm diagram.
The value of this diagram is to clarify the engineering roles, role relationships, and their respective concerns.