TWI686719B - Program integration system and method - Google Patents
Program integration system and method Download PDFInfo
- Publication number
- TWI686719B TWI686719B TW107111930A TW107111930A TWI686719B TW I686719 B TWI686719 B TW I686719B TW 107111930 A TW107111930 A TW 107111930A TW 107111930 A TW107111930 A TW 107111930A TW I686719 B TWI686719 B TW I686719B
- Authority
- TW
- Taiwan
- Prior art keywords
- file
- code
- specifications
- program
- system design
- Prior art date
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
Description
本發明是有關於一種裝置與方法,且特別是有關於一種方案接軌系統及方法。 The present invention relates to a device and method, and particularly relates to a system and method for connecting rails.
所謂軟體過程模型(Software Process Model)是一種開發策略,這種策略針對軟體工程的需求收集、系統分析、系統設計、程式開發和測試等階段提供了一套範形,使工程的進展達到預期的目的。 The so-called software process model (Software Process Model) is a development strategy. This strategy provides a set of paradigms for the stages of software engineering requirements collection, system analysis, system design, program development and testing, so that the progress of the project can reach the expected purpose.
常見的軟體過程模型有瀑布模型(Waterfall Model)、快速原型模型(Rapid Prototype Model)、增量過程模型(Incremental process model)、反覆運算模型(Iterative Model)、螺旋模型(Spiral Model)、統一軟體開發過程(Rational Unified Process,RUP)等,這些模型幾乎都是以瀑布模型為基礎來延伸改進。 Common software process models include Waterfall Model, Rapid Prototype Model, Incremental process model, Iterative Model, Spiral Model, and unified software development. Process (Rational Unified Process, RUP), etc., these models are almost based on the waterfall model to extend and improve.
瀑布模型(Waterfall Model)或稱系統發展生命週期(System Development Life Cycle,SDLC)是由W.W.Royce在1970年首次提出的軟體開發模型,強調系統開發過程要有完整的需求收集、系統分析、系統設計、程式開 發、測試和維護等管理與控制,能有效的確保系統品質,因此成為軟體業界大多數軟體開發的標準。 The Waterfall Model or System Development Life Cycle (SDLC) is a software development model first proposed by WWRoyce in 1970, emphasizing that the system development process must have complete requirements collection, system analysis, and system design , Program open Management and control such as development, testing and maintenance can effectively ensure the quality of the system, so it has become the standard for most software development in the software industry.
然而,模型只是一種開發策略,所以就有廠商會實作相對應的模型發展工具。為了加快系統開發速度,某些模型發展工具會在分析與設計過程當中產生基礎代碼,讓程式開發階段得以快速展開。但是這些工具在開發過程當中只關注於代碼的產生,屬於規格描述的部分卻沒有整合在工具上,這比較容易造成規格和代碼不一致的情況發生,不容易保持良好的系統品質。 However, the model is just a development strategy, so some manufacturers will implement the corresponding model development tools. In order to speed up the development of the system, some model development tools will generate basic code during the analysis and design process, allowing the program development stage to start quickly. However, these tools only focus on the generation of code during the development process, and the part that belongs to the specification is not integrated into the tool. This is more likely to cause inconsistencies between the specifications and the code, and it is not easy to maintain good system quality.
本發明提出一種方案接軌系統及方法,改善先前技術的問題。 The present invention proposes a scheme connection system and method to improve the problems of the prior art.
在本發明的一實施例中,本發明所提出的方案接軌系統包含儲存裝置與處理裝置。儲存裝置儲存系統分析文件包含資料表、畫面以及規格。處理裝置執行以下動作:進行系統設計,系統設計解析資料表的關聯設定、畫面的編排與規格的邏輯設定,以產生代碼雛形框架以納入系統設計文件,並將該系統設計文件儲存該儲存裝置。 In an embodiment of the invention, the proposed system for connecting rails includes a storage device and a processing device. The storage device storage system analysis file includes data tables, screens, and specifications. The processing device performs the following actions: performs system design, system design analyzes the associated settings of the data table, and arranges the screen and logical settings of the specifications to generate a code prototype framework to be included in the system design document and stores the system design document in the storage device.
在本發明的一實施例中,於程式開發時,處理裝置透過輸入輸出裝置以提供規格的邏輯設定及描述的查詢。 In an embodiment of the present invention, when the program is developed, the processing device provides query of the logical setting and description of the specification through the input and output device.
在本發明的一實施例中,輸入輸出裝置接收一業務邏輯,於瀑布模型之程式開發時,處理裝置結合業務邏 輯與代碼雛形框架以產生系統代碼文件。 In an embodiment of the invention, the input/output device receives a business logic, and when the waterfall model is developed, the processing device combines the business logic Edit and code prototype framework to generate system code files.
在本發明的一實施例中,系統分析文件、系統設計文件、代碼雛形框架與系統代碼文件均為結構性文檔。 In an embodiment of the invention, the system analysis file, system design file, code prototype framework and system code file are all structural documents.
在本發明的一實施例中,若輸入輸出裝置接收一需求變更的要求,處理裝置透過解析結構性文檔的工具,將系統運行的最終成果轉換為新的系統分析文件,依據需求變更的要求,以新的系統分析文件進行規格調整。 In an embodiment of the present invention, if the input/output device receives a request for change in demand, the processing device converts the final result of the system operation into a new system analysis file through a tool that analyzes the structured document, according to the request for change in demand, Adjust the specifications with the new system analysis file.
在本發明的一實施例中,本發明所提出的方案接軌方法包含以下步驟:提供系統分析文件包含資料表、畫面以及規格;以及進行一系統設計,系統設計解析資料表的關聯設定、畫面的編排與規格的邏輯設定,以產生一代碼雛形框架以納入一系統設計文件。 In an embodiment of the present invention, the solution integration method proposed by the present invention includes the following steps: providing a system analysis file including a data table, a screen, and specifications; and performing a system design that analyzes the associated settings of the data table and the screen Layout and specification logic settings to generate a code prototype framework to incorporate a system design file.
在本發明的一實施例中,方案接軌方法更包含:於瀑布模型之一程式開發時,提供規格的邏輯設定及描述的查詢。 In an embodiment of the present invention, the method for integrating the solution further includes: when a program of the waterfall model is developed, providing logic setting and description query of specifications.
在本發明的一實施例中,方案接軌方法更包含:若接收一業務邏輯,於瀑布模型之程式開發時,結合業務邏輯與代碼雛形框架以產生一系統代碼文件。 In an embodiment of the present invention, the method for integrating solutions further includes: if a business logic is received, when the waterfall model is developed, the business logic and the code prototype framework are combined to generate a system code file.
在本發明的一實施例中,系統分析文件、系統設計文件、代碼雛形框架與系統代碼文件均為一結構性文檔。 In an embodiment of the invention, the system analysis file, the system design file, the code prototype framework and the system code file are all structural documents.
在本發明的一實施例中,方案接軌方法更包含:若輸入輸出裝置接收一需求變更的要求,透過解析結構性文檔的工具,將系統運行的最終成果轉換為新的系統分析 文件,依據需求變更的要求,以新的系統分析文件進行規格調整。 In an embodiment of the present invention, the method for integrating the solution further includes: if the input and output device receives a request for a change in requirements, the final result of the system operation is converted into a new system analysis through a tool that analyzes the structured document Documents, according to the requirements of changing requirements, adjust the specifications with new system analysis documents.
綜上所述,本發明之技術方案與現有技術相比具有明顯的優點和有益效果。本發明發展了標準產品開發與個案修改協同一致從需求分析到系統分析/系統設計的一體化,並支持後續二次開發時,仍能正向、逆向引入原規格的方式進行後續的擴充開發。各階段的結構化設計成果逐層沿用,取代原本複雜的本文交付,快速提升開發效能。 In summary, the technical solution of the present invention has obvious advantages and beneficial effects compared with the prior art. The present invention develops the integration of standard product development and case modification from the integration of demand analysis to system analysis/system design, and supports the subsequent expansion development by still introducing the original specifications in the forward and reverse directions during the subsequent secondary development. The structured design achievements of each stage are used layer by layer, replacing the original complicated paper delivery and rapidly improving the development efficiency.
由最終程式結果還原系統分析文件,有效降低需求發展人員重工及提昇效能,快速明確地和關係人(例如:客戶)進行溝通。 The system analysis files are restored from the final program results, which effectively reduces the demand for development personnel to rework and improve efficiency, and quickly and clearly communicate with related parties (such as customers).
整個流程大幅提高效能,並從一般基礎只針對系統分析/系統設計/程式開發效能的提昇上,更有效擴展至需求發展時的效能,幫助了規劃人員與需求人員在溝通時的互動,也確保最後程式的達成與最原始的需求一致性最高。 The whole process greatly improves the efficiency, and from the general basis only for the improvement of system analysis/system design/program development performance, it is more effectively extended to the performance during the development of requirements, which helps the interaction between planners and demand personnel in communication, and also ensures The final program has the highest consistency with the original requirements.
以下將以實施方式對上述之說明作詳細的描述,並對本發明之技術方案提供更進一步的解釋。 The above description will be described in detail in the following embodiments, and the technical solutions of the present invention will be further explained.
為讓本發明之上述和其他目的、特徵、優點與實施例能更明顯易懂,所附符號之說明如下: In order to make the above and other objects, features, advantages and embodiments of the present invention more obvious and understandable, the attached symbols are described as follows:
100‧‧‧方案接軌系統 100‧‧‧ Plan connection system
110‧‧‧輸入輸出裝置 110‧‧‧I/O device
120‧‧‧儲存裝置 120‧‧‧Storage device
130‧‧‧處理裝置 130‧‧‧Processing device
200‧‧‧瀑布模型 200‧‧‧Waterfall model
210‧‧‧需求收集 210‧‧‧ demand collection
220‧‧‧系統分析 220‧‧‧System analysis
230‧‧‧系統設計 230‧‧‧System Design
240‧‧‧程式開發 240‧‧‧Program development
250‧‧‧系統測試 250‧‧‧System test
260‧‧‧運行維護 260‧‧‧Operation and maintenance
300‧‧‧方案接軌方法 300‧‧‧ Scheme connection method
S301、S302‧‧‧步驟 Steps S301, S302‧‧‧
為讓本發明之上述和其他目的、特徵、優點與實施例能更明顯易懂,所附圖式之說明如下:第1圖是依照本發明一實施例之一種方案接軌系統的方塊圖; 第2圖是依照本發明另一實施例之一種瀑布模型的示意圖;以及第3圖是依照本發明一實施例之一種方案接軌方法的流程圖。 In order to make the above and other objects, features, advantages and embodiments of the present invention more obvious and understandable, the drawings are described as follows: FIG. 1 is a block diagram of a system for connecting to a solution according to an embodiment of the present invention; FIG. 2 is a schematic diagram of a waterfall model according to another embodiment of the present invention; and FIG. 3 is a flowchart of a method for connecting a solution according to an embodiment of the present invention.
為了使本發明之敘述更加詳盡與完備,可參照所附之圖式及以下所述各種實施例,圖式中相同之號碼代表相同或相似之元件。另一方面,眾所週知的元件與步驟並未描述於實施例中,以避免對本發明造成不必要的限制。 In order to make the description of the present invention more detailed and complete, reference may be made to the accompanying drawings and various embodiments described below. The same numbers in the drawings represent the same or similar elements. On the other hand, well-known elements and steps are not described in the embodiments to avoid unnecessary restrictions to the present invention.
於實施方式與申請專利範圍中,涉及『電性連接』之描述,其可泛指一元件透過其他元件而間接電氣耦合至另一元件,或是一元件無須透過其他元件而直接電氣連結至另一元件。 In the embodiment and the scope of patent application, it refers to the description of "electrical connection", which can generally refer to an element indirectly electrically coupled to another element through other elements, or a element is directly electrically connected to another without other elements One component.
於實施方式與申請專利範圍中,涉及『連線』之描述,其可泛指一元件透過其他元件而間接與另一元件進行有線與/或無線通訊,或是一元件無須透過其他元件而實體連接至另一元件。 In the embodiment and the scope of patent application, the description refers to "connection", which can refer to a component indirectly wired and/or wirelessly communicated with another component through other components, or a component does not need to be physically through other components Connect to another component.
於實施方式與申請專利範圍中,除非內文中對於冠詞有所特別限定,否則『一』與『該』可泛指單一個或複數個。 In the embodiment and the scope of applying for a patent, unless there is a special limitation on articles in the text, "a" and "the" may refer to a single one or plural ones.
本文中所使用之『約』、『大約』或『大致』係用以修飾任何可些微變化的數量,但這種些微變化並不會改變其本質。於實施方式中若無特別說明,則代表以『約』、『大 約』或『大致』所修飾之數值的誤差範圍一般是容許在百分之二十以內,較佳地是於百分之十以內,而更佳地則是於百分五之以內。 The terms "about", "approximately", or "approximately" used in this article are used to modify any slightly variable quantity, but such slight changes will not change its essence. If there is no special explanation in the implementation mode, it means "approximately", "large" The error range of the value modified by "about" or "approximately" is generally allowed within 20%, preferably within 10%, and more preferably within 5%.
第1圖是依照本發明一實施例之一種方案接軌系統100的方塊圖。如第1圖所示,輸入輸出裝置110、儲存裝置120與處理裝置130。在架構上,輸入輸出裝置110、儲存裝置120與處理裝置130電性連接。實作上,舉例而言,輸入輸出裝置110可包含輸入設備與輸出設備,輸入設備可為向電腦輸入數據和信息的設備,輸出設備可用於數據的輸出,把各種計算結果數據或信息以數字、字元、圖像、聲音等形式表示出來。儲存裝置120可為硬碟、快閃記憶體或其他儲存媒介,處理裝置130可為中央處理單元(CPU)執行軟體程式(例如:解析分析裝置、規格與程式開發工具)。
FIG. 1 is a block diagram of a
為了闡述本案方案接軌的方式,請同時參照第1、2圖,第2圖是依照本發明另一實施例之一種瀑布模型200的示意圖。於運作上,儲存裝置120儲存裝置儲存瀑布模型200。若輸入輸出裝置110接收需求規格說明書,處理裝置130進行瀑布模型200之需求收集210,將需求規格說明書儲存於儲存裝置120。
In order to explain the way of connecting the solutions in this case, please refer to Figures 1 and 2 at the same time. Figure 2 is a schematic diagram of a
接下來,於瀑布模型200之系統分析220中,系統分析文件包含資料表、畫面以及規格,當作系統設計的雛形,讓系統設計階段的發展人員繼續維護使用。
Next, in the
接下來,於系統設計230中,繼續依據系統分析的要求,將資料表/畫面/規格進行完稿設計系統設計。系
統設計230解析上述資料表的關聯設定、上述畫面的編排與上述規格的邏輯設定,以產生代碼雛形框架(如:通用的基礎框架),讓程式開發人員可以專注於業務邏輯(如:客製化邏輯)的撰寫。
Next, in the
於瀑布模型200之程式開發240時,處理裝置130可執行上述的規格與程式開發工具以透過輸入輸出裝置110以提供上述規格的邏輯設定及描述的查詢,以及可查看系統分析220階段的規格描述,這樣可以確保程式邏輯與規格的一致性,提升系統的品質與穩定性。
During the
在本發明的一實施例中,輸入輸出裝置110可接收業務邏輯(如:客製化邏輯),於瀑布模型200之程式開發240時,處理裝置130結合業務邏輯與代碼雛形框架以產生系統代碼文件。
In an embodiment of the present invention, the input/
接下來,處理裝置130進行瀑布模型200之系統測試250,系統測試250測試系統代碼文件編譯出來的軟體系統。然後,於瀑布模型200之運行維護260,讓程式開發人員可以依據測試報告來做系統調整。
Next, the
在本發明的一實施例中,上述系統分析文件、代碼雛形框架與系統代碼文件均為結構性文檔。具體而言,為了解決系統分析220、系統設計230這幾個階段的規格描述和程式開發240階段代碼的貼合性,以及讓每個階段的產出都能夠讓下個階段當作發展基礎,減少重工,加快系統開發速度,本發明提供各階段分別適用的結構性文檔(如:XML),並搭配介面友善的實作工具,讓各階段的發展人
員能夠專注於各自的工作。
In an embodiment of the invention, the above-mentioned system analysis file, code prototype framework and system code file are all structural documents. Specifically, in order to solve the specifications of the stages of
舉例而言,系統分析220階段所規劃的資料表/畫面/規格則往下當作系統設計230階段的雛型;系統設計230階段繼續將沿用的資訊調整成設計成果,並產生代碼雛形,讓程式開發人員可以專注於業務邏輯的撰寫,加快系統開發速度。 For example, the data tables/screens/specifications planned in the 220 stage of system analysis are used as the prototype of the 230 stage of system design; the 230 stage of system design continues to adjust the information used to the design results and generate the prototype of the code, so that Program developers can focus on writing business logic and speed up system development.
在本發明的一實施例中,若輸入輸出裝置110接收需求變更的要求,處理裝置130可透過解析結構性文檔的工具(如:上述的解析分析裝置),將系統(如:軟體系統)運行的最終成果轉換為新的系統分析文件,依據需求變更的要求,以此新的系統分析文件進行規格調整。
In an embodiment of the present invention, if the input/
舉例而言,在運行維護階段,若關係人(例如:客戶)有需求變更的要求,則需求發展人員可透過本發明所提供的結構性文檔(如:XML)解析功能,將系統運行的最終成果(如:畫面)轉換為系統分析文件,內容會包含當初的系統分析規格,讓需求發展人員可以使用最新的成果來和關係人(如:客戶)進行溝通,加快溝通速度。 For example, in the operation and maintenance stage, if a related person (for example: a customer) has a requirement to change requirements, the demand developer can use the structural document (such as XML) parsing function provided by the present invention to finalize the operation of the system. Achievements (such as screens) are converted into system analysis files, and the content will include the original system analysis specifications, so that demand development personnel can use the latest results to communicate with related parties (such as customers) to speed up the communication.
為了對上述方案接軌系統100的運作方法做更進一步的闡述,請同時參照第1~3圖,第3圖是依照本發明一實施例之一種方案接軌方法300的流程圖。如第3圖所示,網路連線方法300包含步驟S301、S302(應瞭解到,在本實施例中所提及的步驟,除特別敘明其順序者外,均可依實際需要調整其前後順序,甚至可同時或部分同時執行)。
In order to further elaborate on the operation method of the above-mentioned
於步驟S301,提供系統分析文件包含資料表、畫面以及規格。 In step S301, the system analysis file is provided including the data table, the screen and the specifications.
接下來,於步驟S302,進行瀑布模型200之系統設計230,系統設計230解析資料表的關聯設定、畫面的編排與規格的邏輯設定,以產生代碼雛形框架以納入系統設計文件,系統設計文件也會回存到儲存裝置120。
Next, in step S302, the
在本發明的一實施例中,方案接軌方法300更包含:於瀑布模型200之程式開發240時,提供規格的邏輯設定及描述的查詢。
In an embodiment of the present invention, the
在本發明的一實施例中,方案接軌方法300更包含:若接收一業務邏輯,於瀑布模型200之程式開發240時,結合業務邏輯與代碼雛形框架以產生系統代碼文件。
In an embodiment of the invention, the
在本發明的一實施例中,上述系統分析文件、系統設計文件、代碼雛形框架與系統代碼文件均為結構性文檔。 In an embodiment of the invention, the above-mentioned system analysis file, system design file, code prototype framework and system code file are all structural documents.
在本發明的一實施例中,方案接軌方法300更包含:若接收需求變更的要求,可透過解析結構性文檔的工具,將系統運行的最終成果轉換為新的系統分析文件,依據需求變更的要求,以此新的系統分析文件進行規格調整。
In an embodiment of the present invention, the
綜上所述,本發明之技術方案與現有技術相比具有明顯的優點和有益效果。本發明的方案接軌系統100及方案接軌方法300發展了標準產品開發與個案修改協同一致系統設計的一體化,並支持後續二次開發時,仍能正向、逆向引入原規格的方式進行後續的擴充開發。各階段的結構化設計成果逐層沿用,取代原本複雜的本文交付,快速提升開發效能。
In summary, the technical solution of the present invention has obvious advantages and beneficial effects compared with the prior art. The
由最終程式結果還原系統分析文件,有效降低需求發展人員重工及提昇效能,快速明確地和關係人(例如:客戶)進行溝通。 The system analysis files are restored from the final program results, which effectively reduces the demand for development personnel to rework and improve efficiency, and quickly and clearly communicate with related parties (such as customers).
整個流程大幅提高效能,並從一般基礎只針對系統分析/系統設計/程式開發效能的提昇上,更有效擴展至需求發展時的效能,幫助了規劃人員與需求人員在溝通時的互動,也確保最後程式的達成與最原始的需求一致性最高。 The whole process greatly improves the efficiency, and from the general basis only for the improvement of system analysis/system design/program development performance, it is more effectively extended to the performance during the development of requirements, which helps the interaction between planners and demand personnel in communication, and also ensures The final program has the highest consistency with the original requirements.
雖然本發明已以實施方式揭露如上,然其並非用以限定本發明,任何熟習此技藝者,在不脫離本發明之精神和範圍內,當可作各種之更動與潤飾,因此本發明之保護範圍當視後附之申請專利範圍所界定者為準。 Although the present invention has been disclosed as above in an embodiment, it is not intended to limit the present invention. Anyone who is familiar with this art can make various modifications and retouching without departing from the spirit and scope of the present invention, so the protection of the present invention The scope shall be as defined in the appended patent application scope.
300‧‧‧方案接軌方法 300‧‧‧ Scheme connection method
S301、S302‧‧‧步驟 Steps S301, S302‧‧‧
Claims (6)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW107111930A TWI686719B (en) | 2018-04-03 | 2018-04-03 | Program integration system and method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW107111930A TWI686719B (en) | 2018-04-03 | 2018-04-03 | Program integration system and method |
Publications (2)
Publication Number | Publication Date |
---|---|
TW201942773A TW201942773A (en) | 2019-11-01 |
TWI686719B true TWI686719B (en) | 2020-03-01 |
Family
ID=69184633
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
TW107111930A TWI686719B (en) | 2018-04-03 | 2018-04-03 | Program integration system and method |
Country Status (1)
Country | Link |
---|---|
TW (1) | TWI686719B (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6701381B2 (en) * | 1998-09-03 | 2004-03-02 | Kimono Limited | Data processing system and development method |
TW200638220A (en) * | 2005-04-25 | 2006-11-01 | Univ Nat Chiao Tung | User interface producing system and method thereof |
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 |
CN100520716C (en) * | 2007-08-28 | 2009-07-29 | 北京中企开源信息技术有限公司 | Code automatically generating device based on model component, system and method |
-
2018
- 2018-04-03 TW TW107111930A patent/TWI686719B/en active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6701381B2 (en) * | 1998-09-03 | 2004-03-02 | Kimono Limited | Data processing system and development method |
TW200638220A (en) * | 2005-04-25 | 2006-11-01 | Univ Nat Chiao Tung | User interface producing system and method thereof |
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 |
CN100520716C (en) * | 2007-08-28 | 2009-07-29 | 北京中企开源信息技术有限公司 | Code automatically generating device based on model component, system and method |
Also Published As
Publication number | Publication date |
---|---|
TW201942773A (en) | 2019-11-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
RU2536390C2 (en) | Automated report generation method | |
WO2016197768A1 (en) | Chip verification method, device, and system | |
CN115617327A (en) | Low code page building system, method and computer readable storage medium | |
CN101996131A (en) | Automatic test method and automatic test platform for graphic user interface (GUI) based on x extensive makeup language (XML) packaging key word | |
CN106873974A (en) | Smart code generates automotive engine system and method | |
CN105260189A (en) | Code generating method and system based on model driving | |
WO2011006425A1 (en) | Method and platform for integrating a heterogeneous collaborative design system of work group and product lifecycle management system | |
CN106354492A (en) | Automatic code generation method and system capable of rapidly adjusting transaction process connection | |
CN107122173A (en) | A kind of adaptation activiti, the list generation method that can be pulled | |
CN105242914A (en) | Model driven code generation method and system | |
CN110968294B (en) | Business domain model establishing system and method | |
CN103593197A (en) | Method and device for generating codes | |
CN113065314B (en) | BIOS hardware adaptation method and device based on XML file format | |
WO2023179052A1 (en) | User-defined vehicle controller automatic modeling method | |
CN104156199B (en) | A kind of automatic continuous integrated approach of software and system | |
CN100483429C (en) | Verification operation supporting system and method of the same | |
US20100023922A1 (en) | Linking uml activity diagram nodes to uml class diagram nodes by using properties from applied stereotypes | |
CN108170466B (en) | A kind of C/C++ bugs self-repairing method based on program synthesis | |
CN105574219B (en) | The method of non-standard cell library logic unit automatic placement and routing | |
TWI686719B (en) | Program integration system and method | |
JP2013214278A (en) | Upper hierarchy description generating apparatus, method for generating upper hierarchy description, and program | |
WO2012055133A1 (en) | Method for configuring recipe editor of integrated circuit (ic) equipments | |
CN105426635A (en) | Skill program implementation method capable of establishing Differential Pair Gnd Vias automatically | |
JP2013020437A (en) | Requirements management support device | |
WO2021022702A1 (en) | Log insertion method and apparatus, computer apparatus and storage medium |