2023年全國碩士研究生考試考研英語一試題真題(含答案詳解+作文范文)_第1頁
已閱讀1頁,還剩15頁未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡(jiǎn)介

1、<p>  學(xué)院(部): 計(jì)算機(jī)科學(xué)與工程學(xué)院 </p><p>  專業(yè)班級(jí): 計(jì)算機(jī)09-2班 </p><p>  學(xué)生姓名: 徐 勤 浩 </p><p>  指導(dǎo)教師: 林 玉 娥 </p><p>  2013年 5 月 29 日</p&g

2、t;<p>  Object-oriented analysis and design </p><p>  The basic concept of object-oriented technology and the basic method</p><p>  1.1 software development method </p><p>  

3、Computer after birth, computer technology has been developing in high speed condition, the development of computer science and technology by original only depends on the development of hardware to relying more on softwar

4、e development. In fact, the development of software technology has experienced more than generation process. </p><p>  First generation (50 to 60 s of the 20th century), in programming languages such as FORT

5、RAN and ALGOL technology marked by algorithm </p><p>  Generation to generation. At that time, the program design on people all creative talents, all rely on tips and tricks. Software productivity is very lo

6、w, based on the algorithm procedure is very difficult to understand, programmers write their own program over a period of time even after oneself also look not to understand, this to the software modifications, maintenan

7、ce bring great difficulties. So at the end of the 60 s in the "software crisis". </p><p>  Second generation (in the late 1970 s to 80 s prevailing), such as PASCAL, and COBOL programming language

8、and relational database management system for a structured system analysis and design techniques. In order to overcome the software crisis, people made efforts to mainly from the following two directions: </p><

9、;p>  Methods from the Angle of the management to improve the software development, software engineering method is proposed, and greatly improve the quality and maintainability of the software. </p><p>  S

10、econd is to focus on the analysis in the software development process and design method of research and improvement. Important achievements in this field is developed in the 70 s the rage of structured development method

11、 of structured system analysis and design techniques. </p><p>  Third generation (in the 80 s is still prevalent) represented by Smalltalk, c + + object-oriented software development methods. </p><

12、;p>  Question 1: what is on the development dynamics of object-oriented software development methods? </p><p>  Traditional structured programming algorithm as the core, the original is closely related t

13、o the data and separate to the operation of the data, it is difficult to maintain the consistency of data and operation, its software development method also does not conform to the natural thinking habits, the designed

14、software system solution space and the problem space, the expanded, difficult to understand, modify, and lead to problems in terms of program complexity and software crisis. In order to tra</p><p>  Question

15、 2: what are the advantages of the object-oriented software development method? </p><p>  Object-oriented development method to change the past traditional on the basis of function analysis and function deco

16、mposition of process oriented structural analysis and design method of object-oriented development method to simulate the way people understand and deal with the objective world to analyze the problem, the system as a se

17、ries of collections of objects, its object-oriented design and analysis of results is mapped to a structure of object-oriented implementation tool, has a more dire</p><p>  1.2 the basic concept of object-or

18、iented </p><p>  Object: (1) abstract representations of the objects is an objective entity attributes of the object is described by the data and the data for the operation of the behavior of two parts. <

19、/p><p>  class: class is a collection of objects with the same properties and behavior of abstract description; Internal including attributes and behavior of two main parts. </p><p>  example: clas

20、ses is to have the same properties and behavior of a set of abstract descriptions of objects. Therefore, classes can be used as a user-defined type and create the object model, and according to the model created by the a

21、ctual example of a specific object is a class, often referred to as examples. </p><p>  the message: the message is to request an object it contains a processing operation on the instruction information. Ess

22、ence is to the operation of the object of a class function call, the call to a method. </p><p>  For example, student S1; S1. The display () is a message. </p><p>  A news generally consists of

23、three parts: receiving a message object name, the parameters of the function name, function, operation. </p><p>  the three basic characteristics of object-oriented technology: encapsulation, inheritance, an

24、d polymorphism </p><p>  encapsulation: the so-called encapsulation is the object's properties and behavior combined into a single unit, to the outside world cannot directly access or modify the data and

25、 code, the outside world only through object provides the interface function to change the attributes of the object or obtaining data, it is realized the message is hidden. </p><p>  inheritance: if in a def

