TWI753847B - Operation framework interface product and module code converter product - Google Patents

Operation framework interface product and module code converter product Download PDF

Info

Publication number
TWI753847B
TWI753847B TW104110175A TW104110175A TWI753847B TW I753847 B TWI753847 B TW I753847B TW 104110175 A TW104110175 A TW 104110175A TW 104110175 A TW104110175 A TW 104110175A TW I753847 B TWI753847 B TW I753847B
Authority
TW
Taiwan
Prior art keywords
field
information
category
interface
query
Prior art date
Application number
TW104110175A
Other languages
Chinese (zh)
Other versions
TW201539323A (en
Inventor
林勝雄
Original Assignee
林勝雄
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 林勝雄 filed Critical 林勝雄
Priority to TW104110175A priority Critical patent/TWI753847B/en
Publication of TW201539323A publication Critical patent/TW201539323A/en
Priority to CN201610182442.1A priority patent/CN106020787B/en
Application granted granted Critical
Publication of TWI753847B publication Critical patent/TWI753847B/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/35Creation or generation of source code model driven

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

A Process for Enhance System Development, Building Operation Framework Interface in advance. When the System Analyst and Designer understood the business scenario. First, Looking up the Operation Framework Interfaces to find the Function Frameworks and the Models to check if these meet the requirements. If not, then to build the Model by the Module Converter and to design the Function Framework, after the Function Framework is tested, then to build the Operation Framework Interface for System Analyst and Designer to reference and re-improvement in the future to meet the Core Spirit of OMG 'MDA Development Process.

Description

作業架構介面產品及模組程式碼轉換產品 Operational Framework Interface Products and Module Code Conversion Products

本發明係關於一種系統開發程序的改良,可運用於各種程式語言,目前以爪哇程式語言企業版(Java2Platform,EnterprisesEdition,J2EE)實現此發明。 The present invention relates to an improvement of a system development program, which can be applied to various programming languages. Currently, the invention is implemented in Java programming language Enterprise Edition (Java2Platform, Enterprises Edition, J2EE).

就習知的MDA(Model-DrivenArchitecture-模型驅動架構)在開發程序中,將建構模式分為三大階段,分別是:CIM、PIM及PSM。最後,程式設計師才依據PSM階段產出的UML模式,按圖編碼。首先,在CIM(ComputationIndependentModel-計算無關模型)階段,聚焦於系統環境及需求,但不涉及系統內部的結構與運作細節,而在PIM(PlatformIndependentModel-平台無關模型)階段,則聚焦於系統內部細節,但不涉及實作系統的實體平台。這個階段所建構出來的UML模式是與平台無關的。PSM(PlatformSpecificModel-平台特定模型)階段,則聚焦於系統落實於特定實體平台的細節,進言之,一般而言會藉由PIM的資訊產生與平台相關的元件,如JAVA或C++的元件(程式碼),並配合習知的MVC(Model-View-Controller:模型層-視圖層-控制層)開發架構做為系統開發架構的基礎,該開發架構,可分為視圖層(View)、控制層(Controller)、商務邏輯層(BusinessLogic)及資料存取層(DAO)。商務邏輯層(BusinessLogic)為一般用於處理請求內容,此層會引用PSM所產生的元件、DAO層、或其他因商務邏輯所需的元件,並將請求結果經由控制層回傳至視圖層(View),再由視圖層元件對表單欄位一一處理。 According to the known MDA (Model-DrivenArchitecture-Model-Driven Architecture) in the development process, the construction mode is divided into three stages, namely: CIM, PIM and PSM. Finally, programmers code according to the UML pattern produced in the PSM stage. First of all, in the CIM (ComputationIndependentModel-Computation Independent Model) stage, it focuses on the system environment and requirements, but does not involve the internal structure and operation details of the system, while in the PIM (PlatformIndependentModel-Platform Independent Model) stage, it focuses on the internal details of the system, But not the physical platform that implements the system. The UML schema constructed at this stage is platform independent. The PSM (PlatformSpecificModel-Platform Specific Model) stage focuses on the details of how the system is implemented on a specific physical platform. In other words, in general, platform-related components, such as JAVA or C++ components (codes, are generated from PIM information) ), and cooperate with the conventional MVC (Model-View-Controller: model layer-view layer-control layer) development architecture as the basis of the system development architecture. The development architecture can be divided into view layer (View), control layer ( Controller), business logic layer (BusinessLogic) and data access layer (DAO). The business logic layer (BusinessLogic) is generally used to process the request content. This layer will refer to the components generated by the PSM, the DAO layer, or other components required by business logic, and return the request results to the view layer through the control layer ( View), and then the view layer components process the form fields one by one.

就以習知之技術,因無更細緻之規範,使得開發時,為處理方便,忽略了DAO應有之相同方法(method)的歸納,即使有,其方法也不足以使用,如統計方法,或區間欄位的查詢,皆須寫於商務邏輯層,或其他類別,而無法使應有的相同的方法歸納於一上層的類別以提供商務邏輯層使用,使得相同操作流程之商務邏輯層亦須一再重寫。即使有MDA的開發流程,但無作業架構介面以提供分析、設計開發人員從即有的分析設計中提供參考,亦無法發揮其精神。 With the known technology, because there is no more detailed specification, during development, for the convenience of processing, the induction of the same method that DAO should have is ignored. Even if there is, the method is not enough to use, such as statistical methods, or The query of the interval field must be written in the business logic layer or other categories, and the same method cannot be summarized in an upper-level category to provide the business logic layer for use, so that the business logic layer with the same operation process must also be used. Rewrite again and again. Even if there is an MDA development process, but without a job architecture interface to provide analysis and design developers to provide reference from the existing analysis and design, its spirit cannot be exerted.

