Working on any government contracts requires us to classify and mark all information we generate. Currently this is done manually (as in encode the classification into the title for example) or have an attribute of the artifact track the classification and use scripting to ensure it displays the classification correctly.
At a product level this could be easily implemented such that all first class objects (eg DOORS Next artifacts/Test Plan/Test Suite/Test Case/Test Script/Test Step/Streams/Global Configs/ Projects and Components/ EWM work items/EWM source code items) could have an optional setting that would allow you to pick from a ranked list of short labels and long labels (eg (O) / Official, (O:S) / Official-Sensitive, (PROP) / Company - Proprietary etc.. ) and the application would automatically prepend the short label on all displays...
Example 1 DOORS Requirement -
123455 The system shall do XYZ
This requirement has a security classification of Official-Sensitive.
The user would select this marking and DOORS would display the requirement as
123455 (O:S) The system shall do XYZ
Example 2 ETM objects
12 My Testplan
This test plan has a security marking of Secret so ETM would display the title as
12 (S) My Testplan.
The test suite inside of the test plan
24 My Test suite
has a classification of Official
it would display as
24 (O) My Test suite
etc
The list should be managed at the JTS level where all apps can use the ONE managed list of security markings.
This would be a user managed list so it can be adjusted for any jurisdiction marking.. it can also be used for company markings
(NA)/Not Applicable
(UO)/UNOFFICIAL
(O)/OFFICIAL
(O:S)/OFFICIAL-SENSITIVE
(P)/ PROTECTED
(S) / SECRET
(PROP) / <Compnay Name> Proprietary
(SENS) / <Company Name> Proprietary Sensitive
This would be the first step
Follow on from this is calculation of roll up.. eg a module in doors inherits the highest marking..
56 Module Name
contains requirement 123455
and a requirement 124677 (O) the system shall also do ABC
therefore module would display as
56 (O:S) Module Name
as O:S is ranked higher then O in the list.
At the moment the best we can do is to do this non-realtime with scripting which is very slow and prone to error.
In Rhapsody SE this would also apply with all Sysml V2 elements have the ability to be marked and all diagrams containing objects with markings would inherity the highest marking of the object on it.
eg diagram 1 has three parts on it. (O) Part 1, (O:S) Part 2, (P) Part 3. By having these part on the diagram the diagram should have a marking in top center showing "PROTECTED" in red (although this formatting should be flexible to allow differences in marking rules to be applied.)
This idea is NOT asking for security enforcement.. just marking of the objects to allow us to comply with government regulations.
Would be nice if EWM work items were also accounted for.