CORE(R) 8 README.TXT file Topics addressed include: * Installation and Licensing * Migrating an Existing Project to a CORE 8 Schema * Sharing Data between CORE 7 & CORE 8 * Getting Started * CORE On-line Help and Documentation * Disaster Prevention/Recovery * Important Notes * Uninstalling CORE 8 * Reporting Problems/Making Product Suggestions If you have questions after reviewing this document, or if you encounter any problems while installing or using CORE, please contact Vitech Customer Support as instructed at the end of this document. Installation and Licensing ========================== For detailed installation and licensing instructions, please refer to the "CORE 8 Installation Guide". This document can be obtained from the Downloads section of our website at http://www.vitechcorp.com. Migrating an Existing Project to a CORE 8 Schema ================================================ The baseline CORE 8 schemas include revisions to the previous CORE 7 schemas - changes to classes, relations, and attributes. To migrate your project from CORE 7 to a CORE 8 schema, special steps are required. For detailed information on migration, please review the latest "CORE 8 Data Migration Guide" from the Documents section of our website and contact Customer Support for additional guidance and assistance. Of course, CORE 8 includes copies of the CORE 7 schema files, so you may choose to simply maintain your current schema. In this case, simply import your XML file into CORE 8, and CORE will automatically build the project using the appropriate CORE 7 schema. Note that not all diagrams (particularly some SysML diagrams) and capabilities are available when using older schemas, particularly CORE 6 schemas. Sharing Data between CORE 7 & CORE 8 ==================================== It is recommended that work on a single project be conducted either entirely in CORE 7 or entirely in CORE 8. However, there are many cases in which project responsibilities are distributed among multiple organizations with different licenses, and project work may need to continue during the transition from CORE 7 to CORE 8. To collaborate on a project using both versions, you need to be aware of the following restrictions: o When porting the project to CORE 8, continue using the CORE 7 schema. o CORE 7 and CORE 8 can use the same .XML file format. The format has been slightly refined and upgraded in CORE 7, but a service pack (SP9) for CORE 7 has been produced to ensure compatability. Ensure that this service pack is installed to enable the exchange of data between installations. o The best practice is to migrate users forward from CORE 7 to CORE 8, never backwards from CORE 8 to previous versions. If work on a project must be divided between CORE 7 and CORE 8, all relevant users and groups should originate in CORE 7 and be imported into 8. Getting Started =============== The installation program will create a new program group entry on the start menu with the title "CORE 8". It contains an icon labeled "Empty Repository". To run CORE with the default repository (EmptyRepository.c80), simply click on this menu item. Default Account Name and Password --------------------------------- CORE ships with one user account preconfigured - the Administrator account. To log in, use the account name "Administrator" and password "admin" (without quotes) when prompted at the login dialog. At that point, new users can be created and passwords may be changed via the User/Group Tool. Note: If you change the Administrator password for your local repository, be sure to save the repository. For security reasons, unlike all other account passwords, the Administrator password is never loaded from the disk-resident access control files (ACFs) for use at login. Therefore, the only way to store a new password for the Administrator account is to save the repository after changing the password. Maintaining an Empty Repository ------------------------------- A copy of the empty repository file (EmptyRepository.c80) should be maintained to allow each user to start with a new repository. The installer will mark the installed EmptyRepository.c80 file as read-only. Therefore, the first time you save your image, you will automatically save the image under a new name. Creating and Using Multiple Repositories ---------------------------------------- You can store multiple repositories on your system (e.g., to keep a version history of your system design) and run them simultaneously, if desired. You can create a new image by making a copy of an existing repository (.C80 file) under a new name (keeping the .C80 extension) or, from within CORE, by using the File>>Save Repository As... command. To start a repository other than the default repository, double-click on the .C80 file of your choice from within the Windows Explorer or a Windows directory window. For quicker access, you can create a shortcut for your image file on your desktop. You cannot launch CORE by clicking directly on CORE80.EXE. CORE On-line Help and Documentation =================================== The CORE user reference guide is accessible as an on-line reference available from within CORE.To access context sensitive help from a specific window, simply click in the window and press the F1 function key. If you prefer to navigate by volume, flip through the index, or simply perform an electronic search, the on-line help will meet your needs. Also available from the CORE 8 program group entry on the Start menu are shortcuts to documentation including: * What’s New * CORE Guided Tour * CORE Icon Reference Guide * COREsim User Guide * MBSE Primer * CORE System Definition Guide * CORE Architecture Definition Guide * COREscript Construct Reference * COREscript Expression Language Reference * CORE API Reference * CORE 8 Data Migration Guide * CORE on a WAN Adobe's Acrobat Reader is needed to view this documentation. You can download the latest version of Adobe Acrobat Reader free of charge at http://www.adobe.com. Disaster Prevention/Recovery ============================ CORE repositories (.C80 files) store your local CORE database and the state of the CORE application in a machine-readable binary format. While generally stable, binary files can become damaged or corrupted. Read this brief section to learn what you can do to avoid losing data and to recover from such mishaps if they occur. 1) When an error occurs, particularly when you are saving or launching an image, contact Vitech immediately. Do NOT attempt to save or launch the image a second time. If a non-fatal error occurs at any other time (when you are not launching or saving an image), the first command you should reach for is File>>Export.... 2) In the Confirm Save Repository dialog there are two checkboxes. We recommend that you keep both of these options enabled at all times. When you save your image, the Make Backup option copies the image as you last saved under the same name, but with a .BAK extension instead of the .C80 extension. The Export option simultaneously exports your database to an XML. This generates a human-readable ASCII file which is much less susceptible to corruption and much more recoverable. Even if your database grows so large that exporting your database becomes cumbersome, we recommend that you still export your database on a regular basis. 3) As you work in CORE, all changes made to projects in your local repository are logged to a recovery file. This file has the same name as the repository you loaded but with _RECOVER.LOG appended. In the event of a fatal error resulting in loss of data, you can recover all changes by importing the LOG file using the Tools>>Load Recovery Log... command. Note that for remote projects stored on a CORE Server, there is no recovery log maintained. All changes are immediately written to the server, so a crash on a client will not result in any loss of data. The administrator is responsible for regularly backing up the data on the server. Important Notes =============== Using RDT Files from CORE 2.0, CORE 3.0, and CORE 4.0 ----------------------------------------------------- Beginning with CORE 5.0, XML became the standard file format for exchanging CORE data. However, CORE 8 fully supports legacy RDT files from CORE 2.0 and later. There is an option in CORE that allows exporting the RDT file in 2.x, 3.x, and 4.x formats to enable interchange with previous versions of CORE. Working with Report Files From Previous Versions of CORE -------------------------------------------------------- CORE 8 can read and execute report scripts created in previous versions of CORE. However, report scripts written or modified in CORE 8 cannot be used in earlier versions of CORE. Uninstalling CORE 8 =================== To remove CORE 8 from your system, select Add/Remove Programs from the Windows control panel. Select CORE 8 from the list of applications available to uninstall and click the Add/Remove button. Follow the instructions provided by the installer to remove the application. Reporting Problems/Making Product Suggestions ============================================= If you should encounter a problem with the software (either an error, a deficiency, a feature that works in a manner other than you expected, or a problem with any associated documentation), please notify us via e-mail, phone, or fax as indicated below. Any information you can provide in your report regarding the hardware and software configuration of the host machine, the circumstances in which the problem occurred, conditions to reproduce the problem, and such test data as you can reasonably provide to assist Vitech in reproducing the problem would be greatly appreciated. We hope that you enjoy the new capabilities of CORE 8. All user observations and recommendations are valuable to us. Vitech Corporation 2270 Kraft Drive Suite 1600 Blacksburg, VA 24060 Phone: +1.540.951.3322 Fax: +1.540.951.8222 Email: support@vitechcorp.com Web: http://www.vitechcorp.com Online Community: http://community.vitechcorp.com Copyright (c) 2004-2011 Vitech Corporation. CORE(R) is a registered trademark of Vitech Corporation.