When working in BriefBuilder, you may have noticed that all objects have an ID. The same goes for all requirements.
See below for more explanation.
Object IDs are assigned to all individual objects in BriefBuilder (spaces, systems, segments etc.). They can be seen at the top of each detail view. See image below.
As said, these IDs are automatically generated. They cannot be changed and remain the same even when you make an adjustment to the object’s name or when you move it to a different position within the tree.
Each object ID consists of 2 or 3 letters and then a number, e.g. SP-1 for a space or SYS-3004 for a system.
The letters indicate what kind of object it is (in this example: a space or a system). The numbers have no particular semantic meaning. They are generated ‘on the fly’ when creating objects.
The lettering system is as follows:
|OPF||Folder in the Objectives & principles tree|
|GS||Group of spaces|
|SEF||Folder in the Systems & elements tree|
|PAF||Folder in the Processes & activities tree|
|DLF||Folder in the Deliverables tree|
|BOF||Folders in the Users tree|
|UAF||Folder in the User activities tree|
|UEF||Folder in the User equipment tree|
|SVF||Folders in the Services tree|
|PFF||Folder in Performance failures tree|
|QMF||Folder in the Quality measurements tree|
|STF||Folder in the Standards tree|
|RTF||Folder in the Requirement texts tree|
Just like the objects, all requirements in BriefBuilder automatically get an (unchangeable) ID. These IDs can be found in the last column of any requirement table.
The requirement ID consists of three letters (‘REQ’, for all languages) and a number. The numbers are created chronologically. So, your first ID will be REQ-1, your second REQ-2, and so on.