SummaryA uml modeling method is proposed to simplify requirement analysis and system design. The system requirements are expressed in the use case diagram, and the structure logic and behavior logic of the system are expressed in the design class diagram and collaboration diagram, the requirement analysis, system design, and modeling process concepts are discussed to achieve seamless connection between requirement analysis, information encapsulation, data abstraction, design, and coding. This scheme has been successfully applied in the demand analysis and design phase of the development of the B/S structure foreign expert information management system. KeywordsUnified Modeling Language; Object-oriented; B/S; Management Information System 0 Introduction The object-oriented software analysis and design (OOA & D) method obtains the OO (object-oriented) model. The OOA & D method starts from the model, it is the process of identifying and refining objects, and the development process is the process of continuous iteration [1]. Concise and accurate modeling is the key to grasp the complex system and is an important core part in the development of an excellent system. Its purpose is to communicate the structure to be designed with the behavior of the system, visualization and control of the system architecture, modeling can better understand the system being constructed, and provide opportunities for simplification and reuse. Therefore, object-oriented analysis and design should begin with modeling. Under the guidance of Rational Unified Process, this article applies the object-oriented design method to B/S-structured software systems, use the Rational Rose tool to complete the UML modeling of the B/S structure information management system. Through this UML-based cohesive and Iterative Modeling Design, the logic and framework structure of the system are clearly presented, design a B/S Mode System Modeling solution. Practice has proved that using this solution can effectively control the requirements and technical risks of the management information system, and greatly shorten the development cycle, this makes the developed system powerful, easy to maintain, and scalable. 1 Introduction to UML (Unified Modeling Language) and RUP (Unified Software Process) 1.1 Introduction to UML The Unified Modeling Language (UML) integrates the basic concepts in booch, OMT, and OOSE methods. It is an international standard modeling language and a product of the development of object-oriented analysis and design methods, generate sketch similar to those of other long-term technical disciplines. UML has unified semantics and Symbol Representation, which can make the project rooted in a mature standard modeling language, which can broaden the application scope of the software system and improve its flexibility. UML is a common visual modeling language used to describe, visualize, construct, and establish software systems. UML integrates the basic concepts and advantages of many object-oriented development methods with consistent graphical representation and semantics. At the same time, many UML tools have emerged, which can well support software development, for example, the UML development tool Rational Rose provides a smooth transition mechanism from Object-Oriented Analysis and Design (OOA and OOD) to Object-Oriented Programming (OOP, fully embodies the object-oriented software engineering philosophy [2]. 1.2Static and dynamic modeling mechanisms of UML In applications, when using object-oriented technology to design a system, first, describe the requirements, and then create a static model of the system based on the requirements to construct the system structure. The models created in these two steps are static, including the use case diagram, class diagram (including package), object diagram, component diagram, and configuration diagram, it is a static modeling mechanism of the standard modeling language UML. The third step is to describe the behavior of the system. The created model can be executed, or the time sequence status or Interaction relationship during execution. It consists of four diagrams, including status chart, activity chart, sequence chart, and ing. It is a dynamic modeling mechanism of the standard Modeling Language (UML. UML includes static modeling mechanism and Dynamic Modeling Mechanism. Two types of static structures define the attributes and operations of important objects in the system and the relationships between these objects; dynamic Behavior defines the time characteristics of the object and the mechanism by which the object communicates with each other to complete the target task. UML defines nine types of diagrams for system modeling, which are divided into two types: static structure diagram and dynamic behavior diagram. 1) static structure diagrams can be used to visualize, detail, construct, and document the static aspects of the system. We can regard the static aspect of the system as a representation of the relatively stable skeleton of the system. It consists of the layout of classes, interfaces, collaboration, components, nodes, and other things. The structure includes: Class digraphs describe the static structure of classes in the system. They define the internal structure of classes in the system and the relationships between classes, and are used to capture information and objects in events; object digraphs (Object digraphs) are class instantiation diagrams, and component Diagrams (Component digraphs) are described.ProgramCodeDeployment divisor describes the physical structure of software and hardware in the system, which is used to capture the deployment relationship between system hardware and software components. 2) Dynamic Behavior graphs are used to visualize, detail, construct, and document the dynamic aspects of the system. We can regard the dynamic aspect of the system as a representation of system changes, which are composed of Time-changing information flows and physical movements of components on the network. The behavior diagram includes: Use case diagram describes the functions of the system from the user's perspective, and points out the executors of each function, indicating the relationship between the executors and the provided use cases; sequence diagram) describes the action collaboration relationships between several objects. A collaboration diagram shows the action collaboration relationships between objects from another perspective. It can be converted with a sequence chart. In Rational Rose, a collaboration diagram can be generated from a sequence diagram. A state diagram describes all possible States and State transfer relationships of a class of objects. An activity diagram (Active digraphs) describes the execution sequence of various activities in the system. 1.3 introduction to URP URP, a unified rational process, is a software life cycle method adapted to UML and a general process framework, it can be used for different types of software systems, different application fields, different types of organizations, different functional levels, and different project scales. It is an iterative and incremental software development process based on the Modeling Language UML, an architecture-centered, case-driven, and risk-driven combination. The software development cycle is divided into four stages: initial, refinement, construction, and handover. All development work is organized around five core tasks: requirement capture, analysis, design, implementation, and testing. During the construction phase, a system is built through a series of iterative processes. Each iteration is a small project, and the required use cases need to be analyzed, designed, encoded, tested, and integrated.
UML Visual Modeling System |
Requirement Model |
Use case diagram and activity diagram |
Object Model |
Class diagram, object diagram, package diagram, Cooperation diagram, sequence diagram, and status diagram |
Architecture Model |
Component diagram and configuration Diagram |
The UML visual modeling system supports the entire modeling process from system requirements, system analysis to system design, as shown in table 1. In the demand analysis stage, UML can use cases to capture user requirements. Use requirement modeling to describe the external roles that are interested in the system and their functional requirements for use cases. In the analysis and design phase, the object of the problem domain is modeled through the static modeling mechanism and Dynamic Modeling Mechanism of UML to describe the attributes of the class, the relationship between classes, and the dynamic characteristics of the system. Encoding is an independent stage, and its task is to use object-orientedProgramming LanguageConverts a class from the design stage to the actual code. The UML model can also be used as a basis for testing. The same UML also supports modeling of the system architecture. 2 modeling and Design of foreign expert Management Information System The foreign expert management information system is a software system used to manage the information of foreign experts in China. Its basic task is management. It covers the information involved in various stages from applying for a foreign expert from China to leaving school, at the same time, it also manages the basic information of foreign specialized units and the basic information required by foreign experts. Through this system, we can quickly and conveniently comprehensively and scientifically manage all kinds of information from foreign universities in China, improve office efficiency, and simplify information management within departments (enterprises, in addition, it further increases the degree of information exchange within departments (enterprises), achieves data sharing, and makes management work more standardized, scientific, and comprehensive. B/S structure management information systems are often complex and highly dynamic. By using UML modeling technology and RUP Software engineering technology, the development process can be smoother and the system with B/S structure can be easily maintained in the future. 2.1 users and Roles System Analysis requires users to be exposed, and the system must be able to control different user roles and permissions. By classifying users and understanding their needs, you can determine security mechanisms, functional limitations, user interface groups, and requirements for specific content. Figure 1 shows several groups of different system users (called actors in UML, that is, participants ). The common user type ("common user") is located at the top of the graph. The Hollow arrow indicates the generalization (generalized) relationship, indicating that the "user" can be divided into two types of users: registered users, unregistered user. The selfish characteristics of registered users and unregistered users are described in the corresponding participants. In this example, registered users can be divided into three types: foreign experts, administrators, and administrative staff. The system should handle these users differently. 2.2 requirement model The process of requirement modeling is the process of obtaining use cases. The acquisition of use cases is one of the main tasks in the demand analysis phase, and is the first task to be done. Most of the use cases will be generated in the requirement analysis phase of the project, and more use cases will be found as the work goes deeper, which should be added to the existing use cases in a timely manner. Each case in a case set is a potential requirement. The modeling of system requirements is implemented through the use case diagram of UML. The Use Case Model describes the system functions that the external executor understands. First, it describes the functional requirements of the system to be developed. Second, it regards the system as a black box and understands the system from the perspective of external executors. Third, it drives the development work in various stages after requirement analysis, not only ensures the implementation of all functions of the system during the development process, but also is used to verify and detect the system developed, this affects all stages of development and various UML models. Figure 2 shows the case model for foreign experts to manage information systems. The ellipse in the figure is a use case, indicating a typical interaction between the user and the computer. The graphical representation of the villain is the performer, indicating the role of the user in the system, the line between the use case and performer indicates the association between the two. The system involves many different modules. To describe the functional requirements of the system, you only need to divide the system into multiple modules to describe their functional requirements. This requires multiple use case views. Eight use cases are listed in the figure, management of systems in China, management in China, off-China Management, file management, statistical reports, external recruitment requirements, information management of external recruitment units, and user management. The figure also lists three executors, representing foreign experts, administrative staff, and senior users (system administrators ). The use case diagram allows the designer to focus on the functions of the system at the initial stage of system design, rather than the specific implementation of the system. For complex systems, you can add activity diagrams to display activity flows and concurrent behaviors, making the requirement model more complete. 2.3 System Function Analysis and Design In order to make the system design express in the form of structure, organization and code reuse, the design and planning of the system should overlap with the analysis stage. The demand is constantly evolving, and the design itself will also promote the development of the demand (and vice versa ). In the modeling design of the management information system functions of foreign experts, the following three issues should be concerned: the expression of business objects, the implementation of business services, and the organization of user interfaces.
(1) representation of the business object. In the management information system of foreign experts, the business objects are mainly the representation of databases and data entity classes. In modeling of the management information system of foreign experts, the basic information of foreign experts and the static models of the participating academic activity modules and academic activity modules can be represented by Class Diagrams (3 ), (Only some key information is listed in the figure.) The Hollow arrows represent the generalization relationship between these entity classes and common entity, and inherit the common methods of common entity, the private attributes and methods of these entities are not displayed in this figure. The common arrows indicate the associations or dependencies of object classes. (2) Implementation of business services. The implementation of business services requires the implementation of various business rules and logic, such as information entry, modification, deletion, and query of the academic activity module. The information input, modification, deletion, and query of each module are similar to the implementation of business rules and logic. There are not many rules to follow. Use UML for business service modeling. You can use UML sequence diagram, state diagram, and activity diagram. This part of work is usually done through a series of interactions between classes. To describe the system on a more dynamic level, UML provides many other types of diagrams. For B/S system design, the plot (scenario digram) is particularly useful. For example, how the page cooperates with the code that verifies the user identity. A plot is divided into two types: A collaboration diagram and a sequence diagram ). The UML modeling tool, Rational Rose, can generate a sequence diagram from a collaboration diagram, or vice versa. Figure 4 shows the sequence diagram of the Information entry function of the academic activity information module in the foreign expert management information system. It can generate a collaboration diagram directly. (3) Organization of the user interface. The User Interface layout chart can help organize the layout structure of system pages, files, and services. In UML, you can use a component diagram or a class diagram to create a model for the organization of pages and files. In this system, class diagrams are used to model the interface, and the Page Structure and various business services are bundled to different regions. 2.4 Application Deployment Plan In UML, the system architecture is completed using a deployment diagram. Application Deployment planning is useful for planning the entire B/S system. It identifies an effective way to plan and organize application deployment. It can also be used as a mode in multiple B/S systems. 2.5 code implementation After modeling, developers can use the Rational Rose tool to generate a program code framework and modify and supplement the code framework to form the complete code, you can also generate a UML Model Based on the code. This ensures the consistency between the model and the code. Tests must be carried out throughout the project cycle, and the models created at each stage must be tested to ensure the quality of development and reduce development risks. 3 conclusion Unified Modeling Language (UML) is an epoch-making achievement in the international software engineering field. It is applicable to describing any type of system with object-oriented technology and to different stages of system development, test and maintenance after Requirement Specification Description and system completion. The scale of software systems is growing and the complexity is constantly increasing. The iterative development mode of RUP can reduce risks and adapt to the changing needs. In the modeling and development of foreign expert management information system, the author applies UML to various stages of system development, and establishes the system requirement model, static model and dynamic model. This UML-based iterative development method has unparalleled advantages over traditional development methods. UML modeling fully targets the system design and implements information encapsulation and data abstraction. UML can help people easily construct a B/S structure system model. To a certain extent, the software development automation is realized, the seamless connection between design and coding is realized, and the efficiency and quality of software development are improved. |