Process and system for automatic generation of functional architecture documents and software design and analysis specification documents from natural language - Patents.com
The system addresses the inefficiencies of manual translation by directly generating software design documents from natural language descriptions, ensuring accurate and scalable software design.
Patent Information
- Application Number
- JP2021570418
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-05-28
- Filing Date
- 2020-05-28
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-05-28
AI Technical Summary
The current methods for translating natural language descriptions of software requirements into technical designs suffer from significant inaccuracies and inefficiencies due to the need for manual interpretation and translation by experts, leading to discrepancies between requester needs and final products.
A system that automatically processes natural language descriptions using predefined hierarchical rules to generate functional architecture and software design documents directly from user input, eliminating the need for manual translation and ensuring consistent, accurate representation of requirements.
This approach ensures complete and accurate software design generation, reducing errors and costs associated with manual translation, and enabling scalable, evolutionary designs.
Smart Images

Figure 0007581249000019 
Figure 0007581249000020 
Figure 0007581249000021
Abstract
Description
[Technical field]
[0001] This application claims the benefit of the filing date of U.S. Provisional Patent Application No. 62 / 154,093, entitled "Proceso para generar documentos de especificacion de analisis y de diseno" (Process for generating analysis and design specification documents), filed on April 28, 2015 by the same inventors of this application. The above-mentioned provisional applications are incorporated herein by reference as if published herein.
[0002] The present invention relates generally to the process of modeling reasoning with formal logic that is similar to the abstract thinking that humans use to process natural language, and more particularly to deriving process models from natural language-based case specifications. [Background technology]
[0003] The prior art discloses devices for the automatic generation of software design documents from requirements expressed in terms that are stored in a knowledge base, based on which they model "classes" (in the context of object-oriented programming) that are subsequently visualized as UML diagrams. The prior art also discloses systems and methods for formalizing natural language such that the resulting language can be processed by a computer.
[0004] US Patent Application Publication No. 2013 / 0097583 discloses a system and method that provides an automated support tool to guide / help software engineers to create software products. The system includes input / output, storage, processing, and communication devices. The system assists software engineers to identify and graphically display use cases derived from requirements, actors or entities, systems, and subsystems with one or more phrases describing the involved requirements and actors or entities, and to generate domain models and UML class diagrams for visualizing the domain models. The system also enables the creation of extended use cases, the creation of object interaction models, the creation of sequence diagrams, and the creation of design class diagrams. Based on the design class diagrams, software engineers can create high-quality computer programs. The system may include or be connected to a diagram generator for automatically generating UML (Unified Modeling Language) class diagrams. Unlike our invention, the input of the patent is software requirements written in natural language. Our invention consists of natural language sentences describing a business "case". The input of said patent is one of the specific cases that our invention can solve. The parser (word recognition technology) is conventional and dictionary-based. Our inventive parser is automatic and dictionary-free rule-based. Our invention improves accuracy with much shorter processing time. US2013 / 0097583 requires the involvement of a software engineer to design and develop code supported by diagrams generated by the patent's invention to achieve a complete software design. In our invention, the resulting design is complete, automatic, and contains 100% of the design stated in the explanatory text. Our abstraction of the conceptual domain model is formal, meaning the design always follows the same rules and therefore produces predictable results. In US2013 / 0097583, the conceptual model is 20% handcrafted and case-dependent. do.
[0005] US Patent Application Publication No. 2011 / 0239183 discloses a method in which one or more process models are derived from a natural language use case model. For example, a processor using and accessing a use case model stored in a memory obtained from natural language text information described using a limited list of predefined words with preassigned meanings can convert the model stored in the memory into a process model according to a predefined modeling notation. In the present invention, the design is performed at the level of a functional architecture document based on an open-ended natural language from which different types of software design diagrams can be obtained.
[0006] Every industry faces the challenge of improving its construction process, and the main source of error in that process is the difference between the requester's description (the "case") and what the industry produces (the solution).
[0007] Now, someone wanting to describe the "case" to build a solution based on the above description needs the following: - Industry analyst interprets and documents. This documentation is done by the analyst taking notes on the requester's comments on the "case". Then the analyst analyzes the documentation and creates some diagrams by applying one of the well-known techniques of the industry. When the documentation is well considered, they are sent to the "case" design stage. The content of these diagrams depends solely on the expert's interpretation and his / her ability to convert them into the aforementioned diagrams specific to each industry. - An industry designer who designs the desired solution based on the analysis and above-mentioned documentation for the described "case". The designer takes the analysis diagrams and meets with the analyst for clarifications that allow the designer to maximize his / her accurate understanding of the diagrams, and based on that understanding, the designer can design a solution for the "case". This design is performed by creating other diagrams, which are also industry-dependent. These diagrams represent a new translation of the logic described by the requester into the technical language needed to build a solution for the "case".
[0008] Both analysts and designers are experts trained to understand the case description and translate it into technical analysis and design language that can then be interpreted by those building the solution. That is, several languages are used from the description of the "case" to the start of building the associated solution (see Figure 4 Industrial Design Process). A. Language for describing the "case" (intervening role: requester who imposes requirements): Natural language B. Analysis language of the "case" (intervening role: industry analyst interprets requirements and transforms them into analysis drawings): drawings using standard industry notation, hand-drawn drafts, with supporting explanations expressed in natural language with a design-oriented focus. C. Case Design Language (intervening roles: designer, design engineer who interprets the analyst's work and transforms it into blueprints): Architectural drawings, plans, and diagrams specific to the industry of use that represent the design of the solution.
[0009] The person requesting that a particular solution be designed (requester) is usually not an accomplished designer in a particular industry and therefore cannot build the solution himself. The requester needs industrial analysts and industrial designers to properly interpret the requester's requirements and incorporate those requirements into the design of a solution for the "case". It thus happens that this is not possible in practice because the requester does not understand the design language (design engineers, civil engineers, book designers, software designers, among other applications) and therefore cannot control the resulting design to ensure that a solution is built for the "case" described by the requester. As shown in Figure 1, this is usually where the largest part of the deviation between the description "case" and the actual construction (solution) lies, since there is usually a distortion in the understanding of the meaning due to the change in language. As a result, the requester receives a design and resulting product (house, software, furniture, book, etc.) that is not fully tailored to the requester's needs.
[0010] The industry is constantly working to increase the degree of convergence between the solution and the requester's description of the requester's needs. These efforts focus on improving current methods by training the experts or improving the tools used in their work, without replacing the experts' participation in the handcrafted process of interpreting and structuring said descriptions.
[0011] This approach to dealing with technical problems inevitably generates multiple interpretations of requirements, since the translation of the language used by the requirements person (natural language) into the language used by the analysts and designers (technical language) involves a translation that causes loss of knowledge and which no one can strictly control.
[0012] In the present invention, it is sufficient to use structured sentences in natural language to completely describe a "case". There is no need to manually convert said sentences into diagrams using graphical technical notation to allow understanding and communication of the knowledge contained in the description. These diagrams are generated automatically from the natural language by tools.
[0013] The differences between what currently exists and the present invention are shown in the table below (Figure 4 Industrial Design Process).
[0014] [Table 1]
[0015] Given a real-world description of what a particular industrial design is desired, based on what said description represents, the system structures a natural language description, thereby ensuring the storage of the entire linguistic components of the "case" in a semantically interconnected and coherent manner, and automatically builds a functional architecture document that is useful in multiple industrial applications.
[0016] The present invention illustrates the use of functional architecture documents and their components to build software design applications.
[0017] In this invention, the description of a "case" refers to a real problem for which we want to build a software application that allows a computer to process its logic. Thus, the software industry of "cases" is faced with the task of improving software construction projects whose main error factor is the difference between the requester's description (the problem) and what the "case" solves (the solution). Currently, anyone who wants to describe a "case" on which a software solution should be built needs: - A system analyst interprets and documents. This documentation is generated by the analyst writing down the client's comments about the "case". Then the analyst analyzes the documentation and creates some diagrams by applying one of the well-known techniques of the industry (UML diagrams, flow diagrams, process diagrams). When the documentation is well considered, they are submitted for the "case" design stage. The content of these diagrams depends solely on the analyst's interpretation and his / her ability to transform them into the diagrams mentioned above. - A software designer who designs said software that must allow the automated capture of data generated throughout the described "case". The designer obtains the analysis diagrams, meets with the analyst for clarifications that allow the designer to maximize the designer's accurate understanding of the diagrams, and based on that understanding, the designer can design the "case". This design is performed by creating other diagrams such as database diagrams (for storing system data), screen diagrams (where data upload, retrieval and processing are performed), functional logic diagrams of the "case" (representing the logic of the problem to be solved), architecture diagrams (defining, among other things, the internal organization of the "case" to function in an effective, reliable and sustainable way, client-server, SOA: Service Oriented Architecture). These diagrams represent a new translation of the logic described by the requester into the technical language necessary to build a solution for the "case".
[0018] Both analysts and designers are trained experts whose purpose is to understand the case description and translate it into technical analysis and design languages that can then be interpreted by those developing the application. Figure 1 compares the prior art with the present invention in terms of the languages used in the stages of "case" understanding and translation, from the beginning of the "case" description to software design. In the prior art, the following languages are used: A. Language for describing the "case" (role involved: user imposing requirements): Natural language B. Case Analysis Language (Intervening role: a system that interprets user requirements and transforms them into analysis diagrams): data flow charts, analysis use cases with supporting explanations expressed in natural language with a design-oriented focus. C. The "Case" Design Language (intervening roles: designer, a design engineer who interprets the analyst's work and transforms it into design drawings): a diagram (nowadays mostly UML) representing the functional design of the application, a database diagram representing the design of the database that stores the user data, an architecture diagram representing the layered architecture of the application to be built.
[0019] The type of user who needs custom designed software is typically not a software designer or software development engineer, and therefore cannot build the software themselves: they need analysts and designers to properly interpret their requirements and incorporate those requirements into the resulting design of the "case."
[0020] So what happens is that this is not possible in practice because the requester does not understand the design language and therefore has no control over the resulting design to ensure that the "case" he requested is built. This is where the largest part of the gap between the request (problem) and the actual build (solution) lies. That is, the result is that the requester receives a design and resulting product (software) that is usually not fully aligned with the requester's requirements, modifications, or subsequent changes (which may take longer or be more complex and expensive than originally expected in some cases).
[0021] The industry is making significant efforts to arrive at a solution to this problem through CASE (Computer Aided Software Engineering) tools, but these tools do not work with natural language and therefore present some of the limitations mentioned above.
[0022] This approach to dealing with technical problems inevitably generates multiple interpretations of the problem, since no one can have strict control over it, and translation between the language used by the users or clients who know the process well (natural language) and the language used by the analysts and designers (technical language) involves translations that cause loss of knowledge. [Prior art documents] [Patent documents]
[0023] [Patent Document 1] US Patent Application Publication No. 2013 / 0097583 [Patent Document 2] US Patent Application Publication No. 2011 / 0239183 Summary of the Invention [Means for solving the problem]
[0024] The present invention uses natural language as the sole language for describing, analyzing, and designing software solutions, thereby minimizing knowledge loss that leads to distorted results.
[0025] Unlike the prior art, the present invention allows for a complete description of a "case" using a simple sentence of natural language. Unlike the prior art, the present invention does not require the conversion of said sentence into a diagram that uses a graphical technical notation to understand and communicate process knowledge. Instead, said diagram is automatically generated by the present invention based on natural language using a single deterministic model by applying analysis rules that implement the functional logic of said model that identifies the conceptual components of the language.
[0026] Structuring the description in a single sentence based on a predefined hierarchy of concepts ensures the completeness of the description and allows high-quality software designs to be inferred automatically.
[0027] In order to facilitate understanding of the present invention and to allow easy distinction between the present invention and that available in the prior art, the following comparison table is presented.
[0028] [Table 2]
[0029] Current prior art dictates that software is designed manually or partially manually, which by its very nature results in the following problems, among others: ambiguity in interpreting system requirements, high cost of correcting design errors, difficulty in scaling and developing the design, and out-of-date documentation. The present invention overcomes these difficulties by being based on a fully automated, industrializable process, thereby achieving conceptual rigor, generating scalable evolutionary designs, generating automatically updated documentation, and significantly reducing the cost of software design.
[0030] 4. Glossary Sentence: The smallest possible syntactic composition capable of conveying a statement or expressing the content of a logical proposition. Simple sentence: Contains a single verb. complete simple sentence: a sentence which, from the point of view of the present invention, explicitly answers all stated questions. Natural Language: Natural language is what we call spoken or written language used by humans for normal communication purposes. Functional Requirements: As defined in requirements engineering, functional requirements determine the behavior of a system. Global functional requirements group other more detailed functional requirements that relate to the behavior of the system itself. Class diagram: A diagram that shows the different classes that make up a system and their relationships to each other. A class diagram also shows the classes along with their methods and attributes and their relationships to each other. Case universe: The set of definitions and concepts surrounding the "case". Compound noun: A noun made up of two or more words. For example, price list, document number. +: In this specification, + means "concatenate" to join or add text. Eligible language: Since different languages can be used to describe a "case", it is possible to describe each of them using their respective syntactic and grammatical structures. Concatenate: Given one or more words, concatenation means combining those words into a single phrase separated by spaces. Example: "the", "house". Concatenation of the two words results in "the house". Ground Rule: In the present invention, a ground rule is a behavioral structure defined by a question, the purpose of which is to indicate the morpho-syntactic sequence of words that contains the answer to said question. DO: means direct object. In the present invention, DO refers to the noun word that appears in a What question and follows a transitive verb. [Brief description of the drawings]
[0031] [Figure 1] FIG. 2 is a diagram illustrating the process of natural language conversion of the present invention. [Diagram 2] FIG. 2 illustrates steps in the process of the present invention for obtaining a functional architecture document. [Diagram 3] FIG. 1 illustrates a system of the present invention. [Figure 4] FIG. 2 illustrates steps in the process of the present invention for obtaining a software design document. [Figure 4A] FIG. 1 shows stage A. [Figure 4A1] FIG. 1 is a diagram illustrating the MAS metamodel. [Figure 4A2] FIG. 1 illustrates morphological and syntactic rules. [Figure 4A3] FIG. 13 illustrates an example of application of the MAS metamodel. [Figure 4B] FIG. 1 shows stage B. [Figure 4C] FIG. 1 shows stage C. [Figure 4D] FIG. 1 shows stage D. [Figure 4E] FIG. 1 shows stage E. [Figure 4E1] FIG. 1 illustrates the functional logic of a processor 150 configured as an automatic sentence analyzer 151. [Figure 4F] FIG. 1 shows stage F. [Figure 4F1] FIG. 1 is a functional architecture diagram. [Figure 4G] FIG. 1 shows stage G. [Figure 4G1] FIG. 1 illustrates the functional logic of a processor 150 configured as an automated software designer 152. [Figure 4G2] FIG. 4G2 shows stage 4G2. [Figure 4G2A] FIG. 13 is a diagram showing an example of an FX step. [Figure 4G2B] FIG. 13 is a diagram showing an example of a CC step. [Figure 4G3] FIG. 4G3 shows step 4G3. [Figure 4G3A]FIG. 13 is a diagram illustrating an example of a QS step. [Figure 4H] FIG. 1 shows stage H. [Figure 4I] FIG. 1 shows Stage I. [Figure 4I1] This is a software design diagram. [Figure 4I2] FIG. 2 is a diagram showing the structure of a business document. [Figure 4I3] FIG. 1 is a diagram showing the structure of an analysis document. [Diagram 5] FIG. 13 is a diagram illustrating an example of a class design. [Figure 6] FIG. 1 is a diagram relating to a graphical notation to be used in a functional architecture diagram. [Figure 7] FIG. 1 is a diagram relating to a graphical notation for software design documentation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0032] The present invention provides a solution to the above-mentioned problems by a method implemented by a computer and a visual device for the generation of software design specification documents from requirements expressed in natural language phrases describing cases, stored in a knowledge base. These phrases make it possible to model design components that are subsequently transformed and visualized as class diagrams for the software design. The device may be adapted to interact with a processor.
[0033] First, the process begins with a description of a "case" in a natural language, as shown in Figure 4. In order to carry out said description in the present invention, it is necessary to establish in advance what language will be used in the description, including, among other things, the grammatical and syntactic features of the language, such as the order of adjectives, indicating whether the adjectives are placed before or after the noun, and the list of words that contain the articles of the language.
[0034] To describe a "case" in any language with a defined syntactic structure and grammatical rules, a system such as that shown in FIG. 3 is used to input a natural language "case" description by means of an input / output device 120. The input text is transferred to main memory for later use by a processor 150. The processor is configured to automatically analyze, design and generate documents. The results of each processing function are stored in a database memory 130.
[0035] The components of the system 100 from FIG. 3 are described below. 1. Input / Output Device 120: A device into which natural language text is captured. The input / output device 120 uses the following configuration to present a structure into which a user can input "case" description data, and allows the processor to use a display medium (screen, projector, television, printer, monitor, mobile device, among others) to display the resulting document. a. Language User Interface 121: a visual structure that allows the user to select a language and upload the grammatical and syntactic features of that language which are then stored in the database memory 130. b. Case User Interface 122: A visual structure that allows the user to upload simple sentences describing a "case" that are then stored in the database memory 130. This structure also allows the user to interact with the functions of the processor 150 configured as an automatic sentence analyzer 151 and an automatic software designer 152. c. Formatting, Graphical Notation, and STD Statement User Interface 123: In one embodiment of the present invention, the user is presented with this visual structure that enables the user to add or modify the formats, graphical notations, and STD statements available in the static database memory 160 in preparation for business, analysis, and design documents to be constructed by the processor 150 configured as an automatic document generator 153. d. Document Display User Interface 124: A structure that allows a user to access documents generated by a processor 150 configured as an automatic document generator 153. 2. CPU 110: The processing device of the system 100. This device is designed to execute all of the natural language processing functions for the automatic design generation and contains a main memory that allows the interaction between said functions and the other components of the system. Main Memory 140: A volatile storage device used to transfer information between the input / output device, database memory, and processor. Depending on its configuration, the main memory 140 performs the following functions: i. Figure 141: An arrangement of main memory enabling document processing by a processor 150 configured as an automatic document generator 153 by using formats, graphical notations and STD statements 163 stored in a static database memory 160. ii. Sentence matrix 142: a main memory configuration enabling processing of simple sentences by a processor 150 configured as an automatic sentence analyzer 151 by using the MAS metamodel 161, language, vocabulary, and morphological-syntactic rules 162 stored in a static database memory 160. iii. FC matrix 143: A main memory configuration that enables processing of functional components by a processor 150 configured as an automatic sentence analyzer 151 by using the MAS metamodel 161, language, vocabulary, and morphological-syntactic rules 162 stored in a static database memory 160. iv. DC matrix 144: A main memory configuration that enables processing of design components by a processor 150 configured as an automated software designer 152 by using the MAS metamodel 161, language, words, and morphological-syntactic rules 162 stored in a static database memory 160. b. Processor 150: A device on which processing and switching tasks are performed. Depending on its configuration, the processor 150 performs the following functions: i. Automatic Sentence Analyzer 151: A processor component primarily tasked with automatically generating functional components from simple sentences and sending those functional components to the dynamic database memory 170 for storage. ii. Automated Software Designer 152: A processor configuration tasked primarily with automatically generating design components from simple statements and transmitting those design components to the dynamic database memory 170 for storage. iii. Document Generator 153: A processor configuration primarily tasked with automatically generating design components from simple sentences and sending those design components to the dynamic database memory 170 for storage. 3. Database Memory 130: A persistent memory that stores data uploaded by users and generated by the processor 150 in various configurations of the processor 150. This memory has two storage configurations: one static configuration and one dynamic configuration. The static configuration stores required fixed data that is uploaded for one-time processing and is not "case" specific. The dynamic configuration stores "case" specific data that is uploaded for each case. a. Static Database Memory 160: i. MAS Metamodel 161: A configuration of database memory 130 that contains the rules of highly abstract formal logic that give rise to the language, words, and morpho-syntactic rules stored in morpho-syntactic rule structures 162 of database memory 130. ii. Languages, Words, and Morpho-syntactic Rules 162: A configuration of the database memory 130 containing features of the eligible languages, special words for each eligible language, and the morpho-syntactic rules for that eligible language. iii. Formats, Graphical Notations, and STD Statements 163: Configurations in the database memory 130 that contain the formats applied to the documents, the graphical notations applied to the figures, and the STD statements required for the preparation of the analysis documents. b. Dynamic Database Memory 170: i. Simple sentence questions 171: A configuration of the database memory 130 containing simple sentences uploaded by the user and answers to the questions When, Who, What, How, and Where corresponding to each simple sentence. ii. Functional components 172: Configuration of database memory 130 containing functional components automatically generated by processor 150 configured as automatic sentence analyzer 151. iii. Design components 173: Configuration of the database memory 130 containing design components that have been automatically generated by the processor 150 configured as the automated software designer 152.
[0036] In using the above-described system, the present invention performs a series of steps as illustrated in FIG. 4 and further described below.
[0037] Phase A. Upload the MAS metamodel 161 to the logical structure of the MAS metamodel 161 in the static database memory 160 using the input / output device 120 .
[0038] Phase B. Enter the eligible languages, grammatical and syntactic features of each eligible language using the language user interface 121 on the display device 120 and store that data in a logical structure of languages, words, and morphological-syntactic rules 162 in the static database memory 160.
[0039] Phase C. Enter a description of the "Case" as text in one of the natural languages selected from the list of eligible languages from Phase B using the case user interface 122 on the display device 120. Identify the steps of the "Case" and then store those steps in a logical structure of simple sentences and questions 171 in the dynamic database memory 170.
[0040] Step D. Identify simple sentences and mathematical moments of the "case" corresponding to the step based on Step C, and store those simple sentences and mathematical moments in a logical structure of simple sentences and questions 171 in the dynamic database memory 170 using the case user interface 122 of the display device 120.
[0041] Phase E. Automatically identifying functional and mathematical components of a single sentence based on phase D, with the processor 150 configured as an automatic sentence analyzer 151 that operates according to the logical structure of the MAS metamodel 161 uploaded in phase A (it should be understood that a functional component corresponds to each word of the sentence that is extracted and automatically characterized by the processor 150). The processor 150 keeps temporarily storing said functional components in the logical structure of the FC matrix 143 in the main memory 140. Finally, these components are stored in the logical structure of functional components 172 in the dynamic database memory 170.
[0042] Phase F. Automatically identify design components of the "case" based on the functional and mathematical components from Phase E. It should be understood that design components refer to each software design model corresponding to the functional and mathematical components automatically generated by the processor 150. The design components are created using the processor 150 configured in one embodiment of the present invention as an automated software designer 152 that operates according to the logical structure of the MAS metamodel 161 uploaded in Phase A. The processor 150 keeps temporarily storing said design components in the logical structure of the DC matrix 144 in the main memory 140. Finally, these components are stored in the logical structure of the design components 173 in the dynamic database memory 170.
[0043] Phase G. Using the Format, Graphical Notation, and STD Sentence user interface (of the display device 120), input output formats for business, analysis, and design documents, parameters for standard sentences for requirements, and graphical notations for design drawings, and store them in the logical structure of Format, Graphical Notation, and STD Sentence 163 in the static database memory 160.
[0044] Phase H. Using the format, graphical notation and STD sentences defined in phase G, processor 150 configured as document generator 153 automatically generates business documents (business documents are understood as step-by-step descriptions in natural language of the problem to be solved) from the single sentences from phase D, automatically generates analysis documents (analysis documents are understood as descriptions of the functional requirements of the software to be built) based on the functional and mathematical components from phase E, and automatically generates design documents (design documents are understood as documents containing instructions for building the software) based on the design components from phase F.
[0045] Phase I. Automatically generating a functional architecture document (a functional architecture document is understood to be a graphical diagram that structures in the form of a summary the meaning of a natural language text by representing essential concepts of meaning) based on the functional and mathematical components from phase E by a processor 150 configured as a document generator 153 using a graphical notation specifically defined for this type of document.
[0046] The steps of the process are explained in detail below.
[0047] Phase A. Uploading the MAS Metamodel At this stage, the MAS metamodel and its axiomatic principles are detailed. This metamodel is used to establish the behavior of the processor 150 in its configuration as an automatic sentence analyzer 151.
[0048] 4A1 shows a class model according to the object-oriented paradigm that represents the rules that this metamodel defines to model the logic for the interpretation of natural languages. These rules are used as the basic morphological and syntactic rules that a processor 150 configured as an automatic sentence analyzer 151 uses to generate functional components in stage D.
[0049] At this stage, the MAS metamodel is created by the following sub-stages (Figure 4A):
[0050] Sub-step A1. Memorizing the MAS metamodel At this sub-stage, the logic of the MAS metamodel 161 is uploaded into the static database memory 160 .
[0051] This logic dictates that every word contained in the natural language description is a Word 161-1. When the word is a transitive verb, two new words are automatically defined: Performer Word 161-2, whose name is the transitive verb plus the suffix "ER" to indicate the agent, and Performable Word 161-3, whose name is the transitive verb plus the suffix "BLE." The transitive verb is Performance Word 161-4, which has a relationship 161-5 with Performer Word 161-2 and another relationship 161-6 with Performable Word 161-3.
[0052] Words 161-1 relate to one another such that non-transitive words may define an inheritance relationship 161-9 with a Performer Word 161-2 and / or an inheritance relationship 161-8 with a Performable Word 161-3.
[0053] Each word 161-1 can define an inheritance relationship 161-0 with another word 161-1. Each word 161-1 can define an association relationship 161-7 with another word 161-1.
[0054] The use of the options offered by the MAS metamodel depends on the morphosyntax of the sentence being processed in stage D.
[0055] In this way, all words in the description can be represented by this metamodel, which, taken as a whole, defines the axiomatic rules for the language, assuming that it is satisfied in all cases, and represents a basis for modeling any morpho-syntactic rules of any language.
[0056] Sublevel A2. Memory of MAS logic of morpho-syntactic rules In this sub-stage, the logic of the MAS metamodel is uploaded to the static database memory 160. The logic defines how to characterize words of a natural language to determine their meaning in the context of different functional applications. The structures that deal with the form and syntax of a natural language are called morphological-syntactic structures.
[0057] In the present invention, a set of guidelines for handling natural language is considered as morpho-syntactic rules. Such rules consist of a) question logic: which question (When, Who, What, How, Where) a word in a simple sentence belongs to, b) step type logic: which type of verb constitutes a What question (FX, CC, QS, L, F), and c) word logic: guidelines for handling text that define what type of word it is. The type of word is determined by the grammatical characterization of the word as a verb (VERB), noun (NOUN), preposition (PREP), article (ART), conjunction (CONJ), adverb (ADV).
[0058] An identifier is defined for each morpho-syntactic rule. The identifier of a morpho-syntactic rule is constructed by concatenating the types of words that make up the sentence, except for the types Performer, Performable, and Performance. The identifier could be, for example, ART-NOUN-VERB-ART-PREP-NOUN for sentences consisting of a sequence of words of the following types: article, noun, verb, article, preposition, noun. Words of these types can be treated generally or can refer to specific words of that type. For example, the rule VERB(is)-PREP-NOUN indicates that the sentence to which this rule applies contains a verb, and in particular the word "is" in the word type VERB, followed by an optional preposition PREP, and then an optional noun NOUN. This rule applies to the sentence: is a monkey, is a moon.
[0059] That is, for every simple sentence there exist morpho-syntactic rules that define its structure according to the types of words that compose it.
[0060] Given a simple sentence, the processor 150 configured as an automatic sentence analyzer 151 excludes from the sentence the special words, articles, conjunctions, and prepositions uploaded in sub-stage B2 before the corresponding morpho-syntactic rule identifiers are constructed. The processor 150 then searches the static database memory 160 for the morpho-syntactic rules in the language, word, and morpho-syntactic rule 162 construction. Once a rule with that corresponding identifier is found, if there are two or more rules with the same corresponding identifier, the processor 150 searches in this collection for a match on the special word from the type of words excluded during the construction of the sentence rule identifiers. If there is a match, the processor 150 assigns the rule that matches the particular excluded word. If there is no match, the processor 150 assigns a general rule.
[0061] The MAS metamodel defines the following basic rules from which specific rules for different cases are derived:
[0062] Basic rules There are two basic rules related to the What question, each with its own speciality. - VERB-NOUN rules: General case: VERB-NOUN rule 161-12: Allows modeling sentences that have verb, noun, and noun structures. Specific case: VERB(is)-NOUN rule 161-10: Allows to model sentences with verb-noun structures whose verb is the verb "to be". This verb is a special verb from the point of view of the application of the MAS metamodel. - VERB-NOUN-PREP-NOUN rule: General Case: VERB-NOUN-PREP-NOUN Rule 161-11: Allows modeling sentences with verb, noun, preposition, noun structures. Specific case: VERB(hold responsible)-NOUN-PREP-NOUN rule 161-13: Allows to model sentences with a verb-noun structure where the verb is "to hold responsible". This verb is a special verb from the point of view of the application of the MAS metamodel. Specific case: VERB(link)-NOUN-PREP-NOUN rule 161-14: Allows to model sentences with verb-noun structures whose verb is the verb "to link". This verb is a special verb from the point of view of the application of the MAS metamodel.
[0063] Similarly, there are basic rules for modeling Who in a simple sentence. - NOUN rule: This rule is present in every simple sentence and makes it possible to model the behavior of the main noun that refers to the subject.
[0064] For When, How, and Where questions that do not require mandatory completion, the types of words that appear in the answer are identified and the necessary rule identifiers are generated.
[0065] In one embodiment of the present invention, a user can add basic rules and morphological-syntactic rules at any time according to the logic of the MAS metamodel.
[0066] Given a simple sentence of a natural language, once the morpho-syntactic rules have been found, a processor 150 configured as an automatic sentence analyzer 151 generates functional components by applying guidelines for dealing with the text defined by the rules, namely a) question logic, b) step type logic, and c) word logic, as shown in FIG. 4A2.
[0067] (a) Query logic: determining the question to which the word to which the rule applies belongs Note that a description is a collection of simple sentences that describes a process. Each step of such a process is matched with one simple sentence derived from the answers to the questions Who, What, Where, How, and When.
[0068] (b) Step type logic: Determines the step type to which the word to which the rule applies belongs. Each step can be classified into a step type, which is determined in the rule by the specific words associated with the verb in the What question. Based on the MAS metamodel, every morphosyntactic rule can be classified into the following types, namely, check / verify, query / search, calculate, relational, functional, and inform / alert, depending on the specific verb linked to the What question.
[0069] CC Step: (Step that determines the check / verification action) These are steps where a verb such as check, confirm, restrict, etc. defines a checking or confirming action. In this case, the verb is transitive and the noun following the verb is always combined with a statement that expresses the mathematical logic for the system.
[0070] This step type is assigned a VERB-NOUN morphological-syntactic rule identifier, which adds a mathematical description of the checking / validation logic.
[0071] Some examples of this type of sentence are: check that the items have a positive inventory (VERB-NOUN, "have positive inventory" is the mathematical logic of confirmation), confirm that the client has a tax ID number (VERB-NOUN, "has a tax ID number" is the mathematical logic of confirmation), and restrict the intake of expired merchandise (VERB-NOUN, "expired merchandise" is the mathematical logic of confirmation).
[0072] QS Step (Step containing a Query / Search action) These are steps where verbs such as search, locate, select, query, indicate, display, show, etc. define a query or retrieval action. In this case, the verb is transitive and the noun following the verb indicates the subject of the search / query.
[0073] This step type is assigned a VERB-NOUN morpho-syntactic rule identifier where the noun describes the object of the search, ie, the verb applies to a set of instances of the noun.
[0074] Some examples of this type of statement are: query the items(VERB-NOUN), show the balances(VERB-NOUN), display the data(VERB-NOUN), show the results(VERB-NOUN), search the items(VERB-NOUN), locate the spare parts(VERB-NOUN), select the clients(VERB-NOUN).
[0075] FX Steps (steps that contain explicit calculation actions) An FX step is a step where a verb, such as calculate, group, average, add, etc., explicitly defines a computational action. In this case, the verb is always combined with a statement that expresses the mathematical logic for the system.
[0076] This step type is assigned the VERB-NOUN morpho-syntactic rule identifier, where the noun explains the logic of the computation indicated by the verb.
[0077] Some examples of this type of sentence are calculate the total sales(VERB-NOUN), group the items by color(VERB-NOUN), and average last month's cost(VERB-NOUN).
[0078] L step (the step that contains the action you want to link to) The L-step is a step that defines the action that a verb links, such as relate, link, associate, compose, etc. In this case, the verb is followed by at least two nouns.
[0079] The verb may represent any of the following models:
[0080] Model 1: This step type is assigned the VERB(link)-NOUN-PREP-NOUN morpho-syntactic rule identifier, where the specific verb can be "link" and any synonyms and prepositions, typically "with", but which may vary.
[0081] Some examples of this type of statement are: link the items with the prices(VERB(link)-NOUN-PREP-NOUN), link the equipment with the spare parts(VERB(link)-NOUN-PREP-NOUN), associate the taxes with the shares(VERB(link)-NOUN-PREP-NOUN), compose the product with the inputs(VERB(link)-NOUN-PREP-NOUN).
[0082] Model 2: This step type is assigned the VERB(hold responsible)-NOUN-PREP-NOUN morpho-syntactic rule identifier, which indicates that a particular verb can be "hold responsible" and any synonyms and prepositions, generally "for", although this may vary.
[0083] Some examples of this type of sentence are: hold the client responsible for the payment (VERB(hold responsible)-NOUN-PREP-NOUN), hold the employee responsible for inventory control (VERB(hold responsible)-NOUN-PREP-NOUN).
[0084] Model 3: This step type is assigned the VERB-NOUN-PREP(a)-NOUN morpho-syntactic rule identifier, where the particular preposition can be a, an, or any other preposition.
[0085] Some examples of this type of sentence are measure the item with a unit of measurement (VERB-NOUN-PREP(a)-NOUN) and value the item with a list of prices (VERB-NOUN-PREP(a)-NOUN).
[0086] F-steps (steps that do not correspond to any of the above types) An F step is a step where the verb does not correspond to any of the above types since the verb refers to an action that is specific to a "case".
[0087] The verb may indicate any of the following models:
[0088] Model 1: This step type is assigned the VERB-NOUN morphosyntactic rule identifier and is used for all verbs that are not listed as specific words in either the CC, QS, or FX step types or in models of this same type.
[0089] A transitive verb followed by one or more nouns, for example, Buy an item (VERB-NOUN), Sell fruits (VERB-NOUN), Fix the tools (VERB-NOUN), Solve problems (VERB-NOUN).
[0090] Model 2: This step type is assigned the VERB(is)-NOUN morphosyntactic rule identifier where the specific verb is "to be", which is a very special verb that describes the properties of a noun.
[0091] Some examples of this type of sentence are is fruit (VERB(is)-NOUN), is a company (VERB(is)-NOUN).
[0092] (c) Word logic: determining the word type structure to which the analyzed sentences and questions belong Processor 150 configured as an automatic sentence analyzer 151 (FIG. 4E1) performs the following actions to obtain the relevant functional components from the words of each simple sentence: - for the language of the "case", from the logical structure of languages, words and morpho-syntactic rules 162 in the static database memory 160, the processor 150 obtains verb endings (VE) and a list of special words (SW), among which are a list of grouping words (GRW) and a list of excluded words (EXW). The processor 150 also obtains from the logical structure the morpho-syntactic rules that define the guidelines to be applied. The processor 150 retrieves the "case" simple sentences structured into corresponding questions from the logical structure of simple sentences and questions 171 in the dynamic database memory 170. The processor 150 assigns a sequential number to each sentence in the "case." For each simple sentence in the "CASE" and for each question, the processor 150 takes the words one by one and characterizes them according to word type as follows: If the question is How, processor 150 compares the endings of each word in the question to the verb endings VE to identify a verb. Once a verb is identified, processor 150 compares the remaining words to a list of special words SW to identify prepositions, articles, conjunctions, and adverbs. A word following a verb that is not a SW is a noun. A word following a noun may be a SW that is an element of a list of grouping words GRW, in which case the GRW together with the words immediately preceding and following it constitutes a grouped noun. A remaining word that is not a SW is an adjective. If the question is What, the first word is a verb. Once the verb is identified, processor 150 compares the remaining words to a list of special words to identify prepositions, articles, conjunctions, and adverbs. If the verb is transitive, the word following the verb is not a SW, and the word is a noun acting as a direct object (DO). The word following the noun may be a SW that is an element of a list of grouping words GRW, in which case the GRW together with the words immediately before and after it constitute a grouped noun. The remaining words that are not SWs are adjectives. If the question is Who, processor 150 compares the remaining words to a list of special words to identify prepositions, articles, and conjunctions. The word following the noun may be a SW that is an element of a list of grouping words GRW, in which case the GRW plus the words immediately before and after it constitutes a grouped noun. The remaining words that are not SWs are adjectives.
[0093] The MAS metamodel and morpho-syntactic rule structure are applied in sub-stage E4 to identify functional components useful for creating a functional architecture document, in sub-stage G6 to generate software design components, and in sub-stage H4 to define a graphical notation associated with the software design MAS metamodel. These sub-stages represent a preferred embodiment of the invention in which the transitive verbs of the "case" text as defined in sub-stage A1 are treated.
[0094] Phase B. Input linguistic features and structures In this stage (Figure 4B), the language and its morpho-syntactic features used to describe the "case" in natural language are defined by the following sub-stages:
[0095] Sub-level B1. Defining the order of adjectives Adjective order refers to the placement of adjectives relative to nouns in a language.
[0096] In the input / output device 120 configured as a linguistic user interface 121, the proper order of adjectives for a language is defined from a list of available orders of adjectives, namely: order 1: noun+adjective, order 2: adjective+noun, order 3: modified adjective+modified noun, order 4: adjective+modified noun, order 5: modified adjective+noun. For example, for English, the proper order of adjectives is adjective+noun.
[0097] Sub-stage B2. Uploading special words In the input / output device 120 configured as a language user interface 121, the special words of the language defined in sub-step B1 are uploaded. The special words are used by the processor 150 configured as an automatic sentence analyzer 151 to determine which words should be excluded from the analysis of the sentence. In the context of the present invention, articles (ART), prepositions (PREP), conjunctions (CONJ) and adverbs (ADV) are considered to be special words of the language. In English, "a" and "the" are examples of articles, "for" and "with" are examples of prepositions, "and" and "or" are examples of conjunctions, and "how" and "where" are examples of adverbs.
[0098] Sub-step B3. Upload words to be grouped In the input / output device 120 configured as a linguistic user interface 121, the grouping words of the language defined in sub-stage B1 are uploaded. In the present invention, the grouping words are words from the special words defined in sub-stage B2 that can link two other words to make a compound word. That is the case for "list of prices" which is grouped by the word "of".
[0099] Sub-level B4. Uploading verb endings In an input / output device 120 configured as a linguistic user interface 121, appropriate verb endings of the language from sub-stage B1 are uploaded, which correspond to the last syllable of the fixed verb ending. The verb ending "-ing" is an example for English.
[0100] Step C. Enter a description of the "Case" At this stage (Figure 4C), the case is described in natural language by the following sub-stages:
[0101] Sub-step C1. Choosing a language for case description The language in which the "case" is to be described is selected in the input / output device 120 configured as a case user interface 122. The language is selected from the list of eligible languages uploaded in stage B.
[0102] Sub-step C2. Identifying the components that structure the case context In one embodiment of the present invention, components that structure the context of a "case" are identified.
[0103] This stage deals with a static vision of the world of "cases" and a dynamic vision in time. In the static vision, the conceptual structure of "cases" is observed from a global perspective without considering what happens over time, dividing the concept into its constituent dimensions or main aspects, i.e. layers and resources. In the dynamic vision, the conceptual structure of "cases" is observed in terms of events (temporal activity) that occur over time, in the order in which they occur, i.e. processes, moments and steps.
[0104] To structure the description of a "case" in the proposed embodiment of the invention, layers, resources, processes, sub-processes and moments are identified.
[0105] (a) Identifying the “case” layer A layer is understood as a hierarchy of information that participates in a process and may be treated independently of the others, which may function alone with well-differentiated inputs and outputs. For example, two such layers are identified: a data layer (where the input data of the process are structured and accessed) and a computation layer (where computations are performed using said data).
[0106] (b) Identification of resources used in the Case A resource is a construct that undergoes transformation throughout a process and allows access to other resources, such as the results of the transformation process. For example, an inventory item is a resource that undergoes a sales process.
[0107] (c) Identifying the processes within the “case” A process is an action or group of actions that transforms resources. For example, a process called "marketing inventory items".
[0108] (d) Identifying the sub-processes of each “Case” process A sub-process is a part of a process that allows for analysis of the process by fragments. For example, "providing a quote" and "sale" can be sub-processes contained in a process called "marketing inventory items."
[0109] (e) Identification of the “case” moment In the present invention, a moment is a segment of a sub-process that signals the occurrence of an event related to the sub-process. For example, "When the client is interested" is a moment that occurs within the sub-process "providing a quote."
[0110] Sub-step C3. Identifying the "Case" steps A step is an activity that is performed at any given moment. Example: Activities at the moment "When the person enters the testing office" could be to request the person's identity card, record data from said identity card, perform a family group search for the person, inquire about the person's current job.
[0111] To ensure that the description of the "case" is complete, all of the steps must be included, even steps that are typically omitted because they are deemed obvious.
[0112] Since steps are sentences and their verbs determine the action to be performed, steps can be classified according to the type of action the verb indicates as well as by analysing the noun that follows the verb (excluding the special words defined in sub-stage B2, i.e. articles, conjunctions, adverbs and prepositions).
[0113] The guidelines for classifying sentences by step type are called step type logic as part of the morpho-syntactic rules defined in sub-level A2 and are explained below.
[0114] CC Step: (Step containing a check / verify action) These are steps where verbs like Check, Confirm, Restrict etc. define the checking or confirming action. In this case, the verb is always combined with a statement that expresses the mathematical logic for the system. Some examples of this type of statement are Check that the items have a positive inventory, Confirm that the client has a tax ID number, Restrict the intake of expired merchandise.
[0115] QS Step (Step containing a Query / Search action) These are steps where verbs like Search, Locate, Select, Query, Indicate, Display, Show etc. define a query or retrieval action. In this case, the verb is always followed by a noun or a direct object. Some examples of this type of sentence are Query the items, Show the balances, Display the data, Show the results, Search the items, Locate the spare parts, Select the clients.
[0116] FX Steps (steps that contain explicit calculation actions) These are steps where verbs such as Calculate, Group, Average, Add etc. clearly define the computational action. In this case, the verb is always combined with a statement that expresses the mathematical logic for the system. Some examples of this type of statement are Calculate total sales, Group the items by color, Average last month's cost.
[0117] L step (the step that contains the action you want to link to) These are steps that define the action that a verb such as Relate, Link, Associate, or Compose links. In this case, the verb is followed by at least two nouns. Some examples of this type of sentence are Link the items with the prices, Link the equipment with the spare parts, Associate the taxes with the shares, and Compose the product with the inputs.
[0118] F-steps (steps that do not correspond to any of the above types) These are steps where the verb does not correspond to any of the above types as it refers to an action that is specific to a "case". The verb may represent one of the following models: Model 1: A verb followed by one or more nouns. For example, Buy an item, Sell fruits, Fix the tools, Solve problems. Model 2: A verb not followed by a noun. For example, Enter, Exit.
[0119] The steps are generally described in the following order: 1) F step, 2) CC step, 3) QS step, 4) FX step, 5) L step.
[0120] Stage D. Identifying and memorizing simple sentences and mathematical moments of the "case" At this stage, simple sentences of the "Case" are listed by taking each paragraph of the description of the "Case" and extracting sentences with only one verb, in order to upload them to the case user interface 122 of the input / output device 120. For example, if the description paragraph is "The item is an inventory item. The person measures the item in a unit of measurement and places the Order, for which he is responsible, and links it to an Order Type", the corresponding simple sentences are "The person measures the item in a unit of measurement", "The person places the Order", "The organization holds the person responsible for the Order", "The item is an inventory item", and "The person links the Order to an Order Type".
[0121] In free-form texts, there are sentences with implicit subjects within the same paragraph, typically separated by a conjunction. In such cases, the subject is made explicit to form a complete sentence, with the aim of converting the sentence with the implicit subject into a simple sentence with an explicit subject. For example, the following sentence, separated by the conjunction "and", "The person measures the item in a unit of measurement and places the Order", has an implicit subject and is turned into two simple sentences, "The person measures the item in a unit of measurement" and "The person places the Order".
[0122] Note that in this step, the explanation is a collection of simple sentences that describe the "case": one simple sentence for each step of the process, derived from the answers to the questions Who, What, Where, How, and When.
[0123] For mathematical components, the invention can identify mathematical functions of the input text, and the method identifies sentences for each of the required functional components. That is, each mathematical function is decomposed into several simple sentences. As shown in FIG. 4G2, simple sentences are identified for the mathematical function using five simple question sentences. For example, the mathematical function that allows the calculation of remuneration withholding consists of five simple sentences.
[0124] Once the simple sentences have been identified and completed with an implicit subject, they are uploaded to the case user interface 122 of the input / output device 120 .
[0125] At this stage (Figure 4D), the single sentence “Case” is identified by the following sub-stages:
[0126] Sub-step D1. Answer the questions for each step in the "Case" for steps of types L and F At this stage, each simple sentence in the "Case" is used to answer the questions When, Where, What, How, and When.
[0127] For each simple sentence stored in the simple sentence and question dynamic database memory 171, the processor 150 displays each sentence in the case user interface 122 of the input / output device 120 and asks the questions Who, What, Where, How, and When. For each sentence shown, the user enters answers, ensuring that each answer is a constituent part of the meaning of the sentence. In some cases, it may be impossible to answer one or more of the questions.
[0128] The answers to the above questions clarify any parts of a simple sentence that must be written in the present tense in the preferred embodiment of the present invention.
[0129] The guidelines for classifying sentences according to question type are called the question logic, which is part of the morpho-syntactic rules defined in sub-level A2.
[0130] Sub-step D2. Concatenation of answers from each step of types L and F When answers to questions are uploaded, each answer is concatenated in the following order: When, Who, What, How, Where. In this way, the text of the answer is compiled as one simple sentence and stored in the dynamic database memory 170 in the logical structure of simple sentences and questions 171.
[0131] The answers to the above questions clarify any parts of the simple sentence that must be written in the present tense.
[0132] For example, for the incomplete sentence "Ask for his identification document", when the method described above is applied, the result is the single sentence: When the person enters, the system operator records the number of the identification document.
[0133] Sub-step D3. Identifying the mathematical moments of the case With the aim of structuring the conceptual-mathematical logic of the case description, this stage identifies the mathematical components of the terms used in the case. For example: Moment: calculate the tax withholding. Step 1: Check payments (Type QA) Step 2: Add the paid amounts (type FX) Step 3: Consult aliquot (Type QS) Step 4: Calculate tax (FX type) Step 5: Validate results (Type CC)
[0134] 4G2 and 4G3 show the structure of each step and how the case user interface 122 is presented for each type of step.
[0135] Sub-step D4. Answer questions for each step of the "CASE" for steps of types QS, FX, and CC At this stage, the method of the present invention takes each simple sentence that corresponds to a mathematical moment of a "case" and the questions When, Who, What, How, and Where must be answered for cases that refer to these types of steps.
[0136] For each simple sentence stored in the simple sentence and question dynamic database memory 171, the processor 150 displays each sentence in the case user interface 122 of the input / output device 120 and asks the questions Who, What, Where, How, and When. For each sentence shown, the user enters an answer, ensuring that each answer is a constituent part of the meaning of the sentence according to the mathematical content of the step. In some cases, one or more of the questions may not be answerable.
[0137] When the above questions are answered, all parts of the simple sentences, which in the preferred embodiment of the invention must be written in the present tense, are clarified. In addition to the answers to each question, as for the mathematical case, the required specification of each question must be completed for each type of step. This specification links the meaning of each answer to each question to the functional components generated from the previous step, so that when the sub-steps G2 and G3 are executed, the functional model associated with the mathematical step has all the necessary elements for the automatic generation of the classes formulafx and dominiodx.
[0138] In the case user interface 122-1, a simple statement is entered for an FX step type.
[0139] In the case user interface 122-2, a simple sentence is entered for a CC step type.
[0140] In the case user interface 122-3, a simple statement is entered for a QS step type.
[0141] As examples for each type of step QS, FX, and CC, the following cases are described below.
[0142] QS Step Type Examples In this example, each statement in the case user interface 122 is explained in terms of step type QS by the representation in FIG. 4G3 and the details in FIG. 4G3a.
[0143] [Table 3A]
[0144] [Table 3B]
[0145] [Table 3C]
[0146] FX Step Example In this example, each statement in the case user interface 122 is explained in terms of step type FX by the representation of FIG. 4G2.
[0147] [Table 4A]
[0148] [Table 4B]
[0149] CC Step Example In this example, each statement in the case user interface 122 is explained in terms of step type CC by the representation in FIG. 4G2.
[0150] [Table 5A]
[0151] [Table 5B]
[0152] [Table 5C]
[0153] The guidelines for classifying sentences by question are called the "question logic" as part of the morpho-syntactic rules defined in sub-step A2.
[0154] Sub-step D5. Concatenation of responses for steps of type QS, FX, and CC When answers are loaded for a question, each answer is concatenated in the following order: When, Who, What, How, Where. In this way, the answer texts are concatenated into one simple sentence and stored in the Simple Sentences and Questions 171 logical structure in the Dynamic Database Memory 170.
[0155] The answers to the above questions will explicitly identify all parts of the simple sentence that must be written in the present tense.
[0156] For steps of type QS, FX, and CC, each simple sentence adds a series of additional words to the link to give each sentence meaning. Examples of such competitions are shown in bold below:
[0157] In the case of Step QS type, the construction of a single sentence is as follows: The system checks payments(date, concept, amount), with the condition in force and non-exempt and stores them in payments that apply(date, concept, amount).
[0158] In the case of Step FX type, the construction of a single sentence is as follows: The system calculates the tax, adding the amounts that apply and stores the result in invoice (tax amount).
[0159] In the case of Step CC type, the construction of a simple sentence is as follows: The system validates the result, comparing invoice with total payments and stores the result in attribute RdoValido(checkvalid).
[0160] Phase E. Identifying and remembering functions and mathematical components It will be appreciated that in the context of the present invention, the functional components correspond to each of the words of a sentence that are automatically extracted and classified by the processor 150 according to the grammatical and syntactic structure of the language in which it is expressed.
[0161] In this stage (Figure 4E), the sub-stages for identifying the functional components of a sentence are described.
[0162] Sub-level E1. Breaking down a sentence into words and identifying those words The functional components generated by the processor 150 are divided into the following types: Noun-function constituents 〇What is specified in -> Noun - Direct Object (DO) 〇Specified in Who -> Noun - Person (PER) 〇Specified in When -> Noun (NOUN) 〇Identified in How -> Noun (NOUN) ·Adjective functional components 〇Specified in any of the questions -> adjective (ADJ) Verb-function constituents 〇Specified in What -> Verb (VERB) 〇Specified in How -> Verb (VERB) Adverbial function component 〇Specified in How -> Adverb (ADV)
[0163] The guidelines for structuring words are called word logic as part of the morpho-syntactic rules defined in sub-level A2 and are explained below.
[0164] In this sub-stage, a processor 150 configured as an automatic sentence analyzer 151 performs the following actions for each simple sentence in the "case":
[0165] (a) Make a list of words For every sentence, list each of the words in the sentence.
[0166] (b) Identifying words to be excluded Those words which are excluded as defined in sub-step B2 are excluded from the selection of functional components, unless such words are part of a grouped noun such as list of prices, box of cookies etc.
[0167] (c) Identify the verb Identify the verb by comparing the ending of each word with the list of verb endings defined in sub-step B4, or as the first word in the answer to the question What in a simple sentence.
[0168] (d) Identify the noun Identify non-excluded words as nouns, not verbs
[0169] (e) Tag the noun as &attribute Some nouns behave like & attributes. The & attribute is understood to be the name of a feature of another noun that is not an adjective. In one embodiment of the invention, the & attribute is selected manually for a list of identified nouns. In another embodiment, the processor automatically recognizes the & attribute when nouns are listed in parentheses in the text. Example: In the sentence "upload the document number of the client", "document number" is an & attribute of "client".
[0170] (f) Identify grouped nouns Identifies grouped nouns as nouns when there are two consecutive nouns with a special word between them that acts as a link.
[0171] (g) Identifying functional components based on words From the list of classified words, nouns and verbs are identified as functional constituents and classified accordingly as VERB, DO, NOUN, PERSON.
[0172] (h) Check the prior existence of each functional component, one by one When a new functional component of any type is specified, a check is made to see if it already exists. If it does not exist, the functional component is created. If it does exist, the functional component persists.
[0173] (i) Linking functional components to the questions they answer Classify functional components by the type based on the question to which the word belongs i. If the word belongs to When, the word grouped with the verb is an adverbial component (ADV). ii. If the word belongs to What, the noun following the verb is a functional constituent of the direct object (DO) type. iii. If the word belongs to Who, the first noun is the person (PERS) functional component.
[0174] Processor 150 configured as an automatic sentence analyzer 151 performs the following actions as shown in FIG. 4E1 to obtain the relevant functional components from the words of each simple sentence. For the language of the "case", the processor 150 obtains from the logical structure of the language, words and morpho-syntactic rules 162 in the static database memory 160 the verb endings (VE), the list of special words (SW), among which there is a list of grouping words (GRW) and a list of excluded words (EXW). The processor 150 retrieves the "case" simple sentences structured into corresponding questions from the logical structure of simple sentences and questions 171 in the dynamic database memory 170. The processor 150 assigns a sequential number to each sentence in the "case." For each simple sentence in the "Case", for each question, the processor 150 takes the words one by one and characterizes them according to word type as follows: If the question is How, processor 150 compares the endings of each word in the question to the verb endings VE to identify a verb. Once a verb is identified, processor 150 compares the remaining words to a list of special words SW to identify prepositions, articles, conjunctions, and adverbs. A word following a verb that is not a SW is a noun. A word following a noun may be a SW that is an element of a list of grouping words GRW, in which case the GRW together with the words immediately preceding and following it constitutes a grouped noun. A remaining word that is not a SW is an adjective. If the question is What, the first word is a verb. Once the verb is identified, processor 150 compares the remaining words to a list of special words to identify prepositions, articles, conjunctions, and adverbs. If the verb is transitive, the word following the verb is not a SW, and the word is a noun acting as a direct object (DO). The word following the noun may be a SW that is an element of a list of grouping words GRW, in which case the GRW together with the words immediately before and after it constitute a grouped noun. The remaining words that are not SWs are adjectives. If the question is Who, processor 150 compares the remaining words to a list of special words to identify prepositions, articles, and conjunctions. The word following the noun may be a SW that is an element of a list of grouping words GRW, in which case the GRW plus the words immediately before and after it constitutes a grouped noun. The remaining words that are not SWs are adjectives.
[0175] Sub-step E2. Adding functional components not included in the description In one embodiment of the present invention, the user adds functional components that are not present in the list of automatically identified functional components. Continuing with the same example: · ID number is an attribute & is automatically detected from the sentence. · Age of a person is an attribute that is added by the user.
[0176] In one embodiment of the present invention, corresponding steps and statements are automatically generated for each functional component that is added.
[0177] Sub-step E3. Identification of functional components associated with step types FX, CC, and QS From the mathematical moments and steps shown in sub-stages D3, D4, and D5, a processor 150 configured as an automatic sentence analyzer 151 identifies complementary functional components corresponding to step types FX, CC, and QS as follows:
[0178] Sublevel E3.a - Mathematical components of sentences corresponding to FX step types Apply word logic to the text entered in interface component 122-12 to identify the NOUN (Invoice) and the attributes in parentheses (taxedamount). These attributes constitute {enumeration of attributes &}. b. Define the content of 122-13 to be a functional component {fx expression} linked to the NOUN (Invoice) and attribute (taxedamount) specified in item a of sublevel E3.a.
[0179] Sublevel E3.b - Mathematical components of sentences corresponding to CC step types Apply word logic to the text entered in the interface component 122-22 to identify the NOUN (Result) and the attributes in parentheses (validcheck). These attributes make up the {enumeration of attributes &}. b. Define the content of 122-23 to be the functional component {fx formula} linked to the NOUN (Result) and attribute (validcheck) specified in item a of sub-step E3.b.
[0180] Sublevel E3.c - Mathematical components of sentences corresponding to QS step types Apply word logic to the text entered in interface component 122-31 to identify the NOUN (payments) and the attributes in parentheses (date, concept, amount). These attributes constitute {enumeration of attributes &}. b. Define the content of 122-32 to be a functional entity {fx formula} linked to the NOUN (Payments that Apply), attributes (date, concept, amount) identified in item c of sublevel E3.b. c. Apply word logic to the text entered in interface component 122-33 to identify the NOUN (Payments that Apply) and the attributes in parentheses (date, concept, amount). These attributes constitute {enumeration of attributes &}.
[0181] Sublevel E4. Application of morphological and syntactic rules to functional components In one embodiment of the present invention, the user may enable the use of morphological and syntactic rules so that processor 150 follows the logic defined in sub-stage A2.
[0182] In this embodiment, each word of the simple sentence is classified as Word 161-1 by the MAS metamodel from FIG. 4A1 and assigned one of the following word types: VERB, NOUN, ART, CONJ, ADJ. Performer 161-2 Word and Performable 161-3 Word are also generated, assigning Performance 161-4 to transitive verbs. All of the Words 161-1 classified by type are functional components. As shown in FIG. 4D, once each functional component is generated, it is linked to the sentence it comes from, the question it belongs to, the corresponding word type, and the morpho-syntactic rules that represent the sequence of word types that make up the question as shown in sub-stage A2.
[0183] A special word as defined in sub-stage B2, unless during the selection of a functional constituent the corresponding morpho-syntactic rule marks it as a special word.
[0184] In this embodiment, processor 150 generates two new functional components for each transitive verb: a functional component (Performer 161-2) designated as the verb plus the suffix "ER" and a functional component (Performable 161-3) designated as the verb plus the suffix "BLE". The transitive verb is a Performance 161-4 Word. For nouns that cause transitive verbs to be performed, processor 150 generates the verb "is" associated with the ER of the verb. For target nouns (direct objects of sentences), processor generates the verb "is" associated with the BLE of the verb.
[0185] Phase F. Generate functional architecture documentation At this stage (FIG. 4F), processor 150 configured as document generator 153 generates functional architecture documents using the formats, graphical notations in static database memory 160, and the formats and notations stored in the logical structures of STD statements 163, and displays those functional architecture documents in document display user interface 124 of input / output device 120.
[0186] At this stage (Figure 4F), a functional architecture document is generated by the following sub-stages:
[0187] Sub-stage F1. Establishment of morphological and syntactic rules for functional architecture For each transitive verb followed by the preposition "to" or "to the" as defined in step A, the processor generates the following for the noun that performs the verb: a syntactic component whose name is the verb plus the suffix "er" (hereafter referred to as the ER of the verb), and for the noun that receives the action of the verb: a syntactic component whose name is the verb plus the suffix "ble" (hereafter referred to as the BLE of the verb). The processor generates a new noun called "Performance of the verb" between the original noun and the ER of the verb. For the original noun, the processor generates the verb "is" associated with the BLE of the verb. For the target noun, the processor generates the verb "is" associated with the ER of the verb.
[0188] Sub-step F2. Define the graphical notations used within the functional architecture document In this stage, the graphical notations to be used in the functional architecture document are defined using the format, graphical notations, and STD sentence user interface 123 of the input / output device 120 to indicate the graphical components used in the diagram for each functional and mathematical component according to the corresponding word type. The defined graphical notations are stored in the database memory 130. In this way, the user inputs the graphical notations into the visual grid displayed by the format, graphical notations, and STD sentence user interface 123 as shown in FIG. 6.
[0189] Sub-step F3. Generate Functional Architecture Document Processor 150 configured as document generator 153 retrieves the functional and mathematical components stored in functional components logical structure 172 of dynamic database memory 170 and applies the MAS metamodel in MAS metamodel 161 logical structure of static database memory 160 to construct a functional architecture document using the notation defined in sub-stage F2. To generate a functional architecture diagram, the processor scans the list of functional components and applies the following rules until the processor generates a diagram such as the diagram shown in Fig. 4F1. Rule 1: For each NOUN type functional component, draw an FNOUN graphical element with an FC label in it. Rule 2: For each functional component of VERB type, a line is drawn between the NOUN preceding the VERB and the NOUN following the VERB taking into consideration: i) if the VERB is "be or its conjugations", a FTOBE graphical element is drawn from the NOUN preceding the VERB to the NOUN immediately following the VERB; ii) if the VERB is any other transitive verb, a FERBLE graphical element is drawn from the NOUN preceding the VERB to the NOUN immediately following the VERB; iii) if the VERB is not transitive, a FVERB graphical element is drawn from the NOUN preceding the VERB to that same NOUN. Rule 3: For each PREP type functional component, but only for the prepositions "of" and "of the", draw an FPREP graphical element between the NOUN preceding the preposition and the NOUN following the preposition. Rule 4: For each transitive verb, draw a graphical component corresponding to the word generated based on the MAS metamodel defined in sub-step A1, i.e. FERBLE graphical element for Performer word, FERBLE for Performable word and FPERF for Performance word.
[0190] The processor 150 displays the functional architecture document on the input / output device 120 .
[0191] Phase G. Identifying and remembering design components In the present invention, the design document of a "case" is composed of the following diagrams: a conceptual design diagram, a use case diagram, a class diagram, an entity relationship diagram, a screen design diagram, and a report design diagram.
[0192] Each design document of a "case" represents a graphic. In particular, class diagrams are used in the present invention. Each graphical element that is part of a class diagram according to the Object Oriented (OO) paradigm is called a Design Component (DC). Examples: relationships, attributes, methods of a class.
[0193] For purposes of the present invention, classes, attributes, relationships, and methods shall be understood to be design constructs defined in the Object Oriented (OO) paradigm.
[0194] In this stage (FIG. 4G), a processor 150 configured as an automated software designer 152 automatically designs the software according to the following sub-stages:
[0195] Sub-stage G1. Grouping of functions and mathematical constructs, generating classes and inheritance relationships of those constructs In this sub-stage, a processor 150 configured as an automated software designer 152 performs the following actions to generate classes and inheritance relationships based on the similarities of their attributes:
[0196] (a) Selecting functional components The processor 150 obtains the list of functional and mathematical components generated in stage E, which are stored in the logical structure of functional components 172 in the dynamic database memory 170, except for functional components tagged as "is an attribute" and functional components of VERB word type.
[0197] The processor 150 removes functional and mathematical components that have very similar names (e.g., 90% similarity using the Levenshtein distance algorithm), as in the case of the words "person" and "persons" where "Person" is considered as a single functional component.
[0198] (b) Group similar functional components Processor 150 groups functional components included in the previous step using {&list of attributes} by putting functional components with the same {&list of attributes} into the same group. Processor 150 takes groups with two or more functional components and assigns word names to those groups, e.g., Word01, Word02.
[0199] (c) Generate a class for each group Processor 150 creates a class for each group having two or more functional components, denoting each element of {&list of attributes} as an attribute and assigning the class a word name corresponding to the group.
[0200] (d) Generate inheritance relationships for groups For functional components that belong to a group having two or more elements, processor 150 generates an inheritance relationship between each class to which the functional component belongs and the classes of its respective group according to the group of {& list of attributes} to which the functional component belongs, i.e., an inheritance relationship exists between classes with the same {& list of attributes} generated within the same group of classes from the previous step.
[0201] Sub-stage G2. Generation of expression classes based on FX and CC type steps In this sub-stage, a processor 150 configured as an automated software designer 152 performs the following actions on the single sentences of the "case" separated by question type:
[0202] (a) List the VERB and DO functional components that belong to the FX and CC steps. Processor 150 lists all VERB and DO type functional components and identifies their corresponding step types as defined in sub-stage C3.
[0203] (b) Generating classes for FX and CC type steps Based on the functional and mathematical components belonging to steps of type FX and CC, processor 150 generates classes whose behavior is defined by VERBs. For each VERB, processor 150 generates a class and adds a method called formula that is responsible for computing the formula indicated by {fx formula} specified in sub-stages E3.a and E3.b.
[0204] For each class generated in the previous step, the processor 150 performs the following actions: If DO "Is Attribute", then the processor 150 creates an attribute called DO in the class. b. If DO "Is Attribute", then processor 150 creates a relationship between the class from the previous step and the class that contains DO as an attribute of the class (called TargetClass). Processor 150 names this relationship TargetClass_Movement.
[0205] Sub-stage G3. Generation of domain classes based on QS type steps. In this sub-stage, a processor 150 configured as an automated software designer 152 performs the following actions:
[0206] (a) List the VERB and DO functional components that belong to the QS step. Processor 150 lists all VERB and DO type functional components and identifies their corresponding step types as defined in sub-stage C3.
[0207] (b) Generate classes for QS type steps Based on the functional components belonging to the QS type steps, the processor 150 generates classes with the behavior defined by the VERB. For each VERB, the processor 150 generates a class called VERB+DO and adds a method called fxdomain that is responsible for retrieving data as defined by the {fx formula} specified in sub-step E3.c. The processor 150 generates a class called "domain"+VERB+DO with the & attributes indicated in {list of & attributes}. If the list of & attributes matches the & attributes of one of the previously generated classes, the processor 150 generates an inheritance relationship between those classes in the corresponding direction.
[0208] The fxdomain method calls "domain" + VERB + DO.
[0209] Sub-stage G4. Generation of domain classes based on L-type steps. In this sub-stage, a processor 150 configured as an automated software designer 152 performs the following actions:
[0210] (a) Listing of VERB and DO functional components belonging to the L step Processor 150 lists all VERB and DO type functional components and identifies their corresponding step types as defined in sub-stage C3.
[0211] (b) Creating classes for L-step types Based on the L-type functional components, the processor 150 generates a relationship between a DO and a NOUN called DO+"for"+NOUN.
[0212] Sub-stage G5. Generation of behavior classes based on F-type steps In this sub-stage, a processor 150 configured as an automated software designer 152 performs the following actions:
[0213] (a) Listing of VERB and DO functional components belonging to the F step Processor 150 lists all VERB and DO type functional components and identifies their corresponding step types as defined in sub-stage C3.
[0214] (b) Generation of classes for F-type steps Based on the F type functional components, the processor 150 generates the following classes depending on whether the DO "Is Attribute" or not: If the DO is "Is Attribute", the processor 150 does not create a class. b. For DO "Is Attribute", i. Processor 150 creates a class called Class_Cab called VERB+DO. ii. The DO class from an F-type step is called Class_Rec. The processor 150 creates a 1-to-n relationship between Class_cab and Class_rec. The processor 150 names the relationship "movement"+DO.
[0215] Sub-step G6. Applying morphological and syntactic rules to design components In one embodiment of the present invention, the user may enable the use of morphological and syntactic rules so that processor 150 follows the logic defined in sub-stage A2.
[0216] Based on the morphological and syntactic rules defined in sub-stage A2 and stored in the language, word, and morphological and syntactic rules 162 logical structure in the static database memory 160, the processor 150 determines which software design components (DC) are derived from each functional component (FC) stored in the functional component logical structure 172 in the dynamic database memory 170.
[0217] The processor 150 lists the questions and generates a rule identifier for each question based on the type of words that make up the answer. The processor 150 then searches for the rule identifier in the logical structure of language, words, and morpho-syntactic rules 162 in the static database memory 160 and finds a base rule by matching the identifier. There may be two or more morpho-syntactic rules with the same base rule identifier, in which case the rule that matches the question, F-step type, and specific words found in the text and indicated in the morpho-syntactic rule is selected. If the identifier does not match any base rule, the processor 150 ignores the question.
[0218] In this embodiment, for each transitive VERB identified in the previous sub-step and defined in sub-step A1, processor 150 generates a Word 161-4 associated with the verb, as well as the words Performer 161-2 and Performable 161-3.
[0219] For the case of an L type step, the user can generate morpho-syntactic rules according to the basic rule VERB-NOUN-PREP-NOUN, e.g., the verb "to link" is treated as a specific word. In this case, the step type is L, and the processor 150 generates a relationship between DO and NOUN called DO+"for"+NOUN.
[0220] For the case of a step of type FX, the processor 150 generates, for each mathematical component identified in sub-step E3.a, a word of type formulafx where {fx formula} is entered into interface 122-13, linked to the attribute (taxed amount) identified in item a of sub-step E3.a.
[0221] For the case of step type CC, processor 150 generates, for each mathematical component identified in sub-step E3.b, a word of type formulafx where {fx formula} is entered into interface 122-23, linked to the attribute (validcheck) specified in subparagraph a of sub-step E3.b.
[0222] For the case of step type QS, processor 150 generates, for each mathematical component identified in sub-step E3.c, a word of type fxdomain where {fx formula} is entered into interface 122-32 and a word of type fxformula linked to the previous fxdomain. This formula fx is linked to the {enumeration of attributes &} (date, concept, amount) identified in sub-paragraph c of sub-step E3.b.
[0223] FIG. 4A3 shows the software design class model with an application example illustrating morphological and syntactic rules for software design based on the MAS metamodel 161. These morphological and syntactic rules generate the modeling of the "case" sentence. To design software from natural language, morphological and syntactic rules for software design are defined for each of the questions (When, Who, What, How, Where) that describe the simple sentence. These rules stored in the word, rule, and morphological and syntactic rules static database memory 162 are compared with the rule identifiers calculated for each simple sentence as shown in sub-stage 2A, and based on the matching, the logic used by the processor 150 configured as an automatic software designer 152 to generate software design components is defined.
[0224] Phase H. Definition of formats, graphical notations, and STD statements In this stage (FIG. 4H), the formats for business, analysis and design documents, as well as the parameters required to generate them, are defined by the following steps.
[0225] Sub-step H1. Define the output format for the document At this sub-level, display or print formats for business, analysis and design documents are defined using formats for input / output devices 120, graphical notations and STD text user interfaces 123.
[0226] These definitions include defining the margins, fonts, and sort order of the order in which each document's content is displayed.
[0227] For business documents, the presentation order and sequence of layers, resources, processes, sub-processes, moments, and steps are defined.
[0228] For the analysis document, the presentation order and sequence of global and detailed requirements is defined.
[0229] In one embodiment of the present invention, a user can use the format, graphical representation and STD sentence user interface 123 of the input / output device 120 to modify the formats, graphical representation and standard sentences uploaded in sub-stages F1, F2, F3 and F4.
[0230] Sub-stage H2. Define requirements boilerplate In this sub-stage, using the formats, graphical notations, and STD sentence user interface 123 of the input / output device 120, boilerplate text describing the requirements is entered and written in the language or languages used to generate the requirements, and the boilerplate text is stored in a logical structure of languages, words, and morpho-syntactic rules 162 of the input / output device 160. The boilerplate texts necessary to generate requirements are described below. These sentences must be translated and stored in each of the languages in which it is desired to generate the document requirements.
[0231] (a) Boilerplate for global requirements To generate global requirements, the following boilerplate language is defined, which applies to English: OracionSTD_abm_Sust: "Create, Read, Update and Delete" OracionSTD_abm_Pers: "Create, Read, Update and Delete Entities with role" OracionSTD_verbo_F: "Create transaction record" OracionSTD_verbo_R: "Create rule that" OracionSTD_verbo_conector_R: "with" OracionSTD_verbo: "Create rule that"
[0232] (b) Boilerplate for detailed requirements on NOUN and DO components To generate detailed requirements for the NOUN and DO functional components, the following boilerplate language applicable to English is defined: OracionSTD_Crear: "Create a new element" OracionSTD_Agregar_Atributos: OracionSTD_Agregar_Atributos OracionSTD_Agregar_Controles: "Perform the following controls when an element is created" OracionSTD_Baja: "Exclude a" OracionSTD_Edicion: "Update a" OracionSTD_Consulta: "Search the transaction records of" OracionSTD_complemento_control: "performing the following controls" OracionSTD_complemento_busqueda: "performing the following searches" OracionSTD_crear_atributo: "Create the attribute" OracionSTD_validacion_atributo: "Perform the following controls when the datum is completed"
[0233] (c) Boilerplate for detailed requirements regarding PERSON components To generate detailed requirements for the PERSON functional component, the following boilerplate language is defined, applicable to English: OracionSTD_permitirque: "Allow" OracionSTD_acciones_Persona: "to perform the following actions" OracionSTD_afectacion_Persona: "to be subject to the following actions" OracionSTD_responsabilidad_Persona: "to be performed under the responsibility of"
[0234] (d) Boilerplate for detailed requirements on VERB components In order to generate detailed requirements for VERB functional components associated with a CC-type step or an FX-type step, the following boilerplate text is defined, applicable to the English language: OracionSTD_crear_Fx: "Create a formula for" OracionSTD_argumentos: "using the following data as arguments" OracionSTD_expression: "in the following expression" OracionSTD_msj_error_Fx: "If the formula returns an error, display the following message" OracionSTD_msj_ok_Fx: "If the formula returns a valid result, display the following message" OracionSTD_msj_advertencia_Fx: "If the formula returns a warning, display the following message"
[0235] In order to generate detailed requirements for VERB functional components associated with QS-type steps, the following boilerplate text applicable to English is defined: OracionSTD_crear_busqueda: "Create a rule for" OracionSTD_exponer_atributos: "displaying the following data" OracionSTD_definir_busqueda: "Allow searching for the data of" OracionSTD_conector_orden: "by" OracionSTD_definir_filtro: "Allow filtering the data of" OracionSTD_definir_orden: "Allow sorting the data of" OracionSTD_definir_agrupamiento: "Allow grouping for the data of" OracionSTD_definir_total: "Display the following summarized data"
[0236] In order to generate detailed requirements for VERB functional components related to L-type steps, the following boilerplate text applicable to English is defined: OracionSTD_crear_regla: "Create a rule that" OracionSTD_condicion: "as long as the following condition is met" OracionSTD_vincular: "Link" OracionSTD_conector_vincular: "with" OracionSTD_complemento_control: "performing the following controls" OracionSTD_des vincular: "Unlink" OracionSTD_ consultar: "Search" OracionSTD_ complemento_relacionar: "in a relationship with" OracionSTD_complemento_criteriobusqueda:"using the following search criteria"
[0237] To generate detailed requirements for VERB functional components related to F-type steps, the following boilerplate text applicable to English is defined: OracionSTD_permitir: "Allow" OracionSTD_habilitar_persona: "Enable" OracionSTD_complemento_accionpersona: "to decide on the action" OracionSTD_movimientos: "Allow the movements of" OracionSTD_complemento_acargode: "to affect" OracionSTD_control_nuevo: "Perform the following controls when creating a new transaction record of" OracionSTD_control_eliminar: 「Perform the following controls when deleting the transaction record of」 OracionSTD_control_modificar: 「Perform the following controls when updating the transaction record of」 OracionSTD_precedencia: 「based on the following existing records:」 OracionSTD_nuevo_movimiento: 「Record n movements of」 OracionSTD_control_nuevo_movimiento: 「Perform the following controls when creating a new movement of」 OracionSTD_control_eliminar_movimiento: 「Perform the following controls when deleting the movement of」 OracionSTD_control_modificar_movimiento: 「Perform the following controls when updating the movement of」 OracionSTD_buscar_elemento: 「Search for the elements of」 OracionSTD_complemento_buscarelemento: 「to create a movement, performing the following searches」
[0238] Lower stage H3. Definition of graphical notations used in software design At this stage, the graphical notation used in the software design is defined using the format of the input / output devices 120, the graphical notation, and the STD sentence user interface 123.
[0239] Design diagrams can be displayed in a variety of graphical notations, one of which is the UML notation, that allow for the definition of graphical elements for representing design documents.
[0240] Sub-step H4. Definition of graphical notations related to the MAS metamodel Illustrate the graphical components to be used in the software design diagram for each element of the MAS metamodel defined in sub-phase A1. In this manner, the user inputs the graphical notation into the visual grid displayed by the Format, Graphical Notation, and STD Statement User Interface 123.
[0241] Design diagrams can be displayed in a variety of graphical notations, one of which is the UML notation, and it is possible to define graphical elements to represent the design document as shown in Figure 7.
[0242] Phase I. Automated generation of business, analysis, and design documentation At this stage (FIG. 4I), the processor 150 configured as a document generator 153 generates business, analysis, and design documents using the formats, graphical notations in the static database memory 160, and the formats and notations stored in the STD statements 163 by the following sub-stages, and displays those documents in the document display user interface 124 of the input / output device 120.
[0243] Sub-stage I1. Business document generation At this stage, the processor 150 configured as a document generator 153 composes the text of the business document. In the present invention, the business document is an analyzed document that represents the simple sentences stored in the dynamic database memory 170 and the logical structure of questions 171 by performing the following actions:
[0244] a) Ordering dimensions, time activities, and simple sentences Processor 150 orders the text hierarchically, with layers at the top of the hierarchy and steps at the bottom of the hierarchy, as shown in FIG. 4I2, thus: Layer 310 includes resources 320 The resource 320 includes a process 330. - Process 330 includes a sub-process 340 - Sub-process 340 includes moment 350 - It includes a step 360 in which the moment 350 can be of up to five types as described above. - Step 360 includes the simple sentences 370 with their corresponding completed questions.
[0245] b) Sequentially grouping already ordered components together In the preferred embodiment (FIG. 5), a simple sentence is obtained by putting together the answers to each of the questions in a preferred order, namely, When, then Who, then What, then How, and finally Where; this does not mean that the order cannot be changed.
[0246] When all of the processes are described using this method, a complete and detailed construction of the "case" expressed in natural language is achieved.
[0247] Sub-step I2. Generate analysis documentation At this stage, the processor 150 configured as a document generator 153 structures the functional requirements and automatically generates an analysis document. In the present invention, the analysis document represents the requirements obtained from the functional components stored in the dynamic database memory 170 in a logical structure of simple sentences and questions 171 by performing the following actions:
[0248] a) Composition of global functional requirements The global functional requirements of a "case" are actions that describe the process in the order in which they must be performed so that they can be interpreted in terms of the functional requirements needed to build a software application and the actions to be taken can be determined.
[0249] The processor 150 retrieves the functional components stored in the functional component logic structure 172 of the dynamic database memory 170 and selects only the following: NOUN, PERSON, DO, and VERB. For each of the above functional components, the processor 150 generates global requirements that are part of the scope of the "CASE", defines global requirements for the NOUN components (NOUN, DO, PER), and defines global requirements for the VERB components.
[0250] Global requirements for NOUN components Global requirements are constructed by generating, for each noun-function constituent (NOUN, PERSON, and DO), unless it is an attribute, a tagged and numbered sentence such as the one shown in Table 1, using the formulas defined in sub-step F2.
[0251] [Table 6]
[0252] Global requirements for VERB constructs Global requirements are formulated for each VERB functional component by generating tagged and sequentially numbered statements.
[0253] In this case, a sentence is generated for each step type based on the VERB, using DO and NOUN combined with the VERB in the What question to construct the sentence, as shown in Table 2.
[0254] [Table 7]
[0255] A single global requirement is described by a single functional component from the different steps. In this case, the global requirement is described only once to avoid repetition and is linked to the corresponding steps as many times as necessary.
[0256] b) Developing detailed functional requirements At this stage, the detailed requirements of the "case" are explained in terms of each global requirement: explicit detailed requirements, which are requirements that are clearly stated in the sentence, and implicit detailed requirements, which are requirements that are known to be necessary but are not explicitly explained.
[0257] In the context of the present invention, the sentences shown in quotation marks are preferred sentences obtained from the logical structure of language, words and morpho-syntactic rules 162 in the static database memory 160. However, these sentences may be replaced by sentences having an equivalent meaning and which are suitable for the language selected for the case in the embodiment presented in sub-step F2.
[0258] For each type of functional component, based on its global requirement definition, detailed requirements of the "case" are defined using the formulas defined in sub-step F2.
[0259] For a deeper understanding of the present invention, it should be noted that to generate detailed requirements, the words are replaced according to the following criteria: - NOUN refers to a functional component of this type defined in sub-level D2. - PERSON refers to a functional component of this type defined in sub-level D2. - DO refers to a functional component of this type defined in sub-step D2. - VERB refers to this type of functional component defined in sub-level D2. - {List of &attributes}: A list of &attributes describing NOUNs consisting of NOUNs marked as &attributes in sub-step D2 plus NOUNs added in sub-step D3. - {*List of attributes}: Part of the list of attributes defined in sub-step D2 that is used to search, filter, sort, group or add the results of a search or query. - {List of DO&attributes}: A set of &attributes from the list of &attributes defined in sub-step D2, consisting of elements that are associated to the DO component by the detailed requirements generated in sub-step G3. - {List of NOUN & attributes}: A set of & attributes from the list of & attributes defined in sub-step D2, consisting of elements that are related to NOUN components by the detailed requirements generated in sub-step G3. - {List of PERSON & attributes}: A set of & attributes from the list of & attributes defined in sub-step D2, consisting of elements that are related to the PERSON component by the detailed requirements generated in sub-step G3. - {List of global requirements of type CC}: a set of global requirements consisting of global requirements defined on the basis of NOUN or DO constructs belonging to the steps of type CC identified in sub-step E2. This list contains 0 to n global requirements. If the list contains 0 global requirements, no detailed requirements referring to global requirements of type CC are generated. - {List of global requirements of QS type}: a list of global requirements generated based on the steps of the QS type identified in sub-step E3. This list contains 0 to n global requirements. If the list contains 0 global requirements, no detailed requirements referring to the global requirements of QS type are generated. - {List of F-type global requirements}: a list of global requirements generated based on the F-type steps identified in sub-step E5. This list contains 0 to n global requirements. If the list contains 0 global requirements, no detailed requirements referring to the F-type global requirements are generated. - {fx formula}: A formula that takes the listed data as arguments and relates to a formula specified in sub-step D3 for part of a step of type FX, CC, or QS. - {Error message}: text of the message to be shown in the system if there is an error in executing the formula defined in sub-step D3 for any step of type QS. - {ok message}: text of the message to be shown in the system if the result of the check or validation defined in sub-step D3 for any step of type QS is correct. - {Warning message}: Text of the message to be shown in the system if the result of the check or validation defined in sub-step D3 for any step of type QS is incorrect.
[0260] Define detailed requirements for NOUN components Based on the NOUN type functional components stored in the logical structure of functional components 172 in dynamic database memory 170 and their respective global requirements, the following detailed requirements are generated:
[0261] [Table 8]
[0262] Define detailed requirements for the PERSON construct Based on the functional components of type PERSON stored in the logical structure of functional components 172 in dynamic database memory 170 and their respective global requirements, the following detailed requirements are generated:
[0263] [Table 9]
[0264] Define detailed requirements for VERB components Based on the VERB type functional components stored in the logical structure of functional components 172 in dynamic database memory 170 and their respective global requirements, the following detailed requirements are generated:
[0265] [Table 10A]
[0266] [Table 10B]
[0267] [Table 10C]
[0268] Define detailed requirements for DO components Based on the DO type functional components stored in the logical structure of functional components 172 in dynamic database memory 170 and their respective global requirements, the following detailed requirements are generated:
[0269] [Table 11]
[0270] Sub-stage I3. Generate software design documentation As per the graphical representation defined in sub-step F4, the processor 150 configured as a document generator 153 generates an XML file in which the name of each design component and the code of its corresponding graphical representation are stored between tags.
[0271] For embodiments of the present invention where the UML graphical notation is chosen, the xmi standard is used to generate XML representing the class diagrams.
[0272] Processor 150 configured as a document generator 153 retrieves the data stored in the database memory corresponding to the design and exports the content in a specific XML format according to the definition of the graphical notation selected in sub-step F4 to generate a design document.
[0273] An example of one application of the method Based on the natural language process description, the system automatically generates business, analysis and design documents for the "case."
[0274] The components of the system are those that allow the generation of the documents mentioned above (Figure 3). 1. Input / Output Device 120: A device into which natural language text is input using the following configuration: a. Language User Interface 121 b. Case User Interface 122 c. Formats, Graphical Representations, and STD Document User Interfaces 123 d. Document Display User Interface 124 2. CPU 110: A processing device of the system 100, comprising: a. Main Memory 140: The main memory 140 performs the following functions depending on its configuration: i. Figure 141 ii. Sentence Matrix 142 iii. FC Matrix 143 iv. DC Matrix 144 b. Processor 150: Processor 150 performs the following functions depending on its configuration: i. Automatic Sentence Analyzer 151 ii. Automated Software Designer 152 iii. Document Generator 153 3. Database Memory 130: a. Static Database Memory 160: i. MAS Metamodel 161 ii. Language, words, and morphosyntactic rules 162 iii. Format, Graphical Representation, and STD Document 163 b. Dynamic Database Memory 170 i. Simple Question 171 ii. Functional components 172 iii. Design components 173
[0275] Input / Output Devices The tool consists of persistent memory capable of generating screens on a monitor with fields into which a user can enter data or perform actions.
[0276] Case User Interface 122 The case user interface allows the user to enter requested data and perform actions to store the data in database memory.
[0277] For the tool to function, the user must enter data (layers, resources, processes, sub-processes, moments, steps) in natural language as defined by the method.
[0278] To that end, the case user interface presents this upload interface that allows the user to enter these fields and create relationships between them using the order defined in the method, with each of the components (dimensions, time activities, and simple sentences) requiring the following data fields to be uploaded: - name - explanation - Related subordinate elements
[0279] These data fields are displayed in the interface: Dimensional and temporal activity upload interface where {text1} and {text2} are replaced by the names of the corresponding components when the user fills in the data fields in the prescribed sequence. - First, {text1} = "Layer" and {text2} = "Resource". - When an edit action is performed, the interface, Dimension and Temporal Activity Upload interface is displayed again, but this time with {text1} = "Resource" and {text2} = "Process". o When an edit action is performed, the interface, the dimensional and temporal activity upload interface is displayed again, but this time with {text1} = "Process" and {text2} = "Sub-Process". When an edit action is performed, the interface, dimensional and temporal activity upload interface is displayed again, but this time with {text1} = "Sub-process" and {text2} = "Moment".
[0280] When an edit action is performed, the interface, the dimension and temporal activity upload interface is displayed again, but this time with {text1}="Moment" and {text2}="Step".
[0281] Once a step is completed, a sentence interface is displayed, an interface in which the user must answer questions to generate a complete structured simple sentence structured as defined in the method. The user must also select one of the following options from a list of step types: - F: Function - CC: Check / Control - QS: Inquiry / Search - FX: Calculation - L: Link
[0282] As the user answers a question, the tool completes sentences in which the interface concatenates the text entered into the question to display the sentence.
[0283] Once the data upload task is completed, the user can perform the following actions: - Save: Save the uploaded data in the database memory. - Cancel: Discard the uploaded data in the database memory.
[0284] View Analytics The display of the analysis on the monitor consists of screens displaying the uploaded data organized in a way that allows the user of the tool to read and understand the "cases", guiding the user to perform a precise analysis for the proper generation of global and detailed functional requirements, which are generated automatically by the tool by prompting the user to review and select some data.
[0285] View word analysis This interface presents the user with simple sentences in a structured form (the word analysis interface).Using this interface, the tool allows the user to run the analysis processor and the analysis document processor.
[0286] The user is presented with a table with the entire sentences that have been uploaded, and the user can perform an analysis action on each of those sentences, which engages an analysis processor that returns as a result a list of words contained in the sentence.
[0287] Each word is characterized by: - Word: The word detected by the analysis processor. - Word: The question to which the word belongs in the sentence i.e. When, Who, What, How, Where. - Component Type: The type that the analysis processor automatically assigns to each word, i.e. NOUN, ADV, VERB, DO, ADJ. - In Scope: a column allowing the user of the tool to indicate, if so desired, whether a word in the question is part of the scope of the "case" being designed. The user can choose between the following options: YES / NO. - Is Attribute: A column allowing the user of the tool to indicate whether a word in the question should behave like an attribute if so desired. The user can choose among the following options: YES / NO.
[0288] Once the word analysis task is completed, the user can perform the following actions: - Save: Save the uploaded data in the database memory. - Cancel: Discard the uploaded data in the database memory.
[0289] In this interface, an analysis action can be performed on each word identified by the analysis processor, in which case the analysis document processor is executed and a requirements analysis display is displayed.
[0290] Requirements analysis display This interface (the requirements analysis view) presents to the user the global and detailed requirements generated by the analysis document processor.
[0291] The user is presented with a table with the entirety of the generated global requirements, and a nested table with the detailed requirements corresponding to each global requirement.
[0292] Each global requirement is characterized by: - Word: The word detected by the analysis processor. - Component Type: The type that the analysis processor automatically assigns to each word, i.e. NOUN, ADV, VERB, DO, ADJ. - Step Type: The value selected by the user in the upload interface. - GlobalReqNum: A correlated number generated by the tool. - Global Requirement: A statement generated by the analysis processor that corresponds to a global requirement.
[0293] Each detailed requirement is characterized by: - DetReqNum: Correlation number generated by the tool. - Detailed Requirement: A statement generated by the analysis processor that corresponds to the detailed requirement. - &Attributes: A list of &attributes that describe the word. They must be selected by the user from the list generated by: Manual user input * Auto-generation for words flagged by the user as "Is Attribute". - Message: A list of messages the user wants to specify as responses to error, correct action, and incorrect action situations resulting from the execution of a requirement. This list can be generated by: Manual input by the user. - Expression: The formula to be calculated that the user specifies for step type = CC or FX. - Associated GlobalReq: A list of global requirements that allows the user to reference a GlobalReq from this list and associate it with a detailed requirement. This happens when the scope description does not contain a description of some feature of this kind (which prevents the system from automatically generating the relationship), in which case the user adds it.
[0294] Once the word analysis task is completed, the user can perform the following actions: - Save: Save the uploaded data in the database memory. - Cancel: Discard the uploaded data in the database memory.
[0295] View Design This interface presents the user with the words detected by the analysis processor to enable the design of "cases" based on the results of the analysis.
[0296] The user is presented with a table with the totality of analyzed words, each of which has a nested table containing its related words based on the associated requirements.
[0297] Each word is characterized by the following data derived from the analysis phase: - Word: A word included in the scope being designed. - Word: The question to which the word belongs in the sentence i.e. When, Who, What, How, Where. - Component Type: The type that the analysis processor assigns to each word, i.e. NOUN, ADV, VERB, DO, ADJ. - Step Type: The value selected by the user in the upload interface. - Is &attribute: a feature indicated by the user in the analysis phase, which can be YES or NO.
[0298] In this interface, design actions can be performed on each of the listed words, in which case the design processor is executed and then a representation of the design is displayed along with a list of classes generated for the word and its associated words.
[0299] Each class is characterized by: - Class: The name of the class designed by the design processor. - ClassType: ClassType can be L or NonL. - &Attributes: list of &attributes assigned to the class, which in any case belong to the list of &attributes status in the analysis phase. - Methods: A list of methods assigned to the class. These methods are generated by the design processor.
[0300] Once the classes are designed, a View Diagram action can be performed which presents the class diagram on the screen, an example class diagram.
[0301] Once the word analysis task is completed, the user can perform the following actions: - Save: Save the uploaded data in the database memory. - Cancel: Discard the uploaded data in the database memory.
[0302] Storage Processor To automatically generate analysis and design documents for a "case", the tool provides the processor with three functions: an analysis process that performs analysis actions, a design process that performs design actions, and a document process that generates the resulting documents.
[0303] Automatic Sentence Analyzer The analysis processor takes a set of complete simple sentences uploaded by users into a database memory. Based on the sentences, the analysis processor executes three algorithms. - an algorithm for identifying words relevant to the construction of a "case" (FIG. 4E1), a component method of the invention described in step E. - an algorithm for generating global requirements for the "case", step F, the component method of the invention described in sub-step 1. - an algorithm for generating detailed requirements for a "case", step F, the method of the components of the invention described in sub-step 2.
[0304] Word Algorithm The algorithm (Figure 4E1) executes the routine described for each existing sentence, requesting that the following two lists be uploaded to the database: GRW={grouping words} A set of words that define a grouping, for example the word "of" is a grouping word when it occurs in "list of prices". - PEX={excluded words} A set of words that should be excluded from the analysis. PEX usually consists of prepositions, conjunctions, and articles.
[0305] When this algorithm is run, all of the words are converted into functional components of the "case", classified by component type, and correlated by questions.
[0306] The component type describes the following: -NOUN: NOUN - PER: PERSON NOUN - ADV: ADVERBIAL CONSTRUCTION - VERB: VERB - DO DIRECT OBJECT NOUN - ADJ: ADJECTIVE
[0307] Global Requirements Algorithm The algorithm runs the routine described for each word identified in the scope and requires the following list to be uploaded to the database: - reqgl_abm_Sust: A statement used to construct a global requirement whenever a NOUN construct is identified in scope. The method suggests something similar to "Create, Read, Update and Delete" + {NounWord}. - reqgl_abm_Pers: A statement used to configure global requirements whenever a PER construct is specified in the scope. The method suggests something similar to "Create, Read, Update and Delete Entities with role" + {PersonWord}. - reqgl_verboF: A statement used to constitute a global requirement whenever a VERB linked to an F-type step is identified in the scope. The method suggests something similar to "Create transaction record" + {VerbWord} + {DOWord}. - reqgl_verboF: A statement used to construct a global requirement whenever a VERB linked to an L-type step is identified in the scope. The method suggests something similar to "Create rule that" + {VerbWord} + {DOWord} "with" + {NounWord}. - reqgl_verbo: A statement used to construct a global requirement whenever a VERB linked to a non-F or non-L type step is identified in the scope. The method suggests something akin to "Create rule that" + {VerbWord} + {DOWord}.
[0308] When this algorithm is run, all of the global requirements of the "case" are stored in a database.
[0309] Detailed requirements algorithm The algorithm runs the routine described for each word identified in the scope and requires that a boilerplate text in the selected language for the case description be uploaded to the database.
[0310] Design Process The design processor takes the set of functional components and complements that were added in the analysis phase. - Attribute - message - Formulas - Related requirements
[0311] All of them are linked to functional components that are part of the scope of the "case".
[0312] A design processor algorithm (FIG. 4G1) is executed which implements stage G and automatically generates the classes and relationships that make up the resulting design diagram of the "case".
[0313] Document Processing The tool consists of a persistent memory that can automatically generate documents that are shown on the monitor with fields where the user can see the data coming from the upload memory.
[0314] Business Document Processing The business document generator takes the data uploaded in the upload interface, which is stored in the database, and applies the following algorithm to generate a business document (Figure 4I2): a) The business document generator retrieves the entirety of the uploaded data stored in the order indicated by the method by accessing a database having the following columns and number rows uploaded by the user: Layer, Resource, Process, Sub-Process, Moment, Step, When, Who, What, How, Where, Statement. b) The Business Document Generator concatenates Layer & Resource & Process in the Title variable c) The business document generator concatenates the sub-processes & moments in the subtitle variable. d) The business document generator presents each step with greater indentation. e) The business document generator presents each sentence with a larger indentation.
[0315] The business document generator names the resulting document a business document (Figure 4I2), and the tool enables the user to store the document in a document file, print the document using a printing device (printer, plotter, etc.), and display the document using a display device (monitor, screen, projector, etc.).
[0316] Analytical Document Processing The analysis document processor takes all of the uploaded data as well as the global and detailed generated requirements and applies the following algorithms to generate the analysis document (Figure 4I3): a) An analytical document processor generates the title, subtitle, and steps using the same algorithms as for business documents b) The analytical document processor presents each global requirement associated with a step with a greater indentation than the previous step. c) The analysis document processor presents each detailed requirement related to the global requirement with a greater indentation than the indentation of the preceding global requirement.
[0317] The analysis document processor names the resulting document the analysis document (Figure 4I3), and the tool allows the user to store the document in a document file, print the document using a printing device (printer, plotter, etc.), and display the document using a display device (monitor, screen, projector, etc.).
[0318] Design Document Processing The document processor takes the class data identified by the design processor and generates an XML file that uses the xmi standard for reading UML diagrams.
[0319] The document processor names the resulting document the class design document (Figure 5).
[0320] The resulting document is stored in a document file.
[0321] Database Memory The tool consists of a persistent memory capable of storing the results produced by the tool.
[0322] Database A database in which the uploaded analysis and design data generated by the tool is stored. The database is managed by a database engine.
[0323] Document files A database in which generated documents are stored. Document files are structures set up on a hard disk that are managed by the operating system's file server. [Explanation of symbols]
[0324] 100 Systems 110 CPU 120 Input / Output Devices 121 Language User Interface 122 Case User Interface 122-1 Case User Interface 122-2 Case User Interface 122-3 Case User Interface 122-11 User Interface Components 122-12 User Interface Components 122-13 User Interface Components 122-15 Interface Components 122-16 Interface Components 122-21 User Interface Components 122-22 Interface Components 122-23 User Interface Components 122-24 User Interface Components 122-25 Interface Components 122-27 Interface Components 122-28 User Interface Components 122-29 User Interface Components 122-31 User Interface Components 122-32 User Interface Components 122-33 User Interface Components 122-34 User Interface Components 122-35 Interface Components 122-36 Interface Components 123 Formatting, Graphical Representation, and STD Text User Interfaces 124 Document Viewing User Interface 130 Database Memory 140 Main memory 141 Figure 142 Sentence Matrix 143 FC Matrix 144 DC Matrix 150 processors 151 Automatic Sentence Analyzer 152 Automated Software Designer 153 Automatic Document Generator 160 static database memory 161 MAS Metamodel 161-0 Succession Relationship 161-1 Word 161-2 Performer Word 161-3 Performable Word 161-4 Performance Word 161-5 Relationship 161-6 Relationship 161-8 Succession Relationship 161-9 Succession Relationship 161-10 VERB(is)-NOUN rule 161-11 VERB-NOUN-PREP-NOUN rule 161-12 VERB-NOUN rule 161-13 VERB(hold responsible)-NOUN-PREP-NOUN rule 161-14 VERB(link)-NOUN-PREP-NOUN rule 162 Language, Words, and Morpho-Syntactic Rules 163 Formats, Graphical Representations, and STD Statements 170 Dynamic Database Memory 171 Simple Questions 172 Functional Components 173 Design Components 310 Layer 320 resources 330 Process 340 Subprocess 350 Moments 360 steps 370 Simple Sentences
Claims
1. 1. A computer-implemented method for generating a functional architecture document from natural language phrases and mathematical formulas describing a case, the natural language phrases and mathematical formulas being stored in a database memory (130), comprising: A. uploading, through an input / output device (120), a logical structure named MAS metamodel (161), said MAS metamodel defining axiomatic principles of said natural language and said mathematical expressions according to the morphological and syntactic rules stored in said database memory (130) and determining the behavior of said processor (150) which executes the following functions depending on the configuration of said processor (150): an automatic sentence analyzer (151), an automatic software designer (152) and a document generator (153); stage A includes the following sub-stages: A1. storing in said database memory (130) said MAS metamodel (161) defining logic used by said processor (150) configured as an automatic sentence analyzer to generate analysis and design documents, said logic including automatic generation of Performer words, Performable words, and Performance words based on transitive verbs; A2. storing in said database memory said logic of said MAS metamodel (161) regarding morphological-syntactic rules which defines that every sentence of natural language and mathematical expressions can be built on a) a question logic which defines which questions of the form "when", "who", "what", "how", and "where" the words in a simple sentence belong to, named WH questions, b) a step type logic which defines which types of verbs constitute said WH questions (explicit calculation (FX), check / confirm (CC), query / search (QS), link (L), unspecified (F)), and c) a word logic which defines types of words. The steps consist of: B. inputting the list of eligible languages, the grammatical and syntactic features of each eligible language through a linguistic user interface (121) of said input / output device (120) and storing this data in said database memory (130); C. entering through a case user interface (122) of said input / output device (120) a description of said "case" as text in one of the natural languages selected from said list of eligible languages from step B, and then storing said description in said database memory (130), said text being introduced by a user; D. Identifying the simple sentences and mathematical moments of the case from step C, wherein the user answers the WH questions for each sentence and then uses the case user interface (122) of the input / output device (120) to upload the simple sentences and the mathematical moments so that they may be stored in the database memory, said identifying step comprising the following substeps: identifying said simple sentences together with answers to said questions for each step of said case for steps of type L and type F; Concatenating the answers from each step of said type L and said type F; identifying the simple sentences corresponding to the mathematical moments of the cases along with answers to the questions for each step of the cases for steps of types QS, FX, and CC; Concatenating the responses of each step of type QS, type FX, and type CC The steps include: E. identifying functional and mathematical components for the single sentence from step D by said processor (150) configured as an automatic sentence analyzer (151) as defined in step A and storing said functional and mathematical components in said database memory (130); F. Automatically generating a functional architecture document based on said functional and mathematical components from stage E, by said processor (150) configured as a document generator, using a graphical notation specifically defined for this type of document, said generation of a functional architecture comprising the following sub-stages: F1. Applying said morphological and syntactic rules, based on which said processor (150) configured as a document generator (153) excludes the stated specific words from said functional components and generates new functional components in the case of transitive verbs, i.e. functional components whose names are the verb plus the suffix "ER" indicating the agent and other functional components whose names are the verb plus the suffix "BLE", F2. Defining the graphical notations to be used in the functional architecture diagram using the format, graphical notation, and sentence user interface (STD) (123) of said input / output device (120), indicating the graphical components used in said diagram for each functional component according to the corresponding word type, and storing said graphical notations in said database memory (130); F3. generating, using said processor (150), said functional architecture document based on said functional components stored in said database memory (130) using said representation defined in step F2, and displaying said functional architecture document on said input / output device. Including steps A method comprising:
2. Phase B consists of the following sub-phases: B1. inputting a sequence of adjectives in a selected eligible language through said input / output device (120) and storing said sequence in said database memory (130); B2. inputting through said input / output device (120) special words of said selected eligible language that can be found on said single sentence of text from step D and that should be excluded from a list of functional components, and storing said special words in said database memory (130); B3. inputting through said input / output device (120) grouping words of said selected eligible language that can be used to link functional components containing two or more words and that can be found in said text of said single sentence from step D, and storing said grouping words in said database memory (130); B4. inputting through said input / output device (120) verb endings of infinitive verbs in said selected eligible languages that can be found within said text of said single sentence from step D, and storing said verb endings in said database memory (130). The method according to claim 1, characterized in that
3. Stage C consists of the following sub-stages: C1. selecting, using said input / output device (120) configured as a case user interface (122), from the eligible languages defined in step B, a language in which said case will be written; C3. Identifying said steps of said cases by applying said sub-step A2 and storing said steps in said database memory (130). The method according to claim 1, characterized in that
4. 2. The method of claim 1, wherein step C comprises identifying components, layers, resources, processes, sub-processes and moments that structure the context of the "case" and storing the components, the layers, the resources, the processes, the sub-processes and the moments in the database memory (130).
5. 2. The method of claim 1, wherein step E comprises breaking down the simple sentence into words, characterizing the words according to a selected language, identifying the functional components of the simple sentence, and storing the functional components in the database memory (130).
6. 2. The method of claim 1, wherein in step E, the user adds functional components that are not present in the list of functional components automatically identified from the single sentence.
7. 2. The method of claim 1, wherein step E further comprises identifying the functional components associated with the step types FX, CC, and QS.
8. 2. A method according to claim 1, characterized in that in step E, the user adds formulas describing the mathematical behaviour of said "cases" for all CC and FX type steps.
9. 2. The method according to claim 1, characterized in that the morphological and syntactic rules defined in sub-stage A1 are applied in stage E and, based on said morphological and syntactic rules, the processor (150) configured as an automatic sentence analyzer (151) excludes certain words mentioned in the rules and generates new functional components for the case of transitive verbs, namely a functional component whose name is said verb plus the suffix "ER" indicating an agent and a functional component whose name is said verb plus the suffix "BLE".
10. G. automatically identifying, by said processor (150) configured as an automated software designer (152), design components based on said functional components from phase E and storing said design components in said database memory (130); H. uploading output formats of business documents, analysis documents, and design documents, parameters of boilerplate text for requirements, and the graphical representation for design drawings through the format, graphical representation, and STD text user interface (123) of the input / output device (120) and storing the output formats of business documents, analysis documents, and design documents, parameters of boilerplate text for requirements, and the graphical representation for design drawings in the database memory (130); I. applying the format, graphical notation and STD sentences defined in phase G, by said processor (150) configured as a document generator (153), automatically generating business documents based on said simple sentences from phase D, automatically generating said analysis documents based on said functional components from phase E, and automatically generating said design documents based on said design components from phase F. The method of claim 1 further comprising:
11. Stage G comprises the following sub-stages: G1. Selecting and generating groups of functional components, classes of the functional components, and inheritance relationships, and storing the groups of functional components, classes of the functional components, and inheritance relationships in the database memory (130); G2. Generating an expression class based on an FX type step and a CC type step, and storing said expression class in said database memory (130); G3. Generating domain classes based on QA type steps and storing said domain classes in said database memory (130); G4. Generating a relationship class based on an L-type step and storing said relationship class in said database memory (130); G5. Generating action classes based on F-type steps and storing said action classes in said database memory (130). The method according to claim 10, characterized in that
12. 2. The method of claim 1, wherein in step E, a user adds error messages, validation messages, and warning messages.
13. Phase I comprises the following sub-phases: I1. Generating business documents; I2. Generating analysis documentation; I3. What it consists of generating software design documentation The method according to claim 10, characterized in that
14. Phase I1 subjects the business document to the following actions: a) ordering dimensions, temporal activities, and simple sentences; b) combining already ordered components; and c) displaying said business document on said input / output device (120). The method according to claim 11, characterized in that the product is produced by
15. Phase I2 subjects the analysis document to the following actions: a) formulating global functional requirements, defining global requirements for NOUN components, and defining global requirements for VERB components; b) framing detailed functional requirements and defining detailed requirements for NOUN, PERSON, VERB, and DO components; and c) displaying the analysis document on the input / output device (120). The method according to claim 10, characterized in that the product is produced by
16. 11. The method of claim 10, characterized in that step I3 generates the design document and displays the design document on the input / output device (120).
17. 11. The method according to claim 10, characterized in that in step H, a user may use a template to configure the structure of the text of the functional analysis document of the "case" using the format, graphical notation and STD sentence user interface (123) of the input / output device (120) and then store the structure in the database memory (130).
18. 1. A system for generating functional architecture documents, business documents, analysis documents and software design specification documents from case describing descriptions expressed in natural phrases and mathematical expressions stored in a database, the system comprising: input / output devices (120) configured as a language user interface (121), a case user interface (122), a format, graphical notation, and STD sentence user interface (123), and a document display user interface (124) for inputting a qualified language and a structure of said qualified language, for inputting a description of said "case" in natural language and mathematical expressions, for inputting formats and graphical notations for document generation, and for displaying functional architecture documents and said business documents, said analysis documents, and said software design specification documents; a main memory (140) connected to the input / output device (120) in interaction with a processor (150), configured for volatile storage of the description of the case, functional components, design components, and the functional architecture document and the business document, the analysis document, and the software design specification document; a processor (150) configured to receive at least one of a natural language and a mathematical description from a user, the description including the case and identifying the description of the case; the processor (150) configured as an automatic sentence analyzer for generating simple sentences corresponding to steps of the case and analyzing the simple sentences to automatically generate functional components based on the simple sentences; the processor (150) configured as an automated software designer for identifying the design components of the case and supplemental functional components corresponding to FX, CC, and QS types based on the functional and mathematical components; the processor (150) configured as a document generator for generating functional architecture documents, as well as business documents, analysis documents, and software design specification documents based on the functional components and the design components; said processor (150) configured to statically store MAS metamodels (161), mathematical expressions corresponding to languages, words, FX type expressions, and morpho-syntactic rules (162), as well as formats, graphical notations, and STD sentences (163), and further configured to dynamically store simple sentences and questions (171), functional components (172), and design components (173); The system comprises a database memory (130) connected to the
Citation Information
Patent Citations
Design drawing device
JP1992137073A
Natural language programming system based on object directivity
JP1998031582A
Method of automatically extracting from natural language specifications of system modeling meta-model language model for the system, device, and computer program
JP2010257452A
Deriving process models from natural language use case models
US20110239183A1
Systems and Methods For Automating the Application of a Software Methodology
US20130097583A1
