Method for synchronizing JAVA with UML in a version configuration management system
First Claim
1. In a computer system executing a repository program, a computer-implemented method for synchronizing JAVA with UML, said method comprising the steps of:
- a. determining if a previous revision of JAVA source exist, and if not;
b. creating a new revision of said JAVA source;
c. putting said new revision in a “
created”
state;
d. storing new JAVA source in said new revision;
e. putting said new revision in a “
ready”
state;
f. determining if a previous revision of UML representation exist, and if not;
g. creating a new revision of said UML representation;
h. putting said new revision of said UML in a “
created”
state; and
, i. generating a UML representation of said JAVA source.
9 Assignments
0 Petitions
Accused Products
Abstract
A computer-implemented method for synchronizing JAVA with UML in a computer system executing a repository program. The method comprises the steps of determining if a previous revision of JAVA source exist, and if not; creating a new revision of the JAVA source. Next, the new revision is put in a “created” state and the new JAVA source is stored in the new revision. After this, the new revision is put in a “ready” state. A determination is next made if a previous revision of UML representation exist, and if not; a new revision of the UML representation is created. The new revision of the UML is then put in a “created” state; and, a UML representation of the JAVA source is created.
56 Citations
8 Claims
-
1. In a computer system executing a repository program, a computer-implemented method for synchronizing JAVA with UML, said method comprising the steps of:
-
a. determining if a previous revision of JAVA source exist, and if not;
b. creating a new revision of said JAVA source;
c. putting said new revision in a “
created”
state;
d. storing new JAVA source in said new revision;
e. putting said new revision in a “
ready”
state;
f. determining if a previous revision of UML representation exist, and if not;
g. creating a new revision of said UML representation;
h. putting said new revision of said UML in a “
created”
state; and
,i. generating a UML representation of said JAVA source. - View Dependent Claims (2, 3, 4)
a. determining if JAVA source code is different than a previous revision, and if so;
c. determining if said previous revision is in a “
ready”
state, and if so;
d. putting previous revision in a “
pending”
state;
e. storing a new JAVA source in said new revision of said JAVA source code; and
,f. putting d. creating a new revision of a UML representation of said JAVA source code;
e. embedding a JAVA source revision identifier in said UML representation of class; and
,f. storing modified UML in said new revision.
-
-
3. The method as in claim 1 wherein it is determined that a previous revision of UML representation does not exist, further comprising the steps of:
-
a. creating a new revision of UML representation; and
,b. putting said new revision in a “
created state”
.
-
-
4. The method as in claim 1 further including the steps of:
-
a. storing unique ID'"'"'s for said new revision and UML revision in said UML representation;
b. storing new UML representation in said new revision; and
,c. putting said new revision in a “
ready”
state.
-
-
5. A storage medium encoded with machine-readable computer program code for synchronizing JAVA with UML, wherein, when the computer program code is executed by a computer, the computer performs the steps of:
-
a. determining if a previous revision of JAVA source exist, and if not;
b. creating a new revision of said JAVA source;
c. putting said new revision in a “
created”
state;
d. storing new JAVA source in said new revision;
e. putting said new revision in a “
ready”
state;
f. determining if a previous revision of UML representation exist, and if not;
g. creating a new revision of said UML representation;
h. putting said new revision of said UML in a “
created”
state; and
,i. generating a UML representation of said JAVA source. - View Dependent Claims (6, 7, 8)
a. determining if JAVA source code is different than a previous revision, and if so;
c. determining if said previous revision is in a “
ready”
state, and if so;
d. putting previous revision in a “
pending”
state;
e. storing a new JAVA source in said new revision of said JAVA source code; and
,f. putting d. creating a new revision of a UML representation of said JAVA source code;
e. embedding a JAVA source revision identifier in said UML representation of class; and
,f. storing modified UML in said new revision.
-
-
7. The storage medium as in claim 5 wherein it is determined that a previous revision of UML representation does not exist, further comprising the steps of:
-
a. creating a new revision of UML representation; and
,b. putting said new revision in a “
created state”
.
-
-
8. The storage medium as in claim 5 further including the steps of:
-
a. storing unique ID'"'"'s for said new revision and UML revision in said UML representation;
b. storing new UML representation in said new revision; and
,c. putting said new revision in a “
ready”
state.
-
Specification