Schema Analysis of Jama Contour

Contour Data Schema

This document outlines the data type conventions and tables in the Contour database schema.Some information like column indexes and foreign keys are omitted.Data types may differ slightly depending on which database is being used.

Tips

1.1 Boolean Values

Boolean Values are always represented by a T for true and F for false.

1.2 RefID & Scope Columns

You will notice that several columns include a RefId and Scope column. For certain tables the records can be configured to correspond to the project, organization or system.

The scope field may have the following values:

  1. System
  2. Organization Level
  3. Project
  4. Document Group (Not currently used)
  5. Item (Not currently used)
  6. User (Not currently used)

When writing queries, keep the scope in mind as this will indicate which table to join the ID to obtain the information.For example,if a lookup type has a scope of 2 that means the lookup is used across the entire organization. If the lookup type has a scope of 3 it's unique to each project.

1.3 Naming Conventions

Tables with an underscore such as are link tables that join data together.

Generated by
SchemaSpy
Generated by SchemaSpy on Mon Jun 14 17:03 PDT 2010
Database Type: MySQL - 5.1.45-community

XML Representation
Insertion Order Deletion Order (for database loading/purging scripts)

73 Tables:

Table Children Parents Columns Rows Comments
aclobject 1 8 5
aclpermission 3 9 0 Security permissions
aclpermissionentry 11 13
attachment 4 2 13 33 File attachment information
baseline 2 1 11 2 Baselines
baseline_version 2 2 101 List of artifacts included in each baseline
changerequestassociation 4 10 0
distributiongroup 1 2 9 12 Email distribution groups for outbound email notification
distributiongroup_user 2 2 0 Users associated with distribution groups
document 15 21 80 351 Artifacts such as requirements, use cases etc
document_attachment 2 9 3 File attachments
document_docattach 2 8 0
document_document 5 12 26 Relationships between artifacts
document_tag 2 7 95 Tags
document_url 1 8 3
documentcustomfieldvalue 1 8 29
documentfield 2 18 70 Configuration table that
documentgroup 3 2 17 37 Primary groups table
documenttype 3 15 14 Indicates the type of artifact such as a requirement
documenttypefielddefinition 2 23 110 Configuration of the fields for each artifact
email 1 12 0
estimate 1 8 0 NO LONGER USED
eventactiontype 7 54
evententry 5 18 353 Event log - populates What's New
eventtype 9 10
filter 2 13 13 Filters
glossaryitem 1 8 0 NO LONGER USED
integrationcomponentmapping 1 2 19 0
integrationconnection 2 16 0
integrationdirectiontype 2 6 4
integrationfieldmapping 4 13 0
integrationtype 3 6 1
jamaauthprovider 15 1
jamacomment 2 9 14 Comments
jamaview 4 2 15 28
jobschedule 1 13 4
lookup 22 1 13 159
lookuptype 1 13 55
objecttype 9 17
organization 6 11 1 Organization - typically the company information
perspective 4 2 18 2
perspective_role 2 8 1
perspective_view 2 9 24
perspectiveconfig 2 11 1
perspectivetype 1 6 3
pluginentry 13 0
project 9 11 32 8 Project attributes
projectfield 1 11 27
projectrelease 3 1 12 14 Releases per project
projecttype 2 13 1
projecttypefield 2 22 9
propertyentry 10 40 Table that stored system properties used by Contour
relationshiptype 1 15 3
releasetype 1 11 8 Drop down list values specific to reases
report 3 3 21 16 Reports
report_criterion 1 2 0 Criteria for each report
report_reportformat 2 2 39
reportcriteria 1 9 19
reportformat 1 9 5
reporttype 1 6 3
role 3 10 19 Roles or user groups defined by administrators
signature 2 11 0
subscription 1 8 0
tag 1 8 29 Tags
testresult 2 10 0 Test results
user_job 2 8 0
user_organization 2 8 0
user_role 2 2 15 User assignments to roles by project
userbase 18 2 24 7 Users
version 3 2 10 185 Master versioning table that associates an item with its versions
view_itemtype 1 11 2
viewconfig 2 11 0
viewtype 1 6 8

Columns: 880   Rows: 2,106