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

This article mainly shows you "UML modeling in the financial management system how to apply", the content is easy to understand, clear, hope to help you solve doubts, the following let the editor lead you to study and learn "UML modeling in the financial management system how to apply" this article.

Application of UML Modeling in Financial and Accounting Management system

The rapid development of software engineering technology provides a favorable tool for the development of the information system. Integrating the new technology into the development of the original system can not only expand the function to improve user satisfaction, but also improve the work efficiency of the system. The accounting system discussed in this paper uses the new technology to reengineer on the basis of the original, and uses UML object-oriented method to model UML. First of all, the analysis of the use case of the system attempts, for the three types of users of the system, voucher entry, certificate checker, bookkeeper involved in the accounting business, the system needs to input vouchers, check, bookkeeping, print a series of processing. This process and users are interrelated and in sequence, and there is a logical relationship between them. By straightening out the business logic of these participating users, we can get class diagrams, activity diagrams and so on until we get the deployment diagram of the system.

1. Introduction

With the rapid development of information technology, e-commerce with the Internet as the core is changing the traditional business model. The emergence and development of e-commerce has a great impact on the processing of traditional accounting affairs, which is mainly reflected in that the speed and efficiency of modern information technology is much higher than that of the original manual processing, especially for the collection of massive financial data. therefore, financial information management plays a very important role in the construction of information system.

Unified Modeling language (UnifiedModelingLanguage,UML) is initiated by three world-famous object-oriented technical experts GradyBooch, JimRumbaugh and IvarJacobson. On the basis of Booch representation, OOSE method and OMT method, Unified Modeling language (UML) is a general graphical standard modeling language proposed after repeated modification. It is a standard representation of object-oriented analysis and design and integrates new ideas, new methods and new technologies in the field of software engineering. Its role not only supports the analysis and design of objects, but also supports the whole process of software development starting from requirement analysis. UML can be used to build a good model for the system.

UML includes the semantics, representation and specification of concepts, and provides models of static, dynamic, system environment and organizational structure. At the same time, UML provides two kinds of graphics for modeling, static graph and dynamic graph. In UML modeling, static diagrams include use case diagrams (UsecaseDiagram), class diagrams (ClassDiagram), object diagrams (ObjectDiagram), component diagrams (ComponentDiagram) and configuration diagrams (DeploymentDiagram), while dynamic diagrams include sequence diagrams (SequenceDiagram), collaboration diagrams (CollaborationDiagram), state diagrams (StateDiagram) and activity diagrams (ActivityDiagram). UML builds the whole model and depicts the objective world by establishing the relationship between various classes and classes, and how classes / objects cooperate with each other to realize the dynamic behavior of the system.

In order to facilitate the financial management of the school, the original accounting system is oriented to the financial management staff of the settlement center and realizes the digital management of vouchers and deposit certificates. However, due to the development and internal needs of the school, it is necessary to build a Web platform and set up access to the system, so it needs to be reengineered. This paper focuses on how to expand the functions of the original system and use UML to analyze and model the system.

two。 System modeling

2.1 functional Overview

The system redefines the system requirements under the original system and business requirements, analyzes the original system functions, and develops new functions. Table 1 shows the functional requirements of the original system. And use UML to model.

Table 1 system function sheet

Function name

Function description

Voucher processing

Entry and examination of vouchers for the same day

Account processing

Printing of rolling accounts and related reports

Comprehensive inquiry

Current account, certificate summary table, account balance schedule, account balance summary table query and print

Interest management

Modify term, demand interest rate, interest rate calculation

Report printing

Printing of profit and loss, income and expenditure, and balance sheet

Certificate of deposit management

Management of deposit accounts opened in commercial banks

System management

Maintenance of catalogue information

System maintenance

Database backup

On this basis, a new authorization management is added, which can set the authority for the voucher check, account processing, comprehensive query and system maintenance function in Table 1.

2.2 system modeling process

The modeling process is shown in figure 1. First, the use case diagram is determined according to the system function table, and then the activity diagram and class diagram are generated synchronously according to the use case to complete the development of the subsequent process.

2.2.1 use case view

The use case diagram in UML modeling (shown in figure 2) is the step from requirement analysis to final implementation in the software development process. He describes the function and usage of the system, showing who will be the relevant users, what services the users want the system to provide and the services that users need to provide for the system. It is most commonly used to describe the system and subsystems.

(1) participants in the accounting management system

The users of the settlement center (including voucher entry personnel, certificate checking personnel, bookkeeping personnel, deposit certificate management personnel, system maintenance personnel, etc.) and each kind of business personnel have been granted the corresponding operation authority.

