User interfaces and software reuse in model based software systems
First Claim
Patent Images
1. A method comprising:
- providing a set of business rules for a software system;
scanning said set of business rules;
forming a first pattern signature based on said scanning; and
determining if said pattern signature is present in other portions of said software system.
1 Assignment
0 Petitions
Accused Products
Abstract
In a model based software system, a set of business rules is scanned, and patterns are identified. The patterns are then compared, and similarities identified which indicate that software can be reused in the system. In one embodiment, identifiers of the rules are scanned. In another embodiment, usage patterns are used for designing a middle layer and generating code. In another embodiment of the invention, a data model is generated by capturing data from a user interface for a business document.
-
Citations
54 Claims
-
1. A method comprising:
-
providing a set of business rules for a software system;
scanning said set of business rules;
forming a first pattern signature based on said scanning; and
determining if said pattern signature is present in other portions of said software system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A method comprising:
-
providing a set of business rules for a software system;
scanning said set of business rules;
extracting descriptions of said set of business rules from said scanning;
forming a first pattern signature based on said descriptions of said set of business rules; and
determining if said descriptions are present in other portions of said software system. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A method comprising:
-
capturing user interface data from business documents;
mapping user interface elements to said business documents, and forming a data model for said business documents;
wherein said business documents are represented by business objects; and
wherein said business documents from which said interface data is acquired is represented by interface business objects. - View Dependent Claims (20, 21, 22, 23, 24)
-
-
25. A method comprising:
-
capturing user interface and user action data for a system in a specification repository;
abstracting user interface and user action sequences based on an expected response of said system; and
capturing said expected response of said system as a set of specification data for each said user action. - View Dependent Claims (26, 27)
-
-
28. A computer readable medium comprising instructions available thereon for executing a method comprising:
-
receiving a set of business rules for a software system;
scanning said set of business rules;
forming a first pattern signature based on said scanning; and
determining if said pattern signature is present in other portions of said software system. - View Dependent Claims (29, 30, 31, 32, 33, 34, 35, 36)
-
-
37. A computer readable medium comprising instructions available thereon for executing a method comprising:
-
receiving a set of business rules for a software system;
scanning said set of business rules;
extracting descriptions of said set of business rules from said scanning;
forming a first pattern signature based on said descriptions of said set of business rules; and
determining if said descriptions are present in other portions of said software system. - View Dependent Claims (38, 39, 40, 41, 42, 43, 44, 45)
-
-
46. A computer readable medium comprising instructions available thereon for executing a method comprising:
-
capturing user interface data from business documents;
mapping user interface elements to said business documents, and forming a data model for said business documents;
wherein said business documents are represented by business objects; and
wherein said business documents from which said interface data is acquired is represented by interface business objects. - View Dependent Claims (47, 48, 49, 50, 51)
-
-
52. A computer readable medium comprising instructions available thereon for executing a method comprising:
-
capturing user interface and user action data for a system in a specification repository;
abstracting user interface and user action sequences based on an expected response of said system; and
capturing said expected response of said system as a set of specification data for each said user action. - View Dependent Claims (53, 54)
-
Specification