CN115562625B - Software development method, system and terminal based on business activity drive - Google Patents
Software development method, system and terminal based on business activity drive Download PDFInfo
- Publication number
- CN115562625B CN115562625B CN202211175976.3A CN202211175976A CN115562625B CN 115562625 B CN115562625 B CN 115562625B CN 202211175976 A CN202211175976 A CN 202211175976A CN 115562625 B CN115562625 B CN 115562625B
- Authority
- CN
- China
- Prior art keywords
- business
- service
- software
- development
- activity
- 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.)
- Active
Links
- 230000000694 effects Effects 0.000 title claims abstract description 101
- 238000000034 method Methods 0.000 title claims abstract description 99
- 230000008569 process Effects 0.000 claims abstract description 46
- 230000010354 integration Effects 0.000 claims abstract description 25
- 230000006870 function Effects 0.000 claims description 42
- 238000013507 mapping Methods 0.000 claims description 14
- 238000010586 diagram Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 7
- 230000003993 interaction Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 2
- 238000011161 development Methods 0.000 abstract description 73
- 238000013461 design Methods 0.000 abstract description 18
- 238000010276 construction Methods 0.000 abstract description 13
- 230000006854 communication Effects 0.000 abstract description 5
- 230000009286 beneficial effect Effects 0.000 abstract description 4
- 238000004891 communication Methods 0.000 abstract description 4
- 230000008901 benefit Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008092 positive effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention belongs to the field of software demand development, and discloses a software development method, a system and a terminal based on service activity driving. The invention enables the business user to participate in the construction of the business requirement and the business flow at any time, and pays attention to the coverage condition of the requirement in the development process; the semi-structured natural language description based on the ternary structure provides communication language based on natural language for users and developers, and is beneficial to the developers to rapidly conduct system design and module development from requirements; the requirements of different service systems in the field are found to help solve the problems of system integration and data sharing, so that the development cost is reduced and the development efficiency is improved.
Description
Technical Field
The invention belongs to the field of software development, and particularly relates to a software development method, system and terminal based on business activity driving.
Background
The application of digitization, networking and intelligent technology is accelerating the reform of business direction, the improvement of business informatization capability, the reconstruction of business flow and the like in various fields. This puts new demands on the development of business systems in specific fields:
firstly, the requirements for functions and data sharing are increased. Traditional function sharing is realized by opening a small number of specified function module interfaces or providing specified services, and data sharing is realized by directly providing a data access view required by the specified requirements or realizing data exchange through the services. These two modes share better support for fixed functions and data sharing, but are difficult to solve the sharing requirement of service system change in the field, especially the new functions and data sharing access requirement with larger time difference and larger service field. Conventional business systems have had difficulty providing related redevelopment service support, while business sharing and data sharing of different business systems have difficulty in both communication and technical implementation. In some fields, technical standards and data standards are established in order to solve the problems of data sharing and function sharing. However, when the system is actually realized, few people actually realize the system according to the standard, and particularly when some standards have difficulty in understanding and realizing, the business development enterprises are more unwilling to implement the development according to the technical standard and the data standard.
Secondly, the development efficiency of the service system is higher. The informatization capability of many fields is greatly improved, the information environment of the user is built, more business information systems are built, and the information capability is very high. On the basis, the new service requirement is a temporary service development requirement which is proposed in the directions of service pain points, new service requirement, service capacity deepening and the like, and a development unit is required to complete development tasks in a short time. In order to realize rapid development, the field of software engineering provides a agile development concept to reduce development time and cost. The method has greatly improved development efficiency for software developers, but has difficulty in providing effective support for service flow changes which can occur to service parties, integration of the same functional modules in past service systems and new data integration sharing. For the changed business processes, the business system can only be reconstructed by a software developer or a new business system can be redeveloped to meet new requirements.
Thirdly, development cost and management cost are reduced. With the increase of informatization capability, development and management costs of unit informatization systems are rapidly increasing. On one hand, the difficulty of newly developing a service system is increased, and the development cost is increased; secondly, the demands of service system sharing and data sharing are increasing the integration cost; and thirdly, the more business systems are, the more the management cost is, and the more the management workload is. Therefore, the reduction of the unit development cost is also an important factor that must be considered by the construction unit.
Aiming at the new requirements, the development of the service system in the specific field has the new requirements of high development speed, low development cost, easy integration, flexible reconstruction and the like, the functions of the traditional service information system are fixed, the interfaces are fixed, the information capacity is fixed, the service flow is fixed, and the reconstruction and development efficiency is limited by software development companies. In order to solve the contradiction between the new demand and the traditional business information system, research finds that an effective solution is difficult to obtain by means of the traditional development method. Mainly because the traditional development method takes a software developer as a main angle and takes a software technology as a core, the software development is organized around a software development flow. In the process, business users have little participation and are difficult to participate, and the terms and documents in various processes such as software development requirements, software development designs and the like are difficult to understand. After the service system is deployed, the service user will have insufficient knowledge of the system functions, interfaces, etc., which will be exacerbated over time and with the reduction of later support services.
The invention is based on the ideas of demand sharing, function sharing, architecture sharing and data sharing of the business system in the field, and realizes a software development method driven by business activities. The invention focuses on realizing a software demand development method and system with continuous participation of a user, and describing the guiding function of the later software development process in detail, and emphasizing how the user knows the functions and interfaces of the later software design.
The invention researches the development method of the past software requirement. In recent years, in order to quickly understand the user demand, quickly convert the user demand into a system design, a use case driven demand acquisition method, an object oriented demand acquisition method, and a scene-based demand acquisition method have been sequentially proposed in the past. Duan Zhenhua et al 1 The utility model provides a use case driving requirement acquisition method based on targets and scenes, which is characterized in that the user requirement is collected and mined through a table, and the user requirement is converted into a use case diagram through UML and other tools, so that the design of a software system is realized. The method combines the methods based on the targets and the use cases to further improve the close correlation between the requirements and the services. Although these methods all provide a good solution for the collection and analysis of user needs. But is provided withThe traditional demand collection and analysis process is mainly active by a developer, passive by the developer, and the description of demand results is mainly designed and described by professional developers, so that common users are difficult to understand and participate. In addition, because the description subjectivity of the requirement result is strong, understanding is difficult, development efficiency is low, service requirements become difficult to determine along with the change of personnel and time, repeated development is difficult to avoid, and the integration sharing requirement of different service systems is met.
Through the above analysis, the problems and defects existing in the prior art are as follows:
(1) Demand development lacks continued user engagement. In the past, software developers collect user demands through means of user interviews, brainstorms, questionnaires and the like, the collection process has space-time limitation, and users cannot continuously participate in the demand collection process, so that the demands are imperfect or the demand description is unclear, the number of times of repetition is large, the time is long, the development efficiency is influenced, and the product effect is also influenced.
(2) Demand descriptions are structurally poor and difficult for customers to understand. The requirement specification is formed words, use cases and the like through self understanding by a developer on the basis of the requirement description of a user. The software requirement instruction book is often strong in specialization and large in language description randomness, and service users have difficulty in understanding professional description, so that the language is ambiguous. These lead to business users and developers to have differences in understanding the demands, seriously affecting product effect and development efficiency.
(3) Different service system requirements in the same field are difficult to be melted. At present, the service in the same field is quick in change, the service direction is subdivided, the development quantity of service systems is continuously increased, so that the function modules are overlapped, and higher requirements are provided for sharing the function modules and data sharing requirements of different service systems. The traditional demand development process is mostly paper record files completed by developers, which are difficult to read, inquire and share, and the business demands are difficult to be clearly defined. Therefore, whether there is a coincidence in service functions of the new and old service systems is also difficult to define clearly.
Disclosure of Invention
Aiming at the problems existing in the prior art, the invention provides a software development method, a system and a terminal based on business activity driving.
The invention is realized in such a way that a software development method based on business activity driving comprises the following steps:
step one, saving business activities described by using a semi-structured natural language ternary structure;
generating a service flow chart scene for drawing, modifying or erasing, and drawing a service flow chart according to the first step;
and thirdly, generating a software requirement document, an interface document, a data and function sharing document according to the business activity list and the business flow chart.
Further, the first specific process of the step is as follows:
the business user of the business information system to be developed adopts a ternary structure to describe business activities, namely, a ternary structure of a single entity (business operation object) plus a verb (business activity verb) plus a single entity (operated object in business) is used for describing business activities, wherein the entity can be a person, a matter or a certain component unit in the system, and the like, and the business activity verb refers to a certain operation process in a business flow. In the step, aiming at the requirement of a certain service system in a certain field, only one service user is allowed to perform one-time adding, modifying or deleting operation, and other service users can inquire; different systems within the same domain may allow multiple users to proceed simultaneously. The description of the business activities can be described in a hierarchical manner, namely, a sub business activity requirement description can exist with a certain business activity, but a ternary structure description is also required. The business activity demands of a certain business system described by all business users together form a demand list of the business system. In the requirement list, the description of the business activity is not sequential.
Further, the specific process of the step two is as follows:
the service user establishes a service flow chart according to the usual service processing process, wherein nodes in the chart are the service demand description in the step one, and pointers in the chart are sequence guidance of the service process. If there is an optional process, multiple paths are in parallel. The head-to-tail pointer may be incremented if there is a loop. Each business flow chart reflects a business process link of a certain business, and has non-interruptibility. In this step, the developer can complete the business process together with the user, and can also return to the requirement list to further complete the business requirement description.
Further, the specific process of the third step is as follows:
and constructing user requirements and system designs by using the business activities and the business flow diagrams. The development party further perfects the development requirement according to the service flow chart and the service requirement description, and confirms the user together. On the basis, functional design and interface design are carried out, and the design thought comprises that entities in each requirement are data objects in a program, the requirement in each business flow chart is equivalent to an independent functional module, and each business flow chart is equivalent to a service and the like.
Further, the ternary structure comprises an action and two single entities, and the structure is formed by adding the single entity and the single action and the single entity. The former is the operation object of the business, the verb is the business activity verb, and the latter is the operated object of the business.
Further, the nodes in the service flow chart are service activity numbers in the step one, pointers in the chart are sequence guidance of the service process, multiple paths in the chart can be parallel, and the end-to-end connection pointers can be added to complete circulation of the service process.
Another object of the present invention is to provide a business activity driven based software development system, comprising:
the ternary structure module is used for describing business activities;
the business flow module is used for generating a business flow chart scene which can be drawn, modified or erased by a user; providing the service activity record prompt and the like for a user during scene drawing, and guiding the user to quickly complete drawing of a service flow chart; checking the integrity of the business flow diagram; methods are provided for drawing orders, conditions, and loops.
And the interaction module is used for generating a software requirement document, an interface document, a function and a data sharing document according to the service activity list and the service flow chart, providing an external access interface, realizing interaction with a software design phase difference document and a software integration environment, enabling the described service activity and the service flow chart to realize a mapping relation with software, and generating a mapping relation chart or a mapping relation document for developers and testers to use.
It is a further object of the present invention to provide a computer readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of the business activity driver based software development method.
Another object of the present invention is to provide an information data processing terminal for implementing the business activity driving-based software development system.
In combination with the above technical solution and the technical problems to be solved, please analyze the following aspects to provide the following advantages and positive effects:
the invention is based on the ideas of demand sharing, function sharing, architecture sharing and data sharing of the business system in the field, and realizes a software development method driven by business activities. The invention focuses on realizing a software demand development method and system with continuous participation of a user, and describing the guiding function of the later software development process in detail, and emphasizing how the user knows the functions and interfaces of the later software design.
The demand development system provided by the invention enables a plurality of users in the service to participate in the description of the service demand and the construction of the service flow at any time, and pays attention to the coverage condition of the demand in the software development process.
The semi-structured natural language description based on the ternary structure provides a communication language based on natural language for users and developers.
The ternary structure adopted by the invention is not only beneficial to users to participate in the development process of the demands, but also beneficial to developers to rapidly carry out system design and module development from the demands, shares functional modules and data integration, reduces development cost and effectively improves development efficiency.
The expected benefits and commercial values after the technical scheme of the invention is converted are as follows: after conversion, the invention can bring greater economic benefit and commercial value to software development enterprises and information system construction units respectively:
firstly, the development cost and the management cost of the information system construction unit can be reduced. The main appearance is that: (1) development cost is reduced through function module sharing. The common function modules of different service systems are more overlapped in the same field or the same unit, and the development cost is reduced through function sharing; (2) integration and maintenance costs are reduced by the shared architecture. In fact, the software development based on business activities forces the development and use of the existing architecture and service support technology of the construction unit, so that different business systems are easier to integrate, and a constructor does not need to maintain and manage different business systems, thereby reducing the integration and maintenance cost of the construction unit; (3) the cost of service reconfiguration is reduced by fast reconfiguration. The service conversion is too fast to cause the failure of a plurality of traditional service systems, and the service systems can be quickly reconstructed according to the service flow by utilizing the function sharing module and the quick reconstruction strategy, so that the development investment cost of the service systems is reduced, and the service awareness capability is improved.
And secondly, the software development efficiency of a software development company can be improved. The main appearance is that: (1) focusing on the development of core systems. The strategy integrated with the existing sharing function can enable a software development company to only concentrate on functions and business services which do not exist in the current system; (2) and the development efficiency of software development is improved. Through the method that the user participates in demand development and rapidly converts the demand into design, a software development company can reduce the communication process with the user demand, understand the time of converting the user demand into system design, and improve the software development efficiency.
Third, the present invention has some other commercial value. The main appearance is that: (1) the construction unit can detect the system function realization condition of the software developer according to the business activity and the business flow; (2) the software requirement can be continuously tracked, and a construction unit can avoid more repeated development; (3) the constructor can standardize software development standards and behaviors, and improve software construction quality; (4) the participation degree of service users is deep, and the test and the use of the service system are directly affected.
In a word, the invention can reduce the development cost of both a software developer and a constructor, improve the development speed of the system, realize the integration and sharing of functions and data of different service systems, and has higher commercial value.
The technical scheme of the invention fills the technical blank in the domestic and foreign industries: the invention is based on the realization of software development of business activities of business users, changes the traditional software development process taking software technology of a software developer as a core, pays attention to integration and sharing of information systems and data taking fields or units as a whole, and has great value for improving informatization capability of construction units.
The technical scheme of the invention solves the technical problems that people are always desirous of solving but are not successful all the time:
the demand collection method provided by the prior art lacks continuous participation of users, has poor demand description structure and understanding difference, and simultaneously has difficult integration of demands of different business systems in the same field. The software development system based on the business activity driving is beneficial to integrating users into software development, solves the problems of system integration and data sharing of different business systems in the current field, and can reduce development cost and improve development efficiency.
Drawings
FIG. 1 is a flowchart of a software development method based on business activity driving provided by an embodiment of the present invention;
FIG. 2 is a ternary structure describing business activities provided by an embodiment of the present invention;
FIG. 3 is a sequential directed graph depicting business processes provided by an embodiment of the present invention;
FIG. 4 is a branch directed graph depicting business processes provided by an embodiment of the present invention;
FIG. 5 is a flowchart of a demand development method according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the following examples in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
In order to fully understand how the invention may be embodied by those skilled in the art, this section is an illustrative embodiment in which the claims are presented for purposes of illustration.
As shown in fig. 1, a software development method based on business activity driving provided by an embodiment of the present invention includes:
s101, saving business activities described by using a semi-structured natural language ternary structure;
s102, generating a service flow chart scene for drawing, modifying or erasing, and drawing a service flow chart according to S101;
s103, generating a software requirement document, an interface document, data and a function sharing document according to the business activity list and the business flow chart.
Further, the specific process of S101 is:
the business user of the business information system to be developed adopts a ternary structure to describe business activities, the ternary structure is shown in fig. 2, namely, a ternary structure of a single entity (business operation object) plus a verb (business activity verb) plus a single entity (operated object in business) is used for describing business activities, wherein the entity can be a person, an object or a certain component unit in the system, and the like, and the business activity verb refers to a certain operation process in a business process. In the step, aiming at the requirement of a certain service system in a certain field, only one service user is allowed to perform one-time adding, modifying or deleting operation, and other service users can inquire; different systems within the same domain may allow multiple users to proceed simultaneously. The description of the business activities can be described in a hierarchical manner, namely, a sub business activity requirement description can exist with a certain business activity, but a ternary structure description is also required. The business activity demands of a certain business system described by all business users together form a demand list of the business system. In the requirement list, the description of the business activity is not sequential.
Further, the specific process of S102 is:
the service user establishes a service flow chart according to the usual service processing process, wherein nodes in the chart are the service demand description in the step one, and pointers in the chart are sequence guidance of the service process. If there is an optional process, multiple paths are in parallel. The head-to-tail pointer may be incremented if there is a loop. Each business flow chart reflects a business process link of a certain business, and has non-interruptibility. In this step, the developer can complete the business process together with the user, and can also return to the requirement list to further complete the business requirement description.
Further, the specific process of S103 is:
and constructing user requirements and system designs by using the business activities and the business flow diagrams. The development party further perfects the development requirement according to the service flow chart and the service requirement description, and confirms the user together. On the basis, functional design and interface design are carried out, and the design thought comprises that entities in each requirement are data objects in a program, the requirement in each business flow chart is equivalent to an independent functional module, and each business flow chart is equivalent to a service and the like.
Further, the nodes in the service flow chart are service activity numbers in the step one, pointers in the chart are sequence guidance of the service process, multiple paths in the chart can be parallel, and the end-to-end connection pointers can be added to complete circulation of the service process.
Further, the software development method based on business activity driving further comprises the following steps:
adding sub-activities in the business activities, wherein the sub-activities are described by adopting a ternary structure;
additional conditions are added in the business activity, the additional conditions can be multiple, and the format is not limited.
The business activity list provided by the embodiment of the invention is shown in the table 1, and the sequence numbers are hierarchical and structural; and adding different business flow charts according to daily work business to form different business flow closed loops, and stopping adding the business flow charts when the work is completed.
TABLE 1 Business Activity List
As shown in fig. 3, the construction of the business process order diagram further includes the following procedures:
when the business activities required by the business flow do not exist in the business activity list, the business activities can be added, and the description is further carried out.
Fig. 3 depicts a service user's own service flow, which represents a service processing procedure, and the sequence number of the flow chart must be the service requirement that the user has entered before. If the sequence is structured, the sequence is identified by directional arrows. If a branching structure is adopted, i.e. a business activity is performed, and if a B business activity is performed, the branching is divided into two or more paths, and 1 in table 1 can be 1.1, 1.2 and 1.3 in sequence, if branching selection exists, as shown in fig. 4.
The requirements input by different service users are visible, and fuzzy inquiry is displayed when the service requirements input by the same term are used for prompting the users that the same service requirement description possibly exists.
Furthermore, the software development method based on the business activity driving further comprises sharing the designed demand realization module, so that integration and data sharing of different business systems are promoted.
Further, the software development method based on the business activity driving further comprises the step of manually and automatically searching and marking differences of business flow ordered charts of different business systems or the same business system.
Furthermore, the software development method based on the business activity drive further comprises the steps of realizing business system construction by utilizing a plurality of methods, and rapidly reconstructing a business system adapting to new requirements according to the requirements when the requirements are changed.
The embodiment of the invention also provides a software development system based on business activity driving, which comprises:
the ternary structure module is used for describing business activities;
the business flow module is used for generating a business flow chart scene which can be drawn, modified or erased by a user; providing the service activity record prompt and the like for a user during scene drawing, and guiding the user to quickly complete drawing of a service flow chart; checking the integrity of the business flow diagram; methods are provided for drawing orders, conditions, and loops.
The requirement realization module is used for generating a software requirement document, an interface document, a function and a data sharing document according to the service activity list and the service flow chart, providing an external access interface, realizing interaction with a software design phase difference document and a software integration environment, enabling the service activity and the service flow chart to realize a mapping relation with the software, and generating a mapping relation chart or a mapping relation document for developers and testers to use.
As shown in fig. 5, the embodiment of the invention further provides a demand development method, which specifically includes the following steps:
firstly, a business related user login system inputs business user requirements according to a ternary structure;
then, the service user completes a service flow ordered graph according to the service flow; the sequence number of the flow chart must be the business requirement that the user has entered before;
secondly, unifying terms of a developer and a service party, and confirming service requirements and service flows;
finally, the developer completes the design of prototypes, functions, data, function sharing and the like according to the service requirements, and marks the coverage condition of the requirements; a shared service interface should be provided for each business flow diagram, sharing being provided for each business requirement, in particular the need to design business data.
2. Application example. In order to prove the inventive and technical value of the technical solution of the present invention, this section is an application example on specific products or related technologies of the claim technical solution.
The invention is completed by combining the requirements of current data integration and function integration sharing on the basis of the requirement development experience in the past software development process.
The invention promotes the user to continuously participate in the user demand development and the system function development of the software developer through the ternary structure and the business flow diagram, so that the user can know the functions and the demand conditions of the system in detail, and the integration and the sharing of different business systems are promoted. The invention is adopted in the development of relevant business systems of colleges and universities in the early stage, so that deep participation of business users is promoted. In the use process, because the demand service system of the invention is also disclosed, mainly, a developer describes the user demand through a ternary structure, draws a service flow chart through the user demand, and further confirms the user demand through the user service activity list and the service flow chart, so that the effect is obvious, the service user is easy to understand, and the participation is extremely strong.
At present, with the increasing of hospital service systems, the information processing capability is enhanced, and the demands of hospitals on data integration sharing and system integration sharing are increasing, but the practical problems of difficult coordination and communication of different software development companies, rapid rising of development cost and the like are faced. According to the practical problems, the invention starts to realize a server-less architecture technology according to business activities and business flow charts, and utilizes the idea of functions as services (FaaS) to complete the integration and sharing of functions and data.
The software development method based on the business activity driving provided by the application embodiment of the invention is applied to the information data processing terminal, and the information data processing terminal is used for realizing the software development system based on the business activity driving.
It should be noted that the embodiments of the present invention can be realized in hardware, software, or a combination of software and hardware. The hardware portion may be implemented using dedicated logic; the software portions may be stored in a memory and executed by a suitable instruction execution system, such as a microprocessor or special purpose design hardware. Those of ordinary skill in the art will appreciate that the apparatus and methods described above may be implemented using computer executable instructions and/or embodied in processor control code, such as provided on a carrier medium such as a magnetic disk, CD or DVD-ROM, a programmable memory such as read only memory (firmware), or a data carrier such as an optical or electronic signal carrier. The device of the present invention and its modules may be implemented by hardware circuitry, such as very large scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., as well as software executed by various types of processors, or by a combination of the above hardware circuitry and software, such as firmware.
3. Evidence of the effect of the examples. The embodiment of the invention has a great advantage in the research and development or use process, and has the following description in combination with data, charts and the like of the test process.
The embodiment of the invention fully draws the experience of extremely simple user demand description provided by partial users when the user is in butt joint with the demand, and provides the three-dimensional structure half-structured natural language description method, thereby ensuring that the user does not need technical support to participate in demand development, and ensuring the guiding function of the structure on later development. The semi-structured method reduces the number of times of the opposite connection with the service user, and improves the requirement development efficiency. In the future, by using the method provided by the embodiment of the invention, the interaction mapping effect in the process of demand development and software development is further enhanced through a standardized annotation structure or other methods, the mapping relation between the software demand and the software functional module is discovered, and the software testing efficiency is improved.
The embodiment of the invention also utilizes the business activity to guide the integration and sharing of the software functions and the data, can improve the deep participation of the construction unit and also improve the development efficiency of the development unit. And through the integrated sharing of functions and data, the development cost of both sides is reduced, and the development efficiency is improved.
The foregoing is merely illustrative of specific embodiments of the present invention, and the scope of the invention is not limited thereto, but any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention will be apparent to those skilled in the art within the scope of the present invention.
Claims (4)
1. The software development method based on the business activity driving is characterized by comprising the following steps of:
the method comprises the steps of describing and storing business activities by using a semi-structured language ternary structure, generating a business flow drawing scene for a user to draw a business flow chart, generating a software requirement description document, an interface document, a data sharing and function sharing description document, and providing an external interface to interact with other software;
the software development method based on business activity driving further comprises the following steps of;
step one, saving business activities described by using a semi-structured natural language ternary structure;
generating a service flow chart scene for drawing, modifying or erasing, and drawing a service flow chart according to the first step;
generating a software requirement document, an interface document, a data and function sharing document according to a business activity list and the business flow chart;
the business activity driven software development method further comprises the following steps:
adding, modifying, deleting and inquiring control for business activities in a single system or the same field; identifying and judging the same business activity; describing a certain business activity in a layering way by adopting the same structure;
the business activity driven software development method further comprises the following steps:
providing the service activity record prompt when the scene is drawn, and guiding to finish drawing a service flow chart;
checking the integrity of the business flow diagram;
providing a method for drawing order, conditions and loops;
the business activity driven software development method further comprises the following steps:
providing an external access interface, interacting with a software design phase difference document and a software integration environment, enabling the business activities, the business flow diagrams and the software to realize a mapping relation, and generating a mapping relation diagram or a mapping relation document for developers and testers to use;
the ternary structure comprises a verb and a plurality of entities, wherein the structure is formed by adding a single entity and a single verb to a single entity, the single entity is a business operation object, the verb is a business activity verb, and the single entity is an operated object in a business;
the nodes in the service flow chart are service activity numbers in the step one, pointers in the chart are sequence guidance of the service process, multiple paths in the chart can be parallel, and the end-to-end connection pointers can be added to complete circulation of the service process.
2. A business activity-based software development system that implements the business activity-based software development method of claim 1, wherein the business activity-based software development system comprises:
the ternary structure module is used for describing business activities;
the business flow module is used for generating a business flow chart scene which can be drawn, modified or erased by a user; providing the service activity record prompt and the like for a user during scene drawing, and guiding the user to quickly complete drawing of a service flow chart; checking the integrity of the business flow diagram; providing a method for drawing order, conditions and loops;
the requirement realization module is used for generating a software requirement document, an interface document, a function and a data sharing document according to the service activity list and the service flow chart, providing an external access interface, realizing interaction with a software design phase difference document and a software integration environment, enabling the service activity and the service flow chart to realize a mapping relation with the software, and generating a mapping relation chart or a mapping relation document for developers and testers to use.
3. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the business activity driver-based software development method of claim 1.
4. An information data processing terminal for implementing the business activity driver-based software development system according to claim 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211175976.3A CN115562625B (en) | 2022-09-26 | 2022-09-26 | Software development method, system and terminal based on business activity drive |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211175976.3A CN115562625B (en) | 2022-09-26 | 2022-09-26 | Software development method, system and terminal based on business activity drive |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115562625A CN115562625A (en) | 2023-01-03 |
| CN115562625B true CN115562625B (en) | 2023-12-22 |
Family
ID=84743523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211175976.3A Active CN115562625B (en) | 2022-09-26 | 2022-09-26 | Software development method, system and terminal based on business activity drive |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115562625B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116700678B (en) * | 2023-08-04 | 2023-12-08 | 广州市海捷计算机科技有限公司 | Demand tracking method and device in software development management system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1952882A (en) * | 2006-11-16 | 2007-04-25 | 武汉大学 | A realm model building method based on ontology & meta-modeling |
| CN101004680A (en) * | 2006-11-23 | 2007-07-25 | 福建顶点软件股份有限公司 | Flexible, fast software development method and support system by using kernels of direct operation object model definition |
| CN110058846A (en) * | 2019-04-19 | 2019-07-26 | 深圳市康拓普信息技术有限公司 | A kind of service application software development system and method |
| WO2020032807A1 (en) * | 2018-08-10 | 2020-02-13 | Meaningful Technology Limited | Ontologically-driven business model system and method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10380533B2 (en) * | 2013-12-11 | 2019-08-13 | International Business Machines Corporation | Business process modeling using a question and answer system |
-
2022
- 2022-09-26 CN CN202211175976.3A patent/CN115562625B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1952882A (en) * | 2006-11-16 | 2007-04-25 | 武汉大学 | A realm model building method based on ontology & meta-modeling |
| CN101004680A (en) * | 2006-11-23 | 2007-07-25 | 福建顶点软件股份有限公司 | Flexible, fast software development method and support system by using kernels of direct operation object model definition |
| WO2020032807A1 (en) * | 2018-08-10 | 2020-02-13 | Meaningful Technology Limited | Ontologically-driven business model system and method |
| CN110058846A (en) * | 2019-04-19 | 2019-07-26 | 深圳市康拓普信息技术有限公司 | A kind of service application software development system and method |
Non-Patent Citations (1)
| Title |
|---|
| 面向大型分布式软件项目的敏捷开发模型研究;高松涛，杨东日，刘龙庚，王颖;《办公自动化（综合版）》(第7期);5 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115562625A (en) | 2023-01-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Schmickl et al. | How much do specialists have to learn from each other when they jointly develop radical product innovations? | |
| Kim | Hybridized industrial ecosystems and the makings of a new developmental infrastructure in East Asia’s green energy sector | |
| Cho et al. | Dialectics of resilience: a multi–level analysis of a telehealth innovation | |
| Shane | Selling university technology: Patterns from MIT | |
| Anthony Jnr et al. | Modeling pervasive platforms and digital services for smart urban transformation using an enterprise architecture framework | |
| Fabra et al. | Automatic execution of business process models: Exploiting the benefits of model-driven engineering approaches | |
| CN115562625B (en) | Software development method, system and terminal based on business activity drive | |
| Xing et al. | Evaluation of “innovation chain+ supply chain” fusion driven by blockchain technology under typical scenario | |
| Kuada et al. | Knowledge transfer in the emerging solar energy sector in Ghana | |
| Khisro et al. | Enterprise interoperability development in multi relation collaborations: Success factors from the Danish electricity market | |
| Padilla-Meléndez et al. | Knowledge spillovers, knowledge filters and entrepreneurial university ecosystems. Emerging role of University-focused venture capital firms | |
| Li et al. | How do bike-sharing platform companies overcome the operational challenge? A social exchange perspective | |
| Letsholo et al. | An integrative approach to support multi-perspective business process modeling | |
| Omezzine et al. | New market creation through exaptation: The role of the founding team's prior professional experience | |
| Menten et al. | Using audio and collaboration technologies for distributed requirements elicitation and documentation | |
| Felizardo et al. | Knowledge management for promoting update of systematic literature reviews: An experience report | |
| Shaw et al. | Emergent practices of an environmental standard | |
| Leego et al. | Using fractal enterprise model in technology-driven organisational change projects: a case of a water utility company | |
| Gebhart et al. | Supporting service design decisions | |
| Chen et al. | Overseas M&A integration, innovation networks and home-country industrial technology innovation: case studies from China | |
| Cheng et al. | BPMN++: Comprehensive Business Process Modeling for Industrial Internet Application | |
| Thomas et al. | A step towards the adoption of standards within the UK Ministry of Defence | |
| Feenstra | Women Engendering the Just Energy Transition | |
| da Silva et al. | A framework for governance of sustainability indicator systems in strategic environmental assessment processes | |
| Montoni et al. | Using grounded theory to acquire knowledge about critical success factors for conducting software process improvement implementation initiatives |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |