![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL issues regarding classified and unclassified projects Topic Summary: Created On: 15-Jul-2003 20:16 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi Daniel,
The Partition and Rejoin feature of DOORS can assists with the management of a project that contains both classified and unclassified data. I'm not sure what the laws are in the USA, but I'm pretty sure that it's the same as here in Australia, if any electronic managed data contains classifid military data, it must reside on a secure network that is 100% physically isolated from unclassified networks such as a corporate LAN/WAN. If it's just corporate sensitive classified material, then the isolation is usually managed via access rights to corporate network resources set aside for such material. Partition and Rejoin will allow you to seperate unclassified material from the classified material and make this available on a DOORS database that resides on an unclassified part of the network. When setting up a Partition definition, this will allow you to select which modules (formal and link), which attributes and which views will be copied for export to another database. This will allow you to seperate classified and unclassified data. The useful side of the feature is that the exported material can be edited and merged back into the original database on a regular basis. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
I think Miller means this:
Set up an unclassified project on the unclassified server. "Partiton" the entire unclass project and "rejoin" it in the Classified project. I forget the name of the process, but you then "delete" the partition from the unclass project. Work can continue in the unclass (since there is no outstanding partition), but work cannot continue on the unclass partition in the classified project. When you are ready to updated the classified project, your "return" the partition and discard the output (or just "delete" the partition), then import the new (unclass) partition. And trust me on this one: its easier to become a Saint than it is to "declassify" DOORS archives. Any notion of moving the unclassified portion of the classified DOORS modules down to the unclassified project is NOT going to get approved. - Louie |
|
![]() |
|
![]() |
|
A slick (maybe pronounced sick) way to implement is using the partition/synchronization function in DOORS. With this you would NEVER EVER rejoin the partitions.
It is way too complicated to go into in a simple text e-mail forum, but I will try. You would create two empty databases on a unclassified network. Label one unclass, the other secret. In the one you labeled secret, create two projects, unclass and secret. Take a partition of the unclass project, taking all authority with the partition (this will leave a read-only partiton of the unclass project in the secret db). Import the unclass project into the unclass db (this will give you a project with "write" authority in the unclass db. Archive the empty secret database and take to the secret network. when you make changes to the unclass db, take up a synchronizaton file up to the classified network. again NEVER, NEVER REJOIN! because you will loose your partition of the secret db and will be in the unenviable position of having to partition secret data and convincing security that there is no classified data which you are carrying to the unclassifed network. Now the DOORS Architecture part. Create only a degenerate module on the classified network which only contains the classified "stuff" in it. Each time you create a new object in the classified section, create a object in the unclassifed project as a placeholder for the classified information in the classified network (can only be viewed after synchronization on the classifed network). Create a special link module which contain the links from the degenerate object to the placeholder object. Now in the unclass network, you do all your "bookkeeping", i.e. traceability, metrics, etc. when you go up to the classifed network, you can view the classified data in your specification. Now the ugly ![]() I know this is complicated to follow, but I believe I got all the pertinent information in there such that a really tenatious person could dig it out. Don |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.