Reference Material

02F-SIW-080 JSF Modeling Info Mngmt Aug 02

ABSTRACT: This paper describes the Joint Strike Fighter Program’s ongoing effort to provide coherent modeling information to the JSF suite of models and simulations. It describes the architecture and progress to date in developing a JSF Authoritative Modeling Information Database (JAMID), which encompasses the JSF Distributed Product Description, Authoritative Systems Database, and other modeling information. Challenges in sharing system representations are described and the emerging JSF solution is explained, including its concept of operations, metadata approach, and translation strategy. Implications for the Simulation Based Acquisition concept are noted.

Engineering Complex Systems

by David W. Oliver, Timothy P. Kelliher and James G. Keegan, Jr.

Putting Systems To Work

by Derek K. Hitchins

DAU PROGRAM MANAGERS TOOL KIT

Twelfth Edition (Ver 1.0) December 2002

Information Modelling for System Specification Representation

Abstract -- This paper presents the emerging STEP standard AP-233 with focus on the non-functional requirements that have guided the development process. The purpose of the paper is to present and motivate the modelling assumptions and approach selected for the AP-233 information model, and to present how the EXPRESS information modelling language have been used. Although the paper is focused on AP-233 and the constraints imposed by the STEP framework it is believed the structures and requirements presented are general and applicable to other systems engineering information-modelling projects.

RISK MANAGEMENT GUIDE FOR DOD ACQUISITION

Fifth Edition June 2002

SYSTEMS ENGINEERING FUNDAMENTALS

January 2001 SUPPLEMENTARY TEXT PREPARED BY THE DEFENSE ACQUISITION UNIVERSITY PRESS FORT BELVOIR, VIRGINIA 22060-5565

ECSS–E–10A Space Engineering

System Engineering by ECSS Secretariat ESA–ESTEC Requirements & Standards Division Noordwijk, The Netherlands

INCOSE SYSTEMS ENGINEERING HANDBOOK

A “HOW TO” GUIDE For All Engineers

NASA Systems Engineering Handbook

SP-610S June 1995

ISO/IEC 15288 Life Cycle Management — System Life Cycle Processes

Date: 2000-01-21

Terminology work — Principles and methods

 

Systems Engineering Processes and Requirements

NASA PROCEDURES AND GUIDELINES This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library. Verify that this is the correct version before use: http://nodis.hq.nasa.gov/Library/Directives/NASA-WIDE/TBD

Using Objected - Oriented and UML Tools for Hardware Design: A Case Study

 

Reengineering Configuration Management for use in a Model Driven Design Environment

Abstract -- In the past, Configuration Management (CM) has managed documents that describe products and services organizations produce. The processes and the technologies used in traditional CM environments are typically labor intensive, slow and costly. In the new model driven design environment (MDDE), configuration management needs to be reengineered to provide the basic functionality of CM (i.e. identification, control, reportability and verification) as well as provide improved and better CM processes through the infusion of new information technologies. By extending existing technologies and stream-lining processes to take advantage of these technologies, it is possible for a reengineered CM process to provide JPL the speed, flexibility and ease of use that are required to meet the realities of shorter development cycles. This paper will discuss the current state of configuration management, what is needed to support a model driven design environment and propose a range of technology infusions that would begin with simple mechanisms and gradually introduce increasingly powerful technologies on appropriate parts of a project’s information and modeling data sets.

Developing a Distributed Data Dictionary Service

June 20, 2001 -- Abstract -- In an interconnected world, applications need to interconnect in much the same way that computers are connected today: i.e. through the use of well established standards-based technologies. Data dictionaries are the keys to these applications outlining the meaning and structure of the information contained within them. What is currently missing is an architecture and mechanisms that allows data dictionaries to be systematically linked to each other thus enabling connectivity between applications. This paper will explore the use of combining the Lightweight Directory Access Protocol (LDAP) and the ISO/IEC 11179 Data Element Set as mechanisms for standardizing the structure and communication links between data dictionaries.

Executable Object Modeling with Statecharts

Abstract -- A behaviorally expressive set of diagrammatic languages for modeling object oriented systems is presented It constitutes the constructive subset of UML and is supported by Rhapsody a tool that enables model execution and full code synthesis.

Experiences from the use and development of ISO 10303-AP 233 Interfaces in the Systems Engineering domain

