Model-engineering implementation and expansion Bridge Model Bridge-"self-testing reference answer

1. For the relationship between the main line and the sub-branch of the dependency in the project, design a configuration file structure suitable for the dependency according to the introduction in this chapter.

 

 

Hypothesis:

1) to implement the flexibility of the framework, it is assumed that all abstract types must be defined in the configuration file.

2) assume that all dependencies are abstract orthogonal dependencies.

 

2. An online B2B + B2C project is divided into three layers: UI Layer, service layer, and resource layer. The functions and influencing factors of each layer are as follows:

A. UI Layer: Information Result Presentation and user interaction. The influencing factors include front-end processing logic and interface artist

B. service layer: Process business logic. Influencing factors include business control logic, constraints and rules of business entities and entities, and B2B integrated interfaces.

C. Resource layer: including third-party middleware Products Used for database and B2B Integration

 

Assume that the dependency between the above layers of development content is orthogonal (for example, there is no service layer processing interface element, html content, or the UI Layer directly calls the resource layer to obtain data and packets ), use Case to design the relevant job division based on the description, and draw the dependencies between different positions based on the bridge model.

1. Key Points of dependency analysis:

1) IA, IB, IC, ID level orthogonal relationship

2) IE is the subordinate abstract relationship of IA.

3) IF and IG are sub-Abstract relations of IC, and the relationship between IC and IG is 1: N, and II and IH are sub-Abstract relations of IG.

 

Therefore, the structure of the configuration file is roughly as follows:

<? Xml version = "1.0" encoding = "UTF-8"?>
<Configuration>
<ConfigSections>
<SectionGroup name = "exercise" type = "">
<Section name = "a" type = ""/>
<Section name = "B" type = ""/>
<Section name = "c" type = ""/>
<Section name = "d" type = ""/>
</SectionGroup>
</ConfigSections>

<Exercise>
<A>
<E/>
</A>
<B/>
<C>
<D>
<Add name = "d1" type = "">
<I/>
<H/>
</Add>
<Add name = "d2" type = "">
<I/>
<H/>
</Add>
</D>
</C>
<D/>
</Exercise>

</Configuration>
 

 

2,

The case relationships of team responsibilities are roughly as follows:

 

The dependency relationship after the division of responsibilities of each position is roughly as follows: