User interfaces and software reuse in model based software systems

• US 8,572,563 B2
• Filed: 09/26/2008
• Issued: 10/29/2013
• Est. Priority Date: 03/15/2004
• Status: Active Grant

• Current Assignee: Ramco Systems Limited
• Original Assignee: Ramco Systems Limited
• Inventors: Sundararajan, Parthasarathy, Ramaswamy, Srinivasan, Sethuraman, Rajagopalan, Devalla, Raghuram
• Primary Examiner(s): Chen, Qing
• Application Number:
  US12/238,463
• Publication Number:
  US 20090024657A1
• Time in Patent Office: 1,859 Days
• Field of Search: 717/100, 717/104, 717/105, 717120-123, 715/866
• US Class Current: 717/120
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

User interfaces and software reuse in model based software systems is disclosed. In one embodiment, user interface data is captured from business documents. Further, user interface elements are mapped to the business documents. A data model is formed for the business documents. A set of business rules for each business component in the data model is provided. A sequence of business rules associated with each action in the data model is scanned. In addition, a first pattern signature associated with an action that uniquely identifies each of the sequence of business rules is formed. It is determined if the first pattern signature is present in other actions in the data model. If so, the first pattern signature is included in a set of pattern signatures of the data model, else step of determining for a second pattern signature that is a subset of the first pattern signature is repeated.

Claims

1. A method comprising:

capturing user interface data from business documents by a processor;

mapping user interface elements to said business documents by said processor;

forming a data model for said business documents by said processor, wherein said business documents are represented by business objects, wherein said business documents from which said user interface data is acquired are represented by interface business objects, and wherein said business objects comprise data segments and said interface business objects comprise said user interface elements;

providing a set of business rules for each business component including one or more business objects of said data model by said processor, wherein said set of business rules provides a business logic used in each business component, and wherein said set of business rules includes a sequence of business rules associated with each action performed by an end user;

scanning said sequence of business rules associated with each action in said data model by said processor;

forming a first pattern signature associated with an action that uniquely identifies each of said sequence of business rules based on said scanning by said processor;

determining if said first pattern signature is present in other actions in said data model by said processor;

if present, including said first pattern signature in a set of pattern signatures of said data model by said processor; and

if not present, repeating the step of determining for a second pattern signature that is a subset of said first pattern signature by said processor;

repeating said steps of forming and determining for a pattern signature for each action in said data model by said processor;

analyzing said set of pattern signatures by said processor;

identifying similarities in said set of pattern signatures by said processor; and

identifying said set of pattern signatures that can be reused in one or more data models based on said similarities in said set of pattern signatures by said processor.

2. The method of claim 1, wherein said data segments comprise a hierarchy.

3. The method of claim 2, wherein said data segments have a data identifier that identifies an instance of data in said data segments.

4. The method of claim 3, further comprising:

forming a hierarchy of said data segments.

5. The method of claim 1, wherein said business documents comprise various sections that capture data at various stages in a lifecycle of said business documents.

6. The method of claim 1, further comprising:

using said business objects and said interface business objects to derive a database schema, wherein said database schema comprises a user interface.

7. The method of claim 1, wherein said user interface elements are selected from the group consisting of edit controls, check boxes, text areas, grid controls, combo boxes, list controls, display only controls, hyperlinks, and command buttons.

8. The method of claim 1, wherein each data segment is represented as database tables in a database schema, and wherein each of said database tables includes a primary key formed by a data identifier that is a part of the respective data segment and identifiers of corresponding parent segments.

9. A non-transitory computer readable medium storing instructions thereon for executing a method comprising:

capturing user interface data from business documents by a processor;

mapping user interface elements to said business documents by said processor;

forming a data model for said business documents by said processor, wherein said business documents are represented by business objects, wherein said business documents from which said user interface data is acquired are represented by interface business objects, and wherein said business objects comprise data segments and said interface business objects comprise said user interface elements;

providing a set of business rules for each business component including one or more business objects of said data model by said processor, wherein said set of business rules provides a business logic used in each business component, and wherein said set of business rules includes a sequence of business rules associated with each action performed by an end user;

scanning said sequence of business rules associated with each action in said data model by said processor;

forming a first pattern signature associated with an action that uniquely identifies each of said sequence of business rules based on said scanning by said processor;

determining if said first pattern signature is present in other actions in said data model by said processor;

if present, including said first pattern signature in a set of pattern signatures of said data model by said processor; and

if not present, repeating the step of determining for a second pattern signature that is a subset of said first pattern signature by said processor;

repeating said steps of forming and determining for a pattern signature for each action in said data model by said processor;

analyzing said set of pattern signatures by said processor;

identifying similarities in said set of pattern signatures by said processor; and

identifying said set of pattern signatures that can be reused in one or more data models based on said similarities in said set of pattern signatures by said processor.

10. The non-transitory computer readable medium of claim 9, wherein said data segments comprise a hierarchy.

11. The non-transitory computer readable medium of claim 10, wherein said data segments have a data identifier that identifies an instance of data in said data segments.

12. The non-transitory computer readable medium of claim 11, wherein said method further comprises:

forming a hierarchy of said data segments.

13. The non-transitory computer readable medium of claim 9, wherein said business documents comprise various sections that capture data at various stages in a lifecycle of said business documents.

14. The non-transitory computer readable medium of claim 9, wherein said method further comprises:

using said business objects and said interface business objects to derive a database schema, wherein said database schema comprises a user interface.