軟件體系結(jié)構(gòu)

《軟件體系結(jié)構(gòu)》由會(huì)員分享，可在線閱讀，更多相關(guān)《軟件體系結(jié)構(gòu)（50頁(yè)珍藏版）》請(qǐng)?jiān)谘b配圖網(wǎng)上搜索。

1、軟 件 體 系 結(jié) 構(gòu)體 系 結(jié) 構(gòu) 評(píng) 審Architectural Reviews孫 志 崗 Architectural Reviewsn Architectural reviews are a key step in architecture-based development. They include a method (such as SAAM or ATAM), but the full practice includes more than that.體系結(jié)構(gòu)評(píng)審是開(kāi)發(fā)過(guò)程中的一個(gè)重要環(huán)節(jié)。有專門(mén)的評(píng)審方法(SAAM、ATAM)，但在實(shí)踐中并不僅僅是這些n We will di

2、scuss cost/benefits of architectural reviews different architectural review techniques preconditions for an architectural review architectural review activities outputs from an architectural review Costs of Architectural Reviewsn There are three different types of costs of holding regular architectu

3、ral reviews.direct staff costs直接員工開(kāi)銷organizational overhead組織管理開(kāi)銷indirect staff costs間接員工開(kāi)銷 Examples of Direct Staff Costsn AT each has a different cost and provides different information.有很多種評(píng)審技術(shù)。每種需要不同的開(kāi)銷，提供不同的信息n These techniques fall into one of two categories. questioning techniques: applied to

4、 evaluate any aspect of an architecture for any given reason提問(wèn)技術(shù)：用來(lái)評(píng)價(jià)體系結(jié)構(gòu)的任何方面 measuring techniques: applied to answer questions about a specific quality度量技術(shù)：回答關(guān)于某項(xiàng)質(zhì)量的問(wèn)題 Questioning Techniquesn Scenario-based techniques describes a specific interaction between stakeholders and a system描述角色與系統(tǒng)交互的過(guò)程 e

5、xample: SAAM, ATAM (partially)n Questionnaire-based techniques（基于問(wèn)卷的技術(shù)） Some questions apply to all architectures (especially those in a single domain).有些問(wèn)題被用于所有的體系結(jié)構(gòu)，尤其是在單一領(lǐng)域內(nèi) Some questions ask about details of a specific architecture.有些問(wèn)題詢問(wèn)一個(gè)特定結(jié)構(gòu)的細(xì)節(jié) Some ask about the development process.n “Is th

6、ere a single architect?”n “How do you ensure conformance?”“你們?cè)鯓颖ＷC一致性？” Questioning Techniquesn Questionnaires are reused; they reflect more maturity or experience within a domain.問(wèn)卷可以重用；它們體現(xiàn)了在一個(gè)領(lǐng)域內(nèi)的成熟度和經(jīng)驗(yàn)是否豐富n Scenarios must be developed anew for each system.場(chǎng)景必須為每個(gè)系統(tǒng)重新開(kāi)發(fā) Measuring Techniquesn Metri

7、cs: quantitative interpretations of observable measures量度：可測(cè)質(zhì)量的定量說(shuō)明 complexity metrics identify areas where modifications may be difficult復(fù)雜度的測(cè)量指明在哪個(gè)區(qū)域修改會(huì)很困難 performance metrics suggest areas where bottlenecks may occur性能的測(cè)量提示瓶頸會(huì)在哪里發(fā)生n Reviews tend to focus on results of metrics度量的結(jié)果 assumptions und

8、erlying the interpretation of the metrics (e.g., assumed event distribution)對(duì)度量的解釋中的潛在假定 Measuring Techniquesn Simulations, prototypes, experiments: domain specific models of an architecture or performance model仿真、原型、實(shí)驗(yàn)：建立體系模型或者性能模型are expensive to createoften exist as part of development anywayn Ma

9、y answer issues raised by questioning technique 可以回答提問(wèn)技術(shù)提出的問(wèn)題“What evidence do you have that performance is adequate?”“你憑什么說(shuō)可以達(dá)到這個(gè)性能？” Properties of Review Techniques評(píng)審技術(shù)通用性細(xì)節(jié)等級(jí)階段被評(píng)審對(duì)象提問(wèn)技術(shù)問(wèn)卷通用粗糙早期設(shè)計(jì)和過(guò)程場(chǎng)景特定系統(tǒng)中等中期設(shè)計(jì)度量技術(shù)度量通用或者特定領(lǐng)域好中期設(shè)計(jì)仿真原型 實(shí)驗(yàn)特定領(lǐng)域不定早期設(shè)計(jì) Review Processn An architectural review has three

10、major elements.preconditions: the set of necessary assets and conditions that must be in place before a review can be performed successfully前提：評(píng)審成功進(jìn)行之前，必要的資源和條件必須到位activities of the review itself活動(dòng)：評(píng)審本身 outputs: the report of review results輸出：評(píng)審結(jié)果報(bào)告 Review Preconditionsn Understand the context of th

11、e review理解評(píng)審的上下文n Assemble the right people集合正確的人n Set organizational expectations and support期望和支持n Prepare for review為評(píng)審做準(zhǔn)備n Obtain representation of the architecture獲得體系結(jié)構(gòu)文檔 Preconditions: Contextn Planned review part of normal development activity正常開(kāi)發(fā)活動(dòng)的一部分 non-adversarial（非敵對(duì)性的） scheduled well

12、in advance（事先安排好日程） built into projects schedule and budget包含在項(xiàng)目日程和預(yù)算之內(nèi)n Unplanned usually occurs when project is in trouble通常在項(xiàng)目出現(xiàn)問(wèn)題時(shí)采用 often devolves into finger-pointing導(dǎo)致互相責(zé)備 can be painful for project already struggling對(duì)于已經(jīng)苦苦掙扎了很久的項(xiàng)目而言，有些痛苦 Preconditions: Contextn Timing of the reviewearly “arc

13、hitecture discovery review”n is done after requirements are set, but before the architecture is firm需求分析之后，體系結(jié)構(gòu)還沒(méi)有確定之前進(jìn)行n is used to understand implications of requirements on architecture用來(lái)理解需求在體系結(jié)構(gòu)方面的隱含內(nèi)容 n checks for requirements feasibility（檢查需求的可行性）n prioritizes architectural goals（為質(zhì)量目標(biāo)排序）full

14、 architectural reviewn is done when architectural documentation is available體系結(jié)構(gòu)文檔可用時(shí)進(jìn)行n is used to evaluate qualities of proposed architecture評(píng)價(jià)被評(píng)體系結(jié)構(gòu)的質(zhì)量 Preconditions: Peoplen Representatives of project（項(xiàng)目代表） architect designers of major modules stakeholders representativesn Review team members (i

15、deally, a separate unit)評(píng)審團(tuán)成員(理想情況下是一個(gè)獨(dú)立組織) at least one domain expert included至少有一個(gè)領(lǐng)域?qū)＜?someone to handle logistics (e.g., meeting rooms, supplies)后勤人員(會(huì)議室、茶水、食品) librarian to organize documentation文檔管理員“apprentice reviewer” for growth成長(zhǎng)中的評(píng)審員學(xué)徒 Preconditions: Review Teamn The review team must be as

16、sembled so thatmembers are perceived as impartial, objective, and respected成員要公正、客觀和被尊重members devote their full-time effort to the review成員全心加入評(píng)審members are fluent in architecture and architectural issues成員要訓(xùn)練有素而且口才好 it is located close to artifacts being examined有足夠的權(quán)限檢查被評(píng)審材料 Preconditions: Review

17、 Teamn The team must have access toapplicable domain knowledge (perhaps via consultants to the team)適當(dāng)?shù)念I(lǐng)域知識(shí)design documents設(shè)計(jì)文檔review criteria評(píng)審標(biāo)準(zhǔn)support staff支持人員 Preconditions: OrganizationalExpectationsn A contract between the review team and the sponsor of the review must be established.Who will

18、 be told what upon completion?結(jié)束后，哪些內(nèi)容可以被告訴哪些人What will (not) be the review criteria?什么是(不是)評(píng)審標(biāo)準(zhǔn)？What/who will be made available to team?哪些人和物是評(píng)審團(tuán)可以使用的？What follow-up is expected?希望評(píng)審的結(jié)果如何？ How long will the review take?要評(píng)審多久？ Preconditions: OrganizationalExpectationsn Organizational culture and sup

19、port must be considered. Are reviews part of the standard project life cycle?評(píng)審是項(xiàng)目的基本生命周期的一部分嗎？ Is serving on a review team considered good for ones career?為評(píng)審團(tuán)服務(wù)是份好差事嗎？ Will the organization allow its superior designers time off from their projects to serve on review teams?企業(yè)允許它的高級(jí)設(shè)計(jì)師把他的項(xiàng)目放在一邊來(lái)參加評(píng)審

20、嗎？ Is there a standing review organization (even though members may rotate on and off)?有常設(shè)的評(píng)審組織嗎(即便成員常進(jìn)進(jìn)出出)？ Preconditions: Read-Ahead Materialn For project being reviewed questionnaires scenarios (These are created as part of the review, but time should be allowed for project members to digest the

21、information.)n For review team description of architecture rationale for architecturen Ideally, material will address the review questions. (Passing this test because the questions were known in advance is not cheating, but good engineering!)理想情況，材料要能說(shuō)明評(píng)審時(shí)的問(wèn)題 Preconditions: Ranked Qualityand Behavio

22、ral Requirementsn Plan to examine three to five quality and behavioral requirements.計(jì)劃?rùn)z查3到5個(gè)質(zhì)量和行為需求n A particular representation medium (language) for the architecture is not necessary. As long as the information can be extracted (using project members as necessary), the form of the representation i

23、s not important.一個(gè)專門(mén)的體系結(jié)構(gòu)表述媒體(語(yǔ)言)目前并不是必須的。由項(xiàng)目成員來(lái)講解信息，表述的形式并不重要 Review Activitiesn Evaluate“Run” the scenarios and ask the questions, or answer the items in the checklist.按場(chǎng)景執(zhí)行，并詢問(wèn)相關(guān)問(wèn)題；或者回答問(wèn)卷里的問(wèn)題Perform the experiments.（演示實(shí)驗(yàn)）Execute the prototypes or simulations.運(yùn)行原型或仿真程序n Recordcritical issues highl

24、ighted in the review評(píng)審中發(fā)現(xiàn)的嚴(yán)重問(wèn)題 comments of project members on these issues項(xiàng)目成員對(duì)這些問(wèn)題的說(shuō)明 Review Activitiesn Rank the issuesproject-threatening（生死攸關(guān)）majorminorn Each issue raised should be addressed in terms ofchanging the architecturerelaxing the requirements Review Activitiesn Warning signsarchitectu

25、re forced to match organization組織模式影響體系結(jié)構(gòu)top-level components number over 25頂層組件數(shù)超過(guò)25個(gè)one requirement drives entire design一項(xiàng)需求決定整個(gè)設(shè)計(jì)architecture depends on alternatives in the operating system體系受操作系統(tǒng)選擇的影響 Review Activitiesn Warning signschoice of software components is dictated by hardware personnel

26、由硬件人員選擇軟件組件redundancy not needed for reliability面對(duì)可靠性時(shí)，不考慮冗余手段design is exception driven零散的小的事件影響設(shè)計(jì)no identifiable architect沒(méi)有確定的架構(gòu)師 Output from Reviewn Set of ranked issues supporting data contained in formal report feedback to projectn Enhanced system documentation增強(qiáng)的系統(tǒng)文檔n Set of scenarios for fut

27、ure use將來(lái)會(huì)用到的場(chǎng)景集n Identification of potentially reusable components認(rèn)定潛在的可重用組件 n Estimation of costs and benefits估算成本和收益 SAAM: Software Architecture Analysis Method 一種簡(jiǎn)單的基于場(chǎng)景的評(píng)審技術(shù) Qualities Are Too Vague for Analysisn Is the following system modifiable?這個(gè)系統(tǒng)具有適應(yīng)性嗎？ Background color of the user interfa

28、ce is changed merely by modifying a resource file.通過(guò)修改資源文件，可以改變界面的背景色 Dozens of components must be changed to accommodate a new data file format.必須修改許多組件才能適應(yīng)新的文件格式n A reasonable answer is一個(gè)合理的答案：yes with respect to changing background color有，從改變背景色的角度來(lái)看no with respect to changing file format沒(méi)有，從改變文件

29、格式的角度來(lái)看 Qualities Are Too Vague for Analysisn Qualities only have meaning within a context.質(zhì)量因素只在一定的上下文里才有意義n SAAM specifies context through scenarios.SAAM通過(guò)場(chǎng)景指定上下文 Scenariosn A scenario is a brief description of a stakeholders interaction with a system.場(chǎng)景就是一個(gè)角色與系統(tǒng)交互過(guò)程的簡(jiǎn)單描述n When creating scenarios,

30、 it is important to consider all stakeholders.建立場(chǎng)景的時(shí)候，一定要考慮到所有的角色Customer、User、Developer、Maintainer、Attackern The scenarios that are of most interest in a SAAM evaluation are change scenarios.SAAM最關(guān)心的是變化場(chǎng)景 Steps of a SAAM Evaluationn Identify and assemble stakeholders確認(rèn)和召集角色n Develop and prioritize

31、scenarios制定場(chǎng)景，并排好優(yōu)先級(jí)n Describe candidate architecture(s)描述候選的體系結(jié)構(gòu)n Classify scenarios as direct or indirect把場(chǎng)景分類為直接場(chǎng)景和間接場(chǎng)景n Perform scenario evaluation進(jìn)行場(chǎng)景評(píng)估 n Reveal scenario interactions展現(xiàn)場(chǎng)景間的相互影響n Generate overall evaluation整體評(píng)估 Step 1: Identify and Assemble StakeholdersStakeholder InterestCustom

32、er Schedule and budget; usefulness of system; meeting customers (or markets) expectationsEnd User Functionality, usabilityDeveloper Clarity and completeness ofarchitecture; high cohesion andlimited coupling of parts;clear interaction mechanisms Maintainer Maintainability; ability to locateplaces of

33、change Step 1: Identify and Assemble StakeholdersStakeholder InterestSystem Administrator Ease in finding sources of operational problemsNetwork Administrator Network performance, predictabilityIntergrator Clarity and completeness ofarchitecture; high cohesion andlimited coupling of parts;clear inte

34、raction mechanisms Step 1: Identify and AssembleStakeholdersStakeholder InterestTester Integrated, consistent error handling; limited component coupling; high component cohesion; conceptual integrityApplication Builder Architectural clarity, completeness; interaction mechanisms; simple tailoring mec

35、hanismsRepresentative of the domain Interoperability Step 2: Stakeholders Develop andPrioritize Scenariosn Scenarios should be typical of the kinds of evolution that the system must support:場(chǎng)景應(yīng)該是系統(tǒng)必須支持的各種演化的典型：functionalitydevelopment activitieschange activitiesn Scenarios should represent tasks rel

36、evant to all stakeholders.所有角色都應(yīng)該能在場(chǎng)景中體現(xiàn)出來(lái)n Rule of thumb: 10-15 prioritized scenarios應(yīng)該有10-15個(gè)優(yōu)先的場(chǎng)景 Step 3: Describe CandidateArchitecturesn It is frequently necessary to elicit appropriate architectural descriptions.通常，對(duì)體系結(jié)構(gòu)進(jìn)行適當(dāng)?shù)拿枋鍪欠浅Ｖ匾膎 Structures chosen to describe the architecture will depend

37、on the type of qualities to be evaluated.以我們需要的質(zhì)量為依據(jù)，選擇用來(lái)描述體系結(jié)構(gòu)的結(jié)構(gòu) Step 4: Classify Scenariosn There are two classes of scenarios. Direct scenarios are those that can be executed by the system without modification.直接場(chǎng)景是那些不需要修改系統(tǒng)就能執(zhí)行的場(chǎng)景 Indirect scenarios are those that require modifications to the s

38、ystem.間接場(chǎng)景是那些需要修改系統(tǒng)的場(chǎng)景n The classification depends upon both the scenario and the architecture.場(chǎng)景的類型因系統(tǒng)而異n For indirect scenarios we gauge the order of difficulty of each change: e.g. a person-day, person-week, person-month, person-year.對(duì)間接場(chǎng)景，我們要度量適應(yīng)每個(gè)變化的難度（工作量） Step 5: Perform Scenario Evaluationn

39、For each indirect scenario identify the components, data connections, control connections, and interfaces that must be added, deleted, or modified明確其組件、數(shù)據(jù)連結(jié)件、控制連結(jié)件和要被增加、刪除或修改的接口 estimate the difficulty of modification估算修改的難度n Difficulty of modification is elicited from the architect and is based on

40、the number of components to be modified and the effect of the modifications.修改的難度體現(xiàn)在被修改的組件個(gè)數(shù)和修改的效果 n A monolithic system will score well on this step, but not on next step.只有一個(gè)模塊的系統(tǒng)在此項(xiàng)評(píng)估可以得到高分，但是 Step 6: Reveal Scenario Interactionsn When multiple indirect scenarios affect the same components, this

41、could indicate a problem.當(dāng)多個(gè)間接場(chǎng)景影響同一個(gè)組件時(shí)，可能引發(fā)問(wèn)題 could be good, if scenarios are variants of each other可能是好事，當(dāng)場(chǎng)景是彼此的變體n change background color to green n change background color to red could be bad, indicating a potentially poor separation of concerns可能是壞事，說(shuō)明模塊劃分有問(wèn)題n change background color to redn

42、port system to a different platform Step 7: Generate Overall Evaluationn Not all scenarios are equal.場(chǎng)景生來(lái)不平等n The organization must determine which scenarios are most important.必須明確哪些場(chǎng)景是最重要的n Then the organization must decide as to whether the design is acceptable “as is” or if it must be modified.評(píng)

43、審團(tuán)得出結(jié)論，當(dāng)前的體系結(jié)構(gòu)設(shè)計(jì)可行，還是必須要修改 QeNbJ8G5D1A-w*t$qYnVkSgPdLaI7F3C0z)v&s#pXmUiRfOcK9H6E2B+x(u%rZoWlThQeMbJ8G4D1A-w*t!qYnVjSgPdLaI6F3C0y)v&s#pXlUiRfNcK9H5E2A+x(u$rZoWkThPeMbJ7G4D1z-w&t!qYmVjSgOdLaI6F3B0y)v%s#pXlUiQfNcK8H5E2A+x*u$rZnWkThPeMaJ7G4C1z-w&t!pYmVjRgOdL9I6E3B0y(v%s#oXlTiQfNbK8H5D2A+x*u$qZnWkShPeMaJ

44、7F4C1z)w&t!pYmUjRgOcL9I6E3B+y(v%r#oXlTiQeNbK8G5D2A-x*t$qZnVkShPdMaI7F4C0z)w&s!pXmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbJ8G5D1A-x*t$qYnVkSgPdMaI7F3C0z)v&s!pXmUiRfOcK9H6E2B+x(u%rZoWlThQeMbJ8G4D1A-w*t$qYnVjSgPdLaI7F3C0y)v&s#pXmUiRfNcK9H5E2B+x(u$rZoWkThQeMbJ7G4D1z-w*t!qYmVjSgOdLaI6F3B0y)v%s#pXlUiRfNcK8H5E2A+x(u$

45、rZnWkThPeMbJ7G4C1z-w&t!qYmVjRgOdL9I6F3B0y(v%s#oXlUiQfNbK8H5D2A+x*u$qZnWkShPeMaJ7F4C1z)w&t!pYmVjRgOcL9I6E3B0y(v%r#oXlTiQfNbK8G5D2A-x*u$qZnVkShPdMaJ7F4C0z)w&s!pYmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbK8G5D1A-x*t$qZnVkSgPdMaI7F4C0z)v&s!pXmUjRfOcK9H6E2B+y(u%rZoWlThQeNbJ8G4D1A-w*t$qYnVjSgPdLaI7F3C0y)v&s#pXmUiRfOc

46、K9H5E2B+x(u%rZoWkThQeMbJ8G4D1z-w*t!qYnVjSgOdLaI6F3C0y)v%s#pXlUiRfNcK8H5E2A+x(u$rZnWkThPeMbJ7G4D1z-w&t!qYmVjSgOdL9I6F3B0y)v%s#oXlUiQfNcK8H5D2A+x*u$rZnWkShPeMaJ7G4C1z)w&t!pYmVjRgOcL9I6E3B0y(v%s#oXlTeMbJ7G4D1z-w&t!qYmVjSgOdL9I6F3B0y)v%s#oXlUiQfNcK8H5D2A+x*u$rZnWkShPeMaJ7G4C1z)w&t!pYmVjRgOdL9I6E3B0y(v%s

47、#oXlTiQfNbK8H5D2A-x*u$qZnWkShPdMaJ7F4C1z)w&s!pYmUjRgOcL9H6E3B+y(v%r#oWlTiQeNbK8G5D2A-x*t$qZnVkShPdMaI7F4C0z)w&s!pXmUjRfOcL9H6E2B+y(u%r#oWlThQeNbJ8G5D1A-w*t$qYnVkSgPdLaI7F3C0z)v&s#pXmUiRfOcK9H6E2B+x(u%rZoWlThQeMbJ8G4D1A-w*t!qYnVjSgPdLaI6F3C0y)v&s#pXlUiRfNcK9H5E2A+x(u$rZoWkThPeMbJ7G4D1z-w*t!qYmVjSgOdL

48、aI6F3B0y)v%s#pXlUiQfNcK8H5E2A+x*u$rZnWkThPeMaJ7G4C1z-w&t!pYmVjRgOdL9I6E3B0y(v%s#oXlUiQfNbK8H5D2A+x*u$qZnWkShPeMaJ7F4C1z)w&t!pYmUjRgOcL9I6E3B+y(v%r#oXlTiQeNbK8G5D2A-x*t$qZnVkShPdMaI7F4C0z)w&s!pYmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbJ8G5D1A-x*t$qYnVkSgPdMaI7F3C0z)v&s!pXmUiRfOcK9H6E2B+x(u%rZoWlThQeNbJ8G4D1A-w*

49、t$qYnVjSgPdLaI7F3C0y)v&s#pXmUiRfNcK9H5E2B+x(u$rZoWkThQeMbJ7G4D1z-w*t!qYmVjSgOdLaI6F3C0y)v%s#pXlUiRfNcK8H5E2A+x(u$rZnWkThPeMbJ7G4C1z-w&t!qYmVjRgOdL9I6F3B0y(v%s#oXlUiQfNbK8H5D2A+x*u$qZnWOdLaI6F3C0y)v%s#pXlUiRfNcK8H5E2A+x(u$rZnWkThPeMbJ7G4C1z-w&t!qYmVjRgOdL9I6F3B0y(v%s#oXlUiQfNcK8H5D2A+x*u$rZnWkShPeMaJ

50、7G4C1z)w&t!pYmVjRgOcL9I6E3B0y(v%r#oXlTiQfNbK8G5D2A-x*u$qZnVkShPdMaJ7F4C0z)w&s!pYmUjRgOcL9H6E3B+y(v%r#oWlTiQeNbK8G5D1A-x*t$qZnVkSgPdMaI7F4C0z)v&s!pXmUjRfOcK9H6E2B+y(u%rZoWlThQeNbJ8G5D1A-w*t$qYnVkSgPdLaI7F3C0z)v&s#pXmUiRfOcK9H5E2B+x(u%rZoWkThQeMbJ8G4D1z-w*t!qYnVjSgOdLaI6F3C0y)v%s#pXlUiRfNcK9H5E2A+x(u$

51、rZoWkThPeMbJ7G4D1z-w&t!qYmVjSgOdL9I6F3B0y)v%s#oXlUiQfNcK8H5D2A+x*u$rZnWkShPeMaJ7G4C1z-w&t!pYmVjRgOdL9I6E3B0y(v%s#oXlTiQfNbK8H5D2A-x*u$qZnWkShP9I6F3B0y)v%s#oXlUiQfNcK8H5E2A+x*u$rZnWkThPeMaJ7G4C1z-w&t!pYmVjRgOdL9I6E3B0y(v%s#oXlTiQfNbK8H5D2A-x*u$qZnWkShPdMaJ7F4C1z)w&s!pYmUjRgOcL9I6E3B+y(v%r#oXlTiQeNbK8

