华东交大年夜软件系统结构功课.docVIP

Question # 1: Explain the concept of cohesion and coupling in software architecture and design. Please explain it with examples and diagrams. Cohesion coupling Concept Cohesion from a functional point of view to measure the contact module, which describes the function within the module links. The coupling is between the various modules of the software structure of mutually connected a measure, the coupling strength depends on the complexity of the interface between modules, into, or to access a module point and the data through the interface. Classification (1) accidental cohesion. (2) logical cohesion.(3) within the poly (4) within a process polyethylene (5) communication poly (6) in order within the poly (7) Function cohesive (1) content coupled (2) common coupling (3) The external coupling (4) Control Coupling (5) marker coupling (6) Data coupling (7) A non-direct coupling Question # 2: Which architecture style is best suited for distributed software system? Explain it with examples and diagrams Contrast mainstream B / S and C / S system, that the B / S is more suitable for distributed systems B/S C/S Data security B / S structure of the software because of its data is stored centrally at the headquarters of the database server, the client does not save any business data and database connection information, without the need for any data synchronization, so these security problems will not exist naturally C / S structure software must be installed in various multiple servers, and data synchronization between multiple servers, each data point, the data security affects the entire application data security, in terms of the large-scale application of the Group class C / S structure softwares security is unacceptable. B/S C/S Data consistency The data is stored centrally, the client every business documents directly into the central database, there is no data consistency problems Server must be synchronized daily after the headquarters before you can get the final da