CN115599346A - Full life cycle digital development method for application software - Google Patents

Full life cycle digital development method for application software Download PDF

Info

Publication number
CN115599346A
CN115599346A CN202211282822.4A CN202211282822A CN115599346A CN 115599346 A CN115599346 A CN 115599346A CN 202211282822 A CN202211282822 A CN 202211282822A CN 115599346 A CN115599346 A CN 115599346A
Authority
CN
China
Prior art keywords
business
service
software
digital
items
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211282822.4A
Other languages
Chinese (zh)
Inventor
纪青君
文阳
穆芳阁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dalian Hehua Technology Co ltd
Original Assignee
Dalian Hehua Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dalian Hehua Technology Co ltd filed Critical Dalian Hehua Technology Co ltd
Priority to CN202211282822.4A priority Critical patent/CN115599346A/en
Publication of CN115599346A publication Critical patent/CN115599346A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/10Requirements analysis; Specification techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management

Abstract

The invention discloses a full life cycle digital development method of application software, which comprises the steps of acquiring a business architecture of an enterprise, digitally defining business items and a business system through a business description language and generating a digital script; constructing a service execution engine for analyzing and executing the digital script; determining a software requirement for developing application software according to the digital service requirement, wherein the software requirement comprises a plurality of specific description units; designing and developing according to software requirements, wherein the designing and developing comprise designing a database and a data object, generating a code frame according to business requirements corresponding to the software requirements, and compiling codes by developers according to business operations; and testing and deploying the developed application software. By digitalizing the business items and the business system, an intelligent application system executed based on the digital system is constructed and changes along with the change of the business system, so that the intelligent application system can continuously adapt to the continuous innovation and development of the business, the production efficiency of application software is improved, and the operation and maintenance cost is reduced.

Description

