QA Meimei 15:16 Set up and detailed, what is the template to cover what is more appropriate, more effective? At present, I have access to the generalization, some of which mainly covers the integration of modules, but now it is not in the module data flow as a template, but the interaction between classes and classes, and detailed set is to describe the class
Zhang Keqiang 22:20 is set out in the previous sub-law, as well as highleveldesign and lowleveldesign. To go up, is now the architecture design, then this is set to components or modules.
The generalization may also go down, then to the key class, the key method. But this is already a minority. Set in the agile is abandoned, and now even if you do not engage in agile, also generally not used for detailed set. With the document generation tool, the reverse code is available.
QA Meimei 18:27 [Strong] [strong] [embrace] [embrace] learned
The Zhang Keqiang 18:28 interface is the most critical part of today's design
QA Meimei 18:29 But the interface seems difficult to unify
Zhang Keqiang 18:29 grab the interface and pull the keywords. Whether unified or not unified, can be, but to be clear, not the developer casually defined.
QA Meimei 18:30 What's the call clear?
Zhang Keqiang 18:30 If you have an architect, you should validate each interface, the description of the interface and all should have
QA Meimei 18:31 For example, the company template, sometimes the interface and detailed set, the definition of all classes, but the feeling is not clear, and can not say what is less
Zhang Keqiang 18:31 interface definition file is not a project-level file, is the project to the parent file, project-level template to manage interfaces, is not enough grid
QA Meimei 18:33 is it necessary to have an interface description on an integrated level and a definition of the interface itself? Include data flow, properties, input and output?
Zhang Keqiang 18:34 yes. Another key is to split the component, the interface is long on the component, the connection outside the component is the interface that is worth paying attention to
QA Meimei 18:37 that component should be described clearly?
Zhang Keqiang 18:37 yes, cut the interior too complex, cut small, too many interfaces, tired. So the architect is valuable.
QA Meimei 18:38 [Strong] [Strong]
Zhang Keqiang 18:39 well-cut architect can save 3/4 of the workload for the development team, in fact, the big reason is very simple, easy to do.
As SQA may not be able to do the architecture, but if the development team on the components and interfaces, the same can be criticized
QA Meimei 18:41 This is too professional to be seen by experts like you.
Zhang Keqiang 18:42 can look at the component diagram, the interface is called AH
Zhang Keqiang 18:43 has a simple rule, in addition to the interface description of the document, if more than 20 pages, that in today's conditions are mostly problematic
Zhang Keqiang 18:43 interface instructions should also be written without word
Zhang Keqiang 18:44 If the long word, there must be a problem/::D
QA Meimei 18:45 [bared teeth] development general love to write a lot of detail, but also used to write code to write details, and the interface is always a few words to describe the title of the past
Zhang Keqiang 18:46 first code, and then detailed set, in order to deal with it, the cancellation of detailed requirements can be, detailed set is the 80 's the thing, the year of programming with Fortran,c,cobel or something
Zhang Keqiang 18:45 I personally do not like the analysis of data flow, in Oo, the data flow is not important, can always be done, this is the early C left the east
Zhang Keqiang 18:52 OOP is revolutionary and oose is terrific
Recent development trends in software design dialogue
