EARLIEST PRIORITY DATE:

This Application claims priority from a Complete patent application filed in India having Patent Application No. 202011022953, filed on June 01, 2020 and titled “SYSTEM AND METHOD FOR ENGINEERING STRUCTURE DESIGN”.

BACKGROUND

Embodiment of the present disclosure relate to engineering structure design, and more particularly to, a system and a method to formation and presentation of the engineering structure design.

Business enterprises rely on increasingly sophisticated systems to manage their internal operation and provide goods and services to their clients and customers. The development, deployment, maintenance, and updating of enterprise level system has become essential to carry out almost all business processes. The structure engineering concerns the conceptualization and construction of complex systems. As such, it is an important part of any major project. The structure engineering commences at the initial stages of a project, and continues throughout the project life cycle, thereby having a great impact on the successful completion of the project. The "structure" a system as "a regularly interacting or independent group of items forming a unified whole.

Conventional tools include manual methods of structure design, in that the quality of manual methods generates flawed code because of human error. Further, the structure design is not optimized because the structure design processes are performed by humans using non-optimizing processes. In summary, conventional methods for engineering structure design are non-optimal, resulting in increased cost of development, high maintenance costs, limited reusability, the need for extensive debugging and testing, and poor documentation.

Furthermore, with advancement in technology currently available structure design tools are directed toward efficiency of use in a specific environment, rather than over the broad range of system levels. However, several different tools are necessary at the different system levels, which complicates communication of necessary information between system levels. Further, the specific tools place different operational requirements on the user, thereby reducing the efficiency of using the programs. Some of the currently available methodological processes such as six sigma, agile, lean, Waterfall are not driven by any scientific rule or principal, hence cannot ensure the accuracy of outcome. Moreover, such methodologies do not have strong scientific backbone, hence produce non-uniform result in different operating environment and conditions.

Hence, there is a need for an improved system and method for engineering structure design to address the aforementioned issue(s).

BRIEF DESCRIPTION

In accordance with an embodiment of the present disclosure, a system for engineering structure design is provided. The system includes an information receiving subsystem configured to receive structure design information from a user requirement. The system also includes a boundary creation subsystem configured to create one or more design boundaries on the structure design information received by the information receiving subsystem. The system further includes an object formation subsystem configured to select one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter based on the one or more design boundaries created by the boundary creation subsystem. The one or more object properties comprises at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof. The object formation subsystem is also configured to transform one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generate a conceptualized object. The system further includes a de-conceptualization subsystem configured to present at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design.

In accordance with an embodiment of the present disclosure, a method for engineering structure design is provided. The method includes receiving, by an information receiving subsystem, structure design information from a user requirement. The method also includes creating, by a boundary creation subsystem, one or more design boundaries on the structure design information received by the information receiving subsystem. The method further includes selecting, by an object formation subsystem, one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter based on the one or more design boundaries created by the boundary creation subsystem, where the one or more object properties comprises at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof. The method further includes transforming, by the object formation subsystem, one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generalize a conceptualized object. The method further includes presenting, by a de conceptualization subsystem, at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design.

To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which:

FIG. 1 is a block diagram representation of a system for engineering structure design in accordance with an embodiment of the present disclosure;

FIG. 2 is a block diagram representation of one embodiment of the system of FIG. 1, depicting the structure of the boundary creation subsystem in accordance with an embodiment of the present disclosure.

FIG. 3 is a block diagram representation of one embodiment of the system for engineering structure design of FIG. 1 in accordance with an embodiment of the present disclosure; FIG. 4 is a schematic representation of an exemplary system for engineering structure design of FIG. 1 in accordance with an embodiment of the present disclosure;

FIG. 5 is a block diagram of a computer or a server in accordance with an embodiment of the present disclosure; and

FIG. 6 is a flow chart representing the steps involved in a method for engineering structure design in accordance with an embodiment of the present disclosure.

Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

DETAILED DESCRIPTION

For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.

Embodiments of the present disclosure relate to a system and method for engineering structure design. The system includes an information receiving subsystem configured to receive structure design information from a user requirement. The system also includes a boundary creation subsystem configured to create one or more design boundaries on the structure design information received by the information receiving subsystem. The system further includes an object formation subsystem configured to select one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter based on the one or more design boundaries created by the boundary creation subsystem. The one or more object properties comprises at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof. The object formation subsystem is also configured to transform one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generate a conceptualized object. The system further includes a de-conceptualization subsystem configured to present at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design.

FIG. 1 is a block diagram representation of a system (10) for engineering structure design in accordance with an embodiment of the present disclosure. The system (10) includes an information receiving subsystem (20) to receive structure design information from a user requirement. The structure design information is corresponding to any engineering structure. As used herein, “the engineering structure is widely a collection of sub-systems objects, which interacts with each other to achieve the system functionality. In one embodiment, the structure design information may include an input, an output, a network specification, databases, files, source documents, entity relationship diagrams, structure control, backup or recovery information and the like. The system design information should be structured based on a protocol. The protocol includes execution of a project and designing of the structure and sub-structure object. In one embodiment, the execution of the project may include two phases such as development phase and maintenance phase. In such an embodiment, the development phase may include designing of a system object and implementation of the system object. In another embodiment, the maintenance phase may include understanding the objectified structural design of the system, modification of system object as per requirements and implementation of modified system object. Similarly, designing the system object may include defining the conceptual design of the system.

Furthermore, the system (10) includes a boundary creation subsystem (30) to create one or more design boundaries on the structure design information received by the information receiving subsystem (20). The system (10) further includes an object formation subsystem (40) to select one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter based on the one or more design boundaries created by the boundary creation subsystem (30). The one or more object properties comprises at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof. As used herein, the need is the purpose of deployment, the host is a context of ATM centre, the unique identifier is the ID or name of ATM centre and the object boundary is the boundary /limitation of ATM centre. Similarly, the attributes are defined as components of the deployment environment, the state is the state of ATM centre and the state activity are ready state activity and construction state activity. The structure of the boundary creation subsystem (30) is shown in FIG. 2, where in step 1, from a user need/requirement boundary creation subsystem (30) create one or more design boundaries on received design information. This create a conceptualized object, an object attribute and a host/context of conceptualized object and does the naming. In Step 2, from a user need/requirement boundary creation subsystem (30) create one or more design boundaries on received design information of ‘static and dynamic aspects of created object’ . This create an object state and a need driven state activity and does the naming.

The object formation subsystem (40) further transforms one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generate a conceptualized object. More specifically, the object formation subsystem (40) uses the boundary creation subsystem to create object and conceptualized object. In one embodiment, the object and the conceptualized objects are stored in an object database (OBD). In a specific embodiment, the conceptualized object may include a conceptual design of the one or more object properties including one or more design parameters corresponding to the object properties and a design description of the one or more design parameters. In such an embodiment, the one or more design parameters and corresponding the object properties may provide mapping of standard design artifacts/terms with object properties. The design description of the one or more design parameters may provide the details of design parameters/artifacts/terms. In one embodiment, the information may be received using a communication medium including at least one of a text, a graphic symbol, a diagram, an image, a picture, an animation medium, a voice medium, a programming language or the combination thereof. The one or more object properties are defined in terms of object properties itself to structure in object form and to retain it in object database which is shown in below mentioned tables (table 1-6):

TABLE 1: Conceptual Design of System Host or Context

TABLE 2: Conceptual design of system needs

TABLE 3: Conceptual design of attributes

TABLE 4: Conceptual design of system state

TABLE 5: Conceptual design of “need based execution of state activity”

As used herein, the significant object includes an object which has significance or association with concerned design or selected design information (SDI) by user, an object associated with the structure design information. As used herein, the selected design information (SDI) may include an object and conceptualized object, an object property, a corresponding design parameter of object property, a complete or subset/part of detail design of design parameter.

TABLE 6: Conceptual design of state activity

For improved comprehension, throughout the design object properties of system/subsystems object should not conflict each other.

In addition, the system (10) further includes a de-conceptualization subsystem (50) to present at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design. In one embodiment, the at least one form may include one or more properties of the structure design object, a conceptual design of the object properties, a conceptual/real physical structure/body of an object and conceptualized object with corresponding static and dynamic aspects, a conceptual/real physical structure/body of significant objects with corresponding static and dynamic aspects for selected design information. To understand the engineering structure completely, all the object properties of design should be known to the user. The de-conceptualization subsystem (50) provides a method to unfold the properties of the conceptualized object until its resolve into the known terms. In one embodiment, the presentation window may include an object presentation window (OPW), conceptual design presentation window (CDPW) or physical design presentation window (PDPW). In such an embodiment, the object presentation window displays the properties of the structure or sub-structure of object. The object presentation window includes one or more functions such as user may select any object property. After selecting the object properties user may selects the plurality of options such as option to launch OPW of selected object property, option to launch CDPW for the selected object property, option to launch PDPW for the selected object property and option to mark the selected object parameter as known.

In another embodiment, the conceptual design presentation window shows the conceptual design of selected object property. The conceptual design presentation window includes one or more functions such as invoking the window including the object parameters and corresponding design parameter of object property and design description based on selected object property from OPW. The detail of design parameter may be provided using a communication medium including at least one of a text, a graphic symbol, a diagram, a picture, a programming language, a voice medium or the combination thereof. The de-conceptualization subsystem (50) enables the selection of the design information by the user. The selection of design information enables display of the logical start and end point of the ‘selected design information (SDI), shows the animation for the SDI on PDPW, adjustment of the speed of animation, display of the animation with audio, updating the PDPW based on user’s focus point on SDI while displaying the animation highlight the respective part of SDI, display the conceptual/real physical structure/body of significant objects at start and end point of selected design information, creation of the container view which modifies along with update of significant objects and display the expected next update as per the design. As used herein, the container view shows one or more properties of the structure design object, a conceptual design of the object properties, a conceptual/real physical structure/body of an object and conceptualized object with corresponding static and dynamic aspects, a conceptual/real physical structure/body of significant objects with corresponding static and dynamic aspect for selected design information using the highlighted and greyed out fields. These highlighted and greyed out fields update in sync with execution as per concerned design or selected design information. In yet another embodiment, the physical design presentation window displays a conceptual/real physical structure/body of an object and conceptualized object with corresponding static and dynamic aspects, a conceptual/real physical structure/body of significant objects with corresponding static and dynamic aspect for selected design information . The design principles of physical design presentation window include physical view of attribute of object may be marked by same colour to help in clearly defining the boundary, used symbol should be as close as natural terms of understanding, a table help efficiently understand the difference between achieved and expected design structure of Significant Object by reducing the correlation/comparison time (Tc) and time to switch the focus between conceptual physical view of Significant Object and respective design (or SDI) should be as less as possible for the better comprehension.

In one embodiment, the de-conceptualization subsystem (50) may be used to comprehend the engineering structure design using at least one of a direct method, an identifier method or a combination thereof. To comprehend the object completely, all of the properties should be in known experiential terms. The direct method includes experiencing the objects and corresponding properties through the objectification of sensory information directly originated from physical object. To achieve this de conceptualization subsystem (50) displays one or more properties of the structure design object, a conceptual design of the object properties, a conceptual/real physical stmcture/body of an object and conceptualized object with corresponding static and dynamic aspect, a conceptual/real physical structure/body of significant objects with corresponding static and dynamic aspects for selected design information SDI. Similarly, the identifier method includes experiencing of the object and object properties using identifiers. The identifier method uses, a name given to object and object properties, a symbolic representation of object and object properties or the combination thereof. One embodiment of the de-conceptualization subsystem is described in FIG. 3.

FIG. 3 is a flow chart representing the steps involved in operation of the de conceptualization subsystem (50) of FIG. 1 in accordance with an embodiment of the present disclosure. The operation includes reading or listening the design information from CDPW by the user. If the user faces difficulty in understanding the design information, in such case user takes the following step to make it understandable. The operation includes selecting the object properties from OPW in step 60. The operation also includes demonstrating the selected object property into object form in step 70. If the parameter of CDPW are unresolved into object form, then the CDPW of selected design parameter is opened, the user selects the design information from CDPW in step 80 and 85 respectively. Furthermore, the operation includes demonstrating the selected design information into object form in step 86. If the design information is not demonstrated into object form, then the de-conceptualization subsystem shows the conceptual/real physical structure/body of significant objects with corresponding static and dynamic aspect for the selected design information (SDI) in step 90. In case where attributes are resolved into object forms, the de-conceptualization subsystem opens the OPW of selected design in step 100. In case where selected design information is demonstrated into object form, then de-conceptualization subsystem opens the OPW of selected design information in step 101.

FIG. 4 is a block diagram representation of an exemplary system (10) for engineering structure design of FIG. 1, in accordance with an embodiment of the present disclosure. Considering an example of an ATM machine, where system (10) develops the design of ATM machine which may fulfil the need of cash withdrawal from bank account. The system (10) includes an information receiving subsystem (20) which receives structure design information such as information related to designing of the ATM machine from a user requirement. The system (10) also includes a boundary creation subsystem (30) which creates one or more design boundaries such as designing the cash withdrawal system on the structure design information received by the information receiving subsystem (20). Furthermore, the system (10) includes an object formation subsystem (40) which selects or creates one or more object properties based on the one or more design boundaries created by the boundary creation subsystem (30). The one or more object properties comprises at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof. The object formation subsystem (40) transforms one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generate a conceptualized object. The objectification of cash withdrawal system which unique identifier is ‘ATM machine’ is described below using the one or more properties as mentioned tables 7- 12. In table 7-12 detail of design parameter will be provided using a communication medium including at least one of a text, a graphic symbol, a diagram, a picture, a programming language, a voice medium or combination thereof.

Table 7 describes the conceptual design of system host or context with respect to the ATM machine. The one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter are itself defined in terms of object properties. Such information of object property has to also structure in the object form to retain it in the object database (ODB) (130). In order to define the information in object form, there should have at least a need, a host, a boundary, an attribute and unique identifier. Rest of two properties (state and state activities) shall be added if required. Interpretation of conceptual design of object properties may vary or controlled by system designer.

TABLE 7: Conceptual design of system host or context

Table 8 illustrates the conceptual design of needs of the ATM system.

TABLE 8: Conceptual design of needs

Table 9 illustrates the conceptual design of system attributes. The first system attribute is the keypad of the ATM machine and the second system attribute is the display screen of the ATM machine.

TABLE 9: Conceptual design of system attributes

Table 10 illustrates the conceptual design of system states, where the operational state of the ATM machine is described.

TABLE 10: Conceptual design of system states

Table 11 shows the conceptual design of “need based execution of state activity” of the ATM machine.

TABLE 11 : Conceptual design of “need based execution of state activities”

Table 12 illustrates the conceptual design of state sub-activity, where the sub-activity is “Validation of ATM Card.”

Table 12: Conceptual design of state sub-activity

The system further includes a de-conceptualization subsystem (50) to present at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design. FIG. 5 is a computer or a server (200) for the system for classification of the customer query in accordance with an embodiment of the present disclosure. The server includes processor(s) (210), and memory (220) operatively coupled to the bus (230). The processor(s) (210), as used herein, means any type of computational circuit, such as, but not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a very long instruction word microprocessor, an explicitly parallel instruction computing microprocessor, a digital signal processor, or any other type of processing circuit, or a combination thereof.

The memory (220) includes a plurality of subsystems stored in the form of executable program which instructs the processor (210) to perform the method steps illustrated in FIG. 1. The memory (220) has following subsystems: an information receiving subsystem (20), a boundary creation subsystem (30), an object formation subsystem (40) and a de-conceptualization subsystem (50).

The memory (220) includes an information receiving subsystem (20) configured to receive structure design information from a user requirement. The memory (220) also includes a boundary creation subsystem (30) configured to create one or more design boundaries on the structure design information received by the information receiving subsystem (20). The memory (220) further includes an object formation subsystem (40) configured to select one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter based on the one or more design boundaries created by the boundary creation subsystem (30). The one or more object properties comprises at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof. The object formation subsystem (40) is also configured to transform one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generate a conceptualized object. The memory (220) further includes a de-conceptualization subsystem (50) configured to present at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design. Computer memory (220) elements may include any suitable memory device(s) for storing data and executable program, such as read only memory, random access memory, erasable programmable read only memory, electrically erasable programmable read only memory, hard drive, removable media drive for handling memory cards and the like. Embodiments of the present subject matter may be implemented in conjunction with program modules, including functions, procedures, data structures, and application programs, for performing tasks, or defining abstract data types or low-level hardware contexts. Executable programs stored on any of the above-mentioned storage media may be executable by the processor(s) (210).

FIG. 6 is a flow chart representing the steps involved in a method (300) for engineering structure design in accordance with an embodiment of the present disclosure. The method (300) includes receiving structure design information from a user requirement in step 310. In one embodiment, receiving the structure design information may include receiving the structure design information by an information receiving subsystem. In a specific embodiment, receiving the structure design information may include receiving an input, an output, a network specification, databases, files, source documents, entity relationship diagrams, structure control and backup or recovery information or the like. In such an embodiment, receiving the structure design information may include receiving the structure design information from the user requirement using a communication medium including at least one of a text, a graphic symbol, a diagram, a picture, an animation medium, a voice medium, a programming language or the combination thereof.

The method (300) also includes creating one or more design boundaries on the structure design information received by the information receiving subsystem in step 320. In one embodiment, creating one or more design boundaries on the structure design information may include creating one or more design boundaries on the structure design information by a boundary creation subsystem. The method (300) further includes selecting one or more object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter based on the one or more design boundaries created by the boundary creation subsystem in step 330. In one embodiment, selecting the one or more object properties may include selecting the one or more object properties by an object formation subsystem. The one or more object properties includes at least one of a need, an object boundary, an attribute, a state, a state activity, a host, a unique identifier, or a combination thereof.

The method (300) further includes transforming one or more selected object properties, a corresponding design parameter of object property, a complete or subset of detail design of design parameter into an object form to generalize a conceptualized object in step 340. In one embodiment, transforming one or more selected object properties into an object form may include transforming one or more selected object properties into an object form by the object formation subsystem. In a specific embodiment, the conceptualized object may include a conceptual design of the one or more object properties comprising one or more design parameters corresponding to the object properties and a design description of the one or more design parameters. In one embodiment, the object is stored in an object database.

The method (300) further includes presenting at least one form of the conceptualized object using a presentation window for comprehension of the engineering structure design in step 350. In one embodiment, presenting at least one form of the conceptualized object may include presenting at least one form of the conceptualized object by a de-conceptualization subsystem. In a specific embodiment, the at least one form may include one or more properties of the structure design object, a conceptual design of the object properties, a conceptual/real physical structure/body of an object and conceptualized object with corresponding static and dynamic aspects, a conceptual/real physical structure/body of significant objects with corresponding static and dynamic aspects for selected design information.. In some embodiments, the presentation window comprises an object presentation window, a conceptual design presentation window or a physical design presentation window.

Various embodiments of the present disclosure described above enables unified scientific techniques of structuring and presenting the design information of engineering structure. The system reduces the non-mechanical activities involved in structuring and presenting the structure design. The system also provides the design principal of de-conceptualization subsystem, which takes help of a machine to handle the mechanical aspect of understanding. Further, the system does not require physical object in order to convey structure information. Also, the system requires less efforts to translate the structure design information.

It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof.

While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.