Laserfiche WebLink
<br />e <br /> <br />e <br /> <br />e <br />') <br /> <br />o 0'3 if5',~ <br /> <br />Figures 5, 6 and 7 represent the basic characteristics of the Data Centered <br />Architecture. Figure 5 shows that a Data Centered Architecture is centered <br />around a goo-relational database representing the river system, Around that <br />database a number of application programs are organized, These application <br />programs rely on the database for provision of river system related data, In <br />essence all programs which interact with the database can be considered <br />"applications" regardless their specific contents. Figure 6, then shows how <br />such applications interact with both the database and the user. The central <br />concept here is that of a Data Management Interface or "DMI". The DMI <br />forms the link between both the user and the database in that it "knows" how <br />an application needsto'interact witll' both the"user-and the'database, Every <br />application has its own DMl containing the idiosyncracies of the particular <br />application. <br /> <br />The DMI concept renders a Data Centered Approach very extensible in that <br />applications (models. analysis tools, etc,) can be added to the system through <br />the addition of a DMl for those applications, <br /> <br />Figure 7 shows the concept of an "AMI" or Application Management <br />Interface. An AMI serves a function similar to that of a DMI. but instead of <br />linking an application with both user and database, it links applications with <br />each other. Thus. and AMI is a piece of software which "knows" that <br />relationships between the various applications (for instance, through <br />examining their DMIs) and suppons users in building integrated problems <br />which involve more or other applications, <br /> <br />Data Centered <br />Systems: <br />DMls/AMl's <br /> <br />DAM~S& MOORE/CADSWES-34 <br />