Full life cycle digital development method for application software
Technical Field
The invention relates to the field of application software development, in particular to a full life cycle digital development method of application software.
Background
With the development of computer technology, the application of informatization and intellectualization technology in enterprises is more and more extensive and deeper, but the development process of application software is basically in a manual operation mode, an informatization platform for supporting each stage of the application software is lacked, partial platforms at certain stages are independent from each other and cannot be communicated, the stages can be connected through documents, the documents need to be understood by people, the process efficiency between the two stages is low, the understood deviation can cause errors and misnomers, the errors are transmitted and amplified to the next stage, and larger cost and increased construction period are caused when problems are found in a test stage and are traced forwards; the gap between each stage of the software engineering causes that the overall efficiency of the software engineering is difficult to be greatly improved.
The application system uses a computer as a service, so that the service requirement is the most critical stage of the application system, how to propose and express the service requirement, and how to ensure the consistency and accuracy of the service requirement. Business requirements lack of methods and means for accurately expressing business, business requirements have defects of ambiguity, inconsistency and the like, and the problems spread to the next stage, which can cause greater confusion and errors. The method has the advantages that no accurate business requirement exists, software requirements are basically lost and lose directions, functions can only be used as grippers to finish business operation, and the flexibility of system control and sustainable development capability of a business system are lost. The function-oriented design is designed around the function realization of machinery and technology, although the design principles of high cohesion, low coupling and the like are followed from the professional technical perspective, the guidance of services is lacked, the disordered coupling and the function missing and overlapping between functions are difficult to overcome, and an application system loses the flexibility and the development capability which are originally possessed by the service field and are changed along with the system, so that the system is rigid and difficult to adapt to the development change, the maintenance cost is high, and the life cycle is short. Therefore, how to digitalize and introduce the system into the application system is a key problem to be solved urgently.
The development stage has a plurality of available tools and platforms, including code editing and debugging, interface development and database development, and has a plurality of varieties, but the tools and the platforms are mutually independent and difficult to cooperate, and the data standard specification is difficult to implement uniformly among the platforms.
The software process is a complex project, the current project management software is also independent and is split from the development process, the project management software is not integrated with the software development process, project information needs to be acquired through manual input, the project workload is increased, and the problems of untimely and inaccurate information exist. The method is characterized in that a through method and technology are not available in each stage, although a tool and a platform are supported in each stage, the tool and the platform cannot be communicated with each other, the tool and the platform can only be connected through documents, the gap between the two stages cannot be exceeded, and manual operation is needed for fitting, so that the production efficiency and the quality of the application software are difficult to improve greatly on the whole. On the other hand, because there is no method for accurately expressing the business requirements, the application system constructed by the traditional software engineering becomes a rigid business processing system instead of a flexible business execution system operated according to the system by taking the software requirements as a starting point and taking the functions as the guide design and development.
Disclosure of Invention
The invention provides a full-life-cycle digital development method of application software, which aims to overcome the technical problems.
A full-life-cycle digital development method of application software comprises,
s1, obtaining a business architecture of an enterprise, wherein the business architecture comprises architecture objects and corresponding architecture relations, the architecture objects are mechanisms, departments, posts, business items and business systems of the enterprise, the architecture relations comprise that the enterprise comprises one or more mechanisms, one mechanism comprises one or more departments, one department comprises one or more posts, one post corresponds to one or more business items, the business items comprise one or more business processes and business operations, the business systems are used for expressing the logical relations between the business processes and the business operations, the business processes are logical processes for executing one or more business operations, and the business processes and the business systems are digitally defined through a business description language and generate executable digital scripts;
s2, constructing a service execution engine, which is used for analyzing and executing the executable digital script, wherein the service execution engine comprises the steps of judging the type of the executable digital script, analyzing the digital script and executing the flow if the type of the digital script is the flow, and analyzing the digital script and executing the process if the type of the digital script is the process;
s3, determining a software requirement for developing application software according to the executed digital service requirement, wherein the software requirement comprises a plurality of specific description units, and the specific description units comprise one or more service requirements;
s4, designing and developing according to software requirements, wherein the designing and developing comprise a design database and a data object, a code frame is generated according to business requirements corresponding to the software requirements, and developers write codes according to the business requirements corresponding to the software requirements;
and S5, testing and deploying the developed application software.
Preferably, the digitally defining and generating an executable digital script for the business matters and business systems through the business description language includes: the method comprises the steps of obtaining service items and elements used by a service system, digitally defining the elements, digitally defining the service items according to a service item language in a service description language, digitally defining a service process according to a service process language in the service description language, digitally defining service operation according to a service operation language in the service description language, digitally defining the service system according to the digitally defined service items, service processes and service operations, and generating a digital script by the digitally defined elements, service items, service processes, service operations and service systems.
Preferably, the digitally defining the service item according to the service item language in the service description language means acquiring a service system and posts corresponding to the service item, and defining the service processes or service operations executed by each post according to a flow sequence according to a logical relationship between the service processes and the service operations represented by the service system, including flow constraints of logical relationships, flows, concurrences, and aggregations between the service processes or the service operations.
Preferably, the digitally defining the business process according to the business process language in the business description language means acquiring a business system corresponding to the business process, and defining the business operations according to a flow order, including processing logic, execution conditions, and execution order of the business process, according to a logical relationship between the business operations represented by the business system.
Preferably, the digital definition of the business operation according to the business operation language in the business description language means determining input parameters, entry compliance checks, operation steps and logic, output parameters, exit compliance checks of the business operation, and generating a source code framework.
A full life cycle digital development technology platform of application software is characterized by comprising a service architecture definition module, a service execution engine module, a software requirement definition module, a design development module and a software test deployment module,
the business architecture definition module is used for acquiring business architectures of enterprises, the business architectures comprise architecture objects and corresponding architecture relations, the architecture objects are mechanisms, departments, posts, business items and business systems of the enterprises, the architecture relations comprise that one enterprise comprises one or more mechanisms, one mechanism comprises one or more departments, one department comprises one or more posts, one post corresponds to one or more business items, the business items comprise one or more business processes and business operations, the business systems are used for expressing the logical relations between the business processes and the business operations, the business processes are logical processes for executing one or more business operations, and the business items and the business systems are digitally defined through a business description language and generate executable digital scripts;
the service execution engine module is used for analyzing and executing the executable digital script, and comprises the steps of judging the type of the executable digital script, analyzing the digital script and executing the flow if the type of the digital script is the flow, and analyzing the digital script and executing the process if the type of the digital script is the process;
the software requirement definition module is used for determining the software requirement for developing the application software according to the executed digital service requirement, wherein the software requirement comprises a plurality of specific description units, and the specific description units comprise one or more service requirements;
the design development module is used for carrying out design development according to software requirements, comprises a design database and a data object, generates a code frame according to business requirements corresponding to the software requirements, and compiles codes according to the business requirements corresponding to the software requirements by developers;
and the software testing deployment module is used for testing and deploying the developed application software.
The invention provides a full life cycle digital development method of application software, which is characterized in that service items and a service system are digitalized, and the digitalized service items and the service system are carried through each stage of software engineering, so that the production efficiency of the application software is greatly improved on the whole, meanwhile, an application system executed according to the digitalized service system is constructed based on a software process, the service system can be adjusted and optimized through the application system, the capability of the application system changing along with the needs is improved, and the increasing service requirements are continuously met.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention;
FIG. 2 is a schematic diagram of the operation method of the present invention in the service requirement phase;
FIG. 3 is a schematic diagram of the software requirement phase operation of the present invention;
FIG. 4 is a schematic diagram of the design development phase operation of the present invention;
FIG. 5 is a flow chart of the cell test operation of the present invention;
FIG. 6 is a flow chart of the functional test process of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a flowchart of the method of the present invention, and as shown in fig. 1, the method of this embodiment may include:
s1, obtaining a business architecture of an enterprise, wherein the business architecture comprises architecture objects and corresponding architecture relations, the architecture objects are mechanisms, departments, posts, business items and business systems of the enterprise, the architecture relations comprise that the enterprise comprises one or more mechanisms, one mechanism comprises one or more departments, one department comprises one or more posts, one post corresponds to one or more business items, the business items comprise one or more business processes and business operations, the business systems are used for expressing the logical relations between the business processes and the business operations, the business processes are logical processes for executing one or more business operations, and the business processes and the business systems are digitally defined through a business description language and generate executable digital scripts;
the service architecture is based on the hierarchical relationship which is sorted out according to the mechanisms, departments, posts and service items, and the core content of the service requirement is the precise digital definition of each specific service item through a service description language, as shown in fig. 2. The business architecture carding mainly comprises the following contents: the organization structure of the enterprise, the posts and post responsibilities of each business department, business items contained in each post, and collected business nouns and verbs according to classes. This classification is done per service domain, depending on the particular service. The part of work only needs to know which posts, processes and operations are involved in the business item processing process, and a proper name is created for the posts, the processes and the operations, and classification and collection are carried out according to the business domain, so that a common business semantic basis is provided for the following detailed description of the business items by using the business description language. A service domain refers to a group of services classified according to service affiliation or service execution procedures. Mechanisms, stations, processes, operations, business nouns and the like can become metadata defined by subsequent requirements, so that the consistency of requirement expression can be guaranteed, repetition and errors are avoided, and the efficiency of various subsequent works is improved.
According to the business architecture of an enterprise, the processing process and system of business items are digitally and accurately described through business description language for each relevant business item of the enterprise, and during the business development process of the enterprise, the business items may be triggered by clients, may be triggered internally (such as inventory checking and statistical reports), and may be triggered by external association mechanisms or systems, so the business items are collectively referred to herein as the business items. The business system refers to the enterprise business process, rules, constraint conditions and the like according to which specific matters are made, and is formed by logically combining individual business processes, business operations and algorithms according to the rules. Business operations refer to actions of recording, changing and deleting business states, which are called operations and sometimes referred to as jobs, and business processes generally correspond to a professional business system and are often logical combinations of one or more business operations.
According to each business item, searching business personnel of related posts by referring to a business system, and describing and processing steps in detail according to the grammatical requirements of a business description language. And simultaneously defining the process and the operation by using a business process language and a business operation language respectively, thus forming a digital definition for each business process and business operation. The digital definitions of the business processes and business operations are the important basis for business item description, and they can be shared by various business items, and as the requirements develop, the digital definitions of the business processes and business operations become complete and stable step by step.
The business description language is a generic term for a formalized language that clearly and consistently describes business items. It consists of three sub-languages.
Business item language (BML), a formalized language for clear, consistent definition of business items. A business transaction is generally a process, where different stations perform certain business processes or business operations to complete the processing of a business transaction. The situation in which it degrades may be a process or simply a business operation. It is a system definition aiming at the business item, and can be combined with the latter two languages to accurately define a digital enterprise system.
Business Process Language (BPL) a formal language for clearly and consistently defining business processes. It is usually a simple process that needs to be done by logical combination of several business operations according to a specific business system. The method is matched with BML to define a fine-grained specific business system shared by business items.
Business Operations Language (BOL) a formal language for clear, consistent definition of business operations logic. Operations are the fundamental actions of business matters, involving professional business knowledge such as how to bill, manage products, manage customers and contracts.
Digitally defining the service items and the service system through a service description language, generating a digital script, acquiring elements used by the service items and the service system, and digitally defining the elements, wherein the elements comprise but are not limited to questions, targets, mechanisms, departments, posts, responsibilities, domain vocabularies, service classifications, service logics, user interfaces, system interfaces, data types, structures, queries, reports, parameters, permissions, response time, throughput capacity, dynamic capacity and static capacity;
the step of digitally defining the business items according to the business item language in the business description language refers to acquiring a business system and posts corresponding to the business items, and defining business processes or business operations executed by each post according to a flow sequence according to a logical relationship between a business process and business operations represented by the business system, wherein the flow constraints comprise the logical relationship, circulation, concurrence, convergence and the like between the business processes or the business operations.
The service process is defined digitally according to a service process language in the service description language, which means that a professional service processing process is defined by the service process language, which corresponds to a special service processing system, which is usually a logic combination of one or more service operations, and can be shared and used by a plurality of service items, and the processing logic, execution conditions, execution order and the like of the service process are defined digitally through the service process language.
The service operation is digitally defined according to a service operation language in the service description language, which means that a specific service operation is logically defined according to service regulations, and input parameters, entry compliance check, operation steps and logic, output parameters, exit compliance check and the like of the service operation are determined; the business operation is the bottom logic of enterprise business processing, it can be shared by business process and business affair, it is the subtle logic in the business processing, this operation language only defines the input/output parameter of this business operation and defines its logical process of handling with formalization language, and according to this, produce the source code frame of the concrete operation program, the concrete code needs to be realized in development stage code. As mentioned above this section relates to the subtle logic of business processes, and is a relatively stable part of the system, and is suggested to be implemented by program code, but does not exclude subsequent versions from executing or automatically generating code through business operations language interpretation.
And digitally defining a business system according to the service items, the service processes and the service operations which are digitally defined, wherein the business items, the service processes and the logic relations among the service operations, concurrence, convergence and the like are included.
Through research on various business items, the basic form of the business item processing process is constructed through comprehensive analysis and abstraction:
execution of a post (xx operations/procedures)
If (amount > X) is at opening
Execution of procedure (xx operation/procedure) at a certain post
Otherwise-
Execution of a certain post (xx operation/procedure) }
……
And the xx process corresponds to the professional process of the professional post and is expressed by adopting a business process language. It is usually a system that handles a specific business within a certain department of an enterprise.
xx operation corresponds to specific business operation behavior and is expressed by adopting a business operation language. They are typically business-specific operational behaviors of business personnel within a department of an enterprise, and they are business-specific independent, underlying business logic used to complete business transactions.
S2, constructing a service execution engine, which is used for analyzing and executing the digital script, wherein the service execution engine comprises the steps of judging the type of the digital script, analyzing the digital script and executing the flow if the type of the digital script is the flow, and analyzing the digital script and executing the corresponding process if the type of the digital script is the process;
the business execution engine is an executor for analyzing and executing the business description language, the business description language is used for describing business items and a business system, and the automatic execution of the system is realized by the business driving engine, so that the needed result is realized, the final output of the traditional requirement analysis is a document, developers encode the business system by reading the document, the understood deviation or the alternating deviation can cause the difference between the final result and the expectation, the business personnel can participate in the requirement in the embodiment, the actual business execution process uses the business description language for digitally defining the business and the system, and the application system intelligently executes the business processing process according to the digital requirement; under the support of visual business description language, business personnel can conveniently and flexibly carry out demand innovation and business innovation, and after new business editing is finished, the business can be released and operated after testing and approval, so that enterprises can realize business innovation at the highest speed and the lowest cost, and the latest demands of markets and customers are continuously met.
The business execution engine completes the specific processing of business items, the main logic of business processing is completed through a business description language, coding is not needed to be realized, code development amount is reduced to the maximum extent, the full-digital driving of a flow layer and a process layer of an enterprise business architecture is realized, simultaneously, the requirement can be realized by matching with a UI configuration tool of a development platform, a digital intelligent application system which can be easily handled by business personnel is constructed, business is well decoupled from technology, business innovation and demand innovation are unrelated to the application system, the business description language can completely express business innovation, demand innovation and system innovation, zero coding can be deployed to the application system to operate, and the application system is an intelligent business processing system with the understanding of the business description language.
And S3, taking the executed digital script as a digital service requirement, determining a software requirement for developing application software according to the digital service requirement, acquiring the executed process script, defining the digital requirement on an application framework, a platform framework, a technical framework, a hardware framework and the like according to the process script, dividing a plurality of specific description units according to the process requirement, wherein each specific description unit comprises one or more process requirements, acquiring the executed process script, defining the function requirement of the system according to the process script, formulating a system data standard, and then constructing a user interaction page, a service interaction interface and an interaction interface with other systems. As shown in fig. 3, functional requirements are described on the left side, after the functional requirements are described, an interface of the target system can be presented to a user, and in cooperation with the operating platform, an executable application system can provide a business department for auditing, so that the system review moves forward, and the problem is exposed and solved in the requirement stage. The right side is the non-functional requirements developed according to the target requirements of the business requirement stage, the detailed description is mainly related to the aspects of system performance, processing capacity, safety and the like, and each related item has a standardized template so as to facilitate the accuracy and the measurability of each non-functional description.
After the stage is completed, the system level logic of each business item of the business system is accurately defined, the running script capable of forming the business item is driven by a business execution engine of the platform to execute, various interfaces including UI are completed, design and development are not needed, the work in the design stage is highly simplified, and the design work mainly focuses on the design work of specific data storage and basic operation modules (basic services); the automated document generation system may output a software requirements specification that meets the requirements of the project management standards.
According to the problems existing in the real production process of the user and the targets and requirements provided by the expected system for solving the problems, each specific target is obtained through the layer-by-layer decomposition of the problems and the targets. So as to be used as the acceptance basis for the system to achieve the target. The system targets include functional targets and non-functional targets.
Wherein the functional goals are: the targets provided from the function view point comprise the specific functions which need to be provided by the system for which users and the implementation mode requirements; these goals may be covered by the requirements of one or more business events.
The non-functional goals are: specific quantitative indexes are provided for the throughput, response time, availability, scalability, expansibility, maintainability, multi-language support and the like of the system.
According to the service requirements, the data types, the data elements, the data dictionaries, the codes, the parameters, the data objects and the like are described and expressed, and the standardization, the digital management and the application of a metadata layer are realized.
Data type: the data types (numbers, numerical values, characters and dates) involved by the application system are uniformly managed.
Data element: depending on the data type, the data type is further abstracted and its length and decimal place are normalized.
A data dictionary: and the dependent data element is the data base of the system. A data dictionary is a collection of all underlying data concepts in the system, such as: the 18-digit account number in the personal deposit account represents the complete basic business element of the account number under the account system.
Code: the data elements are of various types (e.g., gender, credential type, etc.) and describe code values (e.g., 0 for female and 1 for male).
Data object: representing a collection of business data elements of a type. This section of work primarily standardizes the naming, type, length of each element. While determining relationships between data objects. For example: the information of the personal deposit account is described and needs to include element information such as an account name, an account number, an account opening row, balance and the like.
Firstly, it is clear which business target the item is used for completing, and secondly, the business item expression is perfected on the basis of business requirements. Firstly, determining business item input elements, perfecting data interaction and processing of the input elements in the business operation step, and finally obtaining output elements of the items. The input and output of the business operation and the algorithm are described in detail, the internal logic of the business operation and the algorithm is summarized, the description is driven by a target, firstly, the expected target of the operation and the algorithm is determined, and the implementation steps are described in detail based on the description, which is an important basis for developing the code.
And designing a user interaction interface of the system through a platform visualization page definition tool. Determining the interaction relationship between the page and the business item (the operation elements in the page, such as buttons, tables and the like, are associated with the business item), so that the interface of the target system can be presented to the user, and the interaction between the page and the service is established.
The architecture planning is based on the non-functional goal of the system, and the planning is given to an application architecture, a platform architecture, a technical architecture, a hardware architecture and the like.
The application architecture comprises the following steps: divisions of microsystems have been clearly defined by departments within the organizational framework. The main business module and structure of the business field are determined.
A platform architecture: the system is a technical support system of the application system, and meets the technical requirements of the application system, such as service scheduling, data access, message, cache and the like.
The technical architecture is as follows: planning is performed from the aspects of extensibility, flexibility, security, and the like, and the technical platform APOS (Application Operating System) of the embodiment accepts main functions of the part of requirements, and provides unified and universal capabilities and technical support for the Application System, for example: security architecture, organizational architecture, user management, rights control, service scheduling, consistency management, file transfer, encryption and decryption, messaging, caching, data access, logging, advertising, and the like. The platform can support flexible matching, can be completely omitted, and can be used for directing the development environment to the existing technical environment of an enterprise, partially or completely.
Hardware architecture: and according to non-functional requirements such as throughput, response time and the like, combining with actual environment requirements to provide hardware and network architecture of the system.
S4, designing and developing according to software requirements, wherein the designing comprises designing a database, a data object, an API (application program interface) interface and the like, generating a code frame according to business requirements corresponding to the software requirements, and compiling codes by developers according to the business requirements corresponding to the software requirements; as shown in fig. 4, the left side is the working steps of the server interface, the database design, the basic operation and the algorithm; the right side is a system architecture design step, and in the field of design and development, a system is constructed by taking requirements as guidance and taking a digital and visual design platform as a basis. The design development stage is entered, the previous requirements are obtained, and a lot of important work of software engineering is completed, and the workload is reduced to the minimum.
The design work mainly needs to complete the storage structure (design database table) of business account book informatization. The development work has mainly focused on the design of the underlying basic business logic and special business control aspects of the front-end interface. The platform completes the whole process management from requirements to design development and test, products of each stage are stored in the platform in a digital mode, and standard documents of each stage can be automatically generated, such as: the system comprises a service requirement specification, a software requirement specification, a design specification, an operation manual, an operation and maintenance manual, a service system, a service operation specification and the like.
The database design belongs to the design development stage, a platform is used for defining a database table structure, and data standards (data types, data elements and data dictionaries) are used for standardizing the name, type and length information of elements. And after the definition of the database table is completed, generating a table building statement and linking the target database for execution.
Basic service logic is derived from service operation, a code template is generated by the platform according to the description of the service operation in soft demand, and a developer finishes writing logic codes according to the specific description of the service operation.
The system interface is completed in the soft demand stage, and the business logic control code writing is completed on the basis of the design and development stage. For example: in the transfer service, the transfer amount must be larger than 0 and cannot exceed service rule control logics such as account balance and the like.
And S5, testing and deploying the developed application software. The testing process can be generally divided into two large stages of "analysis-implementation", the testing management platform is divided into three large blocks of testing analysis, testing implementation and defect management, fig. 5 is the testing process, the key to improve the testing quality is the analysis of testing requirements, and the key to improve the testing efficiency is the design and optimization of the testing process and mode. Any business can be expressed as a process, a rule, and an element. If the flow, rule and element of a business are expressed in proper form, a reliable base point for test analysis to be developed can be obtained. Therefore, the functional test is divided into three levels of test, namely, a service level test, a flow level test and an element level test.
And (3) service level: the business level test completely faces to the business function and the business system to develop test analysis activities;
and (3) flow level: the flow level test needs to analyze the whole business flow correlation, data flow, product full life cycle and the like, and completes the test coverage of various business flow scenes;
interface element level: separating the service, analyzing and testing the UI of the interface, and analyzing each element of the interface only, which is irrelevant to the specific service.
The business operation is the minimum and the minimum basic unit of the business process and belongs to an independent behavior process. The testing of business operations is therefore classified as unit testing. The platform provides an automatic testing capability for business operation.
1. And (3) performing static analysis on business operation, and performing static analysis through tools such as Klocwork, QAC, testBed and the like, and analyzing program logics such as program branches and paths.
2. Generating a test case and test data according to the path, the condition and the like, and generating the test case according to the service requirement description corresponding to the program analysis result for counting the case coverage rate; test data is generated according to the type, length and the like of parameters defined by a program, and expected return result data is set.
3. And automatically executing, selecting a case to be executed, calling and executing, automatically comparing an execution result with an expected result, passing the execution in accordance, failing the execution in accordance, and recording all the execution results.
4. Defect management, the results of executing cases may be correlated to a defect management platform record tracking management.
5. And (4) performing test coverage statistical analysis, namely obtaining test coverage according to the analysis of the service operation codes and the finally generated case statistics, and reinforcing the service coverage analysis on the uncovered part by referring to the data.
6. And the test execution statistical analysis can check the test execution statistical data in real time in the test execution process, and the executed/unexecuted test execution statistical data and the executed/executed test execution statistical data fail.
The test for the service item is positioned as a service-level functional test, and as shown in fig. 6, the test process for the service item is divided into two parts: and (6) test analysis and test execution.
And (3) testing and analyzing:
1. and extracting the business rules, wherein the test analysis activity starts from the extraction of the business rules, and the extraction rules are itemized, so that each business rule only expresses one business content. And forming a testing operation step according to the business item refinement.
2. And (4) rule analysis, after extracting the business rules, combining a proper test analysis method (equivalence class, boundary value, orthogonal combination and functional decomposition) to analyze the rules one by one, labeling normal and abnormal test conditions, confirming a test space and the like.
And (3) test execution:
1. and generating a test case, and generating the test case after the test analysis process is finished. The test key points are formed by combining test analysis conditions, case properties are marked by the conditions, operation steps are refined by specific scenes determined by business matters, and test anticipation is determined when a test space is deployed and is additionally provided with check points. The business operations are case checkpoints for business events. Thus, the basic elements of the test case are determined.
2. The test case is executed, the test execution is divided into manual operation and automation, the automatic test takes the case as a unit, a test script is automatically executed aiming at each case, the execution result is compared with the expected result, the execution is passed if the execution is consistent, the execution fails if the execution is inconsistent, and all the execution results are recorded.
The test case is associated with the management test certificate in the execution process, and the test report can be automatically generated after the case is executed.
3. And defect management, after the case is executed, the case with failed standard can be associated with a defect platform to register the defect and carry out tracking management.
4. And (4) carrying out test coverage statistical analysis, wherein in the test analysis process, the service coverage statistical analysis corresponding to the service items is extracted according to the rule, so that the test coverage rate of the service items can be obtained, and the coverage rate of the service requirements is close to 100% theoretically.
5. Test execution statistical analysis, which can check the test execution statistical data in the test execution process, executed/not executed, execution success/execution failure
According to input and output defined in software requirements and interface rules, cases (or manual analysis) are generated, and public elements (such as date, identity card number, sex and the like), a rule base of industry elements and a case base are accumulated by a platform for many years, so that a test asset base with multiplexing value is formed.
The interface element testing process is basically the same as the service level testing process and is mainly divided into two parts, namely testing analysis and testing execution.
And (3) testing and analyzing: and extracting element rules one by one according to input and output elements defined by software requirements, analyzing the interface rules independently (such as interface skip) and generating element test cases according to the element rules.
And (3) test execution: and recording, tracking and managing the defects by relating to the defect management platform in the same service test execution process.
The target code of the platform construction system is divided into two parts, one part is service description parameters and user interface description parameters, and the other part is basic service (service operation) code written by developers. The platform provides a parameter closing plate and a parameter publishing function, and publishes the parameters to a publishing library for production and use. The source code part is matched with a source code management tool and an automatic construction tool to be issued to an issuing library (mirror image warehouse), wherein the source code management tool comprises git, SVN and CVS, git is a distributed management framework, SVN and CVS are centralized management frameworks, and meanwhile, corresponding issuing script files are generated according to a system framework to achieve automatic deployment. And the issuing process is comprehensively monitored. The technical platform provides complete operation and maintenance management functions, including: real-time monitoring, troubleshooting, operation management, operation analysis, operation and maintenance reporting, intelligent inspection, analysis and the like.
A full life cycle digital development technology platform of application software is characterized by comprising a service architecture definition module, a service execution engine module, a software requirement definition module, a design development module and a software test deployment module,
the business architecture definition module is used for acquiring business architectures of enterprises, the business architectures comprise architecture objects and corresponding architecture relations, the architecture objects are mechanisms, departments, positions, business items and business systems of the enterprises, the architecture relations comprise that one enterprise comprises one or more mechanisms, one mechanism comprises one or more departments, one department comprises one or more positions, one position corresponds to one or more business items, the business items comprise one or more business processes and business operations, the business systems are used for expressing the logical relations between the business processes and the business operations, the business processes are logical processes for executing one or more business operations, and the business items and the business systems are digitally defined through a business description language and generate executable digital scripts;
the service execution engine module is used for analyzing and executing the executable digital script, and comprises the steps of judging the type of the executable digital script, analyzing the digital script and executing the flow if the type of the digital script is the flow, and analyzing the digital script and executing the process if the type of the digital script is the process;
the software requirement definition module is used for determining the software requirement for developing the application software according to the executed digital service requirement, wherein the software requirement comprises a plurality of specific description units, and the specific description units comprise one or more service requirements;
the design development module is used for carrying out design development according to software requirements, comprises a design database and a data object, generates a code frame according to business requirements corresponding to the software requirements, and compiles codes according to the business requirements corresponding to the software requirements by developers;
and the software testing deployment module is used for testing and deploying the developed application software.
The overall beneficial effects are as follows:
the invention provides a full life cycle digital development method of application software, which is characterized in that business items and a business system are digitalized, and the digitalized business items and business system are carried through each stage of software engineering, so that the production efficiency of the application software is greatly improved on the whole, an application system executed according to the digitalized business system is constructed, and meanwhile, the business system can be adjusted, optimized and innovated through the application system, and the capability of the application system changing along with needs and sustainable innovation and development is improved.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (6)