26、ined on the class, add some special attribute or operation, can form a new class, this class is not only inherited the former all characteristics of a class, and with new features, so as a special case of the class befor

27、e, is in front of a class to inherit. A class known as the parent class, before the new class is called a subclass. Through inheritance relationship can form a type hierarchy, called inheritance structure. </p>&l

28、t;p>  Polymorphism (8) : in different classes, the same function name to realize functions of different functions available. Polymorphisms of the advantages: high-level code (algorithm) write it only once and the lowe

29、r can be reused for many times, can improve the programming flexibility and efficiency. </p><p>  Object-oriented programming </p><p>  1.three major mechanisms of object oriented technology (ch

30、aracteristics) : </p><p>  encapsulation mechanism and the design of the class: the so-called encapsulated object attribute data and operation method is allowed to be combined into a single unit, to the outs

31、ide world cannot directly access or modify the data and code, the outside world only through object provides the interface function to change the attributes of the object or obtaining data, it implements the message hidd

32、en; In c + +, class is to support the data encapsulation tool, allowing design class descriptions to</p><p>  Class members to access the principle is: (1) define a class, the data members and member functio

33、ns is the default access private members. (2) a member function can be direct access to the members of the same variables and calls to members of the same function, need not add object name before the function name. (3)

34、members of the private or protected member is limited to the scope of the class that the body and the class member functions; Nonmember functions should be defined as a class of frien</p><p>  the inheritanc

35、e mechanism and derived class definition: </p><p>  the so-called inheritance is allowed on an existing class, add some special attributes or operations, to derive a new class. Not only can the derived clas

36、s inherits a base class member, and can define new member, so can be as special class of a class before. A class known as the parent class, before the new class is called a subclass. Through inheritance relationship can

37、form a type hierarchy, called inheritance structure. Inheritance is one of the Shared properties between classes and service m</p><p>  class person //The base class </p><p>  { protected:<

38、;/p><p>  char name[11];</p><p><b>  char sex;</b></p><p>  int age; </p><p><b>  public:</b></p><p>  person(){ cout<<“person

39、”<<endl;}</p><p>  ~ person(){ cout<<“delete person”<<endl;}</p><p>  int Getage() { return 20; } }</p><p>  class Student:public person</p><p

40、>  { private:</p><p>  char id[9];</p><p>  float score; </p><p><b>  public:</b></p><p>  student() {cout<<“student”<<endl;}</p><

41、;p>  ~ student(){ cout<<“delete student”<<endl;}</p><p>  float GetScore{ return score; }</p><p><b>  }</b></p><p>  void F(person *q) { q->Ge

42、tage(); }</p><p>  void main()</p><p>  { person *p;</p><p>  student s;</p><p><b>  p=&s;</b></p><p>  F(p); // p-> Getage();<

43、/p><p><b>  }</b></p><p>  The results :</p><p><b>  person</b></p><p><b>  student</b></p><p><b>  20</b><

44、/p><p>  delete student</p><p>  delete person</p><p>  The definition of mechanism of polymorphism and virtual functions: </p><p>  Polymorphism refers to the class hiera

45、rchy in the same class or different classes, can use the same function name different operating functionality, which you can use the same call way to invoke these functions with the same name with different functions, su

46、ch as p - > display (). </p><p>  Runtime polymorphism: the class inheritance hierarchy, classes may have different levels of the same name but different functions, the need to run stages according to whi

47、ch class level to determine the call object belongs to the same function. </p><p>  Will only function with the same specification as the virtual function, through object pointer or reference object to call

48、virtual functions, to achieve the runtime polymorphism. </p><p>  UML and its application </p><p>  1,.the system described in the UML model is composed of one or more views. UML provides 9 kind

49、s of views: use case diagram, class diagram, object diagram, component diagram and configuration diagram, sequence diagram, collaboration diagram, state diagram and activity diagram. The 9 kinds of diagrams can be divide

50、d into a use case diagram, static view and dynamic view. </p><p>  2, can also view is divided into five class diagram of UML, UML content is defined by the five class diagram: </p><p>  The fir

