To view the Microsoft.Uml2 domain models, start “Quadrant” by clicking the Start button, choosing All Programs, Microsoft Codename “Oslo” SDK, Tools, and then double-clicking Quadrant. In “Quadrant”, browse the target Repository catalog.

1. Open the Repository database by selecting the View menu, choosing Explorer, and then Repository.

2. Expand the Catalog item and locate Microsoft.Uml2.

   Note:

   If you do not see Microsoft.Uml2 schema under the catalog, you can either completely re-install code name “Oslo” modeling technologies using OsloSetup.exe or use the following command on the command prompt in the installation directory (typically cd “c:\Program Files\Microsoft Oslo\1.0\bin”) to install the Microsoft.Uml2 model image (located in the %Program Files%\Microsoft Oslo\1.0\Sdk\Models\Microsoft.Uml2 directory) in the target repository using the following command: mx.exe install Microsoft.Uml212.mx /d:Repository /r:Repository.mx

3. Expand Microsoft.Uml2 and explore the extents.

4. Close the workpad.

1. Download the sample XMI file to a folder on your machine. For example, this procedure assumes: C:\OsloSamples\UML\XMI

2. Load UML model instances into repository, following these steps:

   • Start a console.
     
     
   • Change the directory to the “Oslo” modeling technologies location. For example: cd “c:\Program Files\Microsoft Oslo\1.0\bin”
     
     
   • Run the UML Loader to populate the repository from the XMI file.
     
     LoadUml.exe c:\OsloSamples\UML\XMI\HiringSystem.xmi /f:Applications/HiringSystemSample /d:Repository /t:Repository
     
     

This section explains how to examine the test data you have installed in the Microsoft.Uml2 domain in the “Oslo” repository.

1. Open “Quadrant”.

2. Open the “Oslo” repository database by opening the View menu and choosing Explorer and then Repository.

3. Select the Applications folder.

4. Refresh this folder by opening the View menu and selecting Refresh.

5. Expand Applications and select HiringSystemSample.

6. Scroll slowly through the items on the right until you find the UML package called Hiring System Root Package, select the small icon preceding the name, and drag it into an empty space in the workspace and drop it to create a new workpad for that package. Note that this package contains two other packages called Unknown Externals and HiringSystem. You can open these packages separately in the same manner.

7. In the Packages – Hiring System Root Package workpad you created, click the UML Package Properties text on the right of the title bar, and switch the view of the root package to Tree Master/Detail.

8. Still in the right-hand tree view pane of the Packages – Hiring System Root Package workpad you created, expand Packages(1), then Hiring System Root Package, then Packages_OwningPackage(2), then HiringSystem, then Classes (6), and finally select the Employee class. Notice that the class properties are shown in the right-hand pane of the Tree Master/Detail view.

9. You can continue to examine further to see all the related UML model elements. To close all the open workpads on the “Quadrant” workspace, select the Home menu and click Close All Workpads.

This procedure shows how to query the test data and view the result in “Quadrant”.

1. Create a new empty workpad by selecting New Workpad in the Home menu.

2. Type in a VB LINQ query in the empty text box (called the query bar). Most queries are reasonably long, so you might want to expand the workpad horizontally to see more of your query. Cut and paste the following query into the query bar to find all the UML packages that contain a name “Hiring”.

   from aPackage in Database.Microsoft_Uml2_Packages _
   select aPackage _
   where aPackage.Name.Contains("Hiring")

3. Execute the query by hitting Enter.

4. Reuse the query bar to exercise various filtering queries. Here are some sample queries for you to try; copy and paste these queries into the workpad query bar and hit Enter.

   Note:
   The query capability in “Quadrant” is still evolving and has very limited support in this release.

   • Select all packages that are root packages.
     
     
     from aPackage in Database.Microsoft_Uml2_Packages _
     Order By aPackage.Name ascending _
     where aPackage.OwningPackage Is Nothing _
     select aPackage

   • Show packages that contain 5 classes or more.
     
     
     from aPackage in Database.Microsoft_Uml2_Packages _
     Order By aPackage.Name descending _
     where aPackage.Classes.Count() > 1 _
     select aPackage

   • Show all classes that inherit from another class.
     
     
     from g in Database.Microsoft_Uml2_Generalizations _
     from c in Database.Microsoft_Uml2_Classes _
     from p in Database.Microsoft_Uml2_Packages _
     where g.SpecificClass.Id.Equals(c.Id) _
     Select g.SpecificClass

   • Show all classes that have other classes inheriting from it.
     
     
     from g in Database.Microsoft_Uml2_Generalizations _
     from c in Database.Microsoft_Uml2_Classes _
     from p in Database.Microsoft_Uml2_Packages _
     where g.SpecificClass.Id.Equals(c.Id) _
     Select g.GeneralClass

   • Show the number of classes that have more than 10 operations.
     
     
     Aggregate aClass In Database.Microsoft_Uml2_Classes _
     Where aClass.Operations.Count() > 10 _
     Into Count()

   • Show all the classes that have no operations.
     
     
     From c in Database.Microsoft_Uml2_Classes _
     Where not c.Operations.Any()