Current location - Training Enrollment Network - Books and materials - Object-oriented analysis and design of book catalogue
Object-oriented analysis and design of book catalogue
The first part of the basic article 1 introduction to object-oriented methods 3 1. 1 .2 What is object-oriented 3 1.2 The formation of object-oriented methods from the perspective of epistemology 5 1.2/software development-the gap between understanding and describing things 5/kloc-. 5 1.2.4 The role of software engineering 8 1.2.5 Object-oriented is the regression of software methodology. 12 1.3 Basic concept of object-oriented method 12 1.3 1 object65438. 5438+04 1.3.3 package 16 1.3.4 inheritance 17 1.3.5 aggregation 18 1.3.6 association 20/kloc. .9 Other Comparisons 22 1.3 10 Terminology 24 1.4 History and present situation of object-oriented methods 26 1.4.2 The whole process from development to software life cycle 27/kloc Analysis and design method 33 2. 1 functional decomposition method 33 2.2 structured method 34 2.3 information modeling method 35 object-oriented catalog analysis and design 2.4 object-oriented method 36 2.4. 1 What is OOA36 2.4.2 What are the main advantages of OOD37 2.4.3 object-oriented method 38 2.4.4 Several typical surfaces? Object-oriented method 4 1 2.4.4. 1 Booch method 43 2.4.4.2 Corde/Yulden method 45 2.4.4.3 Jacobson method 48 2.4.4.4 Lomborg method 52 Chapter III Introduction to Unified Modeling Language UML 56 3. 1 Background and Development History 56 3.2 UML 1. Component 58 3.2.2 Language Architecture and Definition 59 3.2.3 Various diagrams and extension mechanisms of UML 1 62 3.3 UML 2 Overview 66 3.3. 1 From UML 1 To UML 266 3.3.2.65438+ 2.2 UML Superstructure 68 3.3.2.3 Object Constraint Language 69 3.3.2.4 UML Diagram Exchange 70 3.3 Various diagrams of UML 2 70 Chapter 4 OOA Method Overview of this book D 74 4. 1 Introduction 74 4.2 Main concepts 74 4.2. 1 Main model elements 75 4.2.2 Main principles of object-oriented modeling 76 4.3 model and its specification 80 4.3. 1 basic model-class diagram 80 4.3.2 demand model-use case diagram 865433. Model-Other Various Figures 82 4.3.4 Model Specification 82 4.3.5 OOA Model Framework 83 4.3.6 OOD Model Framework 83 4.4 Modeling Process 85 4.4. 1 OOA Process 85 4.4.2 OOD Process 87 4.5 The Relationship between OOA and OOD 88 4.5. 0 Consistency Concept and Representation 88 4.5.2 Location of Different Goals, Contents and Abstraction Levels 89 4.5.3 Location in Software Life Cycle 90 4.5.4 Two Different Views on Division of Labor 90 4.5.5 Viewing the Relationship between OOA and OOD from Model-Driven Architecture 92 Part II Analysis Chapter V Establishing Requirement Model-Use Case Diagram 975. 1 Requirements Analysis and System 98 5.3 System Boundaries and Participants 98 5.3. 1 System Boundaries 98 5.3.2 Participants 99 5.4 What is the content and format of the use case10/5.4.1use case 65438? 8+004 5.5 Use Case Diagram 105 5. 6 5438+0 Model Elements and Representation 105 5. 2 Several Issues Worth Discussing 107 5.6 Development Process and Suggestions 1 10 Chapter 6 Discovering Objects, Define the concept of object class 1 13 6. 1 and its application 654481156.1.4 How to use the concepts of object and class1176. Abstract principle 1 19 6.3.3 strategy and inspiration 120 6.3.4 review and screening 122 6.4 object classification 124 6.4. 1 abstract objects into classes/kloc-0. +025 Chapter VII defines attributes and operations of objects 127 7. 1 attributes and operations 127 7.2 notation 128 7.3 defines attributes 129 7.3. 1 strategy and inspiration/kloc-0. Problems to be considered in later OOD/naming and positioning of properties of kloc-0/3/7.3.4/defining operations of kloc-0/317.4 132 7.4. 1 behavior classification1327. .4 Understanding the Active Behavior of Objects/KOOC-0/34 7.4.5 Describing the Operation Process/KOOC-0/34 7.4.6 Naming and Positioning of Operation/KOOC-0/35 7.5 Concept and Use of Interface/KOOC-0/36 Chapter 8 Establishing the Relationship between Objects/KOOC-0/40 8./. 38+0. 1 related concepts 140 8. 1.2 characterization 142 8. 1.3 How to find the general-special structure1438.1. 1.6 Multiple Heredity and Polymorphism 150 8.2 Whole-Part Structure1528.2./Related Concepts 152 8.2.2 Representation 153 8.2.3 How to Find the Whole? 2.5 Advanced application skills of whole-part structure/KOOC-0/56 8.2.5./KOOC-0/Simplify the definition of objects/KOOC-0/56 8.2.5.2 supports software reuse/KOOC-0/57 8.2.5.3 represents an indefinite number of components/KOOC-0/58 8.2.5.4 represents dynamically changing object features/KOOC-0/. 2.6 Variation between the two structures 162 8.3 correlation 163 8.3. 1 related concepts 163 8.3.2 representation and implementation technology 165 8.3.2. 1 basic representation. .3.3 Use simple association concepts to solve complex association problems 169 8.3.3. 1 association with attributes and operations169 8.3.3.2 ternary association sum? n? A class of meta-association1718.3.3.3 appears many times in association 173. The complexity of the associated endpoints in 8.3.3.4 174 8.3.4 How to establish the association 180 8.4 message 184 8.4. 1 message 188 What is it? . 1. 1 messages in sequential system 184 8.4. 1.2 messages in concurrent system 185 8.4. 1.3 significance of messages to object-oriented modeling 1 878. .5.46665436 Relationship between model diagrams 199 9.2 Package Diagram 2019.2./Concept, usage and representation of package 20 1 9.2.2 Relationship between package and representation 202 9.2.3 How to build a package diagram 205 9 The package model element 205 is named 9.2.3.2 package 208, 9.2.3.3 organizes nested packages 209, 9.2.3.4 reduces the nested hierarchy of packages 265438. 3.5, establishes the relationship between packages 2 10 9.2.4, and uses the visual 2 12 9.3 sequence diagram of the package diagram control system 2 12 9.3. 1 sequence diagram and it. 9.3.4 Discussion on Several Problems of Sequence Diagram 2 19 9.3.5 How to Establish Sequence Diagram 22 1 9.4 Activity Diagram 223 9.4. 1 Activity diagram and its use 223 9.4.2 Main concepts and representations 224 9.4.3 An example of activity diagram 228 9.4.3 9.4.5 How to establish activity diagram 232 9.5 State machine diagram 235 9.5. 655435 State machine diagram 242 9.6 Component diagram 245 9.6.6553 and usage 245 9.6.2. Other model diagrams of component diagram 248 9.7.1object diagram 249 9.7.2 combined structure diagram 250 9.7.3 communication diagram 25 1 9.7.4 interaction overview diagram 252 9. 9.7.6 Deployment Diagram 257 Chapter 10 Model Specification 259 10. 1 Discussion on Related Concepts and Problems 259 10. 1 What is Model Specification 25910./kloc- .3 Selection of Description Language 26010.10.4 Organization of Model Specification 2610.5 About Object Constraint Language OCL262 10.2 Class Diagram 264 10.2. 1 The format of 0.2.3 class specification is 268 654382. 1 adjustment of programming language support ability 277 1 1.3.2.2 Add common classes. Provide * * * the design strategy adopted by the same protocol 282 1 1.3.2.3 to realize multiplexing; improve the performance of 2851.3.4. 2.2 Requirements analysis of human-computer interaction 300 12.2. 1 Analysis participants-people interacting with the system 30 12.2.2 Analysis and handling of abnormal events in human-computer interaction use case analysis 302 12.2.3. Organization of command 306 12.2.5 Organization of output information 309 12.3 Design criteria of man-machine interface 310/2.4 Object-oriented design of man-machine interface 31212.4. Selecting interface support system 365438+ selecting interface elements to realize interaction 3 14 65+02.5.3 Necessity of design 323 12.5.4 Design strategy based on visual programming environment 324 Chapter 65438 +03 Design of control driver 33013./kloc Overall system scheme 330 13.2.2 software architecture 3313.2.3 software architecture in network environment 332 13.2.4 system concurrency 33413.2.4./kl. 3.2.4.3 application system concurrency 337 6543803.3.3 Identification control flow 347 13.3.4 Use 14 35 14. 1 What is the data interface part 35 1 14.2? 438+0 file system 352 14.2.2 database management system 353 14.2.2 1 relational database and database management system 354 14.2.2 object-oriented database and database management system 35614. Design strategy of object storage scheme and data interface 358 14.3. 1 design of file system 35814.3.1image of objects in memory space and file space 35814.3./kloc-0. 0.3 Class 36114.3.1.4 Modify the design of the problem domain part of the design data interface 36214.3.2 RDBMS 36314.3.2.1 Kloc-0/0000000003 366 1 4.337915.3 System Deployment 380 15.3. 1 Organization of Software Products 381Kloc-0/5.3. 3 1.2 From the epistemological point of view, the formation of object-oriented method 5 1.2. 1 software development-understanding and description of things 5 1.2.2 Language gap 5 1.2.3 The development of programming languages has narrowed the gap 5/kloc-. .2.5 Object-oriented is the regression to the foundation of software methodology1210.3 Basic concept of object-oriented method1210/object1313.2 class/kloc-0. Cheng 17 1.3.5 Aggregation 18 1.3.6 Association 20 1.3.7 Message 21.3.8 Polymorphism 221. The history and present situation of object-oriented method 26 1.4. 1 history 26 1.4.2 has developed into the whole process of software life cycle 28 1.4.3 has penetrated into various fields of computer software 30 Chapter 2 Different analysis and design methods 33 2. 1 functional decomposition method 33 2. Information Modeling Method 35 Directory Object-Oriented Analysis and Design 2.4 Object-Oriented Method 36 2.4. 1 What is OOA 36 2.4. 2 ood 37 2.4. 3 Several Typical Object-Oriented Methods 4 1 Chapter 3 Unified Modeling Language (UML)? Introduction 56 3. 1 UML Background and Development History 56 3.2 UML 1 Overview 58 3.2. 1 UML 1 Specification Major Components 58 3.2.2 Language Architecture and Definition 59 3.2.3 UML 1 Various Diagrams and Extension Mechanisms 62 3. .3.1Four specifications from UML 1 to UML266 3.3.2 Various drawings of UML 266 3.3.3 70 Chapter IV OOA &;; Methods Overview D 74 4. 1 Introduction 74 4.2 Main concepts 74 4.2. 1 Main model elements 75 4.2.2 Main principles of object-oriented modeling 76 4.3 model and its specifications 80 4.3. 1 Basic model-class diagram 80 4.3.2 Requirements model-use case diagram 865433. Model-Other Various Figures 82 4.3.4 Model Specification 82 4.3.5 OOA Model Framework 83 4.3.6 OOD Model Framework 83 4.4 Modeling Process 85 4.4. 1 OOA Process 85 4.4.2 OOD Process 87 4.5 The Relationship between OOA and OOD 88 4.5. 0 Consistency Concept and Representation 88 4.5.2 Location of Different Goals, Contents and Abstraction Levels 89 4.5.3 Location in Software Life Cycle 90 4.5.4 Two Different Views on Division of Labor 90 4.5.5 Viewing the Relationship between OOA and OOD from Model-Driven Architecture 92 Part II Analysis Chapter V Establishing Requirement Model-Use Case Diagram 975. 1 Requirements Analysis and System 98 5.3 system boundary and participants 98 5.3. 1 system boundary 98 5.3.2 participants 99 5.4 use case 1 5.4. 1 what is a use case1kloc-0/ 5.4.2 Content and format of use cases 654438+05438+5.4. 2 Content and format of use cases 65496 8+0004 5.5 Use case diagram 651kloc-0/56.1.4 How to use the concepts of objects and classes1. Abstract principle 1 19 6.3.3 strategy and inspiration 120 6.3.4 review and screening 122 6.4 object classification 124 6.4. 1 abstract objects into classes/kloc-0. +025 Chapter VII defines attributes and operations of objects 127 7. 1 attributes and operations 127 7.2 notation 128 7.3 defines attributes 129 7.3. 1 strategy and inspiration/kloc-0. Problems to be considered in the later stage of OOD/naming and positioning of kloc-0/307.3.4 attributes/defining operations of kloc-0/317.417.4/behavior classification1327. .4 Understanding the Active Behavior of Objects/KOOC-0/34 7.4.5 Describing the Operation Process/KOOC-0/34 7.4.6 Naming and Positioning of Operation/KOOC-0/35 7.5 Concept and Use of Interface/KOOC-0/36 Chapter 8 Establishing the Relationship between Objects/KOOC-0/40 8./. 38+0. 1 related concepts 140 8. 1.2 characterization 142 8. 1.3 How to find the general-special structure1438.1. 1.6 Multiple Inheritance and Polymorphism 149 8.2 All Structures 152 8.2. 1 Related Concepts 152 8.2.2 Representation 153 8.2.3 How to Find All Structures/ 2.5 Advanced application skills of the whole part structure 156 8.2.6 Variation between two structures 16 1 8.3 Lenovo 163 8.3. 1 related concepts 163 8.3.2 indicates the relationship with. Association problem 168 8.3.4 How to establish association 179 8.4 message 183 8.4. 1 message 183 8.4.2 How to establish message187 8.4.2. 5. 1 What is dependency 192 8.5.2 Definition and representation of dependency 193 8.5.3 Role of dependency in object-oriented modeling 197 Chapter 9 Building auxiliary model 199. 1 class. 38+0 9.2. 1 Concept, usage and representation of package 20 1 9.2.2 Relationship between package and representation 202 9.2.3 How to establish the visual field of control system of package graph 205 9.2.4219.3 Sequence diagram 2. Organization mechanism and reuse of 12 9.3.3 sequence diagram 2 17 9.3.4 Discussion on several problems of sequence diagram 2 19 9.3.5 How to establish sequence diagram 220 9.4 activity diagram 223 9.4. 1 activity diagram and its use 223 9.4. Example 228 9.4.4 Discussion on Several Issues of Activity Diagram Example 229 9.4.5 How to Establish Activity Legend 232 9.5 State Machine Legend 235 9.5. 1 State Machine Diagram and State Modeling Example 235 9.5.2 Main Concepts and Representation Example 236 9.5.3 How about State Machine Legend 24 1 9.5.4? 9.6 Component Diagram 244 9.6. 1 Source and Use of Component Diagram 245 9.6.2 Main Concepts and Representation 245 9.6.3 How to Establish Other Model Diagram of Component Diagram 248 9.7 249 9.6 5438+0 Object Diagram 249 9.7.2 Combination Structure Diagram 250 9.7.3 Communication 9.7.3 26010.10.3 Selection of Description Language 26010./0.4 Organization of Model Specification 261.10.5 About Object Constraint Language (OCL). Specification of 262 10.2 class diagram 264 10.2 1 objective and measurement 264 10.2.2 class specification content 266 10.2.3 class specification format 268 1 0.3 Specification of other model diagrams 270 653 The third part is the design of the problem domain part in Chapter 65438 +0654333 What is the problem domain part 275 1 1.2 Influence of realization conditions on the problem domain part 276 1 1.3 Design process 277. 0.3. 1 Design Preparation 2771.3.2 Design Contents and Strategies 2771.3.3 Mapping with OOA Documents Chapter 297 Design of Human-Computer Interaction Part12.299965686. 2.2. 65438+ 1.22.2.5 Organization of output information 308 12.3 Design criteria of man-machine interface 309 12.4 Object-oriented design of man-machine interface 312.4./kloc-. 5438+03 14.4.3 Representing interface elements with object-oriented concept 3 15 12.5 Human-machine interface design in visual programming environment 3 19 12.5. 1 problem presentation 3/kloc. 12.5.3 Necessity of design 322 12.5.4 Design strategy based on visual programming environment 323 Chapter 65438 +03 Design of control driver 329 13. 1 What is a control driver 32913. +0 System Overall Scheme System Overall Scheme 329 13.2.2 Software Architecture 330 13.2.3 Software Architecture in Network Environment 3313.2.4 System Concurrency 333 13.3 How to Design Control Driver 34 8+0 Select the software architecture style 34 1 13.3.2 Determine the system distribution scheme 3413.3 Determine the control flow 346 13.3.4 Use the activity class to represent the data of chapter 348 14 of the control flow. It is the data interface part 350 14.2 data management system and its selection 351file system 35 1 1 4.2.2 database management system 352 14.2.3 data management system selection 355 656. Port design strategy 357 14.3. 1 file system design 357 14.3.2 relational database management system design 362 14.3.3 object-oriented database management system design 375 Chapter 15 Based on component and system deployment 377/.