51、st type is a use case diagram, describe system functionality from the user Angle, and points out the function of the operator. </p><p>  The second type is Static diagram (Static diagram), describe the Stati

52、c structure of system, including the class diagram, object diagram. </p><p>  The third kind is Behavior diagrams (behaviors diagram) describing the dynamic Behavior of the system and to participate in the a

53、ctivities of the interaction relationship between objects, including activity diagrams and state diagrams. </p><p>  The fourth class is interaction diagrams (Interactive diagram) to describe the interaction

54、 relationship between objects, including the sequence diagram and collaboration diagram. </p><p>  The fifth class is Implementation diagram (Implementation diagram). Figure - the view include the component

55、diagram and configuration. </p><p>  3, use case diagram </p><p>  Definition of the definition of a use case diagram: use case diagram from the Angle of the user use the system describes the sy

56、stem function of graphical representation methods. </p><p>  A Use Case (Use Case) is used to describe a function of the system requirements, it can accurately express the activists of interaction with the s

57、ystem and the system to provide a service. </p><p>  The Use Case of the contact: Use Case except contact activists have the Use Case .There is a certain link between, including: The generalization relations

58、hip:</p><p>  (a) a special Use Case with another, more general Use Case </p><p>  (b) Use contact: refers to a Use Case with another Use Case of functional behavior. </p><p>  (c)

59、contain contact: a basic Use Case includes another public behavior of a Use Case. </p><p>  (d) expand contact: refers to a basic Use Case can be made by another functional behavior of the Use Case to expand

60、. </p><p>  4, the definition of a class diagram </p><p>  System class diagram is an expression of graphic class and its related logic (logic view). </p><p>  Class diagram is the

61、core of object-oriented design, establishes the state diagram, collaboration diagram and other figure. </p><p>  Class and class relationships: the main related, aggregation/composition, generalization/speci

62、alized, dependence, etc. </p><p>  5, the definition of the sequence diagram </p><p>  Sequence diagram describes the dynamic collaboration between a group of interacting objects, which represen

63、ts the complete one </p><p>  Operating behavior of passing messages between objects and the objects time sequence. The sequence diagram By the object class character, lifeline, activation period and message

64、. </p><p>  6, the definition of collaboration diagrams </p><p>  Behavior of a system is implemented by a group of objects, these objects are done through interaction and collaboration service

65、system. Used to describe the implementation of certain services involving the relationship between objects and their dynamic views (including communication) are called Collaboration diagrams (Collaboration). Available UM

66、L collaboration diagrams to describe the business process. Collaboration diagram is different from the sequence diagram. </p><p>  7, state diagram (StatechartDiagram) state diagram describes the definition

67、of certain object may have in the process of system operation </p><p>  Status, and jump between different states and external trigger the jump </p><p>  Events. State diagram focuses on describ

68、e objects dynamically in its life cycle </p><p>  Behavior. Can also be used for the reaction type object modeling. </p><p>  8, activity diagrams </p><p>  Definition: activity dia

69、grams are used to describe business process or workflow system. Activity diagrams </p><p>  Is composed of a series of motion state, the movement state of the control can be switched from one state to anothe

70、r and the adjacent state. Activity diagram can also be said that decision state, condition, action of parallel execution and message specification, etc. Available strips of lane put the activity into several groups, let

71、an object is responsible for a group, the object must perform the activities contained within the group. </p><p>  9, the definition of the component diagram </p><p>  Components are provides a

72、set of interface functions of physical implementation module, it can be the products of the software development process, such as source code and binary code and an executable code, etc. Classes, interfaces, etc. They ar

73、e the logical model of the physical implementation. Interface is used to describe a class or component of a service operation. Component diagram constitutes the physical components of the system and the link between each

74、 other. Component diagrams can be </p><p>  10, the object oriented system development method based on UML can also be divided into the following steps: </p><p>  the system requirements analysi

75、s: (a) captured or describe the functional requirements and non-functional requirements; (b) tectonic system use case model; (c) detail the use case </p><p>  (2) systems analysis: convert the use case model

76、, analysis model for describing the system basic structure. Analysis model is a series of classes and class instances and their mutual relations. Analysis in the model class is also called analysis class. Commonly used m

77、ethod is to use a noun/verb analysis method to find analysis class. There are three kinds of analysis classes: entity, boundary and control classes. </p><p>  (3) System design: (a) augment and refine class.

78、 Further expand class defined in the analysis phase, and to define new classes to deal with technical issues, including handle nonfunctional requirements. (b) for each use case establish dynamic model, including sequence

79、 diagrams, collaboration diagrams, etc., to describe how to implement case through collaboration of objects in the class diagram of the function. (c) through dynamic modeling to revise and improve the class diagram. (d)

80、design subsy</p><p>  (4)System implementation :(a)The class diagram of the logic model elements (such as class, interface, etc.) grouped packaging form each component is easy to implement, and to establish

81、the connection between the components, constitute a component diagram. Component diagrams can represent a system's components and their connection, clearly describe the software architecture of the system. (b) implem

82、entation component. With programming realization of components has to implement component in the co</p><p>  11, based on UML of relational database design is divided into four stages: </p><p> 

83、 Business Use Case model design: is the database demand analysis, establish business model using Use Case diagrams, etc. </p><p>  The logical data model design: the main application is to determine the syst

84、em needed to persistent data. Using class diagram and database logic model is set up. If it is a relational database design, you may need to design express persistent data entity classes and their contacts, and map them

85、into a relational database Table (Table), View (View), etc. </p><p>  The physical data model design: using the component diagram, configuration diagram, etc., physical model of database design. </p>

86、<p>  Physical implementation design: to transform the physical data model to the actual database environment. Combined with the actual database environment, constitute the base tables of the database, file organiza

87、tion and indexing, etc. </p><p><b>  面向?qū)ο蠓治雠c設(shè)計(jì)</b></p><p>  面向?qū)ο蠹夹g(shù)的基本概念和基本方法</p><p>  1.1 軟件開發(fā)方法的發(fā)展</p><p>  計(jì)算機(jī)誕生之后,計(jì)算機(jī)技術(shù)一直處于高速發(fā)展?fàn)顟B(tài),計(jì)算機(jī)科學(xué)技術(shù)的發(fā)展由原來只依靠硬件的發(fā)展逐漸

88、變?yōu)楦嗟匾揽寇浖陌l(fā)展。事實(shí)上,軟件技術(shù)的發(fā)展經(jīng)歷了多代歷程。</p><p>  第一代(20世紀(jì)50-60年代),是以FORTRAN和ALGOL等編程語言為標(biāo)志的算法技術(shù)時(shí)代。那時(shí),程序設(shè)計(jì)全靠人們發(fā)揮創(chuàng)造才能,全靠技巧和竅門。基于這種算法技術(shù)的軟件生產(chǎn)率非常低,程序很難看懂,甚至程序員自己寫的程序過一段時(shí)間后自己也看不懂,這給軟件的修改、維護(hù)帶來極大的困難。于是60年代末出現(xiàn)了 “軟件危機(jī)”。</p

89、><p>  第二代(20世紀(jì)70年代末開始到80年代盛行的),以PASCAL、COBOL等編程語言和關(guān)系數(shù)據(jù)庫管理系統(tǒng)為標(biāo)志的結(jié)構(gòu)化系統(tǒng)分析和設(shè)計(jì)技術(shù)。為了克服軟件危機(jī),人們主要從如下兩個(gè)方向做了努力:</p><p>  一是從管理的角度改進(jìn)軟件開發(fā)方法,提出了軟件工程方法,大大改善了軟件的質(zhì)量與可維護(hù)性。</p><p>  二是側(cè)重于對(duì)軟件開發(fā)過程中分析與設(shè)計(jì)方

90、法的研究和改進(jìn)。這方面的重要成果就是在70年代出現(xiàn)了風(fēng)靡一時(shí)的結(jié)構(gòu)化開發(fā)方法—結(jié)構(gòu)化系統(tǒng)分析和設(shè)計(jì)技術(shù)。</p><p>  第三代(80年代開始至今還盛行的)以Smalltalk、C++等為代表的面向?qū)ο筌浖_發(fā)方法。 </p><p>  問題1:面向?qū)ο筌浖_發(fā)方法發(fā)展的動(dòng)因是什么?  </p><p>  傳統(tǒng)的結(jié)構(gòu)化程序設(shè)計(jì)以算法為核心,把本來密切相關(guān)的