1. A full life cycle digital development method of application software is characterized by comprising the following steps,
s1, obtaining a business architecture of an enterprise, wherein the business architecture comprises architecture objects and corresponding architecture relations, the architecture objects are mechanisms, departments, posts, business items and business systems of the enterprise, the architecture relations comprise that the enterprise comprises one or more mechanisms, one mechanism comprises one or more departments, one department comprises one or more posts, one post corresponds to one or more business items, the business items comprise one or more business processes and business operations, the business systems are used for expressing the logical relations between the business processes and the business operations, the business processes are logic processes for executing one or more business operations, and the business items and the business systems are digitally defined through a business description language to generate executable digital scripts;
s2, constructing a service execution engine, which is used for analyzing and executing the executable digital script, wherein the service execution engine comprises the steps of judging the type of the executable digital script, analyzing the digital script and executing the flow if the type of the digital script is the flow, and analyzing the digital script and executing the process if the type of the digital script is the process;
s3, determining a software requirement for developing application software according to the executed digital service requirement, wherein the software requirement comprises a plurality of specific description units, and the specific description units comprise one or more service requirements;
s4, designing and developing according to software requirements, wherein the designing and developing comprise a design database and a data object, a code frame is generated according to business requirements corresponding to the software requirements, and developers write codes according to the business requirements corresponding to the software requirements;
and S5, testing and deploying the developed application software.
2. The method for developing the full lifecycle digitization of application software according to claim 1, wherein the digitally defining business items and business regimes through a business description language and generating the executable digital script comprises: the method comprises the steps of obtaining service items and elements used by a service system, digitally defining the elements, digitally defining the service items according to a service item language in a service description language, digitally defining a service process according to a service process language in the service description language, digitally defining service operation according to a service operation language in the service description language, digitally defining the service system according to the digitally defined service items, service processes and service operations, and generating a digital script by the digitally defined elements, service items, service processes, service operations and service systems.
3. The method as claimed in claim 2, wherein the step of digitally defining the service item according to the service item language in the service description language means that a service system and posts corresponding to the service item are obtained, and the service processes or service operations executed at each post are defined according to a logical relationship between the service processes and the service operations represented by the service system and a flow order, including flow constraints of logical relationships, flow, concurrence, and aggregation between the service processes or the service operations.
4. The method according to claim 2, wherein the digitally defining the business process according to the business process language in the business description language means acquiring a business system corresponding to the business process, and defining the business operations according to a logical relationship between the business operations represented by the business system, including processing logic, execution conditions, and execution order of the business process.
5. The method according to claim 2, wherein the defining the business operation digitally according to the business operation language in the business description language comprises determining input parameters, entry compliance checks, operation steps and logic, output parameters, exit compliance checks of the business operation, and generating a source code framework.
6. A full life cycle digital development technology platform of application software is characterized by comprising a service architecture definition module, a service execution engine module, a software requirement definition module, a design development module and a software test deployment module,
the business architecture definition module is used for acquiring business architectures of enterprises, the business architectures comprise architecture objects and corresponding architecture relations, the architecture objects are mechanisms, departments, posts, business items and business systems of the enterprises, the architecture relations comprise that one enterprise comprises one or more mechanisms, one mechanism comprises one or more departments, one department comprises one or more posts, one post corresponds to one or more business items, the business items comprise one or more business processes and business operations, the business systems are used for expressing the logical relations between the business processes and the business operations, the business processes are logical processes for executing one or more business operations, and the business items and the business systems are digitally defined through a business description language and generate executable digital scripts;
the service execution engine module is used for analyzing and executing the executable digital script, and comprises the steps of judging the type of the executable digital script, analyzing the digital script and executing the flow if the type of the digital script is the flow, and analyzing the digital script and executing the process if the type of the digital script is the process;
the software requirement definition module is used for determining the software requirement for developing the application software according to the executed digital service requirement, wherein the software requirement comprises a plurality of specific description units, and the specific description units comprise one or more service requirements;
the design development module is used for carrying out design development according to software requirements, comprises a design database and a data object, generates a code frame according to business requirements corresponding to the software requirements, and compiles codes according to the business requirements corresponding to the software requirements by developers;
and the software testing deployment module is used for testing and deploying the developed application software.
CN202211282822.4A 2022-10-19 2022-10-19 Full life cycle digital development method for application software Pending CN115599346A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211282822.4A CN115599346A (en) 2022-10-19 2022-10-19 Full life cycle digital development method for application software

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211282822.4A CN115599346A (en) 2022-10-19 2022-10-19 Full life cycle digital development method for application software

