|
<< Click to Display Table of Contents >> Introducing Cimera |
  
|
|
<< Click to Display Table of Contents >> Introducing Cimera |
|
The basic Cimera structure is:
For example:
The Jargon
There is, predictably, a bit of jargon that needs to be explained up front. The glossary gives full details, but for starters, the following terms need to be understood
Item
An Item is simply another name for a thing.
A server, a person, a bit of software and a meeting room are all examples of things.
| Item Type |
An Item Type specifies what kind of thing an item is.
| For example | 'Dave' is an Item which has an Item Type of 'Person' |
| 'PR-12345' is an Item which has an Item Type of 'Problem'. |
An Attribute is a quality or a characteristic of an Item.
An Item Type specifies which Attributes every Item of that Item Type will have.
For example:
Item Type |
Person |
Problem |
Meeting Room |
||
Attributes |
Name DOB Address Phone Number Gender |
Unique Reference Id Description Who raised it Where found When found Priority How to recreate |
Name Location Maximum capacity Is there a projector? Phone number |
Two Items can be linked together by defining a relationship between their Item Types
For example:
| Create: |
| • | a hosts relationship between Item Types Environment and Server |
| • | a fixes relationship between Item Types Product Release and Problem |
| • | a has risk relationship between Item Types Project and Risk |
| UAT Environment | hosts Server 123 |
| MyProduct version 2 | fixes Problem 456 |
| Project ABC | has risk Risk 789 |
A Bucket is a logical collection of Item Types, and consequentially Items.
As well as providing a visual grouping of Item Types in the Item Explorer, Buckets allow security rules to be defined on a group of Items.
See Also