91、數(shù)據(jù)和對(duì)數(shù)據(jù)的操作分離開來,很難保持?jǐn)?shù)據(jù)和操作的一致性,其軟件開發(fā)方法也不符合人們的自然思維習(xí)慣,設(shè)計(jì)出來的軟件系統(tǒng)其解空間與問題空間不一致,致使程序難以理解、修改和擴(kuò)充,最終導(dǎo)致程序復(fù)雜性問題和軟件危機(jī)。為了超越程序復(fù)雜性障礙,克服軟件危機(jī),人們提出了面向?qū)ο筌浖_發(fā)方法。</p><p>  問題2:面向?qū)ο筌浖_發(fā)方法的優(yōu)點(diǎn)有哪些?</p><p>  面向?qū)ο箝_發(fā)方法一改過去傳統(tǒng)的

92、以功能分析和功能分解為基礎(chǔ)的面向過程的結(jié)構(gòu)化分析與設(shè)計(jì)方法,面向?qū)ο箝_發(fā)方法模擬人們理解和處理客觀世界的方式來分析問題,把系統(tǒng)視為一系列對(duì)象的集合,其面向?qū)ο蟮脑O(shè)計(jì)又將分析的結(jié)果映射到某種面向?qū)ο髮?shí)現(xiàn)工具的結(jié)構(gòu)上,使映射過程有著比較直接的對(duì)應(yīng)關(guān)系,使分析者、設(shè)計(jì)者和編程者都可使用相同的概念,從而使面向?qū)ο蟮能浖_發(fā)能比較自然地模擬客觀世界的活動(dòng),使問題描述空間與解空間在結(jié)構(gòu)上盡可能一致。因此,采用面向?qū)ο蠓椒梢愿行У亻_發(fā)大型軟件系統(tǒng)

93、。面向?qū)ο蠓椒ǖ姆庋b、繼承、多態(tài)等機(jī)制不僅支持軟件復(fù)用,而且使軟件維護(hù)工作可靠有效,可實(shí)現(xiàn)軟件系統(tǒng)的柔性制造,更好地克服軟件危機(jī)。因此,它已成為成熟的廣為采用的軟件開發(fā)方法。到20世紀(jì)末,面向?qū)ο筌浖こ讨饾u發(fā)展成熟,特別是統(tǒng)一建模語言(UML)標(biāo)準(zhǔn)的形成和廣泛使用,使面向?qū)ο筌浖_發(fā)方法已成為軟件開發(fā)的主流技術(shù)。</p><p>  1.2 面向?qū)ο蟮幕靖拍?lt;/p><p>  對(duì)象

94、:對(duì)象是客觀實(shí)體的抽象表示,是由描述對(duì)象的屬性數(shù)據(jù)和對(duì)這些數(shù)據(jù)進(jìn)行的操作行為兩部分組成。</p><p> ?。?)類:類是具有相同屬性和行為的對(duì)象集合的抽象描述;類的內(nèi)部包括屬性和行為兩個(gè)主要部分。</p><p> ?。?)實(shí)例: 類是對(duì)具有相同屬性和行為的一組對(duì)象的抽象描述。因此,類可作為一種用戶自定義類型和創(chuàng)建對(duì)象的樣板,而按照這種樣板所創(chuàng)建的一個(gè)個(gè)具體對(duì)象就是類的實(shí)際例子,通常稱

95、為實(shí)例。 </p><p>  (4)消息:消息就是請(qǐng)求某個(gè)對(duì)象執(zhí)行它所包含的某項(xiàng)處理操作的指令信息。實(shí)質(zhì)是對(duì)某個(gè)類對(duì)象的操作函數(shù)的調(diào)用,即方法的調(diào)用 。</p><p>  例如, student S1; S1.display()是一個(gè)消息。</p><p>  一個(gè)消息一般由三部分組成:接收消息的對(duì)象名、操作函數(shù)名、函數(shù)的參數(shù)。</p><

