[理学]uml课件Chapter2amp3amp4StateModeling.ppt

Chapter 2 Modeling Modeling as a Design Technique A model is an abstraction of something for the purpose of understanding it before building it. (P15, par.1, first sentence) To build complex systems, the developer must abstract different views of the system, build models using precise notations, verify that the models satisfy the requirements of the system and gradually add detail to transform the models into an implementation. (P15, par.1, last sentence) 2.1 Modeling Designers build many kinds of models for various purposes before constructing things. Models serve several purposes. Testing a physical entity before building it Communication with customers Visualization Reduction of complexity 2.2 Abstraction Abstraction must always be for some purpose, because the purpose determines what is, and is not, important. Many different abstraction of the same thing are possible, depending on the purpose for which they are made. 2.3 The Three Models We find it useful to model a system from three related but different viewpoints, each capturing important aspects of the system, but all required for a complete description. The three kinds models separate a system into distinct views. The different models are not completely independent – a system is more than a collection of independent parts – but each model can be examined and understood by itself to a large extent. The different models have limited and explicit interconnections. A good design isolates the different aspects of a system and limits the coupling between them. 2.3.1 Class Model The class model describes the structure of objects in a system – their identity, their relationship to other objects, their attributes, and their operations. The goal in constructing a class model is to capture those concepts from the real world that are important to an application. Class Diagram 2.3.2 State Model The state model describes those aspects of objects concerned with time and the sequencing of operations – events that mark cha