Patent Application
20140337710
Embodiments of the present disclosure relate to data processing technology, and particularly to an electronic device and a method for processing data using the electronic device.
During a software developing process, an Unified Modeling Language (UML) model of a flow represented by characters and tables, is displayed on a display device for users. However, some specified data of the flow cannot be seen on the display device, for example, the users may not know who executes flow nodes of the flow.
The present disclosure, including the accompanying drawings, is illustrated by way of examples and not by way of limitation. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean “at least one.”
In general, the word “module,” as used hereinafter, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, for example, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware. It will be appreciated that modules may comprise connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays or processors. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable storage medium or other computer storage device.
The system 10 can dynamically load data of a flow on the display device 13, and can display a process flow diagram using graphics on the display device 13 for viewers.
In one embodiment, the storage device 11 may include various types of non-transitory computer-readable storage medium, such as a hard disk, a compact disc, a digital video disc, or a tape drive. The display device 13 may display images and videos, and the input device 14 may be a mouse or a keyboard for input.
In 300, the storing module 100 stores data of flow nodes of a specified flow in the storage device 11. In some embodiment, before storing the data of the flow nodes in the storage device 11, the storing module 100 checks whether the data of the flow nodes of the specified flow is following predetermined rules. The flow nodes include a start node, an end node, and branch nodes. The data of the flow nodes may include, but is not limited to, identifications (IDs) of the flow nodes and tags of the flow nodes. The predetermined rules determine that each of the flow nodes has an ID, and the tag of each of the flow nodes is integrated.
When the data of the flow nodes of the specified flow is following the predetermined rules, the storing module 100 stores the data of the flow nodes in a text file, an Extensible Markup Language (XML™) file, an Access™ database, Structured Query Language (SQL™) database, or an Oracle™ database of the storage device 11. When the data of the flow nodes of the specified flow has not following the predetermined rules, the storing module 100 does not store the data of the flow nodes. In some embodiments, the storing module 100 may output a prompt to indicate that why the data of the flow nodes of the specified flow has not following the predetermined rules. Based on the prompt, people can amend the data of the flow nodes until the data of the flow nodes can be stored.
An example of data of flow nodes of a flow is shown in
In 301, when the specified flow is executed in the electronic device, the acquiring module 101 acquires the data of the flow nodes of the specified flow from the storage device 11. The data of the flow nodes is loaded in a memory of the electronic device 1.
In 302, the determination module 102 determines graphics data and attribute data from the data of the flow nodes. In some embodiments, the graphics data includes, but is not limited to, a start node, an end node, branch nodes, and flow lines. For example, a character string “<Start> . . . </Start>” represents data of the start node, a character string “<End> . . . </End>” represents data of the end node, a character string “<Node> . . . </Node>” represents data of a branch node, a character string “<line> . . . </line>” represents data of a flow line. The attribute data includes a name of the flow node (e.g., second check), a user who executes the flow, contact information of the user and a deputy of the user.
In 303, the creating module 103 creates a first display area on the display device 13 for displaying the graphics data, and creates a second display area on the display device 13 for displaying the attribute data.
In 304, the output module 104 loads the graphics data on the first display area and generates a process flow diagram based on the graphics data. The process flow diagram includes flow nodes, flow lines and other graphics data. The output module 104 displays the process flow diagram on the first display area by a way of “<div>start node information</div><div>branch node information</div><div>end node information</div>”. For example,
In 305, when a specified flow node is triggered, the output module 104 loads attribute data of the specified flow node in the second display area. As shown in
In other embodiments, the creating module 103 may create a single display area. The output module 104 can display the graphics data and attribute data in the single display area.
It should be emphasized that the above-described embodiments of the present disclosure, including any particular embodiments, are merely possible examples of implementations, set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) of the disclosure without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2013101723643 | May 2013 | CN | national |