Abstract -- Systems engineering as core discipline of technical product development uses a variety of different CASE (Computer Aided Systems Engineering) tools. Very often the need arises for data transfer between CASE tools. Due to insufficient interface formats today, a labour intensive manual transfer of data is necessary. An attempt for improvement of the data exchanges between systems engineering CASE tools along the process life cycle is the definition of standards interface formats using the application protocol framework of ISO STEP (STandard for the Exchange of Product model data) product data technology. In this paper we present experiences made while designing, developing and using a STEP ISO 10303 - AP233 conformant import and export interface for the CASE tool Teamwork. The interface demonstrates that AP233 is an efficient medium for tool and vendor independent transfer of systems engineering information. Examples of data exchanges between the CASE tools Teamwork and Statemate are shown.

AP-233 Architecture

ABSTRACT -- This paper outlines the information model architecture of the current working draft, WD4, of ISO 10303 – 233 (AP-233) standard proposal. The objective is to communicate how the architecture of the information model permits the exchange of systems specifications between computer based systems engineering tools. The model architecture makes no assumptions on the complexity of the information exchanged and does not require specific tool capabilities. The paper also illustrates how supplemental information, in particular configuration management and process information, is handled in the information model. We believe that capturing and maintaining this information is crucial for industrial applications and hence for industrial adoption of AP-233 by the systems engineering community.

Relationships between Common Graphical Representations in System Engineering

Most systems engineers today use graphical representations of a system to communicate its functional and data requirements. The most commonly used representations are the Function Flow Block Diagram (FFBD), Data Flow Diagram (DFD), N2 Chart, IDEF0 Diagram, Use Case, Sequence Diagram, Enhanced Function Flow Block Diagram, and Behavior Diagram. This paper discusses the characteristics of each and shows how they are related. When analyzed in the context of specifying functional control and data modeling, it appears that the FFBD and DFD representations are limiting, special cases of the Enhanced Function Flow Diagram and Behavior Diagram. The N2 Chart has the same capability as the DFD, with a more formal format. The IDEF0 is essentially an N2 Chart with some control definition (no constructs) capability. The IDEF0 has the capability to indicate the allocation of functions to system components. Thus, the Enhanced Function Flow Diagram and the Behavior Diagram features comprise a “parent/unified” set of graphical system representations. To achieve the same level of specification completeness, you would have to use an integrated set of the FFBD and one of the data models or augment the FFBD with a graphical representation of the data model, as was done at TRW (then called Function Sequence Diagrams).

Draft - Risk Management (RM) Process Description and DNP Interface Definition

NASA has identified Risk Management as a specific project management and systems engineering activity, and has outlined guidelines for the conduct of this activity. R Ienf 1 and Ref 2, the guidelines are established for significant NASA programs, that is programs costing greater than $200M or programs of significant interest, such as involving international partners. These guidelines encompass areas of risk management, categories of risks to be considered for management, and reporting approaches. The JPL RM Process is consistent with these guidelines, while including some differences in structure.

FOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN

Abstract -- This paper presents an initial viewpoint on an emerging technology: Model Driven System Design (MDSD). In contrast, the current state of practice has been characterized as document centered. Practitioners of system design are well aware of the technical and organizational difficulties of implementing current approaches. By modeling multiple aspects of a system throughout its life cycle, this new view of system design offers dramatic gains in productivity and product quality.

A Virtual Engineering Primer: Foundations for a theory of modeling and simulation

Perhaps the most generic trend in technology is the creation of increasingly complex systems together with a greater reliance on simulation for their design and analysis. Large networks of computers with shared data bases and high-speed communication are used in everything from the design and manufacture of microchips to vehicles such as the Boeing 777. Advances in technology have put us in the interesting position of being limited less by our inability to sense and actuate, to compute and communicate, and to fabricate and manufacture new materials, than by how well we understand, design and control their interconnection and the resulting complexity. While component-level problems will continue to be important, systems-level problems will be even more so. Further, “components” (e.g., sensors) increasingly need to be viewed as complex systems in their own right. This “systems of systems” view is coming to dominate technology at every level.

Abstract—The Object Management Group (OMG™) is

