Behavior models for software architecture

Monterey Phoenix (MP) is an approach to formal software system architecture specification based on behavior models. Architecture modeling focuses not only on the activities and interactions within the system, but also on the interactions between the system and its environment, providing an abstraction for interaction specification. The behavior of the system is defined as a set of events (event trace) with two basic relations: precedence and inclusion. The structure of possible event traces is specified using event grammars and other constraints organized into schemas. The separation of the interaction description from the components behavior is an essential MP feature. The schema framework is amenable to stepwise architecture refinement, reuse, composition, visualization, and multiple view extraction. The approach yields a basis for executable architecture specification supporting early testing and verification, systematic use case generation, and performance estimates with automated tools.Consortium for Robotics and Unmanned Systems Education and Research (CRUSER)Consortium for Robotics and Unmanned Systems Education and Research (CRUSER)Approved for public release; distribution is unlimited.Approved for public release; distribution is unlimited

Formalization and model checking of software architectural style

Formal analysis is required to check the behavior of the system before implementation of any safety critical system. As the complexity of software increases, the need for reasoning about correct behavior becomes more prominent. Algorithmic analysis of different programs is usually carried out in order to prove their properties of execution. Application of formal method is being considered necessary for modeling, verification, and development of any software or hardware systems. In the formal verification of behavioral model, an attempt has been made to formally describe a real-time system e.g., use of Automated Teller Machine (ATM) in Banks. In this thesis, formal models of ATM system are described using state-based languages such as, Z, B, and Alloy as well as event-based language such as, Monterey Phoenix. Model checking is being carried out by automated tools, viz. Z/EVES, Atelier B, and Alloy Analyzer for Z, B, and Alloy specifications respectively. Furthermore, a comparative analysis of different characteristics shown by varied formal approaches has been presented in this thesis. Software architecture plays an important role in the high level design of a system in terms of components, connectors, and configurations. The main building block of software architecture is an architectural style that provides domain specific design semantics. In the analysis of complex architectural style, an attempt has been made in our work to formalize one complex style e.g., C2 (component and connector) using formal specification language Alloy. For consistency checking of modeling notations, the model checker tool e.g., Alloy Analyzer is used. Alloy Analyzer automatically checks properties such as,compatibility between components and connectors, satisfiability of predicates over the architectural structure, and consistency of an architectural style. For modeling and verification of C2 architectural style, one case study on Cruise Control System has been considered. At the end of this study, performance evaluation of different SAT solvers associated with Alloy Analyzer has been performed in order to assess the quality

Formalizing and verifying software architectures

Master'sMASTER OF SCIENC

Analysis of Verification and Validation Techniques for Educational CubeSat Programs

Since their creation, CubeSats have become a valuable educational tool for university science and engineering programs. Unfortunately, while aerospace companies invest resources to develop verification and validation methodologies based on larger-scale aerospace projects, university programs tend to focus resources on spacecraft development. This paper looks at two different types of methodologies in an attempt to improve CubeSat reliability: generating software requirements and utilizing system and software architecture modeling. Both the Consortium Requirements Engineering (CoRE) method for software requirements and the Monterey Phoenix modeling language for architecture modeling were tested for usability in the context of PolySat, Cal Poly\u27s CubeSat research program. In the end, neither CoRE nor Monterey Phoenix provided the desired results for improving PolySat\u27s current development procedures. While a modified version of CoRE discussed in this paper does allow for basic software requirements to be generated, the resulting specification does not provide any more granularity than PolySat\u27s current institutional knowledge. Furthermore, while Monterey Phoenix is a good tool to introduce students to model-based systems engineering (MBSE) concepts, the resulting graphs generated for a PolySat specific project were high-level and did not find any issues previously discovered through trial and error methodologies. While neither method works for PolySat, the aforementioned results do provide benefits for university programs looking to begin developing CubeSats

-ilities Tradespace and Affordability Project – Phase 3

One of the key elements of the SERC’s research strategy is transforming the practice of systems engineering and associated management practices – “SE and Management Transformation (SEMT).” The Grand Challenge goal for SEMT is to transform the DoD community’s current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first, document-driven, point- solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise- oriented, hardware-software-human engineered, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046)

A REPEATABLE THREAT-BASED REQUIREMENTS GENERATION PROCESS LEVERAGING MODEL-BASED SYSTEMS ENGINEERING FOR JOINT EXPLOSIVE ORDNANCE DISPOSAL AND AN ANALYSIS OF RAPID LARGE AREA CLEARANCE

