In this section you will develop the ship design process further.
|
child of |
Singular obligatory |
|
child of |
Singular obligatory |
|
child of |
Singular obligatory |
|
child of |
Belongs to group of single optional Entities |
|
child of |
Belongs to group of single optional Entities |
How to include entities is described in the previous sections.The result so far should look like this:
A ship design always contains a layout with at least a hull and defined reference planes. The entities Decks
and Bulkheads
will be optional for a user to include in their ship design.
Hull
Hull
:
|
Singular obligatory |
|
Singular obligatory |
Reference planes
Reference planes
:
|
Singular obligatory |
|
Singular obligatory |
Decks
Entity Decks
will be developed as a container which contains combined data of all defined singular decks below.
Decks
:Deck |
Multiple, select none, one or more |
The entity Decks
can contain one or more Deck
entities, each with the same content (which will be added shortly), however, the user can provide different input values for each Deck
.
Bulkheads
This ship configurator uses another entity structure for defining (transverse) bulkheads than for defining decks. The same entity structure could be used, but it is more instructive to present (and develop) a different approach.
The development of the Bulkheads
entity is comparable to the Decks
entity. However, above we used a Multiple entity to enable the user to define one or more decks. Here we will develop an entity where the user can create one table to define one or more transverse bulkheads instead of several Bulkhead
entities.
Bulkheads
:Bulkheads |
Singular obligatory |
The complete Ship design
tree should now look like this:
Back to content | <<Previous | Next >>