Rebuilding billing methods

First, let's talk about the naming rules. For Class Diagrams, object naming and parameter naming rules

 

Use Pascal case

 

: All first letters are in upper case and other letters are in lower case.

 

For the data access layer: the class name is followed by the Dal. Note: No Dao exists in. net, and Dao appears in Java. Indicates a data access method.

 

Business logic layer: Add BLL after the class name. If the class name is particularly long, use the abbreviation, but it must be noted in the document. Full name and meaning

 

Page layer: the class for pages in SAP. You do not need to add a UI prefix or suffix.

 

Entity layer: adds entity to the end of the entity layer. If the object layer is called as a parameter in other methods, the parameter is prefixed with lowercase en.

 

Long, abbreviated, but must be noted in the document.

Interface naming guide:

 

Use Pascal case

 

Add "I
"

 

 

Parameters

 

The parameter uses camel case and can be abbreviated

 

 

Attribute

 

Use Pascal case

 

Field

 

Private, proteced use camel case

 

These specifications must be observed, otherwise they must be modified back and forth. The trouble is a problem.

 

To name a class, you need to know the meaning of the class. Otherwise, the class will not be named after a long time, and you must add comments.

 

For the interface class diagram, the method is for the form control method, all only simple operations, for naming is to use camel name.

 

Use case diagram

 

The Use Case chart is based on every function of the system. Do not use the frm name for all names.

 

Package Diagram　

 

The relationship between a package graph is to be drawn. Of course, a package graph can also be nested.

 

 

Relationship between class charts in a package chart

Such as the relationship between layer B and layer D. For this system, adding a link is unnecessary, but complicated.

Of course, you can add the interface implementation relationship.

 

For example

 

 

 

For the Sequence Chart

 

Used to describe the behavior of a use case, implement a user, and complete modeling of system behavior

 

Strict requirements

 

The user role, each class used, and the name of each class object are all instantiated objects in the code, corresponding to their names, so the name

It is essential and appropriate.

Annotations cannot be discarded. The functions, operations, and interfaces of each class are described in many ways.