(2) use case diagram of accounting system

The work of each type of business staff is as follows:

Voucher entry personnel: credential input

Voucher verifier: verify whether the voucher input is true

Bookkeeper: calculate whether the debit and credit is balanced in the accounting business that occurs on a single day, and deal with the bookkeeping.

System maintenance personnel: maintenance of abstracts, vouchers, subject types and authorization to users

2.2.2 activity diagram

The activity diagram in UML modeling describes the execution sequence of various activities in the system, and is usually used to describe the execution flow of each activity to be carried out in an operation. At the same time, it is often used to describe the processing flow of a use case or some kind of interaction flow, which is the state in which something is going on. Activity diagrams usually consist of activities and include descriptions of these activities. When an activity is completed, the control moves to the next activity along the control transfer arrow. The activity diagram can also easily describe the conditions of control transfer and the requirements of parallel execution, which shows the sequence of steps that make up the complex process.

Figure 3 depicts the activity diagram designed by the system based on the use case. After the user logs in to the system, the relevant operations of credentials, certificates of deposit and system management are completed according to the rights granted.

2.2.3 Class Diagram

One of the problems of system modeling with UML is to identify and divide objects and draw class diagrams. In UML modeling, most of the objects are identified according to the use case diagram and its text description. Generally, the information that needs to be analyzed and saved may be a class or object.

Figure 4 depicts the class diagram of user objects and document objects in this system, in which the operator is a parent class, and he generates such classes as deposit receipt administrator, data maintainer, voucher entry, query printer, bookkeeper, voucher checker, and so on. they all have the same static attributes, namely user name, password, campus identifier, and his subclass has its own methods and each method has a special operation on the document object.

2.2.4 State Diagram

A state diagram represents a state mechanism, representing the control flow from one state to another, consisting of a node representing the state and a straight line with arrowheads representing the transition between the state. it usually consists of state, transition, initial state, final state, and decision.

2.2.5 sequence diagram

In UML modeling, the sequence diagram is an interaction diagram that emphasizes the time sequence of messages, describes the time sequence of messages transmitted between objects, represents the behavior order in the use case, and represents the interaction as a two-dimensional graph, the vertical axis is the time axis, and time extends downward along the vertical line; the horizontal axis represents the independent objects in the interaction.

In this system, for each voucher, it is necessary to go through a series of processes such as entry, checking, accounting and printing, and they all involve three types of users. Only after these orderly processes are completed, the financial data are correct and effective. Figure 6 shows the sequence diagram of voucher processing in this system.

2.2.6 collaboration Diagram

Collaboration diagram is another way to represent interaction besides timing diagram. It models the chain between meaningful objects in interaction. In UML, collaboration diagram uses geometric arrangement to represent objects and chains in interaction, the arrows attached to the chain represent messages, and the occurrence order of messages is illustrated by the number at the message arrow.

In this system, three types of users are involved in the processing of vouchers: voucher entry personnel, certificate verifier and bookkeeper. In the whole business process, the processing of voucher documents requires the participation of these three types of users. There is a cooperative relationship between them, and figure 6 shows the cooperative relationship between them.

2.2.7 component diagram

The component diagram in UML modeling describes the various components of the software and the dependencies between them. It can be used to show the dependencies between components during compilation, linking or execution, as well as the interfaces and invocation relationships of components. It is one of the two diagrams for modeling the physical aspects of OO systems, which usually contains three elements: components (Component), interfaces (Interface) and dependencies (Dependency).

In view of the above analysis, the main functional modules of the system are designed as follows: first, users log in to the system to set parameters according to the session read rights, and access to the corresponding functional interface, and then complete their respective business to deal with. Figure 8 describes the components that make up each function for the function of the design.

2.2.8 deployment diagram

In UML modeling, deployment diagram is also called configuration diagram, implementation diagram, which is used to describe the physical topology of system hardware and the software components executed on this structure. It is one of the two diagrams for modeling the physical aspects of object-oriented systems. It can show the topology and communication path of computing nodes, and the software components running on nodes. It is often used to help understand distributed systems.

Figure 9 depicts the deployment structure diagram of the system based on MVC architecture. The user browser as the view display layer, the WEB server as the business layer, contains control and business logic, and the database interacts with the WEB as the data layer.

At the same time, the related functions of forward engineering of UML development tools can be generated by the model. The code for the binding function shown in figure 10 shows the invocation relationship between the various program modules.

These are all the contents of the article "how to apply UML Modeling in Accounting Management system". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.