Publications (1)

Publication Number Publication Date
CN115599346A true CN115599346A (en) 2023-01-13

Family

ID=84848470

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211282822.4A Pending CN115599346A (en) 2022-10-19 2022-10-19 Full life cycle digital development method for application software

Country Status (1)

Country Link
CN (1) CN115599346A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116302081A (en) * 2023-05-24 2023-06-23 江西省水投江河信息技术有限公司 Micro-application management method and system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116302081A (en) * 2023-05-24 2023-06-23 江西省水投江河信息技术有限公司 Micro-application management method and system
CN116302081B (en) * 2023-05-24 2023-08-08 江西省水投江河信息技术有限公司 Micro-application management method and system

Similar Documents

Publication Publication Date Title
Lu et al. Discovering interacting artifacts from ERP systems
Van Der Aalst Business process management demystified: A tutorial on models, systems and standards for workflow management
US9460171B2 (en) Processing data in data migration
US7835932B2 (en) Relational logic management system
Bass et al. Architecture-based development
Buijs Mapping data sources to xes in a generic way
Li et al. Non-functional requirements as qualities, with a spice of ontology
US20100114628A1 (en) Validating Compliance in Enterprise Operations Based on Provenance Data
US20050144150A1 (en) Remote process capture, identification, cataloging and modeling
Söylemez et al. Challenges of software process and product quality improvement: catalyzing defect root-cause investigation by process enactment data analysis
Upadhyaya et al. An approach for mining service composition patterns from execution logs
CN115599346A (en) Full life cycle digital development method for application software
Rodríguez et al. SOA-enabled compliance management: instrumenting, assessing, and analyzing service-based business processes
Pooput et al. Finding impact factors for rejection of pull requests on github
Maggi et al. Explaining non-compliance of business process models through automated planning
El-Saber CMMI-CM compliance checking of formal BPMN models using Maude
CN114911773A (en) Universal meta-model design method
Herzberg et al. Improving business process intelligence with object state transition events
Amin Handling instance spanning constraints in compliance management
Aversano et al. Understanding and improving the maintenance process: A method and two case studies
Saapunki Root cause analysis and escape defect analysis improvement at continuous delivery by data-driven decision-making
Mileva Mining the evolution of software component usage
Bhat et al. Use of ontology for automating knowledge intensive business processes
Wei On the analysis and refactoring of service interfaces for improving service integration efficiency
Tereshchenko Development and implementation of the data quality assurance subsystem for the MDM platform

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination