Search NASASearch

NASA NTRS · 20220018370

Expressing Functionality Using Design Patterns, A Real-World Example

Abstract

Digital Engineering is a transformative strategy that leverages an integrated model-based approach to improve communication, decision making, design understanding, and acquisition efficiency of system development. As modern systems are derived from pre-existing systems, harvesting tacit knowledge from existing systems in a useful, model-based way will reduce the experiential learning and cognition required for new system development, contributing to a Digital Engineering transformation. This study enables such a technique by demonstrating the use of architectural theory in expressing tacit knowledge from existing systems and presenting that knowledge according to the model-based view offered by the Functional Architecture of Systems methodology. By validating the functional information expressed by the design pattern, this work solidifies design patterns as a critical component of a technical architecture and proposes a functional architecture viewpoint for describing mined knowledge in a usable, model-based, way suitable for archival in a modern knowledge management system.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Samuel P. Russell, Benjamin Kruse, Robert Cloutier, Dinesh Verma. Expressing Functionality Using Design Patterns, A Real-World Example. https://ntrs.nasa.gov/citations/20220018370

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

NASA Engineering and Safety Center Lunar Rover Design Concepts Assessments

Mass is a significant risk to programs and projects as they transition from formulation to implementation, especially in larger human space systems where delivery mass or volume can be a constrained commodity. • Concepts developed without an adequate systems-engineering basis, including design and operations experience, may miss significant functionality and subsequent mass required for integration or operations. • Further uncertainty can be associated with not fully understanding design best practices and standards that drive mass, such as design for minimum risk or fault tolerance.1 • Finally, the appropriate systems engineering mass properties management rigor and technical discipline insight are required to set the mass baseline, including appropriate mass growth allowance (MGA) to ensure program success. Mass is a key quantity that should be constantly monitored by the systems engineer and the program/project management stakeholder to ensure mission compatibility throughout the project life cycle. In addition, mass is a key programmatic performance metric monitored by the NASA Chief Financial Officer for current and future program cost estimating. NASA Exploration Systems sought an assessment of reasonableness with respect to different potential rover concepts that balances mass needs and human-class cargo lander capabilities. Appropriate systems engineering mass properties management rigor and technical discipline insight were used, and are required to set the mass baseline, including appropriate MGA to ensure program success. Two independent Lunar rover concepts were evaluated, with a goal to understand concept credibility and the Lunar rover designs potential extensibility for Mars surface operations. A notional generic rover concept is shown in Figure 1.

Systems Engineering

MBSE for the Gateway Program

The Gateway Program and many of its module developers are using Magic Draw to coordinate functions, requirements, and interfaces between the various elements that make up the Gateway Platform. This also extends to the visiting vehicles (Human Lander System, Logistics Module, and Orion). The Propulsion and Power Element (PPE) is using Magic Draw to coordinate the design activities at NASA GRC (Glenn Research Center) and the contractor. This discussion will provide an overview of the MBSE (Model-Based Systems Engineering) efforts and how we are interfacing the various MBSE models into a single integrated model.

Systems Engineering

Using Board Games as Subject Matter for Developing Expertise in Model-Based Systems Engineering

As more organizations transition from traditional document-centric systems engineering to a model-based approach, many are challenged to train their staff in new languages, tools, and methodologies, and manage the expectations of stakeholders and their expected model outcomes. In particular, challenges associated with learning a new modeling language and developing skills in the 'art' of modeling present organizations with formidable obstacles to realizing this transition. This paper hypothesizes that systems engineers may more readily learn how to correctly model with SysML, and develop intuition about the art of modeling and using patterns, if their learning references a commonly and thoroughly-understood subject matter, such as a board game. This paper presents a case for the use of board games as subject matter for new modelers, demonstrates the concept with a sample model of Hasbro's popular board game, Monopoly, and discusses the limitations of this approach and potential adaptations that may broaden the applicability of the learned skills to projects.

Systems Engineering