軟件體系結(jié)構(gòu)
《軟件體系結(jié)構(gòu)》由會員分享,可在線閱讀,更多相關(guān)《軟件體系結(jié)構(gòu)(50頁珍藏版)》請在裝配圖網(wǎng)上搜索。
1、軟 件 體 系 結(jié) 構(gòu)體 系 結(jié) 構(gòu) 評 審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)評審是開發(fā)過程中的一個重要環(huán)節(jié)。有專門的評審方法(SAAM、ATAM),但在實踐中并不僅僅是這些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直接員工開銷organizational overhead組織管理開銷indirect staff costs間接員工開銷 Examples of Direct Staff Costsn AT each has a different cost and provides different information.有很多種評審技術(shù)。每種需要不同的開銷,提供不同的信息n These techniques fall into one of two categories. questioning techniques: applied to
4、 evaluate any aspect of an architecture for any given reason提問技術(shù):用來評價體系結(jié)構(gòu)的任何方面 measuring techniques: applied to answer questions about a specific quality度量技術(shù):回答關(guān)于某項質(zhì)量的問題 Questioning Techniquesn Scenario-based techniques describes a specific interaction between stakeholders and a system描述角色與系統(tǒng)交互的過程 e
5、xample: SAAM, ATAM (partially)n Questionnaire-based techniques(基于問卷的技術(shù)) Some questions apply to all architectures (especially those in a single domain).有些問題被用于所有的體系結(jié)構(gòu),尤其是在單一領(lǐng)域內(nèi) Some questions ask about details of a specific architecture.有些問題詢問一個特定結(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?”“你們怎樣保證一致性?” Questioning Techniquesn Questionnaires are reused; they reflect more maturity or experience within a domain.問卷可以重用;它們體現(xiàn)了在一個領(lǐng)域內(nèi)的成熟度和經(jīng)驗是否豐富n Scenarios must be developed anew for each system.場景必須為每個系統(tǒng)重新開發(fā) Measuring Techniquesn Metri
7、cs: quantitative interpretations of observable measures量度:可測質(zhì)量的定量說明 complexity metrics identify areas where modifications may be difficult復(fù)雜度的測量指明在哪個區(qū)域修改會很困難 performance metrics suggest areas where bottlenecks may occur性能的測量提示瓶頸會在哪里發(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)對度量的解釋中的潛在假定 Measuring Techniquesn Simulations, prototypes, experiments: domain specific models of an architecture or performance model仿真、原型、實驗:建立體系模型或者性能模型are expensive to createoften exist as part of development anywayn Ma
9、y answer issues raised by questioning technique 可以回答提問技術(shù)提出的問題“What evidence do you have that performance is adequate?”“你憑什么說可以達(dá)到這個性能?” Properties of Review Techniques評審技術(shù)通用性細(xì)節(jié)等級階段被評審對象提問技術(shù)問卷通用粗糙早期設(shè)計和過程場景特定系統(tǒng)中等中期設(shè)計度量技術(shù)度量通用或者特定領(lǐng)域好中期設(shè)計仿真原型 實驗特定領(lǐng)域不定早期設(shè)計 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前提:評審成功進(jìn)行之前,必要的資源和條件必須到位activities of the review itself活動:評審本身 outputs: the report of review results輸出:評審結(jié)果報告 Review Preconditionsn Understand the context of th
11、e review理解評審的上下文n Assemble the right people集合正確的人n Set organizational expectations and support期望和支持n Prepare for review為評審做準(zhǔn)備n Obtain representation of the architecture獲得體系結(jié)構(gòu)文檔 Preconditions: Contextn Planned review part of normal development activity正常開發(fā)活動的一部分 non-adversarial(非敵對性的) scheduled well
12、in advance(事先安排好日程) built into projects schedule and budget包含在項目日程和預(yù)算之內(nèi)n Unplanned usually occurs when project is in trouble通常在項目出現(xiàn)問題時采用 often devolves into finger-pointing導(dǎo)致互相責(zé)備 can be painful for project already struggling對于已經(jī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)還沒有確定之前進(jìn)行n is used to understand implications of requirements on architecture用來理解需求在體系結(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)文檔可用時進(jìn)行n is used to evaluate qualities of proposed architecture評價被評體系結(jié)構(gòu)的質(zhì)量 Preconditions: Peoplen Representatives of project(項目代表) architect designers of major modules stakeholders representativesn Review team members (i
15、deally, a separate unit)評審團(tuán)成員(理想情況下是一個獨立組織) at least one domain expert included至少有一個領(lǐng)域?qū)<?someone to handle logistics (e.g., meeting rooms, supplies)后勤人員(會議室、茶水、食品) librarian to organize documentation文檔管理員“apprentice reviewer” for growth成長中的評審員學(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成員全心加入評審members are fluent in architecture and architectural issues成員要訓(xùn)練有素而且口才好 it is located close to artifacts being examined有足夠的權(quán)限檢查被評審材料 Preconditions: Review
17、 Teamn The team must have access toapplicable domain knowledge (perhaps via consultants to the team)適當(dāng)?shù)念I(lǐng)域知識design documents設(shè)計文檔review criteria評審標(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?什么是(不是)評審標(biāo)準(zhǔn)?What/who will be made available to team?哪些人和物是評審團(tuán)可以使用的?What follow-up is expected?希望評審的結(jié)果如何? How long will the review take?要評審多久? Preconditions: OrganizationalExpectationsn Organizational culture and sup
19、port must be considered. Are reviews part of the standard project life cycle?評審是項目的基本生命周期的一部分嗎? Is serving on a review team considered good for ones career?為評審團(tuán)服務(wù)是份好差事嗎? Will the organization allow its superior designers time off from their projects to serve on review teams?企業(yè)允許它的高級設(shè)計師把他的項目放在一邊來參加評審
20、嗎? Is there a standing review organization (even though members may rotate on and off)?有常設(shè)的評審組織嗎(即便成員常進(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!)理想情況,材料要能說明評審時的問題 Preconditions: Ranked Qualityand Behavio
22、ral Requirementsn Plan to examine three to five quality and behavioral requirements.計劃檢查3到5個質(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.一個專門的體系結(jié)構(gòu)表述媒體(語言)目前并不是必須的。由項目成員來講解信息,表述的形式并不重要 Review Activitiesn Evaluate“Run” the scenarios and ask the questions, or answer the items in the checklist.按場景執(zhí)行,并詢問相關(guān)問題;或者回答問卷里的問題Perform the experiments.(演示實驗)Execute the prototypes or simulations.運行原型或仿真程序n Recordcritical issues highl
24、ighted in the review評審中發(fā)現(xiàn)的嚴(yán)重問題 comments of project members on these issues項目成員對這些問題的說明 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ù)超過25個one requirement drives entire design一項需求決定整個設(shè)計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面對可靠性時,不考慮冗余手段design is exception driven零散的小的事件影響設(shè)計no identifiable architect沒有確定的架構(gòu)師 Output from Reviewn Set of ranked issues supporting data contained in formal report feedback to projectn Enhanced system documentation增強的系統(tǒng)文檔n Set of scenarios for fut
27、ure use將來會用到的場景集n Identification of potentially reusable components認(rèn)定潛在的可重用組件 n Estimation of costs and benefits估算成本和收益 SAAM: Software Architecture Analysis Method 一種簡單的基于場景的評審技術(shù) Qualities Are Too Vague for Analysisn Is the following system modifiable?這個系統(tǒng)具有適應(yīng)性嗎? Background color of the user interfa
28、ce is changed merely by modifying a resource file.通過修改資源文件,可以改變界面的背景色 Dozens of components must be changed to accommodate a new data file format.必須修改許多組件才能適應(yīng)新的文件格式n A reasonable answer is一個合理的答案:yes with respect to changing background color有,從改變背景色的角度來看no with respect to changing file format沒有,從改變文件
29、格式的角度來看 Qualities Are Too Vague for Analysisn Qualities only have meaning within a context.質(zhì)量因素只在一定的上下文里才有意義n SAAM specifies context through scenarios.SAAM通過場景指定上下文 Scenariosn A scenario is a brief description of a stakeholders interaction with a system.場景就是一個角色與系統(tǒng)交互過程的簡單描述n When creating scenarios,
30、 it is important to consider all stakeholders.建立場景的時候,一定要考慮到所有的角色Customer、User、Developer、Maintainer、Attackern The scenarios that are of most interest in a SAAM evaluation are change scenarios.SAAM最關(guān)心的是變化場景 Steps of a SAAM Evaluationn Identify and assemble stakeholders確認(rèn)和召集角色n Develop and prioritize
31、scenarios制定場景,并排好優(yōu)先級n Describe candidate architecture(s)描述候選的體系結(jié)構(gòu)n Classify scenarios as direct or indirect把場景分類為直接場景和間接場景n Perform scenario evaluation進(jìn)行場景評估 n Reveal scenario interactions展現(xiàn)場景間的相互影響n Generate overall evaluation整體評估 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:場景應(yīng)該是系統(tǒng)必須支持的各種演化的典型:functionalitydevelopment activitieschange activitiesn Scenarios should represent tasks rel
36、evant to all stakeholders.所有角色都應(yīng)該能在場景中體現(xiàn)出來n Rule of thumb: 10-15 prioritized scenarios應(yīng)該有10-15個優(yōu)先的場景 Step 3: Describe CandidateArchitecturesn It is frequently necessary to elicit appropriate architectural descriptions.通常,對體系結(jié)構(gòu)進(jìn)行適當(dāng)?shù)拿枋鍪欠浅V匾膎 Structures chosen to describe the architecture will depend
37、on the type of qualities to be evaluated.以我們需要的質(zhì)量為依據(jù),選擇用來描述體系結(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.直接場景是那些不需要修改系統(tǒng)就能執(zhí)行的場景 Indirect scenarios are those that require modifications to the s
38、ystem.間接場景是那些需要修改系統(tǒng)的場景n The classification depends upon both the scenario and the architecture.場景的類型因系統(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.對間接場景,我們要度量適應(yīng)每個變化的難度(工作量) 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)在被修改的組件個數(shù)和修改的效果 n A monolithic system will score well on this step, but not on next step.只有一個模塊的系統(tǒng)在此項評估可以得到高分,但是 Step 6: Reveal Scenario Interactionsn When multiple indirect scenarios affect the same components, this
41、could indicate a problem.當(dāng)多個間接場景影響同一個組件時,可能引發(fā)問題 could be good, if scenarios are variants of each other可能是好事,當(dāng)場景是彼此的變體n change background color to green n change background color to red could be bad, indicating a potentially poor separation of concerns可能是壞事,說明模塊劃分有問題n change background color to redn
42、port system to a different platform Step 7: Generate Overall Evaluationn Not all scenarios are equal.場景生來不平等n The organization must determine which scenarios are most important.必須明確哪些場景是最重要的n Then the organization must decide as to whether the design is acceptable “as is” or if it must be modified.評
43、審團(tuán)得出結(jié)論,當(dāng)前的體系結(jié)構(gòu)設(shè)計可行,還是必須要修改 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
- 溫馨提示:
1: 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
2: 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
3.本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
5. 裝配圖網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 2023年六年級數(shù)學(xué)下冊6整理和復(fù)習(xí)2圖形與幾何第7課時圖形的位置練習(xí)課件新人教版
- 2023年六年級數(shù)學(xué)下冊6整理和復(fù)習(xí)2圖形與幾何第1課時圖形的認(rèn)識與測量1平面圖形的認(rèn)識練習(xí)課件新人教版
- 2023年六年級數(shù)學(xué)下冊6整理和復(fù)習(xí)1數(shù)與代數(shù)第10課時比和比例2作業(yè)課件新人教版
- 2023年六年級數(shù)學(xué)下冊4比例1比例的意義和基本性質(zhì)第3課時解比例練習(xí)課件新人教版
- 2023年六年級數(shù)學(xué)下冊3圓柱與圓錐1圓柱第7課時圓柱的體積3作業(yè)課件新人教版
- 2023年六年級數(shù)學(xué)下冊3圓柱與圓錐1圓柱第1節(jié)圓柱的認(rèn)識作業(yè)課件新人教版
- 2023年六年級數(shù)學(xué)下冊2百分?jǐn)?shù)(二)第1節(jié)折扣和成數(shù)作業(yè)課件新人教版
- 2023年六年級數(shù)學(xué)下冊1負(fù)數(shù)第1課時負(fù)數(shù)的初步認(rèn)識作業(yè)課件新人教版
- 2023年六年級數(shù)學(xué)上冊期末復(fù)習(xí)考前模擬期末模擬訓(xùn)練二作業(yè)課件蘇教版
- 2023年六年級數(shù)學(xué)上冊期末豐收園作業(yè)課件蘇教版
- 2023年六年級數(shù)學(xué)上冊易錯清單十二課件新人教版
- 標(biāo)準(zhǔn)工時講義
- 2021年一年級語文上冊第六單元知識要點習(xí)題課件新人教版
- 2022春一年級語文下冊課文5識字測評習(xí)題課件新人教版
- 2023年六年級數(shù)學(xué)下冊6整理和復(fù)習(xí)4數(shù)學(xué)思考第1課時數(shù)學(xué)思考1練習(xí)課件新人教版