Shulou(Shulou.com)06/03 Report--

This article shares with you the content of sample analysis of object-oriented design models in web development. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Many of the elements of the design model are UML diagrams used in the analysis model. The difference is that these diagrams are refined and refined into part of the design, and provide more special details related to the implementation, highlighting the structure and style of the architecture, the components existing in the architecture, and the interface between the components and the outside world.

1. Object-oriented design model

Design modeling tasks:

Architecture design

Package and subsystem design

Class design

Persistent design

(1) component diagram

(2) deployment diagram

(3) State machine diagram

2. Architecture design

(1) 4x1 Architecture View

Logical view, development view, process view, physical view, scene view

(2) logical view design

The logical structure of the software to support functional requirements.

(3) process view design

The process architecture of the software, for non-functional requirements.

The tasks that make up the process are separate control threads, and the software is divided into a set of tasks that are independent of each other. (deployment diagram)

(4) develop view design

The development architecture of the software, that is, how to decompose it into implementation units, is the basis of requirements allocation and the basis of the development organization structure.

As shown in the horizontal split scheme in figure 7-7, six packages are assigned to six development groups and are at different levels of the architecture, and the development group can assign personnel according to the technical level.

The following vertical division scheme allocates tasks in multiple development groups according to business logic, and each development group must have comprehensive development capabilities.

(5) physical view design

The physical architecture of the software, aiming at the availability, reliability, scalability and so on of non-functional requirements. (deployment diagram)

(6) scene view design

The scenario is an example of a use case that organically ties together the four views. It is the driving force for discovering architectural elements and plays the role of verification and illustration.

3. Principles of package design

Reuse-release equivalence: reuse granularity equals release granularity

Common reuse: all classes in the package are reused together

Common closure: all classes in the package are closed to changes of the same type

Acyclic dependency: acyclic dependency structure between packages

Stable dependency: a package should rely on a package that is more stable than it is

Stable abstraction: the most stable package is the most abstract, and the unstable package is the concrete package.

4. Class design

Single responsibility, Lee's replacement, dependency inversion, interface isolation, development-shutdown principle.

5. Persistence design

(1) solid object modeling

(2) Database design

(3) persistence framework.

6. Object-oriented design process

Identify design elements

Determine the architectural style and design the overall structure

Component level design

7. Subsystem design process

(1) define the responsibility of the subsystem, that is, the definition of the interface

(2) determine the elements in the subsystem through the assignment of responsibilities, and realize the responsibilities by components and other elements.

(3) Design the elements in the subsystem, that is, class design (static structure and dynamic structure)

(4) determine the dependency relationship between subsystems.

8. Steps of component-level design

Update Use-case Realization

Subsystem design: design interaction diagrams and VOPC class diagrams for each operation of each interface, similar to the system design, that is, Use case realization

Class design:

(1) create a design class: map an analysis class to a design class

(2) define operations: achieve a single responsibility

(3) definition method: describe the internal implementation of the operation.

(4) define the state: describe the influence of the state of the object on the behavior, and associate the properties of the object with the operation.

(5) define attributes: including the parameters in the method, the state of the object, etc.

(6) define dependency: existential relationship between classes, non-structural relationship.

(7) definition of association: refinement of association relationships, including aggregation and combination, orientation, multiplicity, and association classes

(8) form the specification book of the design class.

9. Time sequence diagram

Extract all kinds of events from the use case event flow and determine the sending object and receiving object of the event interaction behavior, and use the sequence diagram to represent the event sequence and the relationship between the event and the object.

10. State machine diagram

The state diagram depicts the relationship between events and the state of objects. When an object accepts an event, the resulting state change is called a transition.

A state diagram is used to describe the behavior of a class of objects, which determines the sequence of states derived from the sequence of events. Consider only those classes that have important interactive behavior.

The incoming event in the event tracking graph is used as a directed edge (that is, the arrow line) in the state diagram, marked with the event name. The interval between two events is a state.

The arrow line in the event tracking diagram is the behavior that the object represented by this vertical line does when it reaches a certain state (often an event that causes another kind of object state transition).

Thank you for reading! This is the end of this article on "sample analysis of object-oriented design models in web development". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.