【正文】 nagement and Traceability Workflow 60Fig. 63 The initial DOORS Project Set of Modules 61Fig. 64 The initial DOORS Project Set of Modules 61Fig. 65 The Requirements Imported into Rhapsody as Seen in the Gateway 62Fig. 66 Anchoring Requirements to Rhapsody Model Elements 63Fig. 67 Impact Analysis Using the Rhapsody Gateway 64Fig. 68 Traceability Analysis Using the Rhapsody Gateway 65Fig. 69 Traceability Analysis Using the Rhapsody Gateway 66Fig. 610 The DOORS Project Including Modules Exported from Rhapsody 67Fig. 71 Mapping UML Artifacts to DoDAF Architecture Products 68Fig. 72 Setting a DoDAF Stereotype 69Fig. 73 Setting DoDAF Project Tags 70Fig. A51 Setting the Requirement Attribute for DOORS Objects 84Fig. A52 The Rhapsody Requirements Gateway Project Configuration 85Fig. A53 Configuring the Rhapsody Model Export to DOORS 86 Error! No text of specified style in document.1 Introduction ScopeAs part of the System Design and Development (SDD) Phase of the Future Combat Systems program, the Future Combat Systems LSI has developed an architecture document that describes the Embedded Training Architecture for the Future Combat Systems (FCS)equipped portion of the Unit of Action (UA). This document describes the architecture development process for the FCS Training Architecture, the relationship to other FCS architectures, and the operational, systems, and technical views to support the FCS training concept. Embedded Training is expected to be a softwareintensive system that is distributed within the FCS System of Systems. It is important that the developed FCS bat systems and subsystems fully support this FCS Training Architecture.A critical area to examine is the correctness and pleteness of the architecture Operational View. To this end, General Dynamics Land Systems (GDLS) has contracted ILogix Professional Services (IPS) to capture and analyze the Embedded Training Architecture Operational View using an executable UML model. IPS will use ILogix Rhapsody Developer in C++ to create this model. In addition to ILogix Rhapsody, Telelogic Doors will be used for requirements management, and Microsoft Visual Source Safe will be used for configuration management.This Future Combat Systems – Embedded Training (FCSET) Modeling handbook provides guidance by summarizing the approach and best practices followed on this project. The initial release of this handbook contains the best practices that evolved over years of field experience on dozens of projects in the Military amp。 Aerospace, Transportation, Tele, Medical, Industrial Automation and Consumer Electronics industries. As this is a new project with several unique aspects, these best practices are expected to evolve as the project progresses. Consequently, this is a living document and will be updated periodically throughout the project. Document OverviewThis document is intended to apply to any group needing to acplish a task similar to the stated Scope. While IPS effort involved four colocated engineers, this handbook has been developed with scalability in mind to support larger distributed teams, although the guidance provided here may need extension under certain circumstances.As this document’s primary purpose is to convey knowledge to the reader, small illustrative examples are used extensively to provide clear and concise guidance.Note that this handbook is not a substitute for training, but plementary to it. In fact, this handbook assumes the reader has basic working knowledge of the UML, ILogix Rhapsody and it’s addon products, Telelogic DOORS, and Microsoft Visual SourceSafe.The remainder of this document is broken into several sections addressing the major ponents of the model development effort: Modeling Approach Modeling Guidelines Configuration Management Change Management Requirements Traceability Model DocumentationAlso provided are several appendices, including overviews of the FCSET Operational Node Interfaces, Operational Node Hierarchical Structure, a quick reference guide of the ILogix Rhapsody Action Language, a glossary, additional supporting best practices and tips, and a set of references.2 Modeling ApproachThis section describes a modeldriven approach to the specification of the SystemofSystems (SoS) architecture of the Future Combat Systems Embedded Training (FCSET) using the Department of Defense Architectural Framework (DoDAF).First, an introduction to the chosen approach is given. Then, a description of how the approach is implemented in the modeling process for FCSET is provided. Finally, the resulting Rhapsody project structure is outlined along with a discussion on how the project is verified and validated. Fundamentals Service RequestBased System ModelingThe service requestbased system modeling approach specifically supports the design of networkcentric architectures. Its main characteristics are that the internode and intranode munication is based on message exchanges (service requests) rather than on the definition of data/control flows. The approach is UML/SysMLbased and uses the UML notation of required and provided interfaces.In the approach, the system structure is described by means of UML/SysML posite structure diagrams, using blocks (SysML: Assemblies) as basic structure elements and ports as “named connection points”.Fig. 21 UML/SysML Composite Structure DiagramThere are two different kinds of ports (see Fig. 21). Delegation or relay ports forward requests to other ports. Behavioral ports are the parts of the block that actually implement the services.Each port can have provided and/or required interfaces. A provided interface (denoted by a lollipop symbol) specifies a set of messages received at that port from elements outside the current block. A required interface (denoted by a socket symbol) specifies a set of messages sent from that port to elements o