基於上述,為了統合目前所有架構,須要制定一套基礎開發架構。 Based on the above, in order to unify all the current architectures, it is necessary to develop a basic development architecture.

基於為了滿足開發上各類需求,並累積開發經驗,須於基礎開發架構上針對各類需求制定一特定開發架構,此架構以功能架構稱之。 Based on the fact that in order to meet various requirements in development and accumulate development experience, a specific development architecture must be formulated for various requirements on the basic development architecture. This architecture is called functional architecture.

經由開發經驗之積累與觀察,架構中之元件可透過轉換器(程式碼產生器)之技術取得,以縮短開發時程。 Through the accumulation and observation of development experience, the components in the framework can be obtained through the technology of converter (code generator) to shorten the development time.

本案以OMG’MDA(國際對象管理組織的模型驅動架構)的核心精神,即設計者了解商業情境後,不是立即開發模型,而是先行判斷是否有既有的模型,如果沒有再進行"塑模",再至"轉換器"產生元件,並且設計功能架構,於測試完成後,依其適用範圍(共用性)判斷以決定是否予以整理為作業架構介面以供日後系統分析、設計人員、程式開發人員參考並加以循環改善。 This case is based on the core spirit of OMG'MDA (Model-Driven Architecture of the International Object Management Organization), that is, after the designer understands the business situation, he does not develop a model immediately, but firstly judges whether there is an existing model. ", and then go to "Converter" to generate components, and design the functional structure. After the test is completed, it is judged according to its scope of application (community) to decide whether to organize it into an operation framework interface for future system analysis, designers, and program development. People refer to and make circular improvements.

塑模方式是藉由一系統(模組轉換系統)的方式提供,即於客戶端提供塑模者一網路應用程式的操作介面以輸入模型資訊,通過網路傳送模型資訊至系統,由系統以模組架構轉換器依塑模者的模型資訊產生該模組架構程式庫,以提供塑模者下載開發及測試;或由系統下載模組架構轉換器至客戶端的網路應用程式,並以塑模者所提供的模型資訊產生該模組架構程式庫。 The molding method is provided by a system (module conversion system), that is, the client provides the molder with an operation interface of a network application program to input the model information, and the model information is transmitted to the system through the network, and the system The module framework converter is used to generate the module framework library according to the model information of the molder, so as to provide the molder to download, develop and test; or the system downloads the module framework converter to the client's web application, and uses Model information provided by the molder generates the module framework library.

藉由定義一基礎架構(類別繼承架構)及其所提供的應用程式介面(API),該應用程式介面主要包括有:表格資訊類別、表單欄位資訊類別,並藉由表單欄位資訊類別所提供的方法而達成欄位權限的控管;一功能架構,以一商務邏輯類別為主,引用表格資訊類別(EIO)、表單欄位資訊類別(FIO),以及表格資訊邏輯層/類別(EIOLogic)所提供之的方法,完成一共同處理程序的架構,並加以文件整理,而形成功能架構介面,結合應用程式介面(API)及功能架構介面,而形成一作業架構介面。接下來,以實施方式說明所謂的模型,表格的觀念,並以一實例客戶資料表及其關聯表格,說明藉由模組架構轉換器實作基礎架構所提供的應用程式介面及相關類別。 By defining a basic framework (class inheritance framework) and the application programming interface (API) it provides, the application programming interface mainly includes: form information class, form field information class, and is defined by the form field information class. Provides a method to achieve the control of field permissions; a functional structure, mainly based on a business logic category, referring to the table information category (EIO), the form field information category (FIO), and the table information logic layer/category (EIOLogic The method provided by ) completes the framework of a common processing program, and organizes the documents to form a functional framework interface, and combines the application programming interface (API) and the functional framework interface to form an operation framework interface. Next, the concept of the so-called model and table is explained in an embodiment, and an example of the customer data table and its associated table is used to illustrate the application programming interface and related categories provided by the implementation of the infrastructure by the module architecture converter.

第一圖:是客戶資料關聯圖。 The first picture: is the customer data association diagram.

第二圖:是類別繼承架構圖。 The second picture: is the class inheritance architecture diagram.

第三圖:是功能架構基本流程循序圖。 Figure 3: It is a sequential diagram of the basic flow of the functional architecture.

第四圖:是EIO及FIO繼承架構圖。 Figure 4: It is the inheritance architecture diagram of EIO and FIO.

第五圖:是開發程式庫架構圖。 The fifth picture: is the development program library architecture diagram.

第六圖:是功能架構-關聯式單表格-初始化及查詢。 The sixth picture: it is the functional architecture - associative single table - initialization and query.

第七圖:是功能架構-關聯式單表格-修改及保存。 The seventh picture: is the functional architecture - associative single table - modification and saving.

第八圖:是功能架構-關聯式單表格-新增及保存。 The eighth picture: it is the functional architecture - associative single table - adding and saving.

第九圖:是功能架構-關聯式單表格-刪除及確定。 The ninth picture: is the functional architecture - associative single table - delete and confirm.

