I'm working on a logical design (so far) of the War in the Pacific database from going through both the database/scenario editor and the editor manual.
So far, I have a 38-page Word document of a basic data/entity dictionary of 22 entities and about 161 attributes and am working on an entity relationship diagram.
If anybody would be interested in checking the Word document out and see if I left anything out or have questions (I know I have questions I'm writing down to try to figure out myself) feel free to PM me or, for those who have my email, just email me directly.
War in the Pacific Database
Moderators: wdolson, Don Bowen, mogami
War in the Pacific Database
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
RE: War in the Pacific Database
ORIGINAL: dereck
I'm working on a logical design (so far) of the War in the Pacific database from going through both the database/scenario editor and the editor manual.
So far, I have a 38-page Word document of a basic data/entity dictionary of 22 entities and about 161 attributes and am working on an entity relationship diagram.
If anybody would be interested in checking the Word document out and see if I left anything out or have questions (I know I have questions I'm writing down to try to figure out myself) feel free to PM me or, for those who have my email, just email me directly.
Good work, should make understanding the daabase easier.. Thanks
-
el cid again
- Posts: 16984
- Joined: Mon Oct 10, 2005 4:40 pm
RE: War in the Pacific Database
Perhaps we can add some undocumented functions which have been revealed officially? For example, how do get a non-malarial hex in malaria country. [It is awful and ugly, but at least moders would know what the system is and what their options are]. There are some restricted slots NOT stated in the manuals too. Some we know for sure and some we know only approximately. Stuff like that.
WITP Entity Relationship Diagram
This is only round #1 ... more revisions expected.
- Attachments
-
- WITPERDiagram.jpg (87.69 KiB) Viewed 307 times
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
RE: WITP Entity Relationship Diagram
AIR GROUP
Description
User-defined or historical organizations that operated and maintained aircraft in the Pacific theatre during World War II.
Certain air groups must be left in their assigned slots as follows:
0001-0949 Japanese Air Groups
0950-2399 Allied Air Groups
Each Occurrence Of This Entity :
MAY BE an Air Group has one and only one LEADER
MAY BE an Air Group has one or more PILOTS
MAY BE an Air Group is at one and only one LOCATION
MAY BE an Air Group is on one and only one SHIP
MAY BE an Air Group is under one and only one HEADQUARTERS
MAY BE an Air Group uses one and only one AIRCRAFT
AIRCRAFT
Description
User-defined or historical aircraft which saw service in the Pacific theatre during World War II.
Certain aircraft types must be left in their assigned slots as follows:
001-075 Japanese aircraft types
076-249 Allied aircraft types
Furthermore the following slots are reserved for carrier-operable aircraft:
001-007 Japanese carrier aircraft
015-023 Japanese carrier aircraft
077-101 Allied carrier aircraft
Each Occurrence Of This Entity :
MAY BE an Aircraft is used by one or more AIR GROUPS
MAY BE an Aircraft upgrades from one and only one AIRCRAFT
MAY BE an Aircraft upgrades to one and only one AIRCRAFT
MAY BE an Aircraft uses one or more DEVICES
DEVICE
Description
Each weapon is known in War in the Pacific as a 'device'. Devices can be of many different types, running from a Vickers MG to an 18-inch naval gun, or bombs, torpedoes, drop tanks, squads, vehicles, and a number of other items. Essentially, anything that projects power into combat (shoots or can be shot at) is a device.
Devices must be in the following slot ranges:
137-138 Allied devices
139 Japanese device
197 Ohka bomb
213 Atomic bomb
236 Various support squad
237-249 Japanese aircraft engines
250-256 Various support squads
255-314 Japanese devices
315-517 Allied devices
518-526 Industry items
Each Occurrence Of This Entity :
MAY BE a Device is used by one or more AIRCRAFT
MAY BE a Device is used by one or more HEADQUARTERS
MAY BE a Device is used by one or more LAND COMBAT UNITS
MAY BE a Device is used by one or more LOCATIONS
MAY BE a Device is used by one or more SHIP CLASSES
MAY BE a Device is used by one or more SHIPS
MAY BE a Device is used by one or more TABLE OF EQUIPMENT
MAY BE a Device upgrades from one and only one DEVICE
MAY BE a Device upgrades to one and only one DEVICE
HEADQUARTERS
Description
User-defined or historical headquarters which served in the Pacific theatre during World War II.
Headquarters must be assigned the following slot numbers:
0001-0098 Japanese headquarters
0100-0215 Allied headquarters
Each Occurrence Of This Entity :
MAY BE an HQ commands one and only one HEADQUARTERS
MAY BE an HQ commands one or more AIR GROUPS
MAY BE an HQ commands one or more LAND COMBAT UNITS
MAY BE an HQ is based on one and only one TABLE OF EQUIPMENT
MAY BE an HQ is commanded by one and only one HEADQUARTERS
MAY BE an HQ is commanded by one and only one LEADER
MAY BE an HQ uses one or more DEVICES
LAND COMBAT UNIT
Description
A user-defined or historical land combat unit which served in the Pacific theatre during World War II.
Land Combat Units must be in the following ranges:
0979-1999 Japanese land combat units
2120-3499 Allied land combat units
Furthermore the following slots are reserved for the following reasons:
1940-1979 Must be left open as these slots are used by Japanese Militiary ground
units that are automatically mobilized in 1945
1980-1983 Must be left open as these are the slots used by Japanese North
Vietnamese militia units that are mobilized each time (up to a maximum of
four) an Allied unit moves into a border hex inside North Vietnam (from
China to Hue).
Each Occurrence Of This Entity :
MAY BE an LCU has one and only one LEADER
MAY BE an LCU is at one and only one LOCATION
MAY BE an LCU is based on one and only one TABLE OF EQUIPMENT
MAY BE an LCU is under one and only one HEADQUARTERS
MAY BE an LCU uses one or more DEVICES
LEADER
Description
User-defined or historical individuals that influence combat formations, whether through their formation's abilities in combat or logistics.
Up to 19,999 individual leaders (total of both sides) may be created.
Each Occurrence Of This Entity :
MAY BE a Leader commands one and only one AIR GROUP
MAY BE a Leader commands one and only one HEADQUARTERS
MAY BE a Leader commands one and only one LAND COMBAT UNIT
MAY BE a Leader commands one and only one SHIP
MAY BE a Leader commands one and only one TASK FORCE
MAY BE a Leader is one and only one PILOT
LOCATION
Description
A user-defined or historical location/base which will be displayed and moveable to on the WITP map.
Base/location slots are in the following range:
0217-0900
NOTE: Do not move any base/location to a different slot as some parts of the game program assume these bases are in their current slots.
Each Occurrence Of This Entity :
MAY BE a Location contains one or more AIR GROUPS
MAY BE a Location contains one or more LAND COMBAT UNITS
MAY BE a Location contains one or more SHIPS
MAY BE a Location uses one or more DEVICES
PILOT
Description
Special individuals that are generally better trained and have more experience than newer pilots. Up to 19,999 individual pilots (total of both sides) may be created.
Each Occurrence Of This Entity :
MAY BE a Pilot is assigned to one and only one AIR GROUP
MAY BE a Pilot may be one and only one LEADER
SHIP
Description
A user-defined or historical ship which saw service in the Pacific theatre during World War II. Certain ships MUST be left in their assigned slots as follows:
0001-2999 Japanese ships
3000-9999 Allied ships
Each Occurrence Of This Entity :
MAY BE a Ship belongs to one and only one SHIP CLASS
MAY BE a Ship can carry one or more AIR GROUPS
MAY BE a Ship can use one or more DEVICES
MAY BE a Ship has one and only one LEADER
MAY BE a Ship is at one and only one LOCATION
MAY BE a Ship is part of one and only one TASK FORCE
SHIP CLASS
Description
A ship class that was employed in the Pacific theatre of World War II. Certain ship classes MUST be left in their assigned slots as follows:
0001-0171 Japanese Ship Classes
0172-0499 Allied Ship Classes
0501-1199 Japanese Ship Classes
1200-1999 Allied Ship Classes
Each Occurrence Of This Entity :
MAY BE a Ship Class can use one or more DEVICES
MAY BE a Ship Class consists of one or more SHIPS
MAY BE a Ship Class upgrades from one and only one SHIP CLASS
MAY BE a Ship Class upgrades to one and only one SHIP CLASS
TABLE OF EQUIPMENT
Description
A user-defined or historical Table of Equipment layout for units which served in the Pacific theatre during World War II.
Table of Equipments must be located in the following slots:
0901-0977 Japanese TO&Es
2001-2119 Allies TO&Es
Each Occurrence Of This Entity :
MAY BE a TOE can use one or more DEVICES
MAY BE a TOE is the basis for one or more HEADQUARTERS
MAY BE a TOE is the basis for one or more LAND COMBAT UNITS
TASK FORCE
Description
A user-defined or historical task force organization which served in the Pacific theatre during World War II.
Task forces must be in the following range:
3500-3899 Japanese task forces
3900-3999 Allied task forces
Each Occurrence Of This Entity :
MAY BE a TF consists of one or more SHIPS
MAY BE a TF has one and only one LEADER
Description
User-defined or historical organizations that operated and maintained aircraft in the Pacific theatre during World War II.
Certain air groups must be left in their assigned slots as follows:
0001-0949 Japanese Air Groups
0950-2399 Allied Air Groups
Each Occurrence Of This Entity :
MAY BE an Air Group has one and only one LEADER
MAY BE an Air Group has one or more PILOTS
MAY BE an Air Group is at one and only one LOCATION
MAY BE an Air Group is on one and only one SHIP
MAY BE an Air Group is under one and only one HEADQUARTERS
MAY BE an Air Group uses one and only one AIRCRAFT
AIRCRAFT
Description
User-defined or historical aircraft which saw service in the Pacific theatre during World War II.
Certain aircraft types must be left in their assigned slots as follows:
001-075 Japanese aircraft types
076-249 Allied aircraft types
Furthermore the following slots are reserved for carrier-operable aircraft:
001-007 Japanese carrier aircraft
015-023 Japanese carrier aircraft
077-101 Allied carrier aircraft
Each Occurrence Of This Entity :
MAY BE an Aircraft is used by one or more AIR GROUPS
MAY BE an Aircraft upgrades from one and only one AIRCRAFT
MAY BE an Aircraft upgrades to one and only one AIRCRAFT
MAY BE an Aircraft uses one or more DEVICES
DEVICE
Description
Each weapon is known in War in the Pacific as a 'device'. Devices can be of many different types, running from a Vickers MG to an 18-inch naval gun, or bombs, torpedoes, drop tanks, squads, vehicles, and a number of other items. Essentially, anything that projects power into combat (shoots or can be shot at) is a device.
Devices must be in the following slot ranges:
137-138 Allied devices
139 Japanese device
197 Ohka bomb
213 Atomic bomb
236 Various support squad
237-249 Japanese aircraft engines
250-256 Various support squads
255-314 Japanese devices
315-517 Allied devices
518-526 Industry items
Each Occurrence Of This Entity :
MAY BE a Device is used by one or more AIRCRAFT
MAY BE a Device is used by one or more HEADQUARTERS
MAY BE a Device is used by one or more LAND COMBAT UNITS
MAY BE a Device is used by one or more LOCATIONS
MAY BE a Device is used by one or more SHIP CLASSES
MAY BE a Device is used by one or more SHIPS
MAY BE a Device is used by one or more TABLE OF EQUIPMENT
MAY BE a Device upgrades from one and only one DEVICE
MAY BE a Device upgrades to one and only one DEVICE
HEADQUARTERS
Description
User-defined or historical headquarters which served in the Pacific theatre during World War II.
Headquarters must be assigned the following slot numbers:
0001-0098 Japanese headquarters
0100-0215 Allied headquarters
Each Occurrence Of This Entity :
MAY BE an HQ commands one and only one HEADQUARTERS
MAY BE an HQ commands one or more AIR GROUPS
MAY BE an HQ commands one or more LAND COMBAT UNITS
MAY BE an HQ is based on one and only one TABLE OF EQUIPMENT
MAY BE an HQ is commanded by one and only one HEADQUARTERS
MAY BE an HQ is commanded by one and only one LEADER
MAY BE an HQ uses one or more DEVICES
LAND COMBAT UNIT
Description
A user-defined or historical land combat unit which served in the Pacific theatre during World War II.
Land Combat Units must be in the following ranges:
0979-1999 Japanese land combat units
2120-3499 Allied land combat units
Furthermore the following slots are reserved for the following reasons:
1940-1979 Must be left open as these slots are used by Japanese Militiary ground
units that are automatically mobilized in 1945
1980-1983 Must be left open as these are the slots used by Japanese North
Vietnamese militia units that are mobilized each time (up to a maximum of
four) an Allied unit moves into a border hex inside North Vietnam (from
China to Hue).
Each Occurrence Of This Entity :
MAY BE an LCU has one and only one LEADER
MAY BE an LCU is at one and only one LOCATION
MAY BE an LCU is based on one and only one TABLE OF EQUIPMENT
MAY BE an LCU is under one and only one HEADQUARTERS
MAY BE an LCU uses one or more DEVICES
LEADER
Description
User-defined or historical individuals that influence combat formations, whether through their formation's abilities in combat or logistics.
Up to 19,999 individual leaders (total of both sides) may be created.
Each Occurrence Of This Entity :
MAY BE a Leader commands one and only one AIR GROUP
MAY BE a Leader commands one and only one HEADQUARTERS
MAY BE a Leader commands one and only one LAND COMBAT UNIT
MAY BE a Leader commands one and only one SHIP
MAY BE a Leader commands one and only one TASK FORCE
MAY BE a Leader is one and only one PILOT
LOCATION
Description
A user-defined or historical location/base which will be displayed and moveable to on the WITP map.
Base/location slots are in the following range:
0217-0900
NOTE: Do not move any base/location to a different slot as some parts of the game program assume these bases are in their current slots.
Each Occurrence Of This Entity :
MAY BE a Location contains one or more AIR GROUPS
MAY BE a Location contains one or more LAND COMBAT UNITS
MAY BE a Location contains one or more SHIPS
MAY BE a Location uses one or more DEVICES
PILOT
Description
Special individuals that are generally better trained and have more experience than newer pilots. Up to 19,999 individual pilots (total of both sides) may be created.
Each Occurrence Of This Entity :
MAY BE a Pilot is assigned to one and only one AIR GROUP
MAY BE a Pilot may be one and only one LEADER
SHIP
Description
A user-defined or historical ship which saw service in the Pacific theatre during World War II. Certain ships MUST be left in their assigned slots as follows:
0001-2999 Japanese ships
3000-9999 Allied ships
Each Occurrence Of This Entity :
MAY BE a Ship belongs to one and only one SHIP CLASS
MAY BE a Ship can carry one or more AIR GROUPS
MAY BE a Ship can use one or more DEVICES
MAY BE a Ship has one and only one LEADER
MAY BE a Ship is at one and only one LOCATION
MAY BE a Ship is part of one and only one TASK FORCE
SHIP CLASS
Description
A ship class that was employed in the Pacific theatre of World War II. Certain ship classes MUST be left in their assigned slots as follows:
0001-0171 Japanese Ship Classes
0172-0499 Allied Ship Classes
0501-1199 Japanese Ship Classes
1200-1999 Allied Ship Classes
Each Occurrence Of This Entity :
MAY BE a Ship Class can use one or more DEVICES
MAY BE a Ship Class consists of one or more SHIPS
MAY BE a Ship Class upgrades from one and only one SHIP CLASS
MAY BE a Ship Class upgrades to one and only one SHIP CLASS
TABLE OF EQUIPMENT
Description
A user-defined or historical Table of Equipment layout for units which served in the Pacific theatre during World War II.
Table of Equipments must be located in the following slots:
0901-0977 Japanese TO&Es
2001-2119 Allies TO&Es
Each Occurrence Of This Entity :
MAY BE a TOE can use one or more DEVICES
MAY BE a TOE is the basis for one or more HEADQUARTERS
MAY BE a TOE is the basis for one or more LAND COMBAT UNITS
TASK FORCE
Description
A user-defined or historical task force organization which served in the Pacific theatre during World War II.
Task forces must be in the following range:
3500-3899 Japanese task forces
3900-3999 Allied task forces
Each Occurrence Of This Entity :
MAY BE a TF consists of one or more SHIPS
MAY BE a TF has one and only one LEADER
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
-
michaelm75au
- Posts: 12463
- Joined: Sat May 05, 2001 8:00 am
- Location: Melbourne, Australia
RE: WITP Entity Relationship Diagram
Derek
is this based on latest version (1.6) or an earlier version?
As of version 1.4, Japanese carrier capable plane range was changed to 1-25.
Michael
is this based on latest version (1.6) or an earlier version?
As of version 1.4, Japanese carrier capable plane range was changed to 1-25.
Michael
Michael
-
el cid again
- Posts: 16984
- Joined: Mon Oct 10, 2005 4:40 pm
RE: WITP Entity Relationship Diagram
As of version 1.4, Japanese carrier capable plane range was changed to 1-25.
Apparently it is really 1-23. I just did a comprehensive review - and I found only aircraft in those slots came up carrier capable.
RE: WITP Entity Relationship Diagram
I used the manual out of my 1.6 (1.795 patch) directory.
The manual had different slots than what you mentioned so the manual I based my "assumptions" on seems to already be wrong. Which is one reason why I posted on the forum so things like this can be caught.
The manual had different slots than what you mentioned so the manual I based my "assumptions" on seems to already be wrong. Which is one reason why I posted on the forum so things like this can be caught.
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
Updated ER Diagram and Entity Document
I have an updated Entity Relationship diagram and Entity Document available in PDF for anybody interested. PM or if you already have my email just email me directly if you wish the documents.
I still have to figure out all the individual domains used by the entities and then the descriptions for the domains so much more work is still to be done.
I still have to figure out all the individual domains used by the entities and then the descriptions for the domains so much more work is still to be done.
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
-
Pascal_slith
- Posts: 1657
- Joined: Wed Aug 20, 2003 2:39 am
- Location: In Arizona now!
RE: Updated ER Diagram and Entity Document
How about putting it up on Spooky's and Rogue's website?
So much WitP and so little time to play.... 
RE: Updated ER Diagram and Entity Document
ORIGINAL: Pascal
How about putting it up on Spooky's and Rogue's website?
Be happy to. Just have them PM me where to email the PDF files. May not be responding to any emails until tomorrow though if they contact me tonight - think I'm coming down with something and I'm going to crawl under an electric blanket and rest.
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
-
michaelm75au
- Posts: 12463
- Joined: Sat May 05, 2001 8:00 am
- Location: Melbourne, Australia
RE: WITP Entity Relationship Diagram
I just tried it myself and it seems that the upper limit is 24, rather than 25.
Michael
Michael
ORIGINAL: el cid again
As of version 1.4, Japanese carrier capable plane range was changed to 1-25.
Apparently it is really 1-23. I just did a comprehensive review - and I found only aircraft in those slots came up carrier capable.
Michael
-
michaelm75au
- Posts: 12463
- Joined: Sat May 05, 2001 8:00 am
- Location: Melbourne, Australia
RE: WITP Entity Relationship Diagram
The manual has not changed since initial release.[;)]
So there may be some extra information gained by checking the release notes.
Michael
So there may be some extra information gained by checking the release notes.
Michael
ORIGINAL: dereck
I used the manual out of my 1.6 (1.795 patch) directory.
The manual had different slots than what you mentioned so the manual I based my "assumptions" on seems to already be wrong. Which is one reason why I posted on the forum so things like this can be caught.
Michael
RE: WITP Entity Relationship Diagram
ORIGINAL: michaelm
The manual has not changed since initial release.[;)]
So there may be some extra information gained by checking the release notes.
Michael
ORIGINAL: dereck
I used the manual out of my 1.6 (1.795 patch) directory.
The manual had different slots than what you mentioned so the manual I based my "assumptions" on seems to already be wrong. Which is one reason why I posted on the forum so things like this can be caught.
IIRC they did add some more carrier capable slots in one of the patches due to popular demand.
RE: Updated ER Diagram and Entity Document
ORIGINAL: Pascal
How about putting it up on Spooky's and Rogue's website?
Bump.
I still have those new documents. Working off and on on getting a list of individual domains (fields) that are used and will post that too.
Neither individual above has contacted me about them so I guess they won't be being posted [:(]
Still available direct from me though.
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
RE: Updated ER Diagram and Entity Document
ORIGINAL: dereck
ORIGINAL: Pascal
How about putting it up on Spooky's and Rogue's website?
Bump.
I still have those new documents. Working off and on on getting a list of individual domains (fields) that are used and will post that too.
Neither individual above has contacted me about them so I guess they won't be being posted [:(]
Still available direct from me though.
You seem to forget that I also offered to post them...
RE: Updated ER Diagram and Entity Document
The files I currently have available have been sent to AlaskanWarrior and he's going to post them on his website for anybody to download.
I'm working on a newer version (with better descriptive names for fields, etc) and a domain dictionary which lists each individual field and a description. It's still a work in progress.
This is an iterative process and I'm sure I don't have things 100% correct so if you see a glaring error please mention it. If you have any questions bring them up.
I've only been working on entities (tables) and domains (fields) but with the tool I'm using (Oracle Designer) I believe I could also map business rules which could maybe emulate what actions happen when modifying data I believe. Not sure if that would help understand the WITP database process better or not to be honest.
I'm working on a newer version (with better descriptive names for fields, etc) and a domain dictionary which lists each individual field and a description. It's still a work in progress.
This is an iterative process and I'm sure I don't have things 100% correct so if you see a glaring error please mention it. If you have any questions bring them up.
I've only been working on entities (tables) and domains (fields) but with the tool I'm using (Oracle Designer) I believe I could also map business rules which could maybe emulate what actions happen when modifying data I believe. Not sure if that would help understand the WITP database process better or not to be honest.
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
New Updated Documents
I have new updated documents which I've emailed to AlaskanWarrior (so they should be posted hopefully in a few days when he has time). They are also available from me by request as usual.
The new files are:
1 - Entity Definitions (48 pages)
2 - WITP Entity Relationship Diagram (15 pages)
3 - WITP Domains (101 pages ) <-- this replaces the Word document previously posted or sent out
What still needs to be done:
1 - determine the optional/mandatory entity relationships
2 - determine primary/foreign keys
3 - determine actual attributes of domains
4 - determine what other entities and/or domains were overlooked and need to be included
The new files are:
1 - Entity Definitions (48 pages)
2 - WITP Entity Relationship Diagram (15 pages)
3 - WITP Domains (101 pages ) <-- this replaces the Word document previously posted or sent out
What still needs to be done:
1 - determine the optional/mandatory entity relationships
2 - determine primary/foreign keys
3 - determine actual attributes of domains
4 - determine what other entities and/or domains were overlooked and need to be included
PO2 US Navy (1980-1986);
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
USS Midway CV-41 (1981-1984)
Whidbey Island, WA (1984-1986)
Naval Reserve (1986-1992)
-
Mike Solli
- Posts: 16367
- Joined: Wed Oct 18, 2000 8:00 am
- Location: the flight deck of the Zuikaku
RE: WITP Entity Relationship Diagram
ORIGINAL: dereck
This is only round #1 ... more revisions expected.
LOL, looks like the kind of thing my boss puts out weekly.
Created by the amazing Dixie