Guideline: Compilation Dependency in Implementation








var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_OKm3oN7UEdmjRZts2c4ZjQ", "{E1E0DDA3-914F-4CC1-9D0A-ED4B8E8BBA89}", "6.725844217842153E-306"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_2ClPcDIcEdqDs_9ORT1Rig", "6.725844217842153E-306"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Guideline: Compilation Dependency in Implementation















This guideline introduces the concept of dependency between implementation artifacts.






Relationships



Related Elements


Implementation Element






Main Description



Explanation An important use of a dependency relationship is to represent compilation dependencies. A compilation dependency exists from one element to the elements that are needed to compile it. In C++, for example, the compilation dependencies are indicated with #include statements. In Ada, compilation dependencies are indicated by the with clause. In Java the compilation dependency is indicated by the import statement. In general there should be no cyclical compilation dependencies. Example 1: The following component diagram illustrates compilation dependencies between source files. The Invoicing_UI file (the top), requires Invoice, which requires Order to compile. Figure 1: Example Compilation Dependencies (Generic)





©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();