***This specification is not finished.*** TBD: add usecases for new queries. This specification provides usecases of Analysis View features of the XML Tools in NetBeans Enterprise Pack 5.5 Preview. This specification is based on XML Schema Analysis View specification derived by developers. This specification uses Purchase Order Schema from the IDE as a sample of XML schema. For testing needs any other XML schema may be used. Open Sample XML Schema to test Analysis View with. Run IDE. A JavaApplication project should be opened. In this case JavaApplication project named 'JavaApplication1' is opened. In the Projects window, expand the JavaApplication1 project node and select the Source Packages node. Right-click Source Packages node and choose New > File/Folder. In "New File" dialog in the Categories list, expand the XML node and select Sample Schemas. In the File Types list, select Purchase Order Schema and click Next. Type 'po' in File Name field, accept other defaults and click Finish. Result of step 2: "New File" dialog is opened. The Project drop-down list contains the name of the project JavaApplication1. Result of step 5: In the Projects window, the Source Packages node contains a subnode labeled po.xsd under <default package>, which is selected. The Source Editor contains a tab for the XML Schema file, po.xsd, which has three buttons: Schema - selected, Analysis, and Source. In the Source Editor of po schema click on Analysis button to switch to Analysis View. First column of Analysis View contains list of 3 items: Show usages of a primitive type, Find Substitution Groups, Show derivations of a Global Complex Type. Checking Analysis View Show usages of a primitive type feature Analysis View of Purchase Order Schema Sample should be opened. In Analysis View of po schema select Show usages of a primitive type item in the first column. The second column with tree of primitive types should appear. In the second column select a primitive type that is not used in PO schema, e.g. anyURI. Click Show Usages button under primitive types tree. In the third column graph with 1 node should appear: anyURI query node. In the second column select a primitive type that is used in PO schema, e.g. date. Click Show Usages button under primitive types tree. In the third column graph with query node; usage nodes; file node; and other nodes in the path from the usage node to its penultimate-level ancestor, which is a global component under the schema root should appear. 7 nodes: date query node, orderDate and shipDate usage nodes, item, Items, PurchaseOrderType nodes, po.xsd file node. Usage nodes should have generalization links to the query node. orderDate and shipDate usage nodes should have generalization links to date query node. Nodes in the path from the usage node to its penultimate-level ancestor should have composition links to their ancestor. Pair of nodes orderDate-PurchaseOrderType, shipDate-item, item-Items should have composition link. Nodes that are penultimate-level ancestors should have composition links to file node. PurchaseOrderType and Items nodes should have composition link to po.xsd file node. File node should have file link to the query node. po.xsd file node should have file link to date query node. In the second column double-click a primitive type node. In the third column appropriate graph should appear. Checking Analysis View Find Substitution Groups feature Analysis View of Purchase Order Schema Sample should be opened. Switch to Source View of the po schema. Add the following global element: "<xsd:element name="cmntSubst" substitutionGroup="comment" type="xsd:string"/>". Switch to Analysis View of the po schema. Adding cmntSubst global element should not broke schema. In Analysis View of po schema select Find Substitution Groups item in the first column. Click Find Substitution Groups button in the second column. Result of step 1: in the second column Find Substitution Groups button should appear Result of step 2: in the third column graph with head node and all its substitutions linked by generalization edge should appear. 2 nodes should appear: comment, cmntSubs. cmntSubs node should have generalization link to comment node Checking Analysis View Show derivations of a Global Complex Type query feature Analysis View of Purchase Order Schema Sample should be opened. Switch to Source View of the po schema. Add restriction of USAddress type: "<xsd:complexType name="CAdress"> <xsd:complexContent> <xsd:restriction base="USAddress"> <xsd:sequence> <xsd:element name="name" type="xsd:string"/> <xsd:element name="street" type="xsd:string"/> <xsd:element name="city" type="xsd:string"/> <xsd:element name="state" type="xsd:string" fixed="CA"/> <xsd:element name="zip" type="xsd:decimal"/> </xsd:sequence> <xsd:attribute name="country" type="xsd:NMTOKEN" fixed="US"/> </xsd:restriction> </xsd:complexContent> </xsd:complexType>". Adding CAdress global complex type should not broke schema. Switch to Source View of the po schema. Add extension of USAdress type: "<xsd:complexType name="ToAddress"> <xsd:complexContent> <xsd:extension base="USAddress"> <xsd:sequence> <xsd:element name="firstName" type="xsd:string"/> <xsd:element name="lastName" type="xsd:string"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType>". Switch to Analysis View of the po schema. Adding ToAddress global complex type should not broke schema. In Analysis View of po schema select Show derivations of a Global Complex Type item in the first column. In the second column Complex Types tree and Show Derivations button should appear In the second column select complex type node, that has no derivations, e.g. Items. Click Show Derivations button in the second column. In the third column graph with 1 node should appear: Items node. In the second column select complex type node, that has derivations, e.g. USAddress. Click Show Derivations button in the second column. In the third column graph with base complex type node and its derivations nodes, linked by generalization edge, should appear. CAddress and ToAddress nodes should have generalization links to USAddress base complex type node. In the second column double-click a complex type node. In the third column appropriate graph should appear. Checking Find Usages Query from Schema View feature Analysis View of Purchase Order Schema Sample should be opened. Switch to Schema View. In the first column all element, complex type, simple type, group, attribute, attribute group nodes should have enabled Show Usages popup menu item. In the first column under Complex Types node of components tree right-click Item subnode and select Show Usages. XML Usages window should appear. This window is a split pane: on the left side, an explorer (contains path to the usage component), on the right, a graph. In the graph pane a graph with 4 nodes should appear: Items, items, PurchaseOrderType, po.xsd nodes. items node should have generalization link to Items node. items node should have composition link to PurchaseOrderType node. PurchaseOrderType node should have composition link po.xsd file node. po.xsd file node should have file link to Items query component node. In the first column under Elements node of components tree right-click comment subnode and select Show Usages. XML Usages window should appear. This window is a split pane: on the left side, an explorer (contains path to the usage component), on the right, a graph. In the graph pane a graph with 7 nodes should appear: comment, 2 References "comment" nodes, Items, items, PurchaseOrderType, po.xsd nodes. 2 References "comment" nodes should have reference link to comment node. One of References "comment" nodes should have composition link to PurchaseOrderType node. The second References "comment" node should have composition link to item node. item node should have composition link to Items node. PurchaseOrderType, Items nodes should have composition link to po.xsd file node. po.xsd file node should have file link to comment query component node. In the first column under Simple Types node of components tree right-click SKU subnode and select Show Usages. XML Usages window should appear. This window is a split pane: on the left side, an explorer (contains path to the usage component), on the right, a graph. In the graph pane a graph with 5 nodes should appear: SKU, partNum, Items, items, po.xsd. partNum node should have generalization link to SKU node. Pair of nodes partNum-items, items-Items node should have composition links. Items node should have composition link to po.xsd file node. po.xsd file node should have file link to SKU query component node.