52、G5D2A-x*t$qZnVkShPdMaI7F4C0z)w&s!pXmUjRfOcL9H6E2B+y(u%r#oWlThQeNbJ8G5D1A-x*t$qYnVkSgPdMaI7F3C0z)v&s!pXmUiRfOcK9H6E2B+x(u%rZoWlThQeMbJ8G4D1A-w*t!qYnVjSgPdLaI6F3C0y)v&s#pXlUiRfNcK9H5E2B+x(u$rZoWkThQeMbJ7G4D1z-w*t!qYmVjSgOdLaI6F3B0y)v%s#pXlUiQfNcK8H5E2A+x*u$rZnWkThPeMaJ7G4C1z-w&t!qYmVjRgOdL9I6F3B0y(v%s

53、#oXlUiQfNbK8H5D2A+x*u$qZnWkShPeMaJ7F4C1z)w&t!pYmUjRgOcL9I6E3B+y(v%r#oXlTiQfNbK8G5D2A-x*u$qZnVkShPdMaJ7F4C0z)w&s!pYmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbJ8G5D1A-x!pYmUjRgOcL9I6E3B0y(v%r#oXlTiQfNbK8G5D2A-x*u$qZnVkShPdMaJ7F4C0z)w&s!pYmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbJ8G5D1A-x*t$qZnVkSgPdMaI7F4C0z)v&s!pXmUjRfOcK9H

54、6E2B+y(u%rZoWlThQeNbJ8G4D1A-w*t$qYnVjSgPdLaI7F3C0y)v&s#pXmUiRfNcK9H5E2B+x(u%rZoWkThQeMbJ8G4D1z-w*t!qYnVjSgOdLaI6F3C0y)v%s#pXlUiRfNcK8H5E2A+x(u$rZnWkThPeMbJ7G4C1z-w&t!qYmVjSgOdL9I6F3B0y)v%s#oXlUiQfNcK8H5D2A+x*u$rZnWkShPeMaJ7G4C1z)w&t!pYmVjRgOcL9I6E3B0y(v%r#oXlTiQfNbK8H5D2A-x*u$qZnWkShPdMaJ7F4C1z)w&s!

55、pYmUjRgOcL9H6E3B+y(v%r#oWlTiQeNbK8G5D1A-x*t$qZnVkSgPdMaI7F4C0z)v&s!pXmUjRfOcL9H6E2B+y(u%r#oWlThQeNbJ8G5D1A-w*t$qYnVkSgPdLaI7F3C0z)v&s#pXmUibK8G5D1A-x*t$qZnVkShPdMaI7F4C0z)w&s!pXmUjRfOcL9H6E2B+y(u%r#oWlThQeNbJ8G5D1A-w*t$qYnVkSgPdLaI7F3C0z)v&s#pXmUiRfOcK9H5E2B+x(u%rZoWlThQeMbJ8G4D1A-w*t!qYnVjSgPdLaI6F

56、3C0y)v&s#pXlUiRfNcK9H5E2A+x(u$rZoWkThPeMbJ7G4D1z-w&t!qYmVjSgOdLaI6F3B0y)v%s#pXlUiQfNcK8H5E2A+x*u$rZnWkThPeMaJ7G4C1z-w&t!pYmVjRgOdL9I6E3B0y(v%s#oXlTiQfNbK8H5D2A+x*u$qZnWkShPeMaJ7F4C1z)w&t!pYmUjRgOcL9I6E3B+y(v%r#oXlTiQeNbK8G5D2A-x*t$qZnVkShPdMaI7F4C0z)w&s!pXmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbJ8G5D1A-x*t$qY

57、nVgOcL9I6E3B+y(v%r#oXlTiQeNbK8G5D2A-x*t$qZnVkShPdMaJ7F4C0z)w&s!pYmUjRfOcL9H6E3B+y(u%r#oWlTiQeNbJ8G5D1A-x*t$qYnVkSgPdMaI7F3C0z)v&s!pXmUiRfOcK9H6E2B+x(u%rZoWlThQeNbJ8G4D1A-w*t$qYnVjSgPdLaI7F3C0y)v&s#pXmUiRfNcK9H5E2B+x(u$rZoWkThQeMbJ7G4D1z-w*t!qYmVjSgOdLaI6F3C0y)v%s#pXlUiRfNcK8H5E2A+x(u$rZnWkThPeMbJ7G4

58、C1z-w&t!qYmVjRgOdL9I6F3B0y(v%s#oXlUiQfNbK8H5D2A+x*u$rZnWkShPeMaJ7G4C1z)w&t!pYmVjRgOcL9I6E3B0y(v%r#oXlTiQfNbK8G5D2A-x*u$qZngOdL9I6F3B0y(v%s#oXlUiQfNcK8H5D2A+x*u$rZnWkShPeMaJ7G4C1z)w&t!pYmVjRgOcL9I6E3B0y(v%r#oXlTiQfNbK8G5D2A-x*u$qZnVkShPdMaJ7F4C1z)w&s!pYmUjRgOcL9H6E3B+y(v%r#oWlTiQeNbK8G5D1A-x*t$qZnVkSgPdMaI7F4C0z)v&s!pXmUjRfOcK9H6E2B+y(u%rZoWlThQeNbJ8G5D1A-w*t$qYnVkSgPdLaI7F3C0z)v&s#pXmUiRfOcK9H5E2B+x(u%rZoWkThQeMbJ8G4D1z-w*t!qYnVjSgOdLaI6F3C0y)v&s#pXlUiRfNcK9H5E2A+x(u$rZoWkThPeMbJ7G4D1z-w&t!qYmVjSgOdL9I6F3B0y)v%s#oThQeMbJ8