CN114443006A - Software design method based on template self-adaptation - Google Patents

Abstract

The invention relates to a software design method based on template self-adaptation, which belongs to the technical processing field of software design and comprises template management, software self-adaptation configuration and data verification; describing a software interface function through an XML Schema file, using Config. XML to combine and call the XML Schema to form a complete software function, and using the XML Schema file and the Config. XML file as templates to manage; the self-adaptive configuration of the software is realized by analyzing the Config. XML file as a template and the called XML Schema file thereof, and the function and display of the software are dynamically adjusted; verifying the data XML file obtained by the software through the corresponding XML Schema file, and returning a verification result; the invention can improve the software development efficiency, reduce the maintenance cost and simplify the data verification process.

Description

Software design method based on template self-adaptation

Technical Field

The invention belongs to the technical field of software design.

Background

The existing software adaptive design method and configuration technology mainly write the attributes of interface elements into a configuration file, and set the interface elements by loading the configuration file, generally adjusting the style and layout of an interface control. Due to the adoption of the configuration file mode, when a user puts forward a modification requirement on the interface design, the source code can be modified as little as possible, and even the interface can be adjusted only by modifying the configuration file.

With the acceleration of software iterative update, the software function is divided into a plurality of modules, and because the maturity of module development is improved, the existing modules in the previous software can be reused when different software is developed, and new software is developed in a combined calling mode, so that the development cost is reduced, and the development efficiency is improved. However, the adaptive loading of software functions cannot be realized by simply modifying configuration files, because the relationship between the module and the main frame and the relationship between the module and the module need to be described from several angles, the configuration files commonly used in the existing research cannot define the functional relationship of the software, and the adaptive configuration files need to be integrated and managed to form a template, so that the definition of the software functions is realized through the template. Meanwhile, due to different product models, even though software interfaces used by the same functional module have great differences, in order to enable the same software functional module to meet different interface requirements, the interfaces used by the functional module need to be configured adaptively, and the definition of the interfaces also becomes a part of the adaptive template. Besides, the interface is also an important function of the interface, including the value range of input parameters, illegal character judgment and the like, in addition to the style and layout, and the existing research is lack of attention in this respect.

Disclosure of Invention

In order to solve the problem of development cost increase caused by software modification, reduce software development time and improve software development efficiency, the invention provides a software design method based on template self-adaptation.

The invention provides a software design method based on template self-adaptation, which comprises the following contents:

the method comprises template management, software self-adaptive configuration and data verification;

the template management adopts an XML Schema file to describe the functional attribute of the software, the XML Schema file is combined and called through a Config. XML file to form a complete software function, and the XML Schema file and the Config. XML file are used as templates for management; the XML Schema file description comprises software interface frame description, data object description and control style description; the XML file comprises calling XML Schema file information, interface calling information, function calling information and interface calling information; wherein, the XML Schema file defines the coding format of software characters, interface display characters, the type and the style layout of interface controls; defining an interface call relation, an interface layout, an operation authority, a function enabling relation and a software interface in a Config.xml file;

the software self-adaptive configuration dynamically adjusts the function and display of the software by analyzing a Config. XML file and an XML Schema file called by the same;

and the data verification verifies the data XML file obtained by the software through the corresponding XML Schema file, stores the XML file passing the verification, and returns error information to the XML file failing to pass the verification.

Further, the parsing the config.xml file includes:

step 1: loading a Config. XML file, traversing an XML Schema file tag, inquiring a corresponding XML Schema file, analyzing the XML Schema file and generating a corresponding software interface;

step 2: traversing the style labels, setting the software interface at a corresponding position, and setting the interface visualization;

and step 3: traversing the data type label and setting the data type generated by the interface;

and 4, step 4: traversing the function authority labels, and setting the operation authority for adding, deleting, modifying and checking the software interface;

and 5: traversing the function definition tag and setting the function of the software configuration;

step 6: traversing the interface definition tag, and setting interface information used by the software;

the steps of analyzing the XML Schema file are as follows:

step 1-1: the read current XML Schema element obtains DOM tree node information corresponding to the XML Schema element;

step 1-2: judging the XML Schema element type, and generating a corresponding interface control according to the type;

