One of the UML review series (Basic Concept) [Original]
Introduction 1.uml
UML (Unified Modeling Language Uniform Modeling Language) is a visualized modeling language that allows system constructs to establish system blueprints that express their imagination using standard, easy-to-understand ways, and provide a mechanism To make effective sharing and exchange design results between different people.
UML is a "map" representation of a system, through a variety of different "map" production "
Model "(an object model that is easy to use and easy to understand) .uml model only shows what a system should do and not tell us how to do it.
2. Object-oriented profile
Take the object-oriented, with the class and inheritance of the construction mechanism, make full use of interface and polymorphism to provide flexibility, abstract and describe the objective world, and thus designed and constructing the corresponding system.
The construction method based on the construction is the object-oriented technology.
Related concepts: objects, classes, abstractions, inheritance, polymorphism, packages, interfaces.
Object: Data (Object Property Description) and Package of Operation (Object Behavior Description).
Class: Abstract description of objects with common attribute characteristics and behavioral characteristics.
Polymorphism: Decide technology of executing code at runtime.
Interface: Description of the operating specification.
Build: A physical, replaceable system part, which shows an interface collection.
3. Map inuml
Representation by a rectangle. Class name, attribute, operation, responsibilities (what are described by the description) are in the respective boxes.
The type and initial value of the property can be specified in the class diagram, the parameters, and parameter types of the operation.
The relationship between class:
A. Association: Between the relationship between the class, each class plays a role. :
solid line
B. Inherit: The relationship between subclass and parent class. (The UML is also called "generalization"):
Sail line of the hollow arrow
C.
Dependence: The definition of another class is used in a class operation. :
Arrow
D. Gathering: A class consisting of several parts (such as personal computers including CPU, motherboard, disk, memory, mouse keyboard, etc.)
E. Composition: Represents a strong type of aggregation, each of which can only belong to a whole
F. Interface: Describe part of the behavior
A set of operations is a set of operations that are provided to another class.
(Example: The steering wheel control of the car, we don't need to know the drive principle, only related to its operation)
G. Implement: A class and its interface relationship
Explanation: A class can implement multiple interfaces, and an interface can also be implemented by multiple classes.
Interface and dependence example:
Washing machine ----------- △
Washing machine controller (interface) ← -----------
people
Interface dependence
4.
Use case
The use case is a UML component that helps analysts and users to determine system usage, a set of use cases are description of how to use the system from the user's perspective. It can be considered as an example of a group of use of the system, and each scene describes a sequence of events, each sequence from one person, or another system, or a hardware device, or time. Entity initiating event sequence called "
Participant (actor).
Use case multiplexing: A common step from each step sequence is used to form a certain case.
Additional case of use, we can also get one
Extended use case.
Participants, use cases, and interconnects together form an "use case model", for example:
Participants -------- System (use case) --------
Participant
Document Description: 1 Participants of the initiator 2 Use case assumes that 3 Use the pre-condition 4 Scene 5 Scene 5 After the scene is completed, the rear condition 6 after the scene is completed. 6 Participants benefited from the case
5.
State diagram
Objects (or behavioral elements) change their own state (lapse of response event or time), this method of characterization system can be used. The status diagram is just a model for a single object.
Some detail options for the status map: entry action, action, other action, or events. Causes the event that the transfer occurred
Trigger event, or
Dynamic transfer. Details can be added
Protection conditions (only when the conditions are met, the transfer can occur).
One state can be
Substitudes, subtrans from two forms:
Sequence status and
Particular.
6.
Flowchart
The sequence diagram consists of the following objects: The object is represented by the rectangle frame, and the message is indicated by the solid line with arrows, and the time is represented by a vertical dashed line.
A. Object: Down-extended broken line called object
lifeline.
B. Message: Real lines with solid arrows
Call the message, the return of the hollow arrow is called
Return message, asynchronous message
Realization with a hollow arrow.
C. Time: Overhead down.
Explanation: The interaction time in the sequence diagram can also be multiplexed!
7.
Collaboration map
The writing diagram is an extension of the object, and the processing demonstrates the association between the objects, and shows messaging between the objects. The sequence diagram follows the time sequential layout, the writing map follows the spatial organization.
8.
Activity map
Used to simplify the working steps describing a process or operation. Activity sequence reaches a certain point needs to be made
Judgment, then execute one
Concurrent path.
Surpand: Indicates that every role is responsible. It can be understood as a simple combination of sequence diagrams and activity graphs.
9.
Component map (Component)
Define the functionality of a system. An important feature is that it has potential
Recessive! When processing components, you must handle
The component can be.
10.
Deployment diagram
: Mutual connection diagram of each hardware system.
11.
Pack diagram
Package a set of elements provides a namespace (namespace), and the relationship between the package can be generalized, dependent, and so on.
12. Use UML during development
Traditional Process Method: Waterfall Model: Analysis, Design, Coding, Deployment, a phase of a stage, the disadvantage is that it is not conducive to the step-by-step understanding of the problem during project development. The development process is in-depth and enhanced.
ways to improve:
Quick Application Engineering Guidelines (Guidelines for Rapid Application Engineering, Grapple), which is a brief introduction.
Grapple has a list of columns:
1 Requirements Gathering
A. Discover the domain process (product: Capture of steps and judgments in business processes) B. Area Wat Analysis (Product: High-level Class Maps and Talks) C. Identification Collaboration System (Product: Deployment Diagram and Software Components and Its dependency) d. Discovery System Requirements (Products: Packaps, Need
Joint Application Development Conference) E. Submit the results to customers
2 analysis (Analysis)
A. Understanding system usage (Product: A set of cases) b. Enrichment example (product: text description of each use case step) c. Refinetical graph (product: refined class diagram) E. Analytical object status Change (product: status map) f. Define the interaction between objects (products: sequential diagram and collaboration map) g. Analyze and Collaboration System Integration (Product: Detailed System Deployment Diagram and Data Model) 3 Design (Design)
A. Development and Refinement Object Diagrams (Products: Object Diagram and Event Diagram) B. Development Members (Products: Components Figure) c. Develop Deployment Plan (Product: Deployment Chart) D. Design and Development User Interface Original (Product: All use cases are completed) E. Test Design (Product: Working Products with Test Scripts) F. Starting to Preciate Documents (Products: Document Components and Developers to Develop Documents, Develop high-level structure of each document)
4 Development (developments)
A. Compile Code (Product: Code) B. Test Code (Product: Unit Test, Inherited Test, System Test, etc.) c. Building a user interface and user interface to code connection and testing (Product: Features with user interface) D. Complete document (Product: All documents)
5 deployment (deployment)
A. Preparation of Backup and Recovery Plan (Products: Backup and Recovery Plan) b. Install the final system on the hardware (Product: Safe Deployment Computer System) c. Test the installed system (product: Work products after test) D Celebration (Product: New System Generation)
13.
UML Next will introduce the simple modeling tool Visio and Rose
Use, please pay attention, ^ _ ^
14. Tiangye has original, reprint, please keep your full document, Shenzhen Nanshan Science and Technology Park 2004.12.25 18:10:00 Merry Christmas!
