CORE 7 to 8 Data Migration Guide

Transcription

1 CORE 7 t 8 Data Migratin Guide i

2 Cpyright 2011 Vitech Crpratin. All rights reserved. N part f this dcument may be reprduced in any frm, including, but nt limited t, phtcpying, translating int anther language, r strage in a data retrieval system, withut prir written cnsent f Vitech Crpratin. Restricted Rights Legend Use, duplicatin, r disclsure by the Gvernment is subject t restrictins as set frth in subparagraph (c) (1) (ii) f the Rights in Technical Data and Cmputer Sftware clause at DFARS Vitech Crpratin 2270 Kraft Drive, Suite 1600 Blacksburg, Virginia FAX: Custmer Supprt: supprt@vitechcrp.cm CORE is a registered trademark f Vitech Crpratin. Other prduct names mentined herein are used fr identificatin purpses nly, and may be trademarks f their respective cmpanies. Revisin Date: Octber 2011 ii

3 Table f Cntents Overview f schema changes in CORE Changes in bth the Base and DDAF schemas... 2 Changes in the DDAF schema nly... 2 Data Migratin Overview... 4 Step-by-Step Instructins fr Data Migratin... 4 Cmplete List f Schema Changes in v General Changes Included in All Schemas... 5 Systems Engineering Schema Changes... 5 DDAF 2.0 Schema Changes... 8 iii

4 THIS PAGE INTENTIONALLY BLANK iv

5 This guide describes the new schemas prvided with CORE 8 and details hw t migrate prjects using previus schema versins using a special purpse schema and an assciated script. Befre cnducting the migratin prcess n yur data it is imprtant that this guide be read in its entirety. The data migratin steps will change class names, relatinship names, and attribute ptins. Sme data will nt be migrated and will be utput t a lg file fr yu t migrate manually. The database migratin prcess must traverse the database several times t implement the transfrmatin rules. Thugh the migratin can be cmpleted n prjects that reside in a CORE Server, Vitech recmmends that prjects cmplete the migratin in a Lcal Repsitry and then imprt the resulting data file int the CORE Server. After reviewing this guide, cntact Vitech Custmer Supprt if yu need additinal assistance. Our Supprt Team is available Mnday-Friday 9am-6pm Eastern with extended hurs available upn appintment. supprt@vitechcrp.cm Phne: Overview f schema changes in CORE 8 CORE 8 will supprt schemas frm CORE 6 thrugh 8. Hwever, nly CORE 8 schemas will prvide full supprt f new views, diagrams and features. Users shuld assess their prject needs, their prject lifecycle, and the changes present in the v80 schemas t determine if, and when, t migrate their schemas. Prjects nearing a majr milestne r appraching cnclusin shuld strngly cnsider remaining with their current schema. Vitech recmmends that thers cnsider mving t the v80 schemas t take advantage f the latest imprvements in the MBSE language. Pages 5-9 f this dcument cntain a cmplete list f all schema changes. Fr the mst part, these changes reflect additins, rather than revisins r deletins. Hwever, there are sme schema changes that impact existing prject data. These changes are detailed belw. 1

6 Changes in bth the Base and DDAF schemas DcumentFrmat Issue Interfaces Risk Class Detail f Change Impact t Data Data will be utput t the cagecde attribute migratin lg and will nt be remved included in the data mdel. cntractnumber attribute remved severity attribute renamed t imprtance The jins t relatinship is limited t tw targets. likelihd attribute changed frm flat type t enumeratin type Data will be utput t the migratin lg and will nt be included in the data mdel. All existing data will be migrated frm the severity attribute field t the imprtance attribute field. Only mdels being migrated frm the v50 schema are affected. Interfaces that exceed this limitatin will nt be included in the data mdel. The data will be utput t the migratin lg fr manual migratin. The migratin script will prmpt the user t specify threshlds fr the enumeratin levels. Changes will be made t the data mdel. Changes will als be utput t the migratin lg fr cnfirmatin. Changes in the DDAF schema nly Capability Cmpnent Class Detail f Change Impact t Data bjective attribute Data frm the cllectin will be changed frm cllectin cnverted t text. type t text type threshld attribute changed frm cllectin type t text type timeframe attribute changed frm cllectin type t enumeratin type type attribute value Systems Architecture changed t System Architecture Data frm the cllectin will be cnverted t text. Due t the cmplexity f changing between these tw data types data will be utput t the migratin lg and will nt be included in the mdel. The end user will need t reference the migratin lg and determine hw t prceed. All existing data with Systems Architecture selected will be changed t System Architecture. 2

