4.5.5 Object Diagram: Fig8: Object Diagram
In this project, the object diagram mainly consists of classes or frames login frame, db connection, register frame, set level search frame, element level search frame, user frame and server frame the flow of process is carried over all these frames or objects.
4.5.6 State chart Diagram: Fig9: …show more content…
4.5.7. Component Diagram: Fig10: Component Diagram
In his project, the component diagram is specifying the various components of the process. They are uploading the details to linked data sources, keyword query routing, and keyword search using multilevel relationship, compute routing plan and get results.
4.5.8 Deployment Diagram: Fig11: Deployment Diagram
In this, the different interfaces are shown the user interface, the node and the database and the interaction between them.
CHAPTER …show more content…
Every node n' € N' stands for a set of element level entities Nn' ≤ Ne' , i.e., there is mapping type : Ne |->N' that associates every element-level entity n < Ne with a set-level element n' € N'. Every edge e'(n' , Nj')€e' represents a relation between the two sets of element-level entities n' i and n' j. We have E'={e'(n'i,n'j)|e(ni,nj)€Er, type(ni)=n'i,type(nj)=n'j}.
This set-level graph essentially captures a part of the Linked Data schema on the web that are represented in RDFS, i.e., relations between classes. Often, a schema might be incomplete or simply does not exist for RDF data on the web. In such a case, a pseudo schema can be obtained by computing a structural summary such as a data guide [35]. A set-level data graph can be derived from a given schema or a generated pseudo schema. Thus, we assume a membership mapping type : Ne|->N' exists and use n < n' to denote that n belongs to the set n'.We consider the search space as a set of Linked Data sources, forming a web of