Design of dining card System Based on UML

Design of dining card System Based on UML

SummaryUML is an object-oriented visual modeling language. This article briefly introduces the basic functions and design ideas of the dining room dining card system, combined with this example, the system development in the application field based on UML and the internal relationship between various UML diagrams are explored. The system development process based on UML is case-centered.
　
　KeywordsUML; accommodation card; Software Engineering; Object-oriented

　1 Introduction

Dining room dining card system is a computer network system that uses modern information technology and automatic control technology. Its use plays an important role in strengthening the information construction of campus logistics services and improving service quality, management level and economic benefits. In the system, each consumer has a card and registers the payment in the Management Center. The card contains the identity and balance of the consumer. When the card is inserted into the window machine, the amount on the card is displayed. The waiter presses the number key on the window machine, and the window machine automatically calculates and displays the consumption amount and balance. The management center monitors each consumption and prints statistics on the consumption.

2 System Analysis
　2.1 system functions:

(1) system information management: establishes business group archives, card user archives, and cash register archives;
(2) Card Management: account opening, change, card issuance, report loss resolution, cancellation, card supplement, recharge, and statistics;
(3) routine operations: data collection, terminal setup, report loss list, upload transactions, upload recharge, etc;
(4) business summary: the transaction data is automatically summarized, the amount is settled, and corresponding reports are generated;
Renewal query: Real-time recording of each consumption, and querying the card balance or consumption records;
Guest System Maintenance: data backup, data recovery, port settings, Administrator information, and password and permissions;
⑺ Statistical Report: provides summary and detailed reports on Meal cards, dining data of window machines, and blacklists;

　2.2 specifications:
(1) Data Transmission adopts encryption and verification to improve security and reliability, and the consumption records are uploaded in real time;
(2) into the accounting mode when the fault occurs. The consumption records are stored in the memory and can be uploaded to the database;
(3) The consumption report can be flexibly set and queried by day, month, year, or a certain period of time or department;
(4) The consumption system has detailed records for each operation of the system operator, which facilitates query;
⑸ The non-local cards are displayed with special prompts to ensure the security of the system;

2.3 Data Description
(1) database description
It mainly involves consumer accounts and business window accounts. Figure 1 shows the E-R diagram of the system, reflecting the storage data requirements of the system.
　　
(2) Data Flow Diagram

The main process of the system is to interact between consumers, service groups, and systems. Figure 2 shows the data flow diagram of the system.

　

(3) operation requirements
Software: includes the Service Center interface and Pos display interface. The former is based on convenient operations and relatively complete information. The latter must be simple and clear, and the report format should be subject to the requirements of logistics management.

Hardware: communicate with 485. The POS of the window is connected to the 485 interface card at one end of the network cable. The serial port is connected to the computer serial port at the other end of the 485 card, and the rechargeable server is connected to the computer serial port and keyboard interface at the auxiliary connection line.

　3. UML modeling
3.1 Introduction to UML

Unified Modeling Language (UML) is a standard language for business and software application modeling. It is applicable to various software development methods, various stages of the software life cycle, various application fields, and various development tools.

When designing a system, describe the requirements first. Then, create a static model of the system based on the requirements to construct the structure of the system. The third step is to describe the behavior of the system. The models created in step 1 and Step 2 are static, including the use case diagram, class diagram, object diagram, component diagram, and configuration diagram. The model created in step 3 consists of four diagrams, namely the state chart, activity diagram, sequence diagram, and ing diagram. It is a dynamic modeling mechanism of UML.

3.2 use UML to build the model of the system
(1) system use case diagram

The use case diagram is called a model diagram of system functions observed by participants and external users. Figure 3 shows the use case of the system. It consists of three binary Association items, that is, the management items of the card between the consumer and the system server, the consumption items between the stored-value card and the cash register, and the settlement items between the system server and the waiter. The entire system is attended by consumers, administrators, and waiters.
　
(2) system sequence diagram
A sequence chart shows the dynamic cooperative relationship between objects. It emphasizes the order in which messages are sent between objects and displays interactions between objects. In the system, the system server is active. It manages related items and other categories, and carries out route tracking from the objects related to system servers, stored-value cards, and cash registers, discover various message connections in the system. Use the sequence diagram in Figure 4 to describe the consumption case in more detail.
　 　
(3) system deployment Diagram
The deployment view describes the arrangement of running component instances on node instances. A node is a group of running resources, such as computers, devices, or storage. The deployment view is expressed in a deployment diagram. Figure 5 shows the components in the system and the components contained in each node.
　
(4) Modeling stages and related UML Structures
The entire process of UML modeling can be divided into three stages: Conceptual modeling, logical modeling, and physical modeling. Concept-level modeling is used in the demand analysis stage. It is mainly represented by the use case diagram, object diagram, and activity diagram. Logic-level modeling is used in the analysis and preliminary design stages, it is mainly represented by class diagrams, sequence diagrams, and state diagrams. Physical-level modeling is used for detailed design stages. It is mainly represented by class diagrams, database design models, DDL scripts, component diagrams, and configuration diagrams.
　
The system simply provides the corresponding legends for the three phases. In the physical modeling stage, after understanding the interaction between the system and the database, the designer can prepare for turning to the data model, map the class to the table, map the attribute to the column, and map the type to the data type, checks the relationship between systems analysis and database design to avoid database design and application system disconnections.

　4 Conclusion
From the whole system design process, we can see that UML, as an industrial standard in the field of object-oriented modeling, has a huge advantage in the design process of software systems. Its models help developers better understand business processes and build more reliable and complete system models. This allows users and developers to have the same understanding of the problem description to reduce semantic differences and ensure the correctness of the analysis.

　5 References
[1] Duan PeiTong, Wang yihuai. Analysis and Design of Campus Card Management System Based on UML [J]. Journal of Liaocheng University, 2005 (1 ).
[2] Wang Linlin, Hua qibing. Mis Analysis and Design Method Based on UML [J]. Computer Science, 2002 (4 ).
[3] Yu Lei. Application of Unified Modeling Language in small information system design [J]. Computer Engineering, 2002 (7 ).
[4] Yan Weizhong, Ma Zhiyi, translated. UML User Guide [M]. Beijing: Machinery Industry Press, 2003.9-12.
[5] Qiu zhongpan. UML and rational rose2002 from entry to mastery [M]. Beijing: Electronics Industry Press, 2002.8-16.
[6] Wendy bogge. UML with rational rose from entry to proficiency [M]. Beijing: Power Industry Press, 2000.