Method for synchronizing UML with JAVA in a version configuration management system
First Claim
1. In a computer system executing a repository program, a computer-implemented method for synchronizing UML with JAVA in a version configuration management system, said method comprising the steps of:
- a. determining if a previous revision of UML representation exist, and if not;
b. creating a new revision of a UML representation;
c. putting said new revision in a “
created”
state;
d. storing new UML representation in said UML revision;
e. putting said UML revision in a “
ready”
state;
f. determining if there are more UML classes/interfaces, and if so;
g. extracting JAVA revision ID from UML class/interface;
h. determining if JAVA revision exist, and if not;
i. creating a new revision of JAVA source and putting said new revision in a “
created”
state;
j. generating JAVA source from UML representation;
k. storing new JAVA source in JAVA revision and putting it in a “
ready”
state; and
, l. repeating all of the steps f through k until there are no more UML classes/interfaces.
9 Assignments
0 Petitions
Accused Products
Abstract
A computer implemented-method for synchronizing JAVA in a UML in a computer system executing a repository program. The method comprises the steps of determining if a previous revision of UML representation exist, and if not; creating a new revision thereof. Next, the new revision is put in a “created” state and stored in a new UML representation in the UML revision. The UML revision is then put in a “ready” state. After this, a determination is made as to whether or not there are more UML classes/interfaces; and if there are, a JAVA revision ID is extracted from the UML class/interface. Another determination is made as to whether or not a JAVA revision exist, and if not; a new revision of JAVA source is created and put into a “created” state. JAVA source is then generated from a UML representation and stored in the new revision and put into a “ready” state. All of the steps are repeated until there are no more UML classes/interfaces.
37 Citations
8 Claims
-
1. In a computer system executing a repository program, a computer-implemented method for synchronizing UML with JAVA in a version configuration management system, said method comprising the steps of:
-
a. determining if a previous revision of UML representation exist, and if not;
b. creating a new revision of a UML representation;
c. putting said new revision in a “
created”
state;
d. storing new UML representation in said UML revision;
e. putting said UML revision in a “
ready”
state;
f. determining if there are more UML classes/interfaces, and if so;
g. extracting JAVA revision ID from UML class/interface;
h. determining if JAVA revision exist, and if not;
i. creating a new revision of JAVA source and putting said new revision in a “
created”
state;
j. generating JAVA source from UML representation;
k. storing new JAVA source in JAVA revision and putting it in a “
ready”
state; and
,l. repeating all of the steps f through k until there are no more UML classes/interfaces. - View Dependent Claims (2, 3, 4)
a. determining if UML representation is different than previous revision, and if so;
b. determining if said previous revision is in a “
steady”
state, and if so;
c. putting said previous revision in a “
pending”
state.
-
-
3. The method as in claim 1 wherein it is determined that a JAVA revision exist, further comprising the steps of:
-
a. determining if said JAVA revision is in a “
ready”
state, and if so;
b. putting said previous revision in a “
pending”
state.
-
-
4. The method as in claim 3 wherein it is determined that said JAVA revision is not in a “
- ready”
state, further comprising the step of returning to the step of determining if there are more UML classes/interfaces.
- ready”
-
5. A storage medium encoded with machine-readable computer program code for synchronizing UML with JAVA in a version configuration management system, wherein, when the computer program code is executed by a computer, the computer performs the steps of:
-
a. determining if a previous revision of UML representation exist, and if not;
b. creating a new revision of a UML representation;
c. putting said new revision in a “
created”
state;
d. storing new UML representation in said UML revision;
e. putting said UML revision in a “
ready”
state;
f. determining if there are more UML classes/interfaces, and if so;
g. extracting JAVA revision ID from UML class/interface;
h. determining if JAVA revision exist, and if not;
i. creating a new revision of JAVA source and putting said new revision in a “
created”
state;
j. generating JAVA source from UML representation;
k. storing new JAVA source in JAVA revision and putting it in a “
ready”
state; and
,l. repeating all of the steps f through k until there are no more UML classes/interfaces. - View Dependent Claims (6, 7, 8)
a. determining if UML representation is different than previous revision, and if so;
b. determining if said previous revision is in a “
steady”
state, and if so;
c. putting said previous revision in a “
pending”
state.
-
-
7. The storage medium as in claim 5 wherein it is determined that a JAVA revision exist, further comprising the steps of:
-
a. determining if said JAVA revision is in a “
ready”
state, and if so;
b. putting said previous revision in a “
pending”
state.
-
-
8. The storage medium as in claim 7 wherein it is determined that said JAVA revision is not in a “
- ready”
state, further comprising the step of returning to the step of determining if there are more UML classes/interfaces.
- ready”
Specification