7 Dcument ExchangeCharacteristic Gal Guidance Item Requirement PerfrmanceCharacteristic ServiceSpecificatin Standard type attribute value Gals changed t Gal All elements f this class will be cnverted t Requirements. All elements f this class will be cnverted t Requirements with the type attribute set t Prgrammatic All elements f this class will be cnverted t Requirements All type attribute values changed t remve the leading numbers type attribute value Prgram changed t Prgrammatic All elements f this class will be cnverted t Requirements with the type attribute set t Perfrmance datatypes attribute changed t datatype wdsl attribute changed t wsdl All elements f this class will be cnverted t Requirements. All existing data with Gals selected will be changed t Gal. Data frm this class will be mved t the Requirements class. Data frm this class will be mved t the Requirements class and the type attribute will be set t Prgrammatic Data frm this class will be mved t the Requirements class. The leading number will be remved frm the type value. The actual type value will therwise remain the same. All existing data with Prgram selected will be changed t Prgrammatic. Data frm this class will be mved t the Requirements class and the type attribute will be set t Perfrmance. Only the attribute name is edited. The data in the field will remain the same. Only the attribute name is edited. The data in the field will remain the same. Data frm this class will be mved t the Requirements class. 3

8 Data Migratin Overview Migratin frm CORE 7 t CORE 8 is a tw-part prcess. The first part is t upgrade yur CORE sftware frm 7 t 8. (Refer t the CORE 8 Installatin Guide available n the dwnlads page f ur website fr detailed infrmatin regarding upgrading yur sftware and yur license.) The secnd part is t migrate prject data frm the v70 schema t the v80 schema. While Vitech recmmends that users update their sftware t CORE 8 as a sn as pssible, there is n requirement t migrate prject data immediately r at all. CORE 8 supprts bth the new v80 schema as well as the v70 and v60 schemas. Nte that if yu chse nt t upgrade yur schema that yu may nt be able t take full advantage f the views, diagrams and reprts in CORE 8. Step-by-Step Instructins fr Data Migratin All steps f the database migratin shuld be cmpleted by a team member with administratr permissins. 1. Exprt yur prject frm CORE 7 using the File>>Exprt cmmand. Select Prject Backup in XML frmat. 2. If yur prject includes custm schema extensins, exprt yur schema extensins separately using the File>>Exprt cmmand. Select Prject Schema in XML frmat. 3. Imprt yur prject int CORE 8 using the File>>Imprt cmmand. In the Imprt Wizard, select t imprt it int a new prject. (This will use the schema that was included with the exprt in step 1.) 4. Imprt the apprpriate schema migratin file int the prject yu created using the File>>Imprt cmmand. (Bth files referenced belw are lcated in the \Prgram Files\Vitech\CORE 8\Data\Extensins flder. a. Select BaseSchemav70Migratr if yu are using a Base schema (v60 r v70). b. Select DDAFv20Schemav70Migratr if yu are using a DDAF schema 5. Run the v70 t v80 Prject Migratr v1.0 script using the Tls>>Run Script cmmand. a. When prmpted, specify the threshlds fr transfrming the current prject risk likelihds frm flats t a Lw / Medium / High enumeratin. Befre prmpting the user, CORE traverses all risks in the prject t identify the upper likelihd assigned. CORE then suggests cutffs fr Lw and High likelihd (0.3 and 0.7 n a scale f 0.0 t 1.0; 3.0 and 7.0 n a scale f 0.0 t 10.0; r 30.0 and 70.0 fr any maximum likelihd higher than 10). In additin t transfrming the likelihd, the current numerical value is utput t the migratin lg file. b. The script checks fr any Interfaces jined t mre than tw Cmpnents. (This was pssible in a v50 schema befre the maximum targets limitatin was added in the v60 schema.) All Interfaces meeting this cnditin are utput t the migratin lg file. c. The script autmatically detects if the prject schema is a DDAF schema. If s, it cnverts the ExchangeCharacteristic, Gal, Guidance, PerfrmanceCharacteristic, and Standard elements t Requirements and deletes the riginal element. 6. At the cnclusin f the migratin script, CORE will pen the migratin lg file (which is autmatically saved in the \CORE 8\ Output\Temp flder.) Assess whether any items will need t be lgged pst migratin. In particular, Capability timeframes must be manually cnverted frm the v70 test t the v70 enumeratin. 7. Exprt the prject data. Nte that in rder t avid sme f the artifacts f the migratin, using the File>>Exprt cmmand and select Advanced Optins. Select the fllwing checkbxes a. Database and the Stred Views sub-ptin b. Flders c. Filter Definitins d. Hierarchy Definitins e. Srt Definitins 8. Create a new v80 prject (using the Base r DDAF v20 schema as apprpriate) 9. If yu have custm schema extensins, imprt yur schema file frm step 2 int the new prject 10. Imprt yur database frm Step 6 int the new prject. 4

9 a. Yu will receive a cnflict file listing all risks and their crrespnding numeric likelihds. This infrmatin can be retained r discarded as desired. 11. In rder t create a backup f yur pst-migratin prject, exprt yur v80 prject using the File>>Exprt cmmand. Select Prject Backup in XML frmat. 12. Enjy CORE 8! Cmplete List f Schema Changes in v80 Nte: With the release f CORE 8, supprt fr all v40 and v50 schemas has been sunset. General Changes Included in All Schemas (including Legacy Schemas) New classes Package (parallel class t Categry fr navigatin purpses) New relatin pairs packages / packaged by Class changes Element Added auditlg t supprt an autmatically maintained, human-readable textual representatin f changes made t an element. Added bitmap attribute t supprt bitmaps n icns Systems Engineering Schema Changes (als reflected in the DDAF 2.0 Schema) New classes Nexus (abstract superclass fr Issue and Cncern) ChangeRequestPackage Package (parallel class t Categry fr navigatin purpses) ServiceSpecificatin TestItem TestActivity New relatin pairs established by / establishes executed by / executes impacted by / impacts riginated by / riginates packages / packaged by relatinship changes Revised the extends relatinship t supprt unlimited targets. Ratinale: If ne develped use cases at t lw a level then ne wuld nrmally find cmmn functins. While we recmmend against this practice, we recgnize that this case may be pssible when migrating frm ther tls and appraches. Our strng recmmendatin is that the use case extensins be unique because the use cases cntexts tend t limit the alternatives; because ne wuld like t make these extensins be nn-verlapping, which makes the analysis mre tractable. Added a type attribute t the kind f relatinship Ratinale: Separate instancing frm inheritance. Class changes Element Added auditlg t supprt an autmatically maintained, human-readable textual representatin f changes made t an element. 5

10 Added bitmap attribute t supprt bitmaps n icns Cmpnent Added Cntract Line Item Number attribute Added pssible values t the type attribute Family f Systems Netwrk Service Sftware Item SW Element SWCI System Architecture System f Systems Added impacted by relatinship with target classes Issue and Risk CnnectingUnit Added impacted by relatinship with target classes Issue and Risk DecmpsableElement Added impacted by relatinship with target classes Issue and Risk Dcument Added Cntract Line Item Number attribute Added pssible values t the type attribute Agreement Drawing Gal Guidance Infrmatin Asset Prcurement Specificatin Risk Mitigatin Plan Service Level Specificatin Statement f Wrk Strategy Threat Added impacted by relatinship with target class classes Issue and Risk DcumentFrmat Remved cagecde attribute Ratinale: Cage Cde nly applies t DSS clearance activities and is nt required in the schema. Remved cntractnumber attribute Interface Added impacted by relatinship with target classes Issue and Risk Issue Aliased t Cncern Changed fill clr t tan Renamed severity attribute t imprtance (implemented n new Pint class) Added target class UseCase t generated by relatinship (implemented n new Pint class) Added impacts relatinship with the fllwing target classes (implemented n new Pint class) CnnectingUnit DecmpsableElement ImplementatinUnit Interface Organizatin PrgramElement Requirement 6

11 Resurce State/Mde UseCase VerificatinElement Organizatin Added generates relatinship with target class ChangeRequestPackage Added impacted by relatinship with target classes Issue and Risk Added riginates relatinship with target class ChangeRequestPackage PrgramElement Added impacted by relatinship with target classes Issue and Risk Added accmplished by relatinship with target class TestActivity Requirement Added pssible values t the type attribute Incentive Award Fee Criterin Prgrammatic Test Added establishes relatinship with target class TestActivity Added impacted by relatinship with target classes Issue and Risk Resurce Added impacted by relatinship with target classes Issue and Risk Risk Changed fill clr t red Changed likelihd attribute type frm flat t enumeratin Lw Medium High Added pssible values t the type attribute Safety Security Added riskeffectivedate attribute Added statusdescriptin attribute Added impacts relatinship with the fllwing target classes CnnectingUnit DecmpsableElement Dcument ImplementatinUnit Organizatin PrgramElement Requirement Resurce ServiceSpecificatin State/Mde VerificatinElement State/Mde Added impacted by relatinship with target classes Issue and Risk UseCase Added impacted by relatinship with target classes Issue and Risk VerificatinElement Added impacted by relatinship with target class Issue VerificatinRequirement Added executed by relatinship with target class TestActivity Facility changes Dcument Management Added ServiceSpecificatin 7

12 Systems Engineering Added ServiceSpecificatin Verificatin Facility Added DefinedTerm Added Prduct Added PrgramActivity Added PrgramElement Added Resurce Added Risk Added ServiceSpecificatin Added State/Mde Added TestActivity Added TestItem DDAF 2.0 Schema Changes Deleted classes (migratr transfrms all int Requirements) ExchangeCharacteristic Gal Guidance PerfrmanceCharacteristic Standard Ratinale fr all deletins: Standard as a class was deleted because it identifies a brad generalized requirement that must be made specific fr the system under design. Guidance as a class was deleted because it is an abstract representatin f a requirement, mre abstract than a standard. Usually, nn-vitech derived IDEF0 representatin; nrmally use the Cntrl input fr the inclusin f Guidance and ther requirement like input values. Gal as a class was deleted because it is a mre abstract representatin f a prgrammatic requirement affecting the lng range bjective f the Prgram/Architecture. Deleted relatin pairs gverned by / gverns guided by / guides Relatin changes allcated t Remved the perfrmed by alias fr alignment with the base schema Class changes Architecture Remved supprted by relatinship with target class Gal Capability Changed bjective attribute type frm cllectin t text Changed threshld attribute type frm cllectin t text Changed timeframe attribute type frm cllectin t enumeratin Added currentvalue attribute Added impacted by relatinship with target classes Issue and Risk Cmpnent Changed Systems Architecture pssible value t System Architecture fr type attribute Dcument Changed pssible value Gals t Gal fr the type attribute Item Changed pssible values fr media attribute t remve leading numbers PrgramElement Remved achieves relatinship with target class Gal Requirement Changed Prgram pssible value t Prgrammatic fr type attribute Added pssible values t the type attribute 8

13 Capability Gap Risk Added additinal target classes t the impacts relatinship Capability ServiceSpecificatin Renamed datatypes attribute t datatype Renamed wdsl attribute t wsdl 9

14 THIS PAGE INTENTIONALLY BLANK 10

15

16 Vitech Crpratin 2270 Kraft Drive, Suite 1600 Blacksburg, Virginia FAX: Custmer Supprt: