Time：09-20
CodePudding user response:
domain driven understand each different ERP currently used should not
advanced technology domain driven? Baidu, also do not understand, I also write in ERP, is completely don't understand "domain-driven" ah
Quote: refer to the third floor leo2003 response: Advanced technology domain driven? Baidu, also do not understand, I also write in ERP, is completely don't understand "domain-driven" ah Something is software, technology is the lowest (some people put the cart before the horse is full "technology", and finally be silly), if you ask the business, so is not comparable with technology, Is the resource plan (ERP) system, the domestic financial software, OA software, software and so on industry, human resources are later to ERP in the name of the head, In simple terms, ERP is the core of planning theory, systems engineering, and in a wide variety of application of the management science, using the value chain upstream and downstream of each link, of course, some people who only know "to add and delete" also to develop the design of ERP (as long as get a government, army, enterprise of small head), and there are many open source ERP system can be used to fry, so this thing is actually very "complex", Some software analysis of genre again, I don't want to say more, I suggest you look at its effect, it produces the actual design blueprint, don't look at itself iffy primer,
Advanced technology domain driven? Baidu, also do not understand, I also write in ERP, is completely don't understand "domain-driven" ah
, the strength, don't make what domain driven, I said the strength is not only the strength of the architect, you but the whole team's strength, Architects don't have the strength, the design will be out of shape, and deformation after the design is very terrible, the black hole is a resources, a large number of consuming resources and efficiency, If architects have the strength, but programmers don't have the strength to understanding domain driven in place and implement (I believe can have a deep understanding domain driven programmer's proportion is very low), the development will be deformation, the result, in the field of drive, it is a disaster, My conclusion is: Most of the research and development team, unable to realize domain driven, or re-doing the line, you can do to make Domain driven, when it intelligence toys, play, is ok, but don't take it seriously,
Quote: refer to the sixth floor daixf_csdn response: Don't make what domain driven, the strength, strength is not just what I say you are the architect's strength, but the whole team's strength, Architects don't have the strength, the design will be out of shape, and deformation after the design is very terrible, the black hole is a resources, a large number of consuming resources and efficiency, If architects have the strength, but programmers don't have the strength to understanding domain driven in place and implement (I believe can have a deep understanding domain driven programmer's proportion is very low), the development will be deformation, the result, in the field of drive, it is a disaster, My conclusion is: Most of the research and development team, unable to realize domain driven, or re-doing the line, you can do to make Domain driven, when it intelligence toys, play, is ok, but don't take it seriously, Has been using in our company, but it is too complex, the concept of people basically outside come in without a few months training can help to do it, but if you understand it's very simple
Don't make what domain driven, the strength, strength is not just what I say you are the architect's strength, but the whole team's strength, Architects don't have the strength, the design will be out of shape, and deformation after the design is very terrible, the black hole is a resources, a large number of consuming resources and efficiency, If architects have the strength, but programmers don't have the strength to understanding domain driven in place and implement (I believe can have a deep understanding domain driven programmer's proportion is very low), the development will be deformation, the result, in the field of drive, it is a disaster, My conclusion is: Most of the research and development team, unable to realize domain driven, or re-doing the line, you can do to make Domain driven, when it intelligence toys, play, is ok, but don't take it seriously,
Quote: refer to the eighth floor m0_37190407 response: Quote: refer to the sixth floor daixf_csdn response: Don't make what domain driven, the strength, strength is not just what I say you are the architect's strength, but the whole team's strength, Architects don't have the strength, the design will be out of shape, and deformation after the design is very terrible, the black hole is a resources, a large number of consuming resources and efficiency, If architects have the strength, but programmers don't have the strength to understanding domain driven in place and implement (I believe can have a deep understanding domain driven programmer's proportion is very low), the development will be deformation, the result, in the field of drive, it is a disaster, My conclusion is: Most of the research and development team, unable to realize domain driven, or re-doing the line, you can do to make Domain driven, when it intelligence toys, play, is ok, but don't take it seriously, Has been using in our company, but it is too complex, the concept of people basically outside come in without a few months training can help to do it, but if you understand it's very simple Domain driven concept, which is import, as do the head of the ERP in the SAP system, should be applied domain driven, but how to do? I had the opportunity to participate in the secondary development, I don't want to attend the second time, Just tell us about what is your ERP implementation domain driven design concept?
Page link：https//www.codepudding.com/net/16274.html
