THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
While components can depend on one another in the base applications set they should follow the established priority of dependencies. In the diagram below you see existing dependencies and the component dependency priority going from the top of the page down (in other words components higher on the page depend on components lower on the page). Whenever something could go in two or more components, or depends on things in two or more components, it should go in the highest level component so that the lower level components don't depend on something in the higher level ones.
| Digraph | ||
|---|---|---|
| ||
fontname="helvetica-bold" ;
node [shape=plaintext fontname="helvetica-bold" ];
subgraph cluster01 {
label="extended";
style=filled; color=cornsilk;
node [color=cornsilk fontcolor=firebrick];
bi
specialpurpose;
}
subgraph cluster02{
label="base applications"
style=filled; color=cornsilk;
node [color=cornsilk fontcolor=blue];
{rank=same; humanres; marketing;}
{rank=same; order;}
{rank=same; workeffort;}
{rank=same; accounting;manufacturing;}
{rank=same; party;}
{rank=same; product;}
{rank=same; content;}
}
subgraph cluster03{
label="framework";
style=filled; color=cornsilk;
node [color=cornsilk fontcolor=darkgreen];
"entity(ext)";
service;
webapp;
security;
common;
}
edge [color=black weight=1];
marketing->order;
marketing->product;
order->workeffort;
order->accounting;
order->party;
order->content;
order->product;
humanres->accounting;
humanres->party;
manufacturing->product;
workeffort->accounting;
workeffort->party;
workeffort->content;
workeffort->product;
workeffort->manufacturing;
accounting->party;
accounting->product;
product->party;
product->content;
"entity(ext)"->common;
service->common;
service->security;
webapp->common;
webapp->security;
edge [color=grey weight=1];
order->marketing;
party->marketing;
|
specialpurpose
...