請參考第一圖:客戶資料關聯圖,包括有Customer(客戶)表格、Sex(性別)表格、Degree(學歷)表格、CustomerAddr(客戶地址)表格以及Address(地址)表格,由觀察各表格之關聯、資料欄位並以表格資料維護之功能加以抽象思考,可歸納並分類為幾種類型,例如:Sex表格及Degree表格便可為一類型,因其維護表格資料之操作方式相似甚至相同;Address表格則為另一類型,因 其維護表格資料之操作方式須先建立市/縣資料,再建立鄉/鎮/區資料,再建立道路或街名;更廣義的思考,當然亦可將Sex表格、Degree表格及Address表格視為同一類型,然而則須更高的技術層次始可達成;而Customer表格,則另為一類型,因其關聯多個表格且有關聯一一對多的明細檔(CustomerAddr),故所謂的模型,即是,由觀察並依經驗而加以分類的各類型。註:更進一步思考,相似於Customer(客戶)的模型為何?如Employee(員工);相似於Address(地址)的模型為何?如Department(部門)。 Please refer to the first picture: customer data correlation diagram, including Customer (customer) table, Sex (gender) table, Degree (educational education) table, CustomerAddr (customer address) table and Address (address) table, by observing the correlation of each table , Data fields and abstract thinking with the function of table data maintenance, can be summarized and classified into several types, for example: Sex table and Degree table can be one type, because the operation method of maintaining table data is similar or even the same; Address Tables are another type, because The operation method of maintaining table data must first create city/county data, then create township/town/district data, and then create road or street names; in a broader thinking, of course, Sex table, Degree table and Address table can also be regarded as The same type, however, requires a higher technical level to achieve; and the Customer form is another type, because it is associated with multiple forms and is associated with a one-to-many detail file (CustomerAddr), so the so-called model, That is, types classified by observation and by experience. Note: Think further, what is the model similar to Customer? Such as Employee (employee); what is the model similar to Address (address)? Such as Department (department).

各種模型類型皆有其資料流程及維護的操作特性,故而須不同的功能架構,將某功能架構運用UML(UnifiedModelingLanguage-统一建模語言)加以詳述並加以文件整理,而可成為該模型共同流程架構介面,即一功能架構介面。 Each model type has its data flow and maintenance operation characteristics, so different functional structures are required. A functional structure is described in detail and documented by UML (Unified Modeling Language), which can become the common process of the model. Architecture interface, that is, a functional architecture interface.

所謂的表格,除一般資料定義語言(DDL)所創建的表格,進一步,亦可視為一資料之集合,透過結構化查詢語言(SQL)於各表格中以關聯的方式(innerjoin,outerjoin,crossjoin等等)而取得之一結果集,以下所述之表格,即包含單一表格及關聯之結果集。 The so-called table, in addition to the table created by the general data definition language (DDL), can also be regarded as a collection of data, through the structured query language (SQL) in each table in a related way (innerjoin, outerjoin, crossjoin, etc. etc.) to obtain a result set, the table described below includes a single table and an associated result set.

為實現上述功能架構介面,以二部分做為說明:一為垂直部分,即類別繼承架構(請參考第二圖:類別繼承架構圖),此架構為基礎架構,提供開發過程中各類別之繼承依據,即各類別可依其功能之特性,分門別類而形成一繼承架構,最終以Model(模型)為最上層之父類別。另一為水平部分,即功能架構,運用基礎架構已定義之上層/上位類別,或整合現行開源架構,或自行開發,並以習知之MVC架構加以改良,經由開發經驗之積累,將原有DAO層之改良為EIO層,並提供FIO層,及EIOLogic層,並結合視圖層元件使之成為可循環改善之架構(請參考第三圖:功能架構基本流程循序圖)。 In order to realize the above functional architecture interface, two parts are used as an illustration: one is the vertical part, namely the class inheritance architecture (please refer to the second figure: class inheritance architecture diagram), this architecture is the basic architecture, which provides the inheritance of each class in the development process The basis is that each category can be classified into categories according to the characteristics of its functions to form an inheritance structure, and finally the Model (model) is the parent category at the top level. The other is the horizontal part, that is, the functional architecture. The upper layer/superior category has been defined by the basic architecture, or the existing open source architecture is integrated, or it is developed by itself and improved with the known MVC architecture. Through the accumulation of development experience, the original DAO The improvement of the layer is the EIO layer, and provides the FIO layer and the EIOLogic layer, and combines the view layer components to make it a structure that can be improved cyclically (please refer to the third figure: the basic flow sequence diagram of the functional structure).

一、類別繼承架構:以Model為最上層之父類別,繼之以Module(模組)、EntityInformation(EIO)、FieldInformation(FIO)為其子類別;繼之以Operation(作業/操作)為Module之子類別。 1. Class inheritance architecture: Model is the parent class at the top, followed by Module (module), EntityInformation (EIO), and FieldInformation (FIO) as its subclasses; followed by Operation (job/operation) as the child of Module category.

1.表格資訊類別(EIO:EntityInformationObject):增強習知之資料存取層(DAO)之存取功能,用以處理表格之資料查詢、維護、統計及表格欄位名稱、外鍵欄位關聯值之取用,並整理為各個相同方法的名稱而歸納成為一上位/上層之類別,以提供下層類別繼承以實作EIO所定義之方法(請參考第四圖:EIO及FIO繼承架構圖)。 1. Form information category (EIO: EntityInformationObject): Enhance the access function of the conventional data access layer (DAO), which is used to process data query, maintenance, statistics and table field name, foreign key field associated value Take and organize the names of the same methods into a higher-level/upper-level category, so as to provide the lower-level category inheritance to implement the methods defined by EIO (please refer to the fourth figure: EIO and FIO inheritance structure diagram).

1.1.查詢欄位(SKey):為下層類別實作EIO查詢欄位的集合,包括表格所之定義的主鍵、非主鍵並增加區間欄位使之可以含蓋對單一表格大部分查詢欄位的需求,其相對應類別為SText(表單查詢欄位值類別)。 1.1. Query field (SKey): implements a collection of EIO query fields for the lower class, including the primary key and non-primary key defined by the table, and adds interval fields to cover most of the query fields in a single table. requirements, the corresponding category is SText (form query field value category).