Abstract -- The Object Management Group (OMG™) is defining specifications supporting a modeling environment that permits models from a ‘family of modeling languages’ to populate a repository. In that environment, mechanisms that give coherence to the collection of models defining a project are the repository’s common meta-model and constraints enforcing a notion of well-formedness on the content of the repository. This paper argues that additionally what is required to implement a model driven architecture (MDA™) is an ‘intermodel’ language with reach beyond an object context into an ontology of the domain vocabulary and requirements definition. If specifications under this arrangement are modularized properly, reuse of the domain terminology and business sector characterization is possible. The repository federates models into an emergent enterprise model. This paper considers opportunities for an inter-model language in supporting traceability of requirements from domain knowledge to implementations. It explores an idea of modularized specifications where domain knowledge is separated from implementation-biased models and reified refinement relations bridge the gap.

AP 233 Interface for Teamwork Experiences in the Implementation and Use

Abstract -- Systems engineering as core discipline of technical product development uses a variety of different CASE tools. Very often the need arises for data transfer between CASE tools. Due to insufficient interface formats today a labour intensive manual transfer of data is necessary. An attempt for improvement of the data exchanges between systems engineering CASE tools along the process live cycle is the definition of standards interface formats using the application protocol framework of ISO STEP product data technology. In this paper we present experiences made while designing, developing and using a STEP ISO 10303 - AP233 conformant import and export interface for the CASE tool Teamwork. The interface demonstrates that AP233 is an efficient medium for tool and vendor independent transfer of systems engineering information. Examples of data exchanges between the CAS Tools Teamwork, Statemate and DOORS are shown.

NASA PROCEDURES AND GUIDELINES

This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library. Verify that this is the correct version before use: http://nodis.hq.nasa.gov/Library/Directives/NASA-WIDE/TBD NPG: 71xx.x Effective Date: Jan 1, 2003 Expiration Date: Jan 1, 2008 Responsible Office: Code AE / Office of Chief Engineer

NASA ESA Workshop on Product Exchange 2007

The 9th NASA-ESA Workshop on Product Exchange held in Fess Parker's Resort in Santa Barbara, California, U.S.A, May 2-4. Featuring a mixture of presentations from Industry, Academia and Public Sector, PDE 2007 updated attendees on the latest thinking in Electro_mechanical designs and developments, related disciplines, open standards and more. Presentations from the event are now available for download To gain access please use : USERNAME: nasa PASSWORD: pde

Naval Systems of Systems Systems Engineering Guidebook Vol 1

The Naval “Systems of Systems” Systems Engineering Guidebook, Volume 1, Version 2.0 has been developed by the ASN (RDA) Office of the Chief Systems Engineer to support the Naval acquisition community in implementing capability-based acquisition and systems engineering for systems of systems in accordance with SECNAVINST 5000.2C. The Guidebook focus is on a systems engineering process that enables the realization of successful “systems of systems” that provide needed capabilities and functionality within a Net Centric Operating and Warfare environment. Volume I of the Guidebook describes the recommended capability-based systems engineering process activities and products for systems of systems acquisitions.

Naval "Systems of Systems" Systems Engineering Guidebook Volume II

The Naval “Systems of Systems” Systems Engineering Guidebook, Volume 1, Version 2.0 has been developed by the ASN (RDA) Office of the Chief Systems Engineer to support the Naval acquisition community in implementing capability-based acquisition and systems engineering for systems of systems in accordance with SECNAVINST 5000.2C. The Guidebook focus is on a systems engineering process that enables the realization of successful “systems of systems” that provide needed capabilities and functionality within a Net Centric Operating and Warfare environment. Volume II of the Guidebook provides more in-depth descriptions of recommended methods and tools as well as use cases and lessons learned.

Naval "Systems of Systems" Carl Siel presentation

Long powerpoint presentation to System of Systems Engineering Conference July 25, 2006

Naval System of Systems (short) presentations

Zip file of a few short powerpoint presentations on Naval System of Systems by Carl Siel

Naval SoS guidelines concept map linked to AP233 value

A fully hyperlinked concept map of the Naval systems of systems guidelines with the focus on identifying where the capabilities of STEP AP233 and AP2339 add value. Start with the file Naval CSE Siel slide.html Hyperlinks are provided to all other concept maps, illustrative slides and associated documents.

SOA-Service Oriented Architecture

An introductory SOA slide presentation.

Model-based systems

Draft of article accepted for publication in McGraw Hill 2008 Yearbook of Science & Technology

CADM Version 1.5

Technical Specifications for the Core Architecture Data Model (CADM) Version 1.5, 23 April 2007

NASA Systems Engineering Handbook - 2007 Revision

NASA/SP-2007 6105 Rev1