96、p>  面向?qū)ο蠹夹g(shù)的三個(gè)基本特征:封裝性、繼承性、多態(tài)性 </p><p> ?。?)封裝性:所謂封裝就是把對(duì)象的屬性和行為結(jié)合成一個(gè)獨(dú)立的單位,使外界不能直接訪問或修改這些數(shù)據(jù)和代碼,外界只能通過對(duì)象提供的接口函數(shù)來改變或獲取對(duì)象的屬性數(shù)據(jù),這就實(shí)現(xiàn)了消息隱蔽。</p><p> ?。?)繼承性:如果在一個(gè)已定義的類上,增加一些特殊屬性或操作,可以形成一個(gè)新的類,這個(gè)類不僅繼承了

97、前一個(gè)類的全部特征,而且具有新的特性,因此可看作前一個(gè)類的特例,是對(duì)前一個(gè)類的繼承。前一個(gè)類稱為父類,新產(chǎn)生的類叫做子類。通過繼承關(guān)系可形成一種類層次結(jié)構(gòu),叫做繼承結(jié)構(gòu)。</p><p>  (8)多態(tài)性:在不同類中,可用相同的函數(shù)名實(shí)現(xiàn)功能不同的函數(shù)。多態(tài)性的優(yōu)點(diǎn):高層代碼(算法)只需寫一次,低層便可多次復(fù)用,可提高程序設(shè)計(jì)的靈活性和效率。</p><p><b>  面向?qū)ο?/p>

98、程序設(shè)計(jì)</b></p><p>  1、面向?qū)ο蠹夹g(shù)的三大機(jī)制(特征):</p><p> ?。?)封裝機(jī)制和類的設(shè)計(jì):所謂封裝就是允許將對(duì)象的屬性數(shù)據(jù)和操作方法結(jié)合成一個(gè)獨(dú)立的單位,使外界不能直接訪問或修改這些數(shù)據(jù)和代碼,外界只能通過對(duì)象提供的接口函數(shù)來改變或獲取對(duì)象的屬性數(shù)據(jù),這就實(shí)現(xiàn)了消息隱蔽;在c++中,類是支持?jǐn)?shù)據(jù)封裝的工具,即允許設(shè)計(jì)類來抽象描述一組具有相同特性和

99、行為的對(duì)象,即類中可以封裝一組對(duì)象的共同屬性和方法。由此可見,類是實(shí)現(xiàn)數(shù)據(jù)封裝的工具,對(duì)象則是數(shù)據(jù)封裝的實(shí)現(xiàn)。沒有封裝,就沒有面向?qū)ο蠹夹g(shù)。</p><p>  類成員訪問的原則是:(1)定義一個(gè)類時(shí),數(shù)據(jù)成員和成員函數(shù)的默認(rèn)訪問權(quán)限是私有成員。(2)成員函數(shù)可直接訪問同類中的成員變量和調(diào)用同類中的成員函數(shù),不用在函數(shù)名前加上對(duì)象名。(3)私有成員或受保護(hù)成員的作用域僅限于類的說明體和類的成員函數(shù);非成員函數(shù)應(yīng)定

100、義為類的友員函數(shù)才能訪問這個(gè)類的私有成員。 (4)公用成員的作用域不但包括類說明體,還包括它所屬對(duì)象的使用范圍。可以在類外訪問公用成員,但必須在成員名前加上對(duì)象名。</p><p>  繼承機(jī)制與派生類的定義:所謂繼承就是允許在一個(gè)已有類上,增加一些特殊屬性或操作,來派生成新的類。這個(gè)派生類不僅可以繼承基類成員,而且可以定義新的成員,因此可看作前一個(gè)類的特殊類。前一個(gè)類稱為父類,新產(chǎn)生的類叫做子類。通過繼承關(guān)系可

101、形成一種類層次結(jié)構(gòu),叫做繼承結(jié)構(gòu)。繼承是類之間共享屬性與服務(wù)的一種機(jī)制。 </p><p>  class person //基類</p><p>  { protected:</p><p>  char name[11];</p><p><b>  char sex;</b></p><p

102、>  int age; </p><p><b>  public:</b></p><p>  person(){ cout<<“person”<<endl;}</p><p>  ~ person(){ cout<<“delete person”<<endl;}</p>

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 眾賞文庫僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。

評(píng)論

0/150

提交評(píng)論