2.表單欄位資訊類別(FIO:FieldInformationObject):定義一上位/上層之類別,用以處理表格欄位資料轉換為表單查詢欄位及表單欄位並附有維護欄位驗証、長度資訊之類別,且各欄位可依其所關聯欄位顯示其表單欄位型態,使得商務邏輯層可藉此更容易控制取得所需之欄位,進而達成控管欄位權限之功能。 2. Form field information category (FIO: FieldInformationObject): define a upper/upper-level category, which is used to process the conversion of table field data into form query fields and form fields, and a category with maintenance field validation and length information , and each field can display its form field type according to its associated field, so that the business logic layer can more easily control and obtain the required fields, thereby achieving the function of controlling field permissions.

3.表單查詢欄位值類別(SText):用以定義存取表單查詢欄位值及表單查詢欄位邏輯運算元及比較運算元(=、!=、<及like等等)的存取類別,一般相應於查詢欄位(SKey)。 3. Form query field value type (SText): used to define the access type for accessing the form query field value and the logical operator and comparison operator (=, !=, < and like, etc.) of the form query field , generally corresponding to the query field (SKey).

4.Operation(作業/操作)類別,用以提供將特定格式字串或網頁參數值轉為物件之功能,並為商務邏輯層繼承之基礎類別。 4. Operation (operation/operation) category, which is used to provide the function of converting a specific format string or webpage parameter value into an object, and is the basic category inherited by the business logic layer.

二、功能架構:以一商務邏輯類別為主,並繼承自Operation類別,引用類別繼承架構的上層類別表格資訊類別(EIO)、表單欄位資訊類別(FIO),以及表格資訊類別邏輯(EIOLogic)所提供之的方法,完成一共同處理程序的架構,並予以封裝而再利用(請參考第三圖:功能架構基本流程循序圖)。 2. Functional Architecture: Mainly based on a business logic category, which inherits from the Operation category, and refers to the upper-level categories of the category inheritance structure, Form Information Category (EIO), Form Field Information Category (FIO), and Table Information Category Logic (EIOLogic) The provided method completes the structure of a common processing program, and encapsulates it for reuse (please refer to the third figure: the basic flow sequence diagram of the functional structure).

1.表格資訊邏輯層/類別(EIOLogic):用以細分並累積出商務邏輯處理中相同程序之資料處理方法,運用EIO所提供之資料查詢、維護、統計的方法,並配合查詢欄位(SKey)與表單查詢欄位值類別(SText)所組成之條件,使得可將開發經驗上之各種資料處理模式、交易控管方式及訊息回覆方式予以封裝而再利用。 1. Form information logic layer/category (EIOLogic): It is used to subdivide and accumulate the data processing methods of the same procedures in business logic processing. ) and the form query field value type (SText), which makes it possible to encapsulate and reuse various data processing modes, transaction control methods, and message response methods from development experience.

為區分開發繼承架構各層之不同功能,將之區分為三部分,一為核心程式庫、二為功能架構程式庫、三為模組架構程式庫(請參考第五圖:開發程式庫架構圖),並以模組架構轉換器實作基礎架構中所定義之上位/上層類別EIO、FIO的方法,以縮短開發時程。 In order to distinguish the different functions of each layer of the development inheritance architecture, it is divided into three parts, one is the core library, the second is the functional architecture library, and the third is the module architecture library (please refer to Figure 5: Development Library Architecture Diagram) , and use the module architecture converter to implement the methods of the upper/upper layer classes EIO and FIO defined in the infrastructure to shorten the development time.

1.核心程式庫,包含有:Model(模型)、Module(模組)、EntityInformation(實體資訊)、FieldInformation(欄位資訊)等類別,為基礎架構之核心類別。 1. Core library, including: Model (model), Module (module), EntityInformation (entity information), FieldInformation (field information) and other categories, which are the core categories of the infrastructure.

2.功能架構程式庫,包含有:Operation、經循環改善後而形成之各種商務邏輯(Bizlogic)類別及EIOLogic。 2. The functional framework library, including: Operation, various business logic (Bizlogic) categories and EIOLogic formed after cycle improvement.

3.模組架構程式庫,透過模組架構轉換器,依模型資訊(如表一)、實作應用程式介面(如表四、表五)-表格資訊類別、表單欄位資訊類別所定義的上層方法,其所產生的類別,包含有:Entity(實體)、EntitySText(實體表單查詢欄位值類別),EntityEIO(實體表格資訊類別)、EntityFIO(實體表單欄位資訊類別)(註:Entity(實體)為一上位概念之詞,一般相應於表格名稱,以表一所提供之模型資訊為例,則產生之類別為:Customer(客戶)、CustomerSText(客戶表單查詢欄位值類別)、CustomerEIO(客戶表格資訊類別)、CustomerFIO(客戶表單欄位資訊類別),Sex、SexSText(性別表單查詢欄位值類別)、SexEIO(性別表格資訊類別)、SexFIO(性別表單欄位資訊類別),Degree(學歷)、DegreeSText(學歷表單查詢欄位值類別)、DegreeEIO(學歷表格資訊類別)、DegreeFIO(學歷表單欄位資訊類別)。 3. The module framework library, through the module framework converter, according to the model information (such as table 1), the implementation of the application programming interface (such as table 4, table 5) - table information category, form field information category defined The upper-level method, the generated categories include: Entity (entity), EntitySText (entity form query field value category), EntityEIO (entity table information category), EntityFIO (entity form field information category) (Note: Entity ( Entity) is a high-level concept word, which generally corresponds to the table name. Taking the model information provided in Table 1 as an example, the generated categories are: Customer (customer), CustomerSText (customer form query field value category), CustomerEIO ( Customer form information type), CustomerFIO (customer form field information type), Sex, SexSText (gender form query field value type), SexEIO (gender form information type), SexFIO (gender form field information type), Degree (educational education ), DegreeSText (category of educational degree form query field value), DegreeEIO (category of educational degree form information), DegreeFIO (category of educational degree form field information).

請參考表一為一模型資訊,依第一圖:客戶資料關聯圖提供之表格資訊並延伸表單資訊以提供轉換器產生模組架構程式庫。 Please refer to Table 1 for a model information, according to the table information provided in Figure 1: Customer Data Association Diagram and extend the form information to provide the converter to generate the module framework library.

1.維護欄位為新增及修改時依型態之定義而呈現不同的輸入欄位,並依是否有關聯其他表格之外鍵而呈現其應有之值。 1. When adding and modifying the maintenance field, different input fields are presented according to the definition of the type, and its proper value is presented according to whether it is related to other foreign keys in the table.

2.查詢欄位,即上述的SKey,依型態之定義而呈現不同的輸入欄位,並依是否有關聯其他表格之外鍵而呈現其應有之值。 2. The query field, that is, the above-mentioned SKey, presents different input fields according to the definition of the type, and presents its proper value according to whether it is related to other foreign keys in the table.

3.查詢欄位的D/L欄:D表示該欄位為應顯示為區間欄位以供查詢輸入;L表示該欄位會附帶有一邏輯欄位,用以與下一欄位組成一邏輯判斷。 3. The D/L column of the query field: D indicates that the field should be displayed as an interval field for query input; L indicates that the field will be accompanied by a logical field to form a logic with the next field judge.

4.維護欄位驗証:為提供視圖元件依此資訊做欄位資料正確性之檢核。 4. Maintenance field verification: Check the correctness of field data based on this information in order to provide view components.

Figure 104110175-A0305-02-0004-1
Figure 104110175-A0305-02-0004-1

透過上表並以轉換器產生模組架構程式庫之類別,以Customer示例說明,以下以表格的方式說明各比較重要之屬性、方法及執行結果。註:執行結果請參考第一圖:客戶資料關聯圖的客戶資料的表格資料。 Through the above table and using the converter to generate the type of module framework library, take Customer as an example to illustrate, the following describes the more important properties, methods and execution results in the form of a table. Note: For the execution results, please refer to the first figure: the table data of the customer data of the customer data association diagram.

Customer:依表格的名稱及其欄位名稱、資料形態、主鍵、外鍵等等資訊,透過轉換器產生而得。註:方法中應有之參數為方便說明予以省略。 Customer: According to the name of the table and its field name, data form, primary key, foreign key and other information, it is generated through the converter. Note: The parameters that should be in the method are omitted for the convenience of description.

Figure 104110175-A0305-02-0004-2
Figure 104110175-A0305-02-0004-2
Figure 104110175-A0305-02-0005-3
Figure 104110175-A0305-02-0005-3

CustomerSText:依SKey(id、year、sex、createDate),並透過轉換器產生而得,用以存取表單查詢欄位之值。註:1.年齡及創建日期為區間欄位,分別以from(從)及to(到)作為字首組成一屬性。2.年齡附帶了邏輯欄位,以Logical(邏輯)為字尾組成一屬性。 CustomerSText: Based on SKey (id, year, sex, createDate), and generated through a converter, it is used to access the value of the query field of the form. Note: 1. Age and creation date are interval fields, and form an attribute with from (from) and to (to) as prefixes respectively. 2. Age comes with a logical field, and it forms an attribute with Logical as the suffix.

Figure 104110175-A0305-02-0005-4
Figure 104110175-A0305-02-0005-4

CustomerEIO:依上位/上層類別所定義之方法,並依撰寫程式經驗及表一所提供表格之欄位名稱、資料形態、主鍵、外鍵等等資訊而透過轉換器產生而得,用以維護及查詢Customer表格。 CustomerEIO: It is generated by the converter according to the method defined by the upper-level/upper-level category, and based on the programming experience and the information of the field name, data form, primary key, foreign key, etc. Query the Customer table.

Figure 104110175-A0305-02-0005-5
Figure 104110175-A0305-02-0005-5
Figure 104110175-A0305-02-0006-6
Figure 104110175-A0305-02-0006-6

CustomerFIO:依上位/上層類別所定義之方法,並依撰寫程式經驗及表一所提供表單之欄位名稱、資料形態、主鍵、外鍵等等資訊而透過轉換器產生而得,用以提供Customer表格操作介面之欄位名稱及欄位輸入型態。 CustomerFIO: According to the method defined by the upper/upper-level category, and based on the programming experience and the information of the field name, data form, primary key, foreign key, etc. of the form provided in Table 1, it is generated through the converter to provide the Customer The field name and field input type of the form operation interface.

Figure 104110175-A0305-02-0006-8
Figure 104110175-A0305-02-0006-8
Figure 104110175-A0305-02-0007-9
Figure 104110175-A0305-02-0007-9

註:經由上述之歸納整理,將EIO、FIO形成一應用程式介面(應用程式介面呈現如表四、表五),並加入一該模型共同流程架構介面(即功能架構介面),而成為作業架構介面。 Note: After the above summary, EIO and FIO are formed into an application programming interface (the application programming interface is shown in Table 4 and Table 5), and a common process framework interface (ie functional framework interface) of the model is added to become the operation framework interface.

以一關聯式單表格資料維護操作情境及一功能架構,並以Customer關聯模型所產生的Customer模組類別為例,說明一功能架構介面之形成。 Taking a relational single table data maintenance operation situation and a functional framework, and taking the Customer module category generated by the Customer relational model as an example, the formation of a functional framework interface is described.

關聯式單表格資料維護功能架構介面註:此為基本介面範例,將依經驗的積累而循環改善。 Relational single table data maintenance functional structure interface Note: This is an example of the basic interface, which will be improved cyclically based on the accumulation of experience.

一、基本功能:1.資料驗証:依表一所設定之表單驗証資訊處理驗証。2.欄位邏輯:省略。3.商務邏輯:省略。4.排序功能:點選各表單欄位名稱時,依遞增遞減交替排序。 1. Basic functions: 1. Data verification: Process verification according to the form verification information set in Table 1. 2. Field logic: omitted. 3. Business logic: omitted. 4. Sorting function: When clicking the name of each form field, it will be sorted alternately in ascending and descending order.

二、操作功能: 2. Operation function:

1.請參考第六圖:功能架構-關聯式單表格-初始化及查詢。 1. Please refer to Figure 6: Functional Architecture-Associative Single Table-Initialization and Query.

1.1初始化情境:初始化時顯示查詢欄位,功能按鈕(新增、修改、刪除、保存)及表單欄位名稱。 1.1 Initialization situation: The query field, function buttons (add, modify, delete, save) and form field name are displayed during initialization.

1.2查詢情境:輸入查詢條件,點選[確定]後,依查詢條件顯示資料於表查詢欄位下方,並附有一已勾選欄位之欄位。 1.2 Query Context: Enter the query conditions, click [OK], and the data will be displayed below the table query field according to the query conditions, and a field with a checked field will be attached.

2請參考第七圖:功能架構-關聯式單表格-修改及保存。 2 Please refer to Figure 7: Functional Architecture-Associative Single Table-Modify and Save.

2.1修改及保存情境:點選[修改],將已勾選資料依修改功能架構流程轉換為附有輸入型態之資料,以供修改;於修改完成,點選[保存],將已勾選資料依修改後保存功能架構流程資料更新,並顯示資料於操作介面上。 2.1 Modify and save the context: Click [Modify], and convert the checked data into data with input type according to the modification function structure process for modification; after the modification is completed, click [Save], and the selected data will be checked. The data is updated according to the data saved in the functional structure process after modification, and the data is displayed on the operation interface.

3.請參考第八圖:功能架構-關聯式單表格-新增及保存。 3. Please refer to Figure 8: Functional Architecture-Associative Single Form-Add and Save.

3.1新增及保存情境:點選[新增]後,依新增功能架構流程,於第一筆,顯示一筆附有輸入型態且已關連之空白欄位,以供輸入;於新增完成,點選[保存],將已勾選資料依新增後保存功能架構流程資料更新,並顯示資料於操作介面上。 3.1 Add and save context: After clicking [Add], according to the structure flow of the new function, in the first stroke, a blank field with an input type and associated with it is displayed for input; after the addition is completed , and click [Save] to update the selected data according to the data of the function framework process of saving after adding, and display the data on the operation interface.

4.請參考第九圖:功能架構-關聯式單表格-刪除及確定。4.1刪除及確定情境,點選[刪除]後,顯示再確認訊息,點選[確定]後,將已勾選資料依刪除及確定功能架構流程,完刪資料之刪除,並更新資料顯示於操作介面上。 4. Please refer to Figure 9: Functional Architecture - Relevant Single Table - Delete and Confirm. 4.1 Delete and confirm the situation, click [Delete], a re-confirmation message will be displayed, after clicking [OK], the selected data will be deleted and confirmed according to the functional structure process, the deletion of the deleted data will be completed, and the updated data will be displayed in the operation. on the interface.

依上述即為一功能架構介面的基本說明,可依此架構及關聯模型做為基礎,並依相似的關聯模型的特殊需求加以個別說明,並以參數方式處理,累積多數相同的特殊需求及說明而成為基本功能之擴充,而使該功能架構更趨完善。 The above is the basic description of a functional architecture interface, which can be based on this architecture and related models, and individually explained according to the special requirements of similar related models, and processed in parameter mode, accumulating most of the same special requirements and descriptions And become the expansion of the basic function, and make the function structure more perfect.

進言之,依不同的關聯模型,則再訂出不同的功能架構介面,如客戶資料表中尚關聯一明細檔(地址),其介面操作模式可依關聯式單表格資料維護功能架構介面加以延伸,或以新思維訂定一MD(Master-Detail:主檔-明細檔)功能架構介面,然而地址之功能架構介面則可設想為階層式功能架構介面,並依關聯式單表格資料維護功能架構介面之形成方式,而成為另一功能架構介面。 In other words, according to different association models, different functional framework interfaces are defined. For example, if a detail file (address) is still associated in the customer data table, the interface operation mode can be extended according to the function framework interface for maintaining the data in the relational single table. Or define a MD (Master-Detail: master file-detail file) functional framework interface with new thinking, but the functional framework interface of the address can be conceived as a hierarchical functional framework interface, and maintain the functional framework interface according to the relational single table data The way of forming, and become another functional framework interface.

上述為一般較為靜態的關聯模型,更進言之,則有動態的之資料模型如買賣交易檔、工作流程檔等等,此等之資料模型表格,則透過結構化查詢語言SQL)而成為一表格之概念,而其功能架構流程的商務邏輯層則需處理之多數個表格,同樣依關聯式單表格資料維護功能架構介面之形成方式,而成為一交易功能架構介面(由於模型之EIO及FIO分皆有提供相同方法,而可以實現一共同處理程序的架構)。 The above are generally more static relational models. More specifically, there are dynamic data models such as trading transaction files, workflow files, etc. These data model tables are converted into a table through structured query language (SQL). The business logic layer of its functional architecture process needs to deal with multiple tables, which is also a transaction functional architecture interface according to the formation method of the relational single-table data maintenance function architecture interface (due to the EIO and FIO points of the model). Both provide the same method, and can implement a common handler architecture).

以上所述僅為本發明之較佳實施例,任何類別提供相似方法,但其名稱不同,或方法名稱不相同,但其執行結果相似或相同,或依本發明申請專利範圍所做之均等變化與修飾,皆應屬本發明之涵蓋範圍。 The above is only the preferred embodiment of the present invention, any category provides similar methods, but the names are different, or the method names are different, but the execution results are similar or the same, or equivalent changes made according to the scope of the patent application of the present invention and modifications, all should fall within the scope of the present invention.

Claims (10)

一種提升軟體開發生產力的程式碼轉換產品,用以產生一程式庫,包含有:一轉換器/程式碼產生器,用以產生實作於應用程式介面的類別,或一表單查詢欄位值類別,用以存取表單查詢欄位的名稱、值、邏輯運算元以及比較運算元而組成一或複數類別的程式庫,該應用程式介面,包含有:一表格資訊類別,其一表格係單一表格及關聯之結果集,提供新增、修改、刪除、查詢、統計等資料處理的功能;或一表單欄位資訊類別,提供表格欄位值轉換為表單查詢欄位或表單欄位。 A code conversion product for improving software development productivity for generating a library, including: a converter/code generator for generating a class implemented in an application programming interface, or a form query field value class , which is used to access the names, values, logical operands and comparison operands of form query fields to form a library of one or more classes. The application programming interface includes: a form information class, one of which is a single form and the associated result set, providing functions for data processing such as adding, modifying, deleting, querying, and statistics; or a form field information category, providing the conversion of table field values into form query fields or form fields. 如請求項1所述的程式碼轉換產品,其表格資訊類別的資料處理功能的結構化查詢語言的語法的組成係:藉由一表格資訊類別的屬性名稱與一表單查詢欄位值類別的屬性名稱、屬性值、邏輯運算元及比較運算元的排列組合所組成的語法,或由一表格資訊類別的欄位/屬性名稱與一表單欄位資訊類別的欄位名稱、欄位值所組成的語法。 The code conversion product according to claim 1, wherein the syntax of the structured query language of the data processing function of the table information category is composed of: an attribute name of a table information category and an attribute of a table query field value category A syntax consisting of a permutation and combination of names, attribute values, logical operands, and comparison operands, or a field/attribute name of a table information category and a field name and field value of a table field information category grammar. 如請求項1所述的程式碼轉換產品,其表單欄位資訊類別的功能,尚包含有:各欄位驗証、長度之資訊,以及各欄位依其所關聯欄位顯示其表單欄位。 According to the code conversion product of claim 1, the function of the form field information category further includes: each field validation, length information, and each field displays its form field according to its associated field. 如請求項1所述的程式碼轉換產品,其表單查詢欄位值類別的欄位係:一表格的主鍵欄位、非主鍵欄位、區間欄位、以及上述欄位的邏輯運算元以及比較運算元欄位。 The code conversion product according to claim 1, wherein the fields of the form query field value category are: a primary key field, a non-primary key field, an interval field, and the logical operators and comparisons of the above fields Operand field. 一種程式碼轉換的方法,包含:藉由輸入一模型資訊至一轉換器/程式碼產生器以產出一程式庫,該模型資訊,包含有:表格的欄位名稱、資料形態、主鍵、可否空值、外鍵;表單的欄位名稱、長度、欄位驗証及型態,以及查詢欄位之型態,及其為區間欄位或邏輯欄位。 A method for code conversion, comprising: generating a code library by inputting a model information to a converter/code generator, the model information including: field name of a table, data form, primary key, availability Null value, foreign key; form's field name, length, field validation and type, and the type of query field, and whether it is an interval field or a logical field. 如請求項5程式碼轉換的方法,其輸入模型資訊至一轉換器/程式碼產生器的方法,尚包含:或藉由網路下載並安裝、或藉由電子媒體安裝一轉換器/程式碼產生器,並輸入該模型資訊;或藉由網路傳送該模型資訊至一轉換器/程式碼產生器。 As claimed in the method for code conversion of item 5, the method of inputting model information to a converter/code generator further comprises: either downloading and installing via the Internet, or installing a converter/code via electronic media generator, and input the model information; or send the model information to a converter/code generator through the network. 一種作業架構介面產品,包含有:一或複數的功能架構介面,其一功能架構介面,包含有:一或複數應用程式操作介面,用以說明該作業的關聯模型、功能及流程,其關聯模型的資料處理流程會引用或如請求項1所述的程式碼轉換產品的一或複數表格資訊類別或其被實 作的類別;或如請求項1所述的程式碼轉換產品的一或複數表單欄位資訊類別或其被實作的類別;或如請求項1所述的程式碼轉換產品的一或複數表單查詢欄位值類別;或引用上述類別的交互排列組合以說明該作業功能之資料處理流程。 An operation framework interface product, including: one or more functional framework interfaces, one functional framework interface, including: one or more application programming interface, used to describe the related model, function and process of the operation, its related model The data processing flow will reference or code conversion product as described in claim 1 one or more table information categories or their actual class of work; or one or more form field information classes of a code conversion product as described in claim 1 or the class in which it is implemented; or one or more forms of a code conversion product as described in claim 1 Query the field value category; or refer to the interactive arrangement and combination of the above categories to explain the data processing flow of the operation function. 如請求項7作業架構介面產品,其應用程式操作介面中的關聯模型,尚包含有:靜態或動態關聯模型。 For example, the operation framework interface product of claim 7, the association model in the application program interface still includes: static or dynamic association model. 一種建構作業架構介面的功能架構的功能及流程的方法,包含有:藉由繪製一流程圖,並說明其功能,或引用如請求項1所述的程式碼轉換產品的一或複數表格資訊類別或其被實作的類別;或引用如請求項1所述的程式碼轉換產品的一或複數表單欄位資訊類別或其被實作的類別;或引用如請求項1所述的程式碼轉換產品的一或複數表單查詢欄位值類別;或引用上述類別的交互排列組合而形成該作業功能架構各類別間互動的流程。 A method for constructing functions and processes of a functional framework of an operation framework interface, comprising: by drawing a flow chart and explaining its functions, or referencing one or more table information categories of the code conversion product described in claim 1 or a class in which it is implemented; or a reference to one or more form field information classes of a code conversion product as described in claim 1 or a class in which it is implemented; or a reference to a code conversion as described in claim 1 One or more forms of the product query the field value category; or refer to the interactive arrangement and combination of the above categories to form the interaction flow between the categories of the operation function framework. 如請求項9建構作業架構介面的功能架構的功能及流程的方法,尚包含有:應用程式操作介面的欄位權限控管功能,其方法為:藉由引用如請求項1所述的程式碼轉換產品的一或複數表格資訊類別或其被實作的類別,以及一或複數表單欄位資訊類別或其被實作的類別且以一或複數參數取得其參數部分的表單欄位而達成應用程式操作介面的欄位權限控管功能。 According to claim 9, the method for constructing the function and process of the functional framework of the operation framework interface further includes: the field permission control function of the application program operation interface, and the method is: by referencing the code as described in claim 1 Converts one or more form information classes or their implemented classes, and one or more form field information classes or their implemented classes of a product and obtains the form fields of its parameter part with one or more parameters for application The field permission control function of the program operation interface.
TW104110175A 2015-03-30 2015-03-30 Operation framework interface product and module code converter product TWI753847B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
TW104110175A TWI753847B (en) 2015-03-30 2015-03-30 Operation framework interface product and module code converter product
CN201610182442.1A CN106020787B (en) 2015-03-30 2016-03-28 Operation architecture interface and module conversion system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW104110175A TWI753847B (en) 2015-03-30 2015-03-30 Operation framework interface product and module code converter product

Publications (2)

Publication Number Publication Date
TW201539323A TW201539323A (en) 2015-10-16
TWI753847B true TWI753847B (en) 2022-02-01

Family

ID=54851361

Family Applications (1)

Application Number Title Priority Date Filing Date
TW104110175A TWI753847B (en) 2015-03-30 2015-03-30 Operation framework interface product and module code converter product

Country Status (2)

Country Link
CN (1) CN106020787B (en)
TW (1) TWI753847B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101776999A (en) * 2010-01-28 2010-07-14 苏州工业园区进一科技有限公司 Platform for developing and implementing software system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050060317A1 (en) * 2003-09-12 2005-03-17 Lott Christopher Martin Method and system for the specification of interface definitions and business rules and automatic generation of message validation and transformation software
CN101241434A (en) * 2008-03-04 2008-08-13 浪潮集团山东通用软件有限公司 Form self-defining method
CN103631570A (en) * 2012-08-21 2014-03-12 镇江雅迅软件有限责任公司 Form self-definition method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101776999A (en) * 2010-01-28 2010-07-14 苏州工业园区进一科技有限公司 Platform for developing and implementing software system

Also Published As

Publication number Publication date
CN106020787A (en) 2016-10-12
TW201539323A (en) 2015-10-16
CN106020787B (en) 2021-03-23

