Hello , please answer this question reading the pdf.

\begin{tabular}{l|l|l|l|l} What are sources of requirements cha nges on the JUSS scenario / your experiences? & What data would be impacted by the requirements changes addressed in question 1? & What models would be impacted by the requirements changes in question & What challenges would th e JSS program / your experiences need & Wigital behaviors wo uld be most important in addressing the challenges in question 4? \\ \hline \end{tabular} Program overview Welcome to the Joint Unmanned Surface Ship (JUSS) program. JRATS System of Systems JUSS is an element of the Joint Reconnaissance and Target System (JRATS) system of systems. Several systems are already fielded and operating in JRATS: the Army Firebird Unmanned Aerial Vehicle (FUAV), the Marine Corps Joint Unmanned Ground Vehicle (JUGV), and the Air Force's Joint Command and Control System (JCCS) in the Joint Command Center (JCC). At the JCC the Air Force's JCCS will share Joint Training and Maintenance System (JTAMS) information throughout JRATS, as depicted in the OV-1 below. JUSS System The Navy is developing the JUSS as an unmanned Intelligence, Surveillance and Reconnaissance (ISR) platform with direct-fire capability provided by a 57mm naval gun. The JUSS will be operated through the Joint Training and Maintenance System (JTAMS) Ground Station (GS) and exchange information through the Joint Command Center (JCC). Interface software modules developed and maintained as part of the JUSS program will be in stalled on the JTAMS GS, the Firebird Unmanned Aerial Vehicle (FUAV) and Marine Corps Joint Unmanned Ground Vehicle JUGV. This software will monitor critical intelligence, surveillance and reconnaissance (ISR) systems and report back to the JCC regarding friendly and enemy position location. The will use live targeting data from the JRATS system to give the operator the ability to switch ammunition types during operation. JUSS Program Engineering Environment JUSS uses numerous engineering models: physical, data, algorithm, and process based. These include mission models, operational models, requirements models, test models, architecture models, manufacturing models, etc. The current infrastructure allows manual data sharing through email and file sharing across a developmental network, accessible by laboratories, test units, development organizations and other program stakeholders. JUSS uses traditional documentation and configuration management approaches. These include digitized views of the program's Work Breakdown Structure, Bill of Materials, diagrams, risk records, test results and chart / graphs, but these digital records are stored in unconnected databases. The table below identifies some of the engineering models being used in the development of the JUSS. Table 1: Current Models Technical approach: The JUSS Program Office plans to create a digital engineering environment, establishing a system functional model and incorporating these existing digital tools and any future models into a single federated Authoritative Source of Truth for the program. This will allow continuous, automatic sharing of digital artifacts both within the Program and with organizations outside the Program Office. - Upgrade the JUSS Engineering Environment (JEE) to benefit from the Digital Engineering Environment as stated in the DOD DE Strategy. - Update the System Security Engineering/Program Protection Plan - Enable Air Force red teams to conduct cyber penetration testing. DE Implementation Plan Digital engineering implementation plan is an appendix to the JUSS Systems Engineering Plan (SEP). The Chief Engineer is responsible for the digital engineering activities the program will conduct as part of its systems engineering activities. The plan establishes the following methods, processes, and tools, categorized as stated in the DoDI 5000.88 Engineering of Defense Systems, 3.4. SEP and the SEP Outline Version 4.0 Appendix E. Modeling Methodologies The JUSS Program is establishing a digital engineering infrastructure and environment for rapid capability engineering and integration. A Model Based Systems Engineering (MBSE) approach will be used to create a formal System Model using the Systems Modeling Language (SysML). This model will allow the use of the Unified Architecture Framework (UAF) to generate model-based DoD Architecture Framework (DoDAF) views. This model will provide all stakeholders with the ability to view JUSS model elements, element relationship diagrams, activity diagrams, block definition diagrams, and use case diagrams. The JUSS plans to use a Modular Open System Approach (MOSA), similar to the USAFs SysML-based Weapon Open System Architecture (WOSA) reference architecture. This open approach will facilitate integration of existing capabilities and allow incorporation of future capabilities. The Office of the USD(R\&E)(OUSD(R\&E)) provides Mission Engineering and integration management guidance, standards, and infrastructure to govern and digitally facilitate integration and data sharing across all DoD and OSD Components and lifecycle phases. The PM will make the relevant JUSS digital models accessible to OSD, Joint Staff stakeholders, and interdependent programs, throughout the life of the program in order to support this data sharing paradigm. Digital engineering is an essential foundational element of Mission Engineering that allows for sustainment of mission threads (MTs) and architectures, integrated analytical capabilities, common mission representations, and an extensible set of tools. Configuration Control Baseline JUSS will migrate formal configuration control to the formal System Model. The system functional, allocated, and product baselines will be maintained as an integrated set of digital representations. The evolution of this configuration controlled digital baseline will allow a continuous end-to-end digital representation of the system throughout its life cycle. The owner of each model federated with the System Model is authorized to make changes and support others in the proper use of their model. Once model data is incorporated into a system baseline, the model owner may only make changes when authorized by the Configuration Control Board. The PM will assign the roles and responsibilities required to accomplish configuration management tasks. These tasks will include the naming, marking, and tagging needed to make the models discoverable, accessible, reusable, and trusted. Authoritative Data The JUSS Engineering Environment (JEE) uses the foundations of data, modeling, and software to create and maintain the digital enterprise. The System Model federates all the specialty models in the programs into a single digital Authoritative Source of Truth (ASoT). This federated ASoT will facilitate the use and reuse of information across functional areas and among stakeholders. Collaboration JUSS will establish infrastructure and environment for programs and projects to conduct reviews and audits, hold technical meetings, perform analysis, and collaboratively develop models. This collaboration environment will ensure internal and external stakeholders (e.g., OSD, Joint Staff, and interdependent programs) have the necessary access and availability of technical data and acquisition artifacts for both short-term decisions and long-term system life cycle management in the digital ecosystem. All stakeholders (systems engineers, discipline and domain engineers, program managers, and decision-makers) will work in this common environment. The JUSS program will share Digital Artifacts with the Open Model Based Engineering Environment (OpenMBEE) tool. Stakeholders use a web-based interface called View Editor to create and access Program documents. The View Editor interface allows easier sharing of model artifacts, and it allows direct commenting and even modification of model elements for users with the correct credentials. Technical reviews will take place in the DE environment using the online View Editor interface. This improves the visibility and collection of review feedback and facilitates its implementation. It establishes easy visibility into the ASoT source for the JUSS program and follows digital engineering practices for model management. The team encourages digital feedback during the review process through this webbased interface, but the model documents can be exported to PDF and spreadsheet forms if required. Model Use The program's existing modeling, simulation, and analysis tools are identified in Table 1. In order to improve engineering and system safety activities, the Chief Engineer will identify an owner for each model who will be responsible for connecting it with the JUSS System Model. The data and the model need to be planned and captured with appropriate metadata for model assurance and reuse purposes. A preliminary assessment of digital capability was conducted by an independent review team as follows: This assessment provides a snapshot of key behaviors related to the use of key elements such as digital twin, digital thread, digital artifacts, and authoritative source of truth. System Security Engineering / Program Protection Plan The JUSS PM delegates responsibility to members of the program staff with technical knowledge of cybersecurity to produce the Cybersecurity Strategy Annex of the Program Protection Plan. The cybersecurity annex will document how the system will operate in a cybercontested environment. For platform and weapon systems that require an ATO in accordance with DoDI 8510.01, the cybersecurity annex will document the following - A plan of action and milestones (POA\&M) to address known vulnerabilities. - Implementation of continuous monitoring of risk based on cyber threats, vulnerabilities, and mitigations. - Implementation of the Risk Management Framework (RMF) process within the program management office's acquisition and engineering processes for development, procurement, testing, and sustainment. - The need for operational cyber resilience and, if appropriate, the resulting monitoring, responding, and recovering of the system and mitigation of the vulnerabilities. - Air Force red teams will conduct cyber penetration testing at demonstration. The current challenges that exist for following file sharing cybersecurity best practices are as follows: - Files and information are currently distributed in isolated authoritative sources. - Digital Artifacts identified as Controlled Unclassified Information (CUI) to identify and share across service networks. Weapons The JUSS will incorporate several technological innovations in the coming years. The first effort will add direct control of software programmable munitions the Bofors MK 110 Mod 057mm gun. This weapon gives the JUSS superior capability against traditional threats such as anti-ship missiles, aircraft, ships and shore targets, including those with armor protection. Future plans include incorporation of a multi-role Naval Strike Missile. In order to meet rigorous design and system safety goals, the JUSS plans to use a Modular Open System Approach (MOSA), modeled on the USAFs SysML-based Weapon Open System Architecture (WOSA) reference architecture described below. Each new weapon uses MOSA to establish interfaces between weapon and platform software interfaces. These will be Native Digital Projects, using models for design and simulation, and transitioning to operational dashboards for C4ISR. Each system model will mirror physical components, generating data to be reused for simulated mission control training and exercises. Data feeds will be the only difference between simulation and operational software interfaces. JUSS is an element of the Joint Reconnaissance and Target System (JRATS) system of systems. We will be adopting digital engineering best practices in order to facilitate the safe and effective integration of new capabilities throughout the life cycle of the system. Acronym list \begin{tabular}{l|l|l|l|l} What are sources of requirements cha nges on the JUSS scenario / your experiences? & What data would be impacted by the requirements changes addressed in question 1? & What models would be impacted by the requirements changes in question & What challenges would th e JSS program / your experiences need & Wigital behaviors wo uld be most important in addressing the challenges in question 4? \\ \hline \end{tabular} Program overview Welcome to the Joint Unmanned Surface Ship (JUSS) program. JRATS System of Systems JUSS is an element of the Joint Reconnaissance and Target System (JRATS) system of systems. Several systems are already fielded and operating in JRATS: the Army Firebird Unmanned Aerial Vehicle (FUAV), the Marine Corps Joint Unmanned Ground Vehicle (JUGV), and the Air Force's Joint Command and Control System (JCCS) in the Joint Command Center (JCC). At the JCC the Air Force's JCCS will share Joint Training and Maintenance System (JTAMS) information throughout JRATS, as depicted in the OV-1 below. JUSS System The Navy is developing the JUSS as an unmanned Intelligence, Surveillance and Reconnaissance (ISR) platform with direct-fire capability provided by a 57mm naval gun. The JUSS will be operated through the Joint Training and Maintenance System (JTAMS) Ground Station (GS) and exchange information through the Joint Command Center (JCC). Interface software modules developed and maintained as part of the JUSS program will be in stalled on the JTAMS GS, the Firebird Unmanned Aerial Vehicle (FUAV) and Marine Corps Joint Unmanned Ground Vehicle JUGV. This software will monitor critical intelligence, surveillance and reconnaissance (ISR) systems and report back to the JCC regarding friendly and enemy position location. The will use live targeting data from the JRATS system to give the operator the ability to switch ammunition types during operation. JUSS Program Engineering Environment JUSS uses numerous engineering models: physical, data, algorithm, and process based. These include mission models, operational models, requirements models, test models, architecture models, manufacturing models, etc. The current infrastructure allows manual data sharing through email and file sharing across a developmental network, accessible by laboratories, test units, development organizations and other program stakeholders. JUSS uses traditional documentation and configuration management approaches. These include digitized views of the program's Work Breakdown Structure, Bill of Materials, diagrams, risk records, test results and chart / graphs, but these digital records are stored in unconnected databases. The table below identifies some of the engineering models being used in the development of the JUSS. Table 1: Current Models Technical approach: The JUSS Program Office plans to create a digital engineering environment, establishing a system functional model and incorporating these existing digital tools and any future models into a single federated Authoritative Source of Truth for the program. This will allow continuous, automatic sharing of digital artifacts both within the Program and with organizations outside the Program Office. - Upgrade the JUSS Engineering Environment (JEE) to benefit from the Digital Engineering Environment as stated in the DOD DE Strategy. - Update the System Security Engineering/Program Protection Plan - Enable Air Force red teams to conduct cyber penetration testing. DE Implementation Plan Digital engineering implementation plan is an appendix to the JUSS Systems Engineering Plan (SEP). The Chief Engineer is responsible for the digital engineering activities the program will conduct as part of its systems engineering activities. The plan establishes the following methods, processes, and tools, categorized as stated in the DoDI 5000.88 Engineering of Defense Systems, 3.4. SEP and the SEP Outline Version 4.0 Appendix E. Modeling Methodologies The JUSS Program is establishing a digital engineering infrastructure and environment for rapid capability engineering and integration. A Model Based Systems Engineering (MBSE) approach will be used to create a formal System Model using the Systems Modeling Language (SysML). This model will allow the use of the Unified Architecture Framework (UAF) to generate model-based DoD Architecture Framework (DoDAF) views. This model will provide all stakeholders with the ability to view JUSS model elements, element relationship diagrams, activity diagrams, block definition diagrams, and use case diagrams. The JUSS plans to use a Modular Open System Approach (MOSA), similar to the USAFs SysML-based Weapon Open System Architecture (WOSA) reference architecture. This open approach will facilitate integration of existing capabilities and allow incorporation of future capabilities. The Office of the USD(R\&E)(OUSD(R\&E)) provides Mission Engineering and integration management guidance, standards, and infrastructure to govern and digitally facilitate integration and data sharing across all DoD and OSD Components and lifecycle phases. The PM will make the relevant JUSS digital models accessible to OSD, Joint Staff stakeholders, and interdependent programs, throughout the life of the program in order to support this data sharing paradigm. Digital engineering is an essential foundational element of Mission Engineering that allows for sustainment of mission threads (MTs) and architectures, integrated analytical capabilities, common mission representations, and an extensible set of tools. Configuration Control Baseline JUSS will migrate formal configuration control to the formal System Model. The system functional, allocated, and product baselines will be maintained as an integrated set of digital representations. The evolution of this configuration controlled digital baseline will allow a continuous end-to-end digital representation of the system throughout its life cycle. The owner of each model federated with the System Model is authorized to make changes and support others in the proper use of their model. Once model data is incorporated into a system baseline, the model owner may only make changes when authorized by the Configuration Control Board. The PM will assign the roles and responsibilities required to accomplish configuration management tasks. These tasks will include the naming, marking, and tagging needed to make the models discoverable, accessible, reusable, and trusted. Authoritative Data The JUSS Engineering Environment (JEE) uses the foundations of data, modeling, and software to create and maintain the digital enterprise. The System Model federates all the specialty models in the programs into a single digital Authoritative Source of Truth (ASoT). This federated ASoT will facilitate the use and reuse of information across functional areas and among stakeholders. Collaboration JUSS will establish infrastructure and environment for programs and projects to conduct reviews and audits, hold technical meetings, perform analysis, and collaboratively develop models. This collaboration environment will ensure internal and external stakeholders (e.g., OSD, Joint Staff, and interdependent programs) have the necessary access and availability of technical data and acquisition artifacts for both short-term decisions and long-term system life cycle management in the digital ecosystem. All stakeholders (systems engineers, discipline and domain engineers, program managers, and decision-makers) will work in this common environment. The JUSS program will share Digital Artifacts with the Open Model Based Engineering Environment (OpenMBEE) tool. Stakeholders use a web-based interface called View Editor to create and access Program documents. The View Editor interface allows easier sharing of model artifacts, and it allows direct commenting and even modification of model elements for users with the correct credentials. Technical reviews will take place in the DE environment using the online View Editor interface. This improves the visibility and collection of review feedback and facilitates its implementation. It establishes easy visibility into the ASoT source for the JUSS program and follows digital engineering practices for model management. The team encourages digital feedback during the review process through this webbased interface, but the model documents can be exported to PDF and spreadsheet forms if required. Model Use The program's existing modeling, simulation, and analysis tools are identified in Table 1. In order to improve engineering and system safety activities, the Chief Engineer will identify an owner for each model who will be responsible for connecting it with the JUSS System Model. The data and the model need to be planned and captured with appropriate metadata for model assurance and reuse purposes. A preliminary assessment of digital capability was conducted by an independent review team as follows: This assessment provides a snapshot of key behaviors related to the use of key elements such as digital twin, digital thread, digital artifacts, and authoritative source of truth. System Security Engineering / Program Protection Plan The JUSS PM delegates responsibility to members of the program staff with technical knowledge of cybersecurity to produce the Cybersecurity Strategy Annex of the Program Protection Plan. The cybersecurity annex will document how the system will operate in a cybercontested environment. For platform and weapon systems that require an ATO in accordance with DoDI 8510.01, the cybersecurity annex will document the following - A plan of action and milestones (POA\&M) to address known vulnerabilities. - Implementation of continuous monitoring of risk based on cyber threats, vulnerabilities, and mitigations. - Implementation of the Risk Management Framework (RMF) process within the program management office's acquisition and engineering processes for development, procurement, testing, and sustainment. - The need for operational cyber resilience and, if appropriate, the resulting monitoring, responding, and recovering of the system and mitigation of the vulnerabilities. - Air Force red teams will conduct cyber penetration testing at demonstration. The current challenges that exist for following file sharing cybersecurity best practices are as follows: - Files and information are currently distributed in isolated authoritative sources. - Digital Artifacts identified as Controlled Unclassified Information (CUI) to identify and share across service networks. Weapons The JUSS will incorporate several technological innovations in the coming years. The first effort will add direct control of software programmable munitions the Bofors MK 110 Mod 057mm gun. This weapon gives the JUSS superior capability against traditional threats such as anti-ship missiles, aircraft, ships and shore targets, including those with armor protection. Future plans include incorporation of a multi-role Naval Strike Missile. In order to meet rigorous design and system safety goals, the JUSS plans to use a Modular Open System Approach (MOSA), modeled on the USAFs SysML-based Weapon Open System Architecture (WOSA) reference architecture described below. Each new weapon uses MOSA to establish interfaces between weapon and platform software interfaces. These will be Native Digital Projects, using models for design and simulation, and transitioning to operational dashboards for C4ISR. Each system model will mirror physical components, generating data to be reused for simulated mission control training and exercises. Data feeds will be the only difference between simulation and operational software interfaces. JUSS is an element of the Joint Reconnaissance and Target System (JRATS) system of systems. We will be adopting digital engineering best practices in order to facilitate the safe and effective integration of new capabilities throughout the life cycle of the system. Acronym list