The mission of the Joint Explosive Ordnance Disposal (JEOD) program is to reduce or eliminate explosive hazards that jeopardize personnel, operations, installations, or materiel. The JEOD program develops equipment in support of this mission. The equipment development begins with identification of a threat. JEOD has a defined process for threat analysis and capability gap assessment but lacks a process for the generation of system requirements for the Joint Capabilities Integration and Development System (JCIDS). This thesis studied the shortcomings of the current JEOD requirements generation process and developed a new repeatable threat-based process based on a comprehensive review of systems engineering requirements processes. The new JEOD requirements process incorporates model-based systems engineering (MBSE) to analyze the threat and capability gaps and translate them into quantifiable requirements. The thesis applied this new process using MBSE tools and Monterey Phoenix behavior modeling to the JEOD mission of Rapid Large Area Clearance (RLAC) as a case study to identify common mission scenarios and stakeholder requirements that can be used to develop system requirements. The new process can be used for future JEOD requirements development to reduce the burden on JEOD technicians, shorten the requirements development timeline, and produce more comprehensive and accurate requirements. The new process is extensible to the broader DOD requirements generation community.Civilian, Department of the NavyApproved for public release. Distribution is unlimited

MODELING SYSTEM BEHAVIORAL OF INDIVIDUAL PROCEDURES AT THE TACTICAL LEVEL OF THE MARINE CORPS HUMAN RESOURCE DEVELOPMENT PROCESS—DO HRDP POLICY, PROCEDURES, AND IMS SUPPORT OR HINDER THEMSELVES?

In February 2021, the Marine Corps released its official guidance on the Human Resource Development Process (HRDP). The Marine Corps outlined the HRDP phases of Guidance, Planning, Production, Assignment, and Assessment as co-occurring and continuous operations. Each process within the phases produces vast amounts of qualitative and quantitative data for the Marine Corps. Using Monterey Phoenix to model both the HRDP and Information Management System (IMS) system behaviors supporting the HRDP, I evaluated the Marine Corps' IMS ability to support Talent Management 2030. First, processes designed in the industrial era and carried into the digital age should not persist. This study recommends IT IMS changes to deal with the legacy processes and methodologies from a bygone era. Secondly, this report provides a framework, tools, and examples to conduct process analysis across all administrative functions across the force, allowing Marine Corps leadership to capitalize on efficiencies already gained by Fleet Marine Forces.Captain, United States Marine CorpsApproved for public release. Distribution is unlimited

APPLICATIONS OF GRAPH THEORY FOR REUSE OF MODEL BASED SYSTEMS ENGINEERING DESIGN DATA

This dissertation contributes to systems engineering (SE) by introducing and demonstrating a novel graph-based design repository (GBDR) tool. GBDR enables engineers to leverage system design information from a heterogenous set of system models created using multiple model based systems engineering (MBSE) software tools as an integrated body of knowledge. Specifically, the research provides a set of approaches that allow the use of system models described in Systems Modeling Language and Lifecycle Modeling Language as an integrated body of design information. The coalesced body of system design information serves to support concept ideation and analysis within SE. The research accomplishes this by using a graph database to store system model information imported from digital artifacts created by MBSE tools and applying principles from graph theory and semantic web technologies to identify likely connections and equivalent concepts across system models, modeling languages, and metamodels. The research demonstrates that the presented tool can import, store, synthesize, search, display, distribute, and export information from multiple MBSE tools. As a practical demonstration, feasible subsystem design alternatives for a small unmanned aircraft system government reference architecture are identified from within a set of existing system models.OSD CAPECivilian, Office of the Secretary of DefenseApproved for public release. Distribution is unlimited

Consortium for Robotics and Unmanned Systems Education and Research (CRUSER) 2019 Annual Report

Prepared for: Dr. Brian Bingham, CRUSER DirectorThe Naval Postgraduate School (NPS) Consortium for Robotics and Unmanned Systems Education and Research (CRUSER) provides a collaborative environment and community of interest for the advancement of unmanned systems (UxS) education and research endeavors across the Navy (USN), Marine Corps (USMC) and Department of Defense (DoD). CRUSER is a Secretary of the Navy (SECNAV) initiative to build an inclusive community of interest on the application of unmanned systems (UxS) in military and naval operations. This 2019 annual report summarizes CRUSER activities in its eighth year of operations and highlights future plans.Deputy Undersecretary of the Navy PPOIOffice of Naval Research (ONR)Approved for public release; distribution is unlimited

Consortium for Robotics and Unmanned Systems Education and Research (CRUSER) 2019 Annual Report

Prepared for: Dr. Brian Bingham, CRUSER DirectorThe Naval Postgraduate School (NPS) Consortium for Robotics and Unmanned Systems Education and Research (CRUSER) provides a collaborative environment and community of interest for the advancement of unmanned systems (UxS) education and research endeavors across the Navy (USN), Marine Corps (USMC) and Department of Defense (DoD). CRUSER is a Secretary of the Navy (SECNAV) initiative to build an inclusive community of interest on the application of unmanned systems (UxS) in military and naval operations. This 2019 annual report summarizes CRUSER activities in its eighth year of operations and highlights future plans.Deputy Undersecretary of the Navy PPOIOffice of Naval Research (ONR)Approved for public release; distribution is unlimited