Similar Documents

Publication Publication Date Title
Mazairac et al. BIMQL–An open query language for building information models
Lerman Programming Entity Framework: Building Data Centric Apps with the ADO. NET Entity Framework
KR101665152B1 (en) Extending collaboration capabilities to external data
CN101454779B (en) Search-based application development framework
US7735062B2 (en) Software development system and method
Muñoz et al. Automatic generation of ETL processes from conceptual models
US20060168577A1 (en) Software development system and method
US20060168555A1 (en) Software development system and method
US10248386B2 (en) Generating a software complex using superordinate design input
US20120124550A1 (en) Facilitating database application code translation from a first application language to a second application language
JP2018514878A (en) A computer-implemented method for displaying software-type applications based on design specifications
CN103914290A (en) Operating command processing method and device
US20230086854A1 (en) Dynamically controlling case model structure using case fragments
US10474435B2 (en) Configuration model parsing for constraint-based systems
Naujokat et al. Meta-level reuse for mastering domain specialization
US10289620B1 (en) Reporting and data governance management
Tauscher et al. A modular graph transformation rule set for IFC‐to‐CityGML conversion
EP1684170A2 (en) Software development system and method
JP6427687B2 (en) System design apparatus and method
TWI753847B (en) Operation framework interface product and module code converter product
US10318524B2 (en) Reporting and data governance management
Dogdu et al. A data-model driven web application development framework
Maruna et al. The business process transformation framework implementation through metamodel extension
US9405793B2 (en) Native language support for intra-and interlinked data collections using a mesh framework
Souza et al. A UML Profile for Modeling Framework-based Web Information Systems.