if the XML Schema element type is a complex data type, the software interface generation module creates a grouping frame at the corresponding position of the interface according to the DOM tree node information obtained in the step 1-1, and sets corresponding name information for the grouping frame; turning to step 1-3;

if the XML Schema element type is an enumerated data type, the software interface generation module creates a drop-down list at the corresponding position of the interface according to the DOM tree node information obtained in the step 1-1, assigns values to the drop-down list and turns to the step 1-4;

if the XML Schema element type is a simple data type, the software interface generation module creates an edit box at the corresponding position of the interface according to the DOM tree node information obtained in the step 1-1, sets corresponding style information for the edit box, and turns to the step 1-4;

step 1-3, if the DOM tree node corresponding to the current XML Schema element has unprocessed child nodes, returning to the step 1-2; otherwise, entering the step 1-4;

step 1-4, if the DOM tree node corresponding to the current XML Schema element has unprocessed brother nodes, returning to the step 1-2; otherwise, entering the step 1-5;

step 1-5, if the DOM tree node corresponding to the current XML Schema element has an unprocessed father node, returning to the step 1-4; otherwise, finishing the interface generation and finishing the step 1.

The invention adopts an XML Schema file to describe the interface attribute of the software, combines and calls the XML Schema through a Config. XML file to realize the function configuration, manages the XML Schema file and the Config. XML file as templates, performs the software self-adaptive configuration according to the templates, and verifies the data through the XML Schema file. The invention carries out the self-adaptive configuration of the software interface and the function through the template, and verifies the data file through the XML Schema, thereby improving the software development efficiency and reducing the software development cost.

Drawings

FIG. 1 is a general flow of parsing an XML Schema.

The interface in the software of fig. 2 generates a depth-first traversal.

Detailed Description

The invention provides a template self-adaptive-based software design method, which adopts an XML Schema file to describe the interface attribute of software, combines and calls the XML Schema through a Config. XML file to form a complete software function, and manages the XML Schema file and the Config. XML file as templates; the self-adaptive configuration of the software is realized by analyzing the Config. XML file and the called XML Schema file thereof, and the function and the display of the software are dynamically adjusted; and verifying the data XML file obtained by the software through the corresponding XML Schema file, storing the XML file passing the verification, and returning error information to the XML file failing to pass the verification. The XML Schema file description used by the template comprises software interface frame description, data object description, control style description and the like, and the Config. XML file used by the template comprises XML Schema file information, interface calling information and the like, function calling information, interface calling information and the like. The software framework description describes the document version information through an XML version attribute in an XML Schema file, an encoding attribute describes a character encoding format, a title attribute describes an interface title, and a pattern attribute describes interface style information. The data object description defines simple type data object information by the < xs: simpleType > tag in the XML Schema file, the < xs: enumeration > tag defines enumerated type data object information, the < xs: complexType > tag defines complex data object information, and the < xs: sequence > tag defines the drain location of the data object. The control style description is defined by < style _ style > in the XML Schema file, and the attribute description format is similar to the definition of CSS in HTML language, including the style, font information and the like for defining the control. XML file call XML Schema file information calls XML Schema file Name through < Name > tag description in config.xml, < Visible > tag description Interface visually displays whether a user can be displayed, a < Location > tag description Interface discharge position, an < Enable > tag description part operation authority condition of the user on data, a < Type > tag description data Type, a < Function > tag description software Function, and an < Interface > tag description Interface definition.

Specifically, the method comprises three parts of template management, software self-adaptive configuration and data verification:

a first part: template management

XML file description used by the template comprises software interface frame description, data object description, control style description and the like, and a Config. XML file used by the template comprises XML Schema file information, interface calling information and the like;

describing the document version information through an XML version attribute in an XML Schema file by a software framework, describing a character coding format by an encoding attribute, describing an interface title by a title attribute in xmlns, describing interface style information by a pattern attribute in xmlns;

the data object description defines simple type data object information through an < xs: simpleType > tag in an XML Schema file, the < xs: enumeration > tag defines enumerated type data object information, the < xs: complexType > tag defines complex data object information, and the < xs: sequence > tag defines the discharge position of the data object;

the control style description is defined by < style in XML Schema file, the attribute description format is similar to the definition of CSS in HTML language, including the style and font information of the control;

