【正文】 Table of FiguresFCS Embedded Training (FCSET) Modeling HandbookRelease/Revision:Release/Revision Date:2022/9/14Prepared by: 190。190。190。190。190。190。190。190。190。190。190。190。 190。190。190。190。190。190。190。190。190。190。190。190。 190。190。190。190。190。190。190。190。190。190。190。190。 Jim CollinsPaul Urban Stephen DiCamilloILogix Professional ServicesILogix Professional ServicesILogix Professional ServicesApproved By:190。190。190。190。190。190。190。190。190。190。190。190。 Peter HoffmannILogix Professional ServicesTable of Contents1 Introduction 1 Scope 1 Document Overview 12 Modeling Approach 3 Fundamentals 3 Service RequestBased System Modeling 3 Documentation of Internodal and Intranodal Communication 5 SystemofSystems Operational View Modeling Workflow 7 Building the FCSET Operational View Model 9 Static Modeling 10 Dynamic Modeling 11 Project Structure in Rhapsody 18 Operational View Package 18 Verification and Validation 24 Verification and Standards Compliance 24 Validation Against Requirements 243 Modeling Guidelines 28 General Guidelines and Drawing Conventions 28 Essential UML Diagrams 29 Use Case Diagram 29 Structure Diagram 31 Sequence Diagram 35 Activity Diagram 38 Statechart Diagram 41 Profiles and Customization 44 FCSET Profile 44 DoDAF Profile 454 Configuration Management 46 Strategy 46 Dependency on Model Structure 47 Rhapsody Model Elements 47 Rhapsody Project File 49 Mapping Project Structure to Archive 49 Protecting from Loss of Data 52 References 52 Release Guidelines 52 Labeling 52 Workflow 52 Versioning 555 Change Management 56 Strategy 56 Internal Change Management Workflow 56 External Change Management Workflow 57 Failure Incidents 57 Requirements Changes 586 Requirements Traceability 59 Strategy 59 Workflow 60 Requirements Identification in the Source Documents 61 Requirements Reorganization to Support the Project Structure 61 Importing Requirements into the Rhapsody Model 62 Linking Requirements to Model Elements in Rhapsody 63 Impact Analysis 63 Requirements Traceability Report Generation 64 Exporting the Rhapsody Model to DOORS 667 Model Documentation 68 DoDAF Report Generation 68 DoDAF Stereotypes: 68 Tags 69 Generating a DoDAF Report 70Appendix 1 Operational Node N2 Chart Derived From Scenarios 71Appendix 2 Operational Node Connectivity Description Tiers 76Appendix 3 Action Language 77 Basic syntax 77 Assignment and Arithmetic Operators 77 Printing 77 Comparison Operators 78 Conditional Statements 78 Incremental Looping Statements 79 Conditional Looping Statements 79 Invoking Operations 79 Generating Events 79 Referring to Event Parameters in Transitions 80 Testing the Port on which an Event Arrives 80 Testing the State of a State Machine 80Appendix 4 Best Practices for Working with Visual SourceSafe 81 Setting up VSS and Rhapsody to show version numbers in SCC 81 Tips with SourceSafe 81 Working with Rhapsody Project for the First time 82Appendix 5 Tips for Requirements Management and Traceability 84 Marking Requirements in DOORS 84 Setting up the Requirements Gateway Project 84 Exporting Requirements to DOORS 85Glossary 87References 88Attachment I: NonDisclosure Agreement 89Table of FiguresFig. 21 UML/SysML Composite Structure Diagram 3Fig. 22 Service RequestDriven Modeling Approach 4Fig. 23 Documentation of Node Input/Output by Means of an N2 Chart (DFD Notation) 5Fig. 24 Documentation of Inter/IntraNode Communication Using UML/SysML Notation 6Fig. 25 SoS Operational View Modeling Workflow 7Fig. 26 Transition from BlackBox View to WhiteBox View 8Fig. 27 Modified Operational View Modeling Workflow for FCSET 10Fig. 28 N11FcsCommonEtSubsystem Structure Diagram and portion of N2 Chart 11Fig. 29 Provided Scenario Synchronize Training Data Files 13Fig. 210 Integrated Scenario Synchronize Training Data Files 13Fig. 211 Populated Operational Nodes after Realization of Messages and Operations 14Fig. 212 Allocation of Messages to Interfaces (Port pN241 of N51AtiaM) 15Fig. 213 Protocol State Machine for N241FcsWebServices 15Fig. 214 Protocol State Machine for N1111UtManagementSystem 16Fig. 215 Protocol State Machine for N1111UtManagementSystem SynchronizeTrainingDataMode 17Fig. 216 TopLevel Project Structure 18Fig. 217 Operational View Package Structure 18Fig. 218 Use Cases Package Structure 19Fig. 219 Operational Nodes Package Structure 20Fig. 220 N1FcsBattleCommandSystem Node Deposition 21Fig. 221 N1111UtManagementSystem Node Deposition 21Fig. 222 Interfaces Package Structure 22Fig. 223 Contents of the TO_N241_Pkg Interface Package 23Fig. 224 Model Deployment using Components 24Fig. 225 Recording an Animation Script 25Fig. 226 Test Conductor Driver Scenario Synchronize Training Data Files 26Fig. 227 Graphical Test Engine (FCSET Targeting Console) 27Fig. 31 Use Case Diagram 30Fig. 32 Structure Diagram 33Fig. 33 Sequence Diagram 36Fig. 34 Activity Diagram 39Fig. 35 Statechart Diagram 42Fig. 41 Connection to Configuration Management Archive 47Fig. 42 Visual SourceSafe Archive Reflects Model Hierarchy 48Fig. 43 Rhapsody Model Structure 50Fig. 44 Windows Files Structure 50Fig. 45 CM Repository Structure 51Fig. 46 Including Descendants in Check Out Operation 51Fig. 47 Synchronize Operation 52Fig. 48 Configuration Items Dialog 53Fig. 49 Flow of Users Accessing the Same File 54Fig. 51 Internal Change Request Spreadsheet 56Fig. 52 External Change Request Spreadsheet 56Fig. 53 Internal Change Management Workflow 57Fig. 54 External Change Management Workflow 58Fig. 61 Requirements for the Operational View 59Fig. 62 Requirements Ma