# US 2014/0196002 A1 · Tool and method thereof for efficient design of information technology systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0196002 A1 - Document ID: US20140196002A1 - Status: Published application - Kind: A1 - Application number: 14/149,037 - Filed: 2014-01-07 - Published: 2014-07-10 - Earliest claimed: 2013-01-08 - Inventors: Shahak SHEFER - Web page: https://patentgrep.com/patent/US20140196002A1 ## CPC - G06F 8/10: Requirements analysis; Specification techniques - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A design tool and method for designing information technology (IT) systems are provided. The method includes receiving at least one requirement for the IT system; receiving a layout of the IT system; extracting the at least one requirement and the layout; classifying the at least one requirement; selecting a design pattern respective of each of the at least one classified requirement and the layout; linking each of the at least one classified requirement to at least one design dimension; producing an at least one complete design of the IT system; and querying a user to determine whether the at least one complete design of the IT system has been approved by the user. ## Claims ### Claim 1 A method for designing an information technology (IT) system, comprising: receiving at least one requirement for the IT system; receiving a layout of the IT system; extracting the at least one requirement and the layout; classifying the at least one requirement; selecting a design pattern respective of each of the at least one classified requirement and the layout; linking each of the at least one classified requirement to at least one design dimension; producing an at least one complete design of the IT system; and querying a user to determine whether the at least one complete design of the IT system has been approved by the user. ### Claim 2 (depends on 1) The method of claim 1, wherein extracting the at least one requirement and the at least a layout further comprises extracting information related to at least one of: entities, properties, meta-data, forms, commands, navigation, users, roles, authorizations, actions, and action items. ### Claim 3 (depends on 1) The method of claim 1, further comprising: determining whether each of the at least one requirement is a distinct requirement, wherein the distinct requirement is a classified requirement being associated with only one design dimension; and determining whether each of the at least one requirement is an optimized requirement. ### Claim 4 (depends on 1) The method of claim 1, wherein linking the at least one classified requirement to at least one design dimension further comprises: linking at least one property of the at least one design dimension, wherein the at least one property is at least one of: type, sub-type, level, priority, origin, stage, span, amount, frequency, timing, input, output, mandatory, counter, activity, visibility, position, pointer, severity, probability, completeness percentage, approval status, and status. ### Claim 5 (depends on 1) The method of claim 1, further comprising: upon receiving approval for the at least one complete design, generating detailed documents describing at least system context diagrams, component models, and deployment models. ### Claim 6 (depends on 1) The method of claim 1, further comprising: communicating with an IT concept dictionary to create or maintain a hierarchical list of professional concepts, wherein the IT concept dictionary contains a glossary of professional concepts. ### Claim 7 (depends on 1) The method of claim 1, wherein the at least one requirement is classified as at least one of: hardware type, graphical user interface (GUI), database, training, and security. ### Claim 8 (depends on 1) The method of claim 1, further comprising: generating at least displays of the IT system being designed in real-time. ### Claim 9 (depends on 8) The method of claim 8, wherein the at least displays of the IT system include any of: a simulation of the IT system, user experience and layout design modes, graphic dynamic displays and interfaces of navigation, menus and database design, hierarchical displays and interfaces of the at least one requirement, business vocabulary, actions, users, roles, and action items. ### Claim 10 A design tool for designing an information technology (IT) system, comprising: an interface configured to receive at least one input requirement and a layout of the IT system to be designed; a processor; a memory connected to the processor and configured to contain a plurality of instructions that, when executed by the processor, configure the system to: extract the at least one requirement and the layout; classify the at least one requirement; select a design pattern respective of each of the at least one requirement and the layout; link the at least one requirement to at least one design dimension; and produce at least one optimized design pattern. ### Claim 11 (depends on 10) The design tool of claim 10, further comprising a solution repository containing at least logical connections between an input requirement and at least one design dimension. ### Claim 12 (depends on 10) The design tool of claim 10, wherein the system is further configured to: determine whether each of the at least one requirement is a distinct requirement, and determine whether each of the at least one requirement is an optimized requirement, wherein the distinct requirement is a classified requirement being associated with only one design dimension. ### Claim 13 (depends on 10) The design tool of claim 10, wherein the system is further configured to: generate detailed documents describing at least one of: system context diagrams, component models, and deployment models. ### Claim 14 (depends on 10) The design tool of claim 10, wherein the system is further configured to: communicate with an IT concept dictionary to create or maintain a hierarchical list of professional concepts, wherein the IT concept dictionary contains a glossary of professional concepts. ### Claim 15 (depends on 10) The design tool of claim 10, further comprising at least one of: a generator, a knowledge extractor, a literal scanner, and a requirement analyzer. ### Claim 16 (depends on 15) The design tool of claim 15, wherein the knowledge extractor is configured to extract information related to at least one of: entities, properties, meta-data, forms, commands, navigation, users, roles, authorizations, actions, and action items. ### Claim 17 (depends on 15) The design tool of claim 15, wherein the generator is configured to at least generate displays and functions of the IT system being designed in real-time. ### Claim 18 (depends on 17) The design tool of claim 17, wherein the displays and functions of the information technology system may be any of: a simulation of the IT system, user experience and layout design modes, graphic dynamic displays and interfaces of navigation, menus and database design, hierarchical displays and interfaces of the at least one requirement, business vocabulary, actions, users, roles, and action items. ### Claim 19 (depends on 15) The design tool of claim 15, wherein the literal scanner is configured to at least perform a textual analysis of the at least one requirement. ### Claim 20 (depends on 15) The design tool of claim 15, wherein the requirement analyzer is configured to classified the at least one requirement as at least one of: hardware type, graphical user interface (GUI), database, training, and security. ### Claim 21 A non-transitory computer readable medium having stored thereon instructions for causing one or more processing units to execute a process for designing an information technology (IT) system, comprising: receiving at least one requirement for the IT system; receiving a layout of the IT system; extracting the at least one requirement and the layout; classifying the at least one requirement; selecting a design pattern respective of each of the at least one classified requirement and the layout; linking each of the at least one classified requirement to at least one design dimension; producing an at least one complete design of the IT system; and querying a user to determine whether the at least one complete design of the IT system has been approved by the user.