XML file call XML Schema file information calls XML Schema file Name through < Name > tag description in config.xml, < Visible > tag description Interface visually displays whether a user can be displayed, a < Location > tag description Interface discharge position, an < Enable > tag description part operation authority condition of the user on data, a < Type > tag description data Type, a < Function > tag description software Function, and an < Interface > tag description Interface definition.

And the template management displays the uploaded detailed information of the schemas and the Config. xml in a list form through a management interface, and provides an adding, deleting, modifying and checking function for the schemas and the Config. xml files.

During database design, the data is integrally designed into a CLOB type and stored in a database (the system adopts an ORACLE database, the CLOB type is a large string type data supported in the database software and used for storing XML documents), and the design and implementation of a data table are shown as table 1:

table 1 design of data storage data table

Serial number	Name of field	Data type	Key with a key body	Description of the invention
					1	METADATA_ID	NUMBER	Main key	Data ID (self-increment)
2	DATA_NO	VARchar2(100)		Corresponding full-pulse data or intermediate-frequency data path
					3	REGISTER	NUMBER	External key	Registrant (reference user)
4	AUDITOR	NUMBER	External key	Auditor (refer to user)
					5	XMLDOC	CLOB		XML document
6	REGIST_TIME	DATE		Registration time
					7	VERIFY_TIME	DATE		Time of audit
8	STATUS	NUMBER		Audit status
					9	XSDFILEPATH	VARchar2(50)		schema type
10	INPUTCODE	CLOB		Interface code
					11	E_ID	NUMBER		ID of last element
12	B_ID	NUMBER		ID of last plus button
					13	TEMP_SAVE	NUMBER		Whether or not it is a temporary storage

When the data is stored, the corresponding file path is stored, the data management software can inquire the position of the corresponding full data file through the data, and the full data file can be read and displayed in a visual playback mode.

A second part: software adaptive configuration and interface generation

The XML Schema is a template for controlling the style of the XML document, namely a template for data entry interface style and a template for verifying the format of the data entry interface style, which is established according to the requirements of a user. The software needs to generate a software interface according to the element constraint in the designed Schema by analyzing the Schema.

The XML schema is also an XML document, the structure of the XML schema is a tree structure, the root node of the XML schema is < xs: schema >, and the following three child nodes are provided: < xs: complexType >, < xs: simpleType > and < xs: element >, which are used to define the complex type, the simple type of the element and the element itself, respectively.

Schema > represents the root node of an XML Schema, all schemas have the element represented by this tag as the root node, and all elements are children of this node. There are four attributes in this element: xs represents a namespace referenced by the element; the elementary FormDefault is used for defining whether an element appearing in the XML document needs to refer to a namespace prefix or not, and the qualified indicates that the namespace prefix needs to be referred to; AttributeFormDefault is used to define whether attributes appearing in an XML document need to reference a namespace prefix, and unqualified indicates that no namespace prefix needs to be referenced. The complete root node representation is as follows:

<xs:schema xmlns:xs＝"http://www.w3.org/2001/XMLSchema"xmlns:tab＝"http://www.hhu.edu.cn"elementFormDefault＝"qualified"attributeFormDefault＝"unqualified">

element nodes are represented by < xs: element > tags. There are six attributes in an element: name defines the name of the element; type defines the type of the element, and whether the content of the element is in the specification or not is verified in the future; id defines the unique designation of an element; minOccurs defines the minimum number of occurrences of an element, 0 indicates that the element may not appear in an XML document; maxOccurs defines the maximum occurrence number of an element, and unbounded represents that the element can occur countless times in an XML document; tab: TabNO is the attribute customized by the developer, and is used for defining the Tab page in which the element is typeset and referencing the customized namespace.

The element also has an embedded sub-element < xs: annotation >, which is an annotation node, and an embedded sub-element < xs: annotation >, which represents a text annotation and records annotation information by a plain text. The complete element node representation is as follows:

complex type nodes are defined with the label < xs: complexType >. It has an attribute name that defines the name of the type. Below the complex type is a sub-element < xs: sequence >, which defines the order in which the sub-elements below it appear in the XML document. The elements defined below < xs: sequence > are all sub-elements included in the complex element, and the definition of the sub-elements is the same as that of the general elements, and is not described again. The complete complex type node is represented as follows:

simple type nodes are defined with the label < xs: simpleType >. It has an attribute name that defines the name of the type. Under the simple element there is a sub-element < xs: restriction >, which is used to define the value of this simple element. There is an attribute base, which specifies the type of the simple element value, and xs string represents that the value is string type. The enumeration > defines an enumeration value list of values in a simple type, wherein attribute value represents a specific value, and id represents a unique mark of the enumeration value. The complete simple type node representation is as follows:

since elements of the same name can appear repeatedly and they can appear under different parent elements, an interface can only be created by finding the depth-first traversal order of each element in the DOM tree.

An interface generation depth-first traversal algorithm in data management software is shown in fig. 2, and first obtains an element name and an id number of an element to be searched, then performs initialization, assigns a variable element _ NO storing a traversal sequence number to-1, and assigns a count variable count to-1. Then, the first Tab node is found and is taken as the root node to perform depth-first traversal. If the element with the same name is found, the count is added with 1, if the element with the same name and the same id is found, the uppermost layer is returned, and the traversal sequence number is returned to the position for calling the function. If the element to be searched is not found under the node Tab1, the next node Tab is found, and the operation process is the same as before. Since the element to be searched must exist in the DOM tree, the element must be found under the branch of a certain Tab node and the sequence number of the depth-first traversal is returned

The specific steps of interface dynamic generation and XML document generation are as follows:

step 1, reading an XML Schema file to a memory, and then establishing a mapping relation between an XML Schema DOM tree and a software interface in a depth-first order. Starting from the root element of the XML Schema DOM tree, the parsing module traverses each node by adopting depth first and performs corresponding operation on the nodes;

step 2, for the XML Schema elements read by the current analysis module, the software interface generation module positions the XML Schema elements to the corresponding positions in the XML Schema DOM tree;

if the element type is complexType, turning to step 3;

if the element type is simpleType, go to step 4;

if the element type is an enumeration type, turning to step 5;

step 3, a grouping frame is created at a set position, attribute information (including ID, NAME, value limit and CSS information of elements) in the Schema node is read according to an analysis module, and the attributes of the grouping frame just created are assigned and CSS information is added; turning to step 6;

step 4, generating an edit box according to the simpleType definition at the set position, assigning values to each attribute of the edit box just created according to each attribute information (including ID, NAME, value limit and CSS information of elements) in the Schema node and adding CSS information; turning to step 7;

step 5, in a set position, generating a drop-down list according to the enumeration type definition, sequentially filling the enumeration value defined in the enumeration type into each option of the drop-down list, and assigning values to each attribute of the table element just created and adding CSS information according to each attribute information (including ID, NAME, value limit and CSS information of the element) in the Schema node; turning to step 7;

step 6, judging whether the XML Schema element currently processed has unprocessed child nodes; if yes, accessing the child node, and turning to the step 2; otherwise, turning to step 7;

step 7, judging whether the XML Schema element currently processed has the next unprocessed brother element; if yes, accessing the brother element, and turning to the step 2; otherwise, turning to step 8;

step 8, judging whether the current element has a father node, if so, returning to the father node, and turning to step 7; otherwise, the second part ends;

for software, if the interface needs to be modified due to a change in the requirement, only the elements in the XML Schema are adjusted accordingly (for example, a control on the interface is added or deleted, which corresponds to adding or deleting a certain element in the Schema file; and the positions of some controls on the interface are changed, which corresponds to adjusting the positions of some elements in the Schema file), without editing the interface and even without managing various settings of the controls in the code. Thus, the modification to the interface is converted into a modification to the XML Schema.

XML files used by the template include calling XML Schema file information, interface calling information and the like, function calling information, interface calling information and the like. XML file call XML Schema file information calls XML Schema file Name through < Name > tag description in config.xml, < Visible > tag description Interface visually displays whether a user can be displayed, a < Location > tag description Interface discharge position, an < Enable > tag description part operation authority condition of the user on data, a < Type > tag description data Type, a < Function > tag description software Function, and an < Interface > tag description Interface definition.

And a third part: data validation

DOM4J is used for verification of XML documents, and an error handler is required to be created, an XML document object is loaded, and an XML Schema file used by a parser and specific attributes of the XML Schema file are set. The XML document object is then validated against the previous settings and an error result is returned.

The CLOB storage is performed in two steps, the first step is to empty the field storing the XML document object, and the second step is to store string data to the field. Before storing, however, the XML fields in the database must be put into a buffer stream, and the buffer stream is used to store the character strings to be stored into the corresponding fields in the database.

The method comprises the following specific steps:

step 1, when data is submitted, packaging the data into an XML document according to the Schema of the interface;

and 2, creating an error handler, loading the XML document object, and setting the XML Schema file used by the parser and the specific attributes of the XML Schema file. Then, the XML document object is verified according to the previous setting, and an error result is returned;

step 3, returning the verification result, mapping the verification result to each element, and defining the error mark by self;

step 4, storing the XML document into a database, which comprises the following steps:

step 4-1, setting the field of the XML document object to be null, and putting the XML field in the database into a buffer stream;

step 4-2, storing the character strings to be stored into corresponding fields of a database through a buffer stream;

if the user wants to modify the data, turning to the step 4, otherwise, ending;

and 5, regenerating an interface according to the Schema and the data filled in the interface, and turning to the step 1 after the user finishes filling.

Claims (2)

1. A software design method based on template self-adaptation is characterized in that: the method comprises template management, software self-adaptive configuration and data verification;

the template management adopts an XML Schema file to describe the functional attribute of the software, the XML Schema file is combined and called through a Config. XML file to form a complete software function, and the XML Schema file and the Config. XML file are used as templates for management; the XML Schema file description comprises software interface frame description, data object description and control style description; the XML file comprises calling XML Schema file information, interface calling information, function calling information and interface calling information; wherein, the XML Schema file defines the coding format of software characters, interface display characters, the type of interface controls and the style layout; defining an interface call relation, an interface layout, an operation authority, a function enabling relation and a software interface in a Config.xml file;

the software self-adaptive configuration dynamically adjusts the function and display of the software by analyzing a Config. XML file and an XML Schema file called by the same;

and the data verification is to verify the data XML file obtained by the software through the corresponding XML Schema file, store the XML file passing the verification and return error information to the XML file failing to pass.

2. The template-adaptive-based software design method according to claim 1, characterized in that: the parsing config.xml file includes:

step 1: XML file is loaded, XML Schema file labels are traversed, corresponding XML Schema files are inquired, the XML Schema files are analyzed, and corresponding software interfaces are generated;

step 2: traversing the style labels, setting the software interface at a corresponding position, and setting the interface visualization;

and step 3: traversing the data type label and setting the data type generated by the interface;

and 4, step 4: traversing the function authority labels, and setting the operation authority for adding, deleting, modifying and checking the software interface;

and 5: traversing the function definition tag and setting the function of the software configuration;

and 6: traversing the interface definition tag, and setting interface information used by the software;

the steps of analyzing the XML Schema file are as follows:

step 1-1: the read current XML Schema element obtains DOM tree node information corresponding to the XML Schema element;

step 1-2: judging the XML Schema element type, and generating a corresponding interface control according to the type;

if the XML Schema element type is a complex data type, the software interface generation module creates a grouping frame at the corresponding position of the interface according to the DOM tree node information obtained in the step 1-1, and sets corresponding name information for the grouping frame; turning to step 1-3;

if the XML Schema element type is an enumerated data type, the software interface generation module creates a drop-down list at the corresponding position of the interface according to the DOM tree node information obtained in the step 1-1, assigns values to the drop-down list and turns to the step 1-4;

if the XML Schema element type is a simple data type, the software interface generation module creates an edit box at the corresponding position of the interface according to the DOM tree node information obtained in the step 1-1, sets corresponding style information for the edit box, and turns to the step 1-4;

step 1-3, if the DOM tree node corresponding to the current XML Schema element has unprocessed child nodes, returning to the step 1-2; otherwise, entering the step 1-4;

step 1-4, if the DOM tree node corresponding to the current XML Schema element has unprocessed brother nodes, returning to the step 1-2; otherwise, entering the step 1-5;

step 1-5, if the DOM tree node corresponding to the current XML Schema element has an unprocessed father node, returning to the step 1-4; otherwise, finishing the interface generation and finishing the step 1.

Images