SYSTEMS THINKING & MBSE Track 3 Session 2 Moderator: Mark Walker Deployment of MBSE and Systems Thinking in an energy technology company and an evaluation of interfaces in a system of systems development. Loyd Baker - Paper 2: Model-Based Systems Engineering (MBSE) Connecting The Dots Process
Is Model Based Systems Engineering (MBSE) something new? No, MBSE methods and techniques have been individually practiced by many good engineers and analyst. The MBSE process presented in this presentation is about “Connecting the Dots”. The problem has been that project management has been obsessed with ‘deliverable documents’ rather than delivering an engineering data-model that can be used to support analyses, end-to-end traceability, and automatically produce the deliverable documents from the data-model.
· The engineering data-model usually consists of entities, attributes, relationships, and diagrams that specify the system architecture.
· Remember a diagram (graphical model) is worth a thousand words. These diagrams aid in communicating ideas/concepts among project personnel and the customer.
What is new is the SysML modeling language. It should help with communication issues by having a common way to describe system architectures
Mark Walker: Model Based Systems Engineering Initial Stages for Power & E...EnergyTech2015
EnergyTech2015.com
PROCESS AND METHODS
Track 3 Session 1 Moderator: Matthew Hause
Capturing stakeholder needs with MBSE and using the System of Systems VEE™ model for evaluating control, communications, and threat and vulnerability assessment.
Mark Walker- Paper 1: Process and Methods: A fundamental premise of this presentation is that capturing stakeholder needs and the initial development of Systems Engineering documents and architecture models, with top level capability needs/requirements, in a well written rational Concept Document (OCD). This needs to be developed during the first stages of a development which is absolutely critical for the entire life cycle of the system development. With this information in the OCD, written substantially in the stakeholder’s operational terminology, and with Systems Modeling Language (SysMLTM) architecture views, this set of integrated products provide the foundation for all future stages of a development and the system’s operational life. The primary emphasis is the critical importance of the “System” Use Case Diagrams (SysUCD), their associated Scenarios and Sequence Diagrams and how essential it is to develop these with the operational customer in this first stage. This is accomplished by applying the Stakeholder Needs Analysis process using the recommended Object Oriented Systems Engineering Method (OOSEM) and translating the information into well-defined stakeholder and systems engineering products and architecture views/models
Mark Minnucci: Deployment of MBSE and the Emergence of a Systems-Thinking Cul...EnergyTech2015
SYSTEMS THINKING & MBSE
Track 3 Session 2
Moderator: Mark Walker
Deployment of MBSE and Systems Thinking in an energy technology company and an evaluation of interfaces in a system of systems development.
Mark Minnucci – Paper 1: Deployment of MBSE and Emergence of a Systems-Thinking Culture
Schneider Electric is a global specialist in the markets of energy management and automation. Historically, the Schneider portfolio has concentrated on mass-production of electro-mechanical consumer products. Today, Schneider product functionality and complexity are both rapidly increasing through the addition of embedded control software and wireless connectivity. In this presentation, I will share how my organization has championed this culture change, our roadmap for growing a community of experts from the ground up, and lessons-learned that will be applicable to all members of the audience who may be facing the same challenges in their own companies. This presentation will also provide a brief overview of the specific MBSE framework that Schneider Electric is using.
THE ENERGY GRID & Integration of IOT
Track 3 Session 3 Moderator: Mark Walker
Quantified results of an Energy Grid Management Use Case that explore grid performance boundaries in the face of proliferated residential solar array deployments is presented. The Use Case demonstrates how modern IT open source tools can be integrated into a grid simulation that provides a decision support tool for the utility industry to manage future change. GridLab-D is used as an agent based model to simulate energy consumer nodes in a complex inter-connected grid using a modern IBM SystemG graph computing engine. The resulting simulation environment executes the simulated grid network with structured and unstructured data results stored in the graph database. Big Data Analytics performed on the resulting simulation data using IBM Big Data Analytics tools and Sandia National Lab DAKOTA uncertainty quantification and statistical analysis tools allow for interrogation of the resulting performance database to establish performance characteristics visualized through graphs. The work is leverages DoD sponsored research in Uncertainty Quantification in complex System of System Modeling and Simulation environments and demonstrates future model based techniques for risk management, financial modeling, grid resiliency and critical infrastructure protection.
This document provides a summary of the Systems Engineering Handbook version 3 published by the International Council on Systems Engineering (INCOSE). The handbook aims to describe key systems engineering processes and activities over the lifecycle of a system. It includes sections on systems engineering overview, generic lifecycle stages, technical and project processes, enabling activities, and specialty engineering activities. The handbook is intended to serve as a guide for practitioners and references internationally accepted standards for systems engineering.
Model based engineering tutorial thomas consulting 4_sep13-1seymourmedia
This document discusses model-based system engineering (MBSE) and its application to the design of electro-optical sensors. It describes how MBSE differs from traditional engineering approaches by enabling integrated modeling across disciplines. Examples are given that show how MBSE allows designs to be evaluated earlier and problems to be identified and resolved more quickly. Both advantages and disadvantages of the MBSE approach are outlined. The author's goal of promoting wider adoption of MBSE methods through consulting is also mentioned.
See the major new features and improvements in Innoslate 4.3. The latest version of Innoslate has two brand new diagrams Interface Control Diagram (ICD) and a Risk Burndown Chart. You asked and we delivered; a ReqIF Import and Export. We've also added that Cross Project Entities will be visual noticeable in all views with a new purple symbol indicator, dashed purple lines, or purple background color. Now search has been redesigned for a more flexible user experience. All entity’s attributes can now be searched as well as searching by entity id, relationship name, and attribute name. Dr. Dam will demonstrate best practices for using all the new diagrams, features, and even some of the improvements. Stay for the question and answer session to ask any or all your questions. We look forward to having you there!
Software Architecture: introduction to the abstractionHenry Muccini
The document provides an introduction to software architecture concepts including:
- Software architecture is defined as a set of components and connectors communicating through interfaces along with architecture design decisions.
- Multiple views are used to describe architectures including logical, process, deployment, and more.
- Architectural styles like pipe-and-filter and layered styles guide architecture design.
- Careful architecture design is important as it impacts system properties like performance, scalability, and testability.
This document introduces software architecture and provides examples using GitHub. It defines software architecture as the fundamental concepts or properties of a system embodied in its elements, relationships, and design principles. The document outlines Philippe Kruchten's 4+1 view model for describing software architecture, including logical, process, physical and development views in addition to scenarios. Diagrams for GitHub's class, component, sequence and deployment architectures are presented as examples.
Mark Walker: Model Based Systems Engineering Initial Stages for Power & E...EnergyTech2015
EnergyTech2015.com
PROCESS AND METHODS
Track 3 Session 1 Moderator: Matthew Hause
Capturing stakeholder needs with MBSE and using the System of Systems VEE™ model for evaluating control, communications, and threat and vulnerability assessment.
Mark Walker- Paper 1: Process and Methods: A fundamental premise of this presentation is that capturing stakeholder needs and the initial development of Systems Engineering documents and architecture models, with top level capability needs/requirements, in a well written rational Concept Document (OCD). This needs to be developed during the first stages of a development which is absolutely critical for the entire life cycle of the system development. With this information in the OCD, written substantially in the stakeholder’s operational terminology, and with Systems Modeling Language (SysMLTM) architecture views, this set of integrated products provide the foundation for all future stages of a development and the system’s operational life. The primary emphasis is the critical importance of the “System” Use Case Diagrams (SysUCD), their associated Scenarios and Sequence Diagrams and how essential it is to develop these with the operational customer in this first stage. This is accomplished by applying the Stakeholder Needs Analysis process using the recommended Object Oriented Systems Engineering Method (OOSEM) and translating the information into well-defined stakeholder and systems engineering products and architecture views/models
Mark Minnucci: Deployment of MBSE and the Emergence of a Systems-Thinking Cul...EnergyTech2015
SYSTEMS THINKING & MBSE
Track 3 Session 2
Moderator: Mark Walker
Deployment of MBSE and Systems Thinking in an energy technology company and an evaluation of interfaces in a system of systems development.
Mark Minnucci – Paper 1: Deployment of MBSE and Emergence of a Systems-Thinking Culture
Schneider Electric is a global specialist in the markets of energy management and automation. Historically, the Schneider portfolio has concentrated on mass-production of electro-mechanical consumer products. Today, Schneider product functionality and complexity are both rapidly increasing through the addition of embedded control software and wireless connectivity. In this presentation, I will share how my organization has championed this culture change, our roadmap for growing a community of experts from the ground up, and lessons-learned that will be applicable to all members of the audience who may be facing the same challenges in their own companies. This presentation will also provide a brief overview of the specific MBSE framework that Schneider Electric is using.
THE ENERGY GRID & Integration of IOT
Track 3 Session 3 Moderator: Mark Walker
Quantified results of an Energy Grid Management Use Case that explore grid performance boundaries in the face of proliferated residential solar array deployments is presented. The Use Case demonstrates how modern IT open source tools can be integrated into a grid simulation that provides a decision support tool for the utility industry to manage future change. GridLab-D is used as an agent based model to simulate energy consumer nodes in a complex inter-connected grid using a modern IBM SystemG graph computing engine. The resulting simulation environment executes the simulated grid network with structured and unstructured data results stored in the graph database. Big Data Analytics performed on the resulting simulation data using IBM Big Data Analytics tools and Sandia National Lab DAKOTA uncertainty quantification and statistical analysis tools allow for interrogation of the resulting performance database to establish performance characteristics visualized through graphs. The work is leverages DoD sponsored research in Uncertainty Quantification in complex System of System Modeling and Simulation environments and demonstrates future model based techniques for risk management, financial modeling, grid resiliency and critical infrastructure protection.
This document provides a summary of the Systems Engineering Handbook version 3 published by the International Council on Systems Engineering (INCOSE). The handbook aims to describe key systems engineering processes and activities over the lifecycle of a system. It includes sections on systems engineering overview, generic lifecycle stages, technical and project processes, enabling activities, and specialty engineering activities. The handbook is intended to serve as a guide for practitioners and references internationally accepted standards for systems engineering.
Model based engineering tutorial thomas consulting 4_sep13-1seymourmedia
This document discusses model-based system engineering (MBSE) and its application to the design of electro-optical sensors. It describes how MBSE differs from traditional engineering approaches by enabling integrated modeling across disciplines. Examples are given that show how MBSE allows designs to be evaluated earlier and problems to be identified and resolved more quickly. Both advantages and disadvantages of the MBSE approach are outlined. The author's goal of promoting wider adoption of MBSE methods through consulting is also mentioned.
See the major new features and improvements in Innoslate 4.3. The latest version of Innoslate has two brand new diagrams Interface Control Diagram (ICD) and a Risk Burndown Chart. You asked and we delivered; a ReqIF Import and Export. We've also added that Cross Project Entities will be visual noticeable in all views with a new purple symbol indicator, dashed purple lines, or purple background color. Now search has been redesigned for a more flexible user experience. All entity’s attributes can now be searched as well as searching by entity id, relationship name, and attribute name. Dr. Dam will demonstrate best practices for using all the new diagrams, features, and even some of the improvements. Stay for the question and answer session to ask any or all your questions. We look forward to having you there!
Software Architecture: introduction to the abstractionHenry Muccini
The document provides an introduction to software architecture concepts including:
- Software architecture is defined as a set of components and connectors communicating through interfaces along with architecture design decisions.
- Multiple views are used to describe architectures including logical, process, deployment, and more.
- Architectural styles like pipe-and-filter and layered styles guide architecture design.
- Careful architecture design is important as it impacts system properties like performance, scalability, and testability.
This document introduces software architecture and provides examples using GitHub. It defines software architecture as the fundamental concepts or properties of a system embodied in its elements, relationships, and design principles. The document outlines Philippe Kruchten's 4+1 view model for describing software architecture, including logical, process, physical and development views in addition to scenarios. Diagrams for GitHub's class, component, sequence and deployment architectures are presented as examples.
This document provides an introduction to software architecture design. It discusses key concepts like the relationship between requirements and architecture, architecture styles, quality attributes, and tradeoff analysis. The document is divided into multiple parts that cover topics such as an overview of software architecture, common architecture styles, quality attributes, and some rules of thumb for architecture design.
This document provides an introduction to complex system engineering. It defines what a system is, provides examples of complex systems like information systems, and discusses key aspects of systems engineering including the system lifecycle, iterative processes, requirements, architecture, integration, and verification and validation. Key definitions and concepts in systems engineering are explained at a high level.
1. Systems engineering is an interdisciplinary approach that focuses on designing and managing complex systems as a whole rather than individual parts. It involves considering all aspects of a problem and relating technical and social factors.
2. A system is made up of interacting elements that work together to achieve specific purposes. Systems engineering is concerned with both the internal structure of a system's components and interactions, as well as a system's external relationships.
3. There are many common misconceptions about systems engineering, but it provides value through a holistic, big-picture thinking style and enabling complex problems to be addressed and transformations delivered through the life of a project.
The document provides an overview of Team 2's final project on the Systems Engineering Body of Knowledge (SEBoK). It includes:
1) An introduction to the SEBoK that describes its history, purpose, description of its seven major parts, and current status.
2) An overview of the SysML modeling language that describes its history, purpose, key diagrams like requirements, block definition, internal block and parametric diagrams, and how it relates to systems engineering processes.
3) A potential application of SysML for Millennium Systems to benefit from modeling system requirements, structure, behavior and performing engineering analysis using its constraint blocks and equations.
Systems Analysis,
Systems Design,
Systems Modelling,
Systems Architecture,
System Development and Testing,
System Maintenance and Evolution,
SDLC example (Cloud Service life cycle)
This document outlines the course objectives and content for a software architectures course. The key topics covered include:
- Understanding what constitutes software architecture, architectural drivers, styles and views.
- Examining quality attribute workshops, architectural views, styles and documenting architectures.
- Exploring specific architectural styles, views, patterns and how they are used to specify system architecture.
- Analyzing architectures for emerging technologies like service-oriented architectures, cloud computing and adaptive structures.
The course aims to help students understand how to design architectures that meet requirements and explain the influence of architecture on technical and business activities. It covers important architectural concepts and how to apply styles and views.
This document outlines a proposed systematic architecture design (SAD) framework that aims to integrate non-functional requirements (NFRs) into model-driven development (MDD) processes. It presents a motivation example comparing two travel agency systems with different NFRs. It then proposes an NFR-aware MDD process with either automatic or interactive variants. The SAD contributions include tools like ArchiTech and an ontology-based knowledge system called Arteon. Future work includes further implementing and validating parts of the proposed framework through empirical studies.
Using Innoslate for Model-Based Systems EngineeringElizabeth Steiner
Dr. Steve Dam will walk you through the process of using Innoslate’s modeling and simulation capabilities while applying a MBSE methodology.
At its core, Innoslate is a full model-based systems engineering tool. Within Innoslate, system models are formalized and capable of simulation to derive cost, schedule, and performance data.
Your webinar will cover:
Functional modeling
Functional modeling is at the heart of how Innoslate derives new requirements and ensures logical accuracy.
Physical modeling
We can describe synthesizing the physical model in Innoslate with eight different diagrams, including the Asset Diagram, Layer Diagram, Block Definition Diagram, and Internal Block Diagram.
Executing a model
Innoslate includes a ‘Discrete Event Simulator’ to verify functional diagram’s logic, calculate cost, compute time, and quantify performance.
Relating Requirements to Diagrams
Requirements traceability ensures that the lifecycle and origin of a requirement is fully tracked. Innoslate includes relationship matrices to represent traceability relationships between entities in tabular view.
Requirements Generation
After modeling the system, often an engineer will derive textual requirements from the models by hand. Innoslate includes an automatic facility that generates requirements documents in a standard format (as outlined in “The Engineering Design of Systems: Models and Methods“).
System of Systems Engineering (SoSE),
System “ilities” (Reliability, Availability, Maintainability, and Changeability),
State Series,
System Evolution Analytics,
System Network Evolution Rules,
System Network Complexity,
System Evolution Recommender
Service Evolution Analytics
Software Architecture and Design IntroductionUsman Khan
The document discusses software architecture and design. It defines software architecture as describing a system's major components, their relationships, and how they interact. Software design provides a plan for how system elements fit and work together. An important role of architecture is to identify requirements that affect structure and reduce risks. Quality attributes, both static and dynamic, are important non-functional properties like maintainability, performance, and security. Architects must consider these attributes and deliver solutions that technical teams can implement.
A Model-Based Systems Engineering Approach to Portfolio ManagementElizabeth Steiner
Learn about the importance of The Lifecycle Modeling Language (LML) to portfolio management. LML provides an open standard ontology and diagram framework that enables more effective communications to all stakeholders in the acquisition process.
Innoslate® implements and extends LML making Innoslate easier to learn and adopt than any other tool available today in the program management and systems engineering domains. You will also learn how Innoslate is built on a modular open systems approach (MOSA) architecture and can be easily integrated with other modern tools. This webinar will also include a sneak preview of Innoslate 4.5's program management features.
Innoslate is a full lifecycle systems engineering tool that provides you with the capability to perform requirements analysis, functional and physical modeling, simulation, testing, and more all in one place.
Systems Engineering is a very broad , overarching, and generally applicable engineering discipline. Many types of systems are developed using SE. These include biomedical systems, space vehicle systems, weapon systems, transportation systems, and so on.
Systems Engineering involves the coordination of work performed by engineers from all other engineering disciplines (electrical, mechanical, computer, software, etc.) as required to complete the engineering work on the project/program.
The document discusses software architecture, where it comes from, and what it is. Architectures are influenced by system stakeholders and their requirements, the developing organization, and the architects' experience. An architecture defines elements, their relationships, and properties. It is important because it represents early design decisions, dictates implementation, organizational structure, and quality attributes. Architectural patterns, reference models, and reference architectures capture common architectural elements but are not full architectures themselves.
Design patterns are general reusable solutions to common problems in software design. The Gang of Four patterns are 23 classic design patterns divided into creational, structural, and behavioral categories. Design principles provide guidelines for building software, such as using registries as a single source of truth, adopting a mobile-first design strategy, and ensuring privacy and security by design. Well-defined registries should be self-maintainable, have non-repudiable data, extensible schemas, and support open APIs. A cloud-first strategy employs patterns like external configuration, cache-aside, and federated identity. A minimalistic approach focuses on auto-scaling, decoupled microservices, and separating reads from writes.
Software Architecture by Reuse, Composition and Customization Ivano Malavolta
Ivano Malavolta.
Research Fellow at the Computer Science Department of the University of L'Aquila (Italy).
PhD thesis presentation, University of L'Aquila, March 2012.
The full PhD thesis is available here:
http:www.di.univaq.it/malavolta/files/IvanoMalavoltaPhDThesis.pdf
Interdisciplinary Science, Engineering, and Management,
Systems theory,
Systems thinking,
System development life cycles,
Synergy,
Project management,
Engineering Domains (Industry 4.0) , and
Communities (INCOSE and IEEE SMC Society).
This document provides an overview of software architectures and architectural structures. It discusses different types of architectural structures, including module structures, component-and-connector structures, and allocation structures. Module structures focus on modules and their relationships, component-and-connector structures examine runtime components and connectors, and allocation structures show how software elements map to environments. The document then examines specific architectural structures like modules, layers, classes, processes, repositories, and deployment. It emphasizes that an architect should focus on a few key structures like logical, process, development, and physical views to validate that the architecture meets requirements.
Software architecture refers to the high-level structures of a software system and the discipline of designing these structures. It involves making fundamental choices about components, interactions, and properties that are difficult to change later. Documenting software architecture facilitates communication between stakeholders and allows reuse of design elements. It provides an abstract understanding of a complex system before implementation to enable analysis, reuse, risk management, and cost reduction. The concepts of software architecture have developed since the 1960s with increased research in the 1990s focusing on styles, documentation, and formal methods.
Presenter: Pawel Chadzynski, Aras
Systems engineering driven businesses often times have different needs than supply chain-oriented operations. Find out how ECAD connnectors can expose the logical structure of schematics as part of the RFLP while still providing electronic design data across fabrication and assembly.
The document discusses best practices for deploying changes from development environments to production in Aras Innovator. It recommends establishing a baseline, separate development, test, and production environments, and planning deployments. The process involves exporting changes, comparing to the baseline, resolving conflicts, creating deployment packages, importing to test, and validating before deployment to production. Tools like source control, XML diff/merge tools, and the Aras import tool are important for deployment. Examples demonstrate single and multiple developer scenarios.
This document provides an introduction to software architecture design. It discusses key concepts like the relationship between requirements and architecture, architecture styles, quality attributes, and tradeoff analysis. The document is divided into multiple parts that cover topics such as an overview of software architecture, common architecture styles, quality attributes, and some rules of thumb for architecture design.
This document provides an introduction to complex system engineering. It defines what a system is, provides examples of complex systems like information systems, and discusses key aspects of systems engineering including the system lifecycle, iterative processes, requirements, architecture, integration, and verification and validation. Key definitions and concepts in systems engineering are explained at a high level.
1. Systems engineering is an interdisciplinary approach that focuses on designing and managing complex systems as a whole rather than individual parts. It involves considering all aspects of a problem and relating technical and social factors.
2. A system is made up of interacting elements that work together to achieve specific purposes. Systems engineering is concerned with both the internal structure of a system's components and interactions, as well as a system's external relationships.
3. There are many common misconceptions about systems engineering, but it provides value through a holistic, big-picture thinking style and enabling complex problems to be addressed and transformations delivered through the life of a project.
The document provides an overview of Team 2's final project on the Systems Engineering Body of Knowledge (SEBoK). It includes:
1) An introduction to the SEBoK that describes its history, purpose, description of its seven major parts, and current status.
2) An overview of the SysML modeling language that describes its history, purpose, key diagrams like requirements, block definition, internal block and parametric diagrams, and how it relates to systems engineering processes.
3) A potential application of SysML for Millennium Systems to benefit from modeling system requirements, structure, behavior and performing engineering analysis using its constraint blocks and equations.
Systems Analysis,
Systems Design,
Systems Modelling,
Systems Architecture,
System Development and Testing,
System Maintenance and Evolution,
SDLC example (Cloud Service life cycle)
This document outlines the course objectives and content for a software architectures course. The key topics covered include:
- Understanding what constitutes software architecture, architectural drivers, styles and views.
- Examining quality attribute workshops, architectural views, styles and documenting architectures.
- Exploring specific architectural styles, views, patterns and how they are used to specify system architecture.
- Analyzing architectures for emerging technologies like service-oriented architectures, cloud computing and adaptive structures.
The course aims to help students understand how to design architectures that meet requirements and explain the influence of architecture on technical and business activities. It covers important architectural concepts and how to apply styles and views.
This document outlines a proposed systematic architecture design (SAD) framework that aims to integrate non-functional requirements (NFRs) into model-driven development (MDD) processes. It presents a motivation example comparing two travel agency systems with different NFRs. It then proposes an NFR-aware MDD process with either automatic or interactive variants. The SAD contributions include tools like ArchiTech and an ontology-based knowledge system called Arteon. Future work includes further implementing and validating parts of the proposed framework through empirical studies.
Using Innoslate for Model-Based Systems EngineeringElizabeth Steiner
Dr. Steve Dam will walk you through the process of using Innoslate’s modeling and simulation capabilities while applying a MBSE methodology.
At its core, Innoslate is a full model-based systems engineering tool. Within Innoslate, system models are formalized and capable of simulation to derive cost, schedule, and performance data.
Your webinar will cover:
Functional modeling
Functional modeling is at the heart of how Innoslate derives new requirements and ensures logical accuracy.
Physical modeling
We can describe synthesizing the physical model in Innoslate with eight different diagrams, including the Asset Diagram, Layer Diagram, Block Definition Diagram, and Internal Block Diagram.
Executing a model
Innoslate includes a ‘Discrete Event Simulator’ to verify functional diagram’s logic, calculate cost, compute time, and quantify performance.
Relating Requirements to Diagrams
Requirements traceability ensures that the lifecycle and origin of a requirement is fully tracked. Innoslate includes relationship matrices to represent traceability relationships between entities in tabular view.
Requirements Generation
After modeling the system, often an engineer will derive textual requirements from the models by hand. Innoslate includes an automatic facility that generates requirements documents in a standard format (as outlined in “The Engineering Design of Systems: Models and Methods“).
System of Systems Engineering (SoSE),
System “ilities” (Reliability, Availability, Maintainability, and Changeability),
State Series,
System Evolution Analytics,
System Network Evolution Rules,
System Network Complexity,
System Evolution Recommender
Service Evolution Analytics
Software Architecture and Design IntroductionUsman Khan
The document discusses software architecture and design. It defines software architecture as describing a system's major components, their relationships, and how they interact. Software design provides a plan for how system elements fit and work together. An important role of architecture is to identify requirements that affect structure and reduce risks. Quality attributes, both static and dynamic, are important non-functional properties like maintainability, performance, and security. Architects must consider these attributes and deliver solutions that technical teams can implement.
A Model-Based Systems Engineering Approach to Portfolio ManagementElizabeth Steiner
Learn about the importance of The Lifecycle Modeling Language (LML) to portfolio management. LML provides an open standard ontology and diagram framework that enables more effective communications to all stakeholders in the acquisition process.
Innoslate® implements and extends LML making Innoslate easier to learn and adopt than any other tool available today in the program management and systems engineering domains. You will also learn how Innoslate is built on a modular open systems approach (MOSA) architecture and can be easily integrated with other modern tools. This webinar will also include a sneak preview of Innoslate 4.5's program management features.
Innoslate is a full lifecycle systems engineering tool that provides you with the capability to perform requirements analysis, functional and physical modeling, simulation, testing, and more all in one place.
Systems Engineering is a very broad , overarching, and generally applicable engineering discipline. Many types of systems are developed using SE. These include biomedical systems, space vehicle systems, weapon systems, transportation systems, and so on.
Systems Engineering involves the coordination of work performed by engineers from all other engineering disciplines (electrical, mechanical, computer, software, etc.) as required to complete the engineering work on the project/program.
The document discusses software architecture, where it comes from, and what it is. Architectures are influenced by system stakeholders and their requirements, the developing organization, and the architects' experience. An architecture defines elements, their relationships, and properties. It is important because it represents early design decisions, dictates implementation, organizational structure, and quality attributes. Architectural patterns, reference models, and reference architectures capture common architectural elements but are not full architectures themselves.
Design patterns are general reusable solutions to common problems in software design. The Gang of Four patterns are 23 classic design patterns divided into creational, structural, and behavioral categories. Design principles provide guidelines for building software, such as using registries as a single source of truth, adopting a mobile-first design strategy, and ensuring privacy and security by design. Well-defined registries should be self-maintainable, have non-repudiable data, extensible schemas, and support open APIs. A cloud-first strategy employs patterns like external configuration, cache-aside, and federated identity. A minimalistic approach focuses on auto-scaling, decoupled microservices, and separating reads from writes.
Software Architecture by Reuse, Composition and Customization Ivano Malavolta
Ivano Malavolta.
Research Fellow at the Computer Science Department of the University of L'Aquila (Italy).
PhD thesis presentation, University of L'Aquila, March 2012.
The full PhD thesis is available here:
http:www.di.univaq.it/malavolta/files/IvanoMalavoltaPhDThesis.pdf
Interdisciplinary Science, Engineering, and Management,
Systems theory,
Systems thinking,
System development life cycles,
Synergy,
Project management,
Engineering Domains (Industry 4.0) , and
Communities (INCOSE and IEEE SMC Society).
This document provides an overview of software architectures and architectural structures. It discusses different types of architectural structures, including module structures, component-and-connector structures, and allocation structures. Module structures focus on modules and their relationships, component-and-connector structures examine runtime components and connectors, and allocation structures show how software elements map to environments. The document then examines specific architectural structures like modules, layers, classes, processes, repositories, and deployment. It emphasizes that an architect should focus on a few key structures like logical, process, development, and physical views to validate that the architecture meets requirements.
Software architecture refers to the high-level structures of a software system and the discipline of designing these structures. It involves making fundamental choices about components, interactions, and properties that are difficult to change later. Documenting software architecture facilitates communication between stakeholders and allows reuse of design elements. It provides an abstract understanding of a complex system before implementation to enable analysis, reuse, risk management, and cost reduction. The concepts of software architecture have developed since the 1960s with increased research in the 1990s focusing on styles, documentation, and formal methods.
Presenter: Pawel Chadzynski, Aras
Systems engineering driven businesses often times have different needs than supply chain-oriented operations. Find out how ECAD connnectors can expose the logical structure of schematics as part of the RFLP while still providing electronic design data across fabrication and assembly.
The document discusses best practices for deploying changes from development environments to production in Aras Innovator. It recommends establishing a baseline, separate development, test, and production environments, and planning deployments. The process involves exporting changes, comparing to the baseline, resolving conflicts, creating deployment packages, importing to test, and validating before deployment to production. Tools like source control, XML diff/merge tools, and the Aras import tool are important for deployment. Examples demonstrate single and multiple developer scenarios.
Presenter: Kevin Richard, Aras
In this how-to session you will explore the underlying architecture of the Technical Documentation application and walk through a sample customization exercise to illustrate how to make it work with many styles of documentation.
Presenter: Lopa Subramanian, Aras
Managing product variability in Assemble / Build / Configure-to-order businesses is daunting. Learn about our vision in managing variants and engage in a lively discussion around scenarios you encounter in your organization.
Presentation given at Product Camp Austin 16 on 13 February 2016. Introduces Model-Based Systems Engineering, SysML, and advanced requirements management tools. Also discusses how Agile and Safety-Critical software development fit together
Branndon Kelley Keynote on Cybersecurity and the Smart Utility EnergyTech2015
In an effort to make a Utility more “Smart” the business units within are requiring additional data for business intelligence, predictive and data analytics and asset optimization. To acquire the necessary data points the once “disconnected” power plants, electric grid, and the consumer now have to be connected. Utilizing sensor technology, advanced metering, and automated controls the systems within the power plant, transmission & distribution grid, and even a home or business now become vulnerable. In addition to this business-enabling concept the threat of a full-fledged cyber-attack or at the minimum cyber espionage is real. Utilities are now faced with these threats and must spend enormous amounts of capital and operational dollars to protect their assets utilizing a “not if, but when” mentality. The two competing concepts create a paradox – the more we connect the utility, the more vulnerable it be- comes -however, without connecting the utility, the less “Smart” we can be.
Josh Long: Minimum Cyber Security Requirements for a 20 MW Photo Voltaic Field EnergyTech2015
EnergyTech2015.com Track 4 Session 3 RESILIENT APPLICATIONS Moderator: Mike Delamare
Josh Long: Minimum Cyber Security Requirements for a 20 MW Photo Voltaic Field
Brian Patterson: The role of Direct Current micro-grids and data centers for efficiency and resilience
Irv Badr: Managing Risk Factors in Critical Infrastructure
Anurandha Annaswamy: Computation Model of the Nexus Between Natural Gas and E...EnergyTech2015
THE GAS AND ELECTRIC UTILITY INDUSTRY: CARBON CONSTRAINED
Monday, November 30th Track 1 Session 3
This session will focus on the impact U.S. EPA Clean Power Plan (CPP) will play in shaping changes to the natural gas market, including the shale gas marketplace both domestically and perhaps internationally. The inter-dependency between the natural gas and electric industry is growing as there is more movement toward natural gas fired generation and away from coal fired generation. Natural gas companies are already seeing an increased need for infrastructure expansion from the growing gas-electric inter-dependency. What are the benefits and risks facing the natural gas industry? What role does the shale gas industry play? What will the changes mean for gas producers, electric utilities and technology now and in the future both in the U.S and abroad?
Track One Changing Dynamics of the Global Energy Landscape: What are the major forces driving the sea-changes occurring in all phases of Energy Systems i.e., Exploration, Generation, Distribution, Consumption, etc; Systems Support to Policy & Decision Makers; Energy Economics and Politics; how will Systems Engineering facilitate decision making?
Anurandha Annaswamy from Massachusetts Institute of Technology
Jenita McGowan is responsible as Chief of Sustainability for advising the City on policies related to sustainability and the oversight of the Office of Sustainability; leading the coordination of Sustainable Cleveland 2019 to develop new strategies that allow Cleveland to use sustainability as an innovation engine for economic growth, and reducing the City’s ecological footprint with solutions that also save the City money.
SPACE POWER SYSTEMS
Track 2 Session 4 Moderator: James Soeder
This session explored power technologies being developed to enable more advanced deep space missions including; unique power systems, autonomous and intelligent control and real time simulation
Ms Anne McNellis: Paper 1: NASA Intelligent Power Control,
Dr Benjamin Loop: Paper 2: Real Time Simulation for NASA Intelligent Power Control Development,
Dr Brad Glenn: Paper 3: Helm Algorithm Development for NASA Intelligent Power Control,
William Good: Extra Small Modular ReactorsEnergyTech2015
EnergyTech2015.com
TERRESTRIAL POWER TECHNOLOGY II
Track 2 Session 2
Moderator: Don Brown, NASA
This session continued the previous session’s exploration of technologies to improve terrestrial power systems including; power systems for building and industrial power, advanced generation, energy storage and smart grid developments.
David J. Sadey: Paper 1: Operation and Control of a Three-Phase Megawatt-Class Variable Frequency Power Generation and Distribution System
William Good: Paper 2: Modular Nuclear Power
Josh Sparber: Paper 3: Effective Measures for Protection of US Power Grid
Neil Tyrrell : Paper 4: Fast and flexible combined cycle gas turbines
Tues.1040 am states role in protecting electric grids from emp and gmd with a...EnergyTech2015
EnergyTech2015.com Track 4 Session 2 SHAPING POLICY ON CRITICAL INFRASTRUCTURE PROTECTION AND RECOVERY Moderator: Mike DeLamare Panelists will briefly present current policy efforts, or the effects of policy on providers. This will be followed by Q&A from the audience. Panelists: Andrea Boland: Discuss current and pending Legislation for the State of Maine as compared to other States: /Maine John Ostrich: Speaking on the Space Weather Policy and Action Plan Patrick Shaw: Addressing the business continuity and the emergency management consequences of long-term power outages Kevin Goodman: Policy effects on Power and Data Centers Chuck Manto: Policy as a catalyst for technical innovations
Gareth Digby: Systems-Based Approach to Cyber Investigations EnergyTech2015
EnergyTech2015.com
ENERGIZING MBSE IN ORGANIZATIONS
Track 3 Session 4 Moderator: Matthew Hause
Implementing System Engineering disciplines and practices in an energy company and a panel discussion of how to promote the use of MBSE in the energy systems.
Gareth Digby: A Systems-based Approach To Cyber Investigations The presentation discusses the role of a systems-based approach to cyber investigations and demonstrates how such an approach can help the investigator ensure that a holistic view is take to the identification and analysis of appropriate evidence. Systems engineers are familiar with the need to consider the system within its environment while being aware of the interaction of the system with both people and other systems. These aspects also need to be considered when we investigate what has happened to a system as well as when we create systems.
One element of this systems-based approach is the Human-System-Environment matrix, which offers an appropriate framework to guide the collection of evidence. In particular the matrix emphasizes the temporal aspects associated with evidence gathering. In addition the cyber investigator is not dealing with a system in isolation. The systems-based approach discusses the need to identify the interfaces of the system with the greater system-of-systems.
The value of this systems-based approach to the various stages of a cyber investigation is described, including during the incident investigation, the collection of evidence and the analysis of data. This systems-based approach for an investigation gives the investigator the freedom to go in appropriate directions as the investigation proceeds while ensuring the investigator covers the breadth needed
Benjamin Loop: Simulation Environment for Power Management and Distribution D...EnergyTech2015
EnergyTech2015.com
SPACE POWER SYSTEMS
Track 2 Session 4 Moderator: James Soeder
This session explored power technologies being developed to enable more advanced deep space missions including; unique power systems, autonomous and intelligent control and real time simulation
Ms Anne McNellis: Paper 1: NASA Intelligent Power Control,
Dr Benjamin Loop: Paper 2: Real Time Simulation for NASA Intelligent Power Control Development
Dr Brad Glenn: Paper 3: Helm Algorithm Development for NASA Intelligent Power Control
Andrew Ritch: Interruption in the Utility IndustryEnergyTech2015
EnergyTech2015.com
INTERRUPTION IN THE UTILITY INDUSTRY?
Track 1 Session 1
Electricity markets are experiencing fundamental changes because of solar, wind, electric vehicles, energy efficiency programs, storage and other forms of distributed generation that may be intermittent or require changes/upgrades to the electric grid. There is also an increase in the availability of smart meters and other devices that can help customers control their electric demand and usage. As a result, demand is less predictable and more volatile. This change also creates challenges for transmission and distribution for all load serving entities, even with new real-time data availability and grid visibility. What technological, regulatory, and/or policy changes are needed in the short term and longer term to keep pace? What will these changes mean for reliability? How will the traditional utility model change in the coming years?
Moderator: Commissioner Beth Trombold, PUCO
Robert Wargo, Vice President, Reliability First Corp.
Andrew Ritch, Energy Wholesale Renewables Director, Duke Energy
Andrew Ott, Executive Vice President, PJM Interconnection
EnergyTech2015.com Track 4 Session 2 SHAPING POLICY ON CRITICAL INFRASTRUCTURE PROTECTION AND RECOVERY Moderator: Mike DeLamare Panelists will briefly present current policy efforts, or the effects of policy on providers. This will be followed by Q&A from the audience. Panelists: Andrea Boland: Discuss current and pending Legislation for the State of Maine as compared to other States: /Maine John Ostrich: Speaking on the Space Weather Policy and Action Plan Patrick Shaw: Addressing the business continuity and the emergency management consequences of long-term power outages Kevin Goodman: Policy effects on Power and Data Centers Chuck Manto: Policy as a catalyst for technical innovations
David Sadey, Operation and Control of a Three-Phase Megawatt Class Variable F...EnergyTech2015
EnergyTech2015.com
TERRESTRIAL POWER TECHNOLOGY II
Track 2 Session 2
Moderator: Don Brown, NASA
This session will continue the previous session’s exploration of technologies to improve terrestrial power systems including; power systems for building and industrial power, advanced generation, energy storage and smart grid developments.
David J. Sadey: Paper 1: Operation and Control of a Three-Phase Megawatt-Class Variable Frequency Power Generation and Distribution System
William Good: Paper 2: Modular Nuclear Power
Josh Sparber: Paper 3: Effective Measures for Protection of US Power Grid
Neil Tyrrell : Paper 4: Fast and flexible combined cycle gas turbines
George Baker: Nuclear EMP and Solar GMD Effects, National Protection Impasse,...EnergyTech2015
This document discusses the threats of nuclear electromagnetic pulse (EMP), solar geomagnetic disturbances (GMD), and radiofrequency weapons to critical infrastructure systems. It summarizes the key findings and recommendations of the Congressional EMP Commission to improve protection against these threats. However, progress has been impeded by misconceptions about the threats, reluctance of stakeholders to address vulnerabilities, and the lack of a clear authority to coordinate protection efforts across government and industry. Recent developments have been limited and do not adequately address the commission's recommendations to prioritize protection of critical systems.
Irv Badr: Managing Risk Safety and Security Compliance EnergyTech2015
EnergyTech2015.com
Track 4 Session 3
RESILIENT APPLICATIONS
Moderator: Mike Delamare
Josh Long: Paper 1 - Minimum Cyber Security Requirements for a 20 MW Photo Voltaic Field
Brian Patterson: Paper 2 - The role of Direct Current micro-grids and data centers for efficiency and resilience
Irv Badr: Paper 3 - Managing Risk Factors in Critical Infrastructure
Connecting the dots mbse process dec02 2015loydbakerjr
Loyd Baker presented on connecting dots in the MBSE (Model-Based Systems Engineering) process. He discussed how systems engineering projects traditionally managed information across documents, which lacked consistency and traceability. The emerging MBSE approach promotes data-model centric processes over document-centric ones. Baker explained how models provide benefits like improved communication, traceability, and validation compared to documents. He outlined an example MBSE process that could be applied to projects using modeling notations in Cradle to iteratively develop requirements, logical architectures, physical architectures, and integrate models at different levels.
Sean Lynch has over 15 years of experience leading teams that deliver software projects on time and under budget. He currently works as a Senior System Analyst and Solutions Architect at Blue Cross Blue Shield, where he has helped design and implement their large national data warehouse system. Previously he has worked as a consultant for several insurance and financial companies, managing projects and teams. He has a focus on quality results and extensive experience across the software development lifecycle.
C19013010 the tutorial to build shared ai services session 2Bill Liu
This document provides an agenda and overview for a tutorial on building shared AI services. The session will cover AI engineering platforms, data pipelines, traditional AI roles and their challenges, skills required for AI engineers, and benchmarking machine learning and deep learning approaches. It includes a live demo of building an end-to-end AI pipeline with Kafka, NiFi, Spark Streaming and Keras on Spark.
TMPA-2017: Stemming Architectural Decay in Software SystemsIosif Itkin
TMPA-2017: Tools and Methods of Program Analysis
3-4 March, 2017, Hotel Holiday Inn Moscow Vinogradovo, Moscow
Stemming Architectural Decay in Software Systems
Nenad Medvidovic (Professor, USA University of Southern California, ACM SIGSOFT Executive Committee Chair)
For video follow the link: https://youtu.be/D7ZVSifyJoA
Would like to know more?
Visit our website:
www.tmpaconf.org
www.exactprosystems.com/events/tmpa
Follow us:
https://www.linkedin.com/company/exactpro-systems-llc?trk=biz-companies-cym
https://twitter.com/exactpro
This document is a resume for Mark D. Andrews that summarizes his skills and experience as a data architect. He has over 25 years of experience in database design, development, and optimization using technologies like Java, SQL, Oracle, PostgreSQL, and Python. His most recent role was as a data architect at Advanti Solutions where he developed data ingestion components in Python and REST APIs to access data. Prior to that, he held roles at Thomson Reuters and BIOSIS where he performed tasks like database migrations, performance tuning, and developing applications and reporting systems that utilized Oracle databases.
Knowledge-Based Analysis and Design (KBAD): An Approach to Rapid Systems Engi...Elizabeth Steiner
The document describes Knowledge-Based Analysis and Design (KBAD), a methodology developed by Systems and Proposal Engineering Company for rapid systems engineering and architecture development. KBAD combines system engineering and program management disciplines to develop an executable knowledge base that can support decision-making across a system's lifecycle. It utilizes a modified form of Model-Based Systems Engineering (MBSE) with simplified constructs and relationships between elements. The goal is to reduce complexity and capture the essential information needed for analysis and design in a more cost-effective manner than traditional approaches.
The document provides a summary of Prabhakar KR's work experience and skills. He has over 8 years of experience with SQL and PL/SQL and has worked extensively on Oracle database administration, performance tuning, query optimization, and ETL processes. Some of the projects he has worked on include implementing a fast search optimization solution for Dell, deduplicating customer records for Sony, an data transformation project for Bridgestone, and a data integration project for Genworth Financial. He is proficient in technologies like Oracle, SQL, PL/SQL, and has expertise in areas such as database design, query tuning, and utilities like SQL Loader.
Lokesh Reddy has over 10 years of experience as an analyst programmer at Accenture, USA. He has expertise in DataStage, Teradata, Oracle, SQL Server, and MSBI tools. Some of his roles include designing and developing DataStage jobs, writing SQL scripts, testing, and promoting code between environments. He has experience leading teams and working on projects for clients such as FTB, RBS Citizens Bank, MillerCoors, Aon, Jemena, and MHRA.
Veera Narayanaswamy is an Oracle PL/SQL developer with over 5 years of experience developing business applications using Oracle databases. He has expertise in all phases of development including analysis, design, development, testing and maintenance. He is proficient in SQL, PL/SQL, Unix scripting and tools like SQL Developer and Toad. Some of his project experience includes migrating legacy data to a new Oracle application for Kaiser Permanente, developing reports, procedures and packages to support daily data feeds for a pension fund client, and creating forms, reports and database objects for an HR application for AT&T. He is a skilled full-stack developer who enjoys working on diverse Oracle projects.
Siddhartha Bikash Sinha has over 4 years of experience as an Oracle DBA supporting multiple production databases running on AIX and Solaris servers. He has experience performing database installations, upgrades, migrations, backups, recovery and maintenance. Currently he works as an Oracle DBA for HCL Technologies supporting two large Oracle databases for Bed Bath & Beyond's return authorization and planning systems totaling over 4 terabytes in size.
Tony Reid has over 30 years of experience as a software engineer and analyst with expertise in C#, ASP, Visual Basic, databases like Oracle and SQL Server, and methodologies including Agile and Waterfall. He has strong communication skills and experience managing both in-house and offshore development teams. Currently he is a Senior Systems Analyst at Eli Lilly where he has led projects involving data migration, application development, and technical support.
Enterprise guide to building a Data MeshSion Smith
Making Data Mesh simple, Open Source and available to all; without vendor lock-in, without complex tooling and to use an approach centered around ‘specifications’, existing tools and baking in a ‘domain’ model.
This document provides an overview of querying and manipulating data using Entity Framework in .NET. It discusses Entity Framework concepts like Entity Data Models, Code First development, inheritance hierarchies, and querying. The document also covers ADO.NET connections, Entity Framework performance, and transactions. Key topics include creating EF data models, implementing POCO objects, querying with DbContext, and loading related data using lazy and eager loading.
The document discusses the database life cycle and its phases: initial study, design, implementation and loading, testing and evaluation, operation, and maintenance and evaluation. It also discusses database schema, including physical, conceptual, and external schemas. Finally, it discusses project management techniques like Gantt charts and PERT charts that can be used to plan and track database development projects.
Aden Bahdon has over 15 years of experience as an Oracle developer and database administrator, specializing in designing and implementing data warehouse solutions. He has extensive experience working on projects for clients such as IBM Canada, Bell Canada, and the Department of National Defence, where he developed databases, ETL processes, and reports. His skills include Oracle, SQL, PL/SQL, Java, DataStage, MicroStrategy, and he has experience in all phases of the software development lifecycle.
Mark Cooper is a senior DevOps cloud engineer with over 15 years of experience in cloud development, DevOps, and cloud infrastructure. He has extensive skills in Java, Python, cloud technologies like OpenStack, and DevOps tools like Chef and Ansible. His background includes roles providing automated provisioning for IBM's cloud services, developing microservices for BlueMix, and managing deployments and pipelines. He aims to deliver high-quality solutions through an agile approach and effective communication skills.
APPLICATION 2.4Projectile motionAbout 400 yr ago, the phys.docxarmitageclaire49
APPLICATION 2.4
Projectile motion
About 400 yr ago, the physicist Galileo observed that certain projectiles follow a parabolic path. For instance, if a cannon fires a shell at a 30 degree angle with a speed of 250 feet per second, then the path of the shell is modeled by the equation
,
where h is the elevation of the shell trajectory and d is the corresponding horizontal distance from the cannon when the elevation is h.
1. Does the graph of this equation open up or down? How did you determine this?
2. Describe what happens to the projectile as time passes.
3. Use the quadratic equation to determine at what distance from the cannon the shell hits the ground.
4. Will the shell be at a high point or be at a low point at the middle of the trajectory? How do you know?
5. What is the highest elevation the shell will attain?
6. When the shell is at its highest, how far (horizontally) will it be from the cannon?
7. What is the point of the vertex? How does this number relate to your answers in parts e. and f?
8.
How many solutions are there to the equation ? How do you know?
9. What do the solutions represent?
MAT/117
2
2
32
0.577
1.5(250)
hdd
=-
2
2
32
0.5770
1.5
dd
v
-=
Running Head: DATABASE MANAGEMENT 1
DATABASE MANAGEMENT 2
Advanced Database Systems(CS352-1901A-01)
Database Management
Charles Williams
1/8/2019
Table of Contents
Table of Contents…………………………………………………………………………………………………………………………………….2
The Database Models, Languages, and Architecture 3
Database System Development Life Cycle 5
Database Management Systems 6
Advanced SQL 7
Web and Data Warehousing and Mining in the Business World 8
References 9
Database management
It is important that a formal design methodology is used as it provides a mathematical approach to coming up with a reliable database that consolidates all the environments that use the database. A design methodology helps as it provides a way in which the whole designing and development can be done with minimum errors. The design methodology helps in identifying the requirements, the specifications and design levels of the database and data warehouse up for development. The planning stage of the consolidated data base is very important as it involves the coming up with plans that will guide the development of the database (Mabogunje, 2015). The plans help in managing quality, time, risks and other related issues that might affect the design and development of the database and eventually the data warehouse.
The three layers of the 3-level ANSI-SPARC architecture include; a physical schema which is responsible for defining how data is to be stored, a conceptual schema which is responsible for indexing and relating data, and the external schema which is responsible for showing how informatio.
Dave Blankenship Computer Systems Analyst Longdavebedave
Dave Blankenship is a highly experienced IT technician and computer systems analyst with skills in Sharepoint, database design, SQL, and solving complex problems. He has over 10 years of experience consulting for businesses to design mission critical solutions. His resume lists technical skills like analyzing systems, writing proposals, and communicating technical information to non-technical audiences. He has worked as an adjunct professor teaching database courses and has held roles at several companies conducting business and technical analysis, systems design, and software testing.
This document provides an overview of ADO.NET Entity Framework (EF), which is an object-relational mapping (ORM) framework that allows .NET developers to work with relational data using domain-specific objects. It discusses key EF concepts like the entity data model, architecture, features, and lifecycle. The document explains that EF maps database tables and relationships to .NET classes and allows LINQ queries over object collections to retrieve and manipulate data, hiding SQL complexity. It also covers the ObjectContext class that manages database connections and entities.
This document contains a resume for Rudhra.R summarizing their experience as an Oracle Database Administrator and Network Engineer over 6 years. They are seeking a responsible position that provides learning and growth opportunities. Their experience includes Oracle database installation, configuration, backup/recovery, user management, and monitoring production databases.
Similar to Loyd Baker: MBSE - connecting the dots process with loyd baker (20)
Tues PM banquet keynote featuring Virginia A GreimanEnergyTech2015
Virginia Greiman is professor of megaprojects and planning and international development and project finance at Boston University and holds academic appointments at Harvard University Law School and Harvard Kennedy School of Government. She is a recognized scholar on infrastructure and innovation megaprojects, project finance and governance, international law and development, cyber law and cyber security.
Brian Patterson: Reinventing Building PowerEnergyTech2015
This document discusses reinventing building power through the use of hybrid AC/DC microgrids and the creation of interconnecting microgrids called the "Enernet". It describes how distributed energy resources like solar can be harvested and connected in a massively distributed mesh network of microgrids at the building, campus and community level. Standards are being developed to allow digital on-off grid operation and the key benefits of this approach include increasing the use of renewable energy and improving reliability, security and resilience of power systems.
Matthew Hause: The Smart Grid and MBSE Driven IoT EnergyTech2015
EnergyTech2015.com
Track 3 Session 3
Moderator: Mark Walker
The integration of the Internet of Things (IoT) and MBSE in an Energy System and Complex energy grid management in a changing and dynamic future.
Matthew Hause – Paper 1: Making the Smart Grid Smarter, MBSE Driven IoT The future of IoT success, including technology advancements and revenue generating potential across the business spectrum, is dependent on the application of solid Systems Engineering and Model Based Systems Engineering (MBSE) principals. Without MBSE, the complexity involved in the design, development, and deployment of IoT systems would consume both system and operational providers. Absent of any industry standards, IoT systems cannot be built in a vacuum and their success will only be realized through application of modern day systems engineering processes, methods, and tools. The infrastructure and management will need to be established prior to, or in conjunction with, the smart systems that support them. This paper will show an Energy system and connected systems and how an MBSE and SoS approach will help guide development.
David Long Keynote on Beyond MBSE Looking Towards the Next Evolution in Syste...EnergyTech2015
This document discusses the evolution of systems engineering and the potential next steps beyond model-based systems engineering (MBSE). It begins by defining systems engineering and describing its focus on interdisciplinary processes to satisfy customer needs. It then outlines some key characteristics of modern systems and discusses how systems engineering has expanded from aerospace/defense to other domains. The document notes challenges in applying systems engineering to today's interconnected world and proposes plotting a journey beyond MBSE with steps like leveraging collective insights, aligning with reference architectures, and incorporating feedback/learning. It envisions connecting supporting theories and recognizing the future of systems engineering. The document concludes by joining engineering colleagues to enable model-based engineering and discussing how systems engineering may adapt to 21st century needs
Flora Flygt: Clean Power Plan Impact on Transmisssion Planning, Development a...EnergyTech2015
EnergyTech2015.com
Track 1 Session 2
THE U.S. ENVIRONMENTAL PROTECTION AGENCY CLEAN POWER PLAN: HOW WILL IT AFFECT THE ELECTRIC UTILITY INDUSTRY NOW AND IN THE FUTURE?
On June 2, 2014, the U.S. EPA, proposed a plan with the stated purpose of reducing carbon emissions from electric generating units, under Section 111(d) of the Clean Air Act. The CPP sets a CO2 emission target for each state, and utilizes four “building blocks” in devising those rates. The CPP suggests power to be dispatched based upon environmental considerations. Today, regional electric markets dispatch power based upon economic considerations and not environmental considerations. More than four million entities submitted comments on the proposed CPP and on August 3, 2015, the U.S. EPA issued their final plan. What is the overall affect on states, utilities, and ratepayers? What is the timeline for implementation of the CPP? What does the plan mean for the future electric generation mix? How will reliability and prices be impacted? What kinds of technology and regulatory policy changes will be needed?
Moderator: Maria Ilic, CMU Professor
Asim Haque, PUCO Commissioner
Flora Flygt, Strategy Planning & Policy Advisor, American Transmission Company
Neil Kirby: VSC HVDC Transmission and Emerging Technologies in DC GridsEnergyTech2015
The document discusses emerging HVDC transmission and grid technologies presented by Neil Kirby at EnergyTech2015. It summarizes HVDC converter types, control methods for HVDC grids using slack bus and droop control, protection challenges for DC grids, and future converter technologies like modular multi-level converters that enable DC circuit breakers. It presents diagrams and examples of various converter configurations including full bridge and alternate arm designs that could help realize more versatile and controllable DC grids.
Anne McNelis: Intelligent Power Controller Development for Human Deep Space ...EnergyTech2015
EnergyTech2015.com
SPACE POWER SYSTEMS
Track 2 Session 4 Moderator: James Soeder
This session explored power technologies being developed to enable more advanced deep space missions including; unique power systems, autonomous and intelligent control and real time simulation
Ms Anne McNellis: Paper 1: NASA Intelligent Power Control,
Dr Benjamin Loop: Paper 2: Real Time Simulation for NASA Intelligent Power Control Development
Dr Brad Glenn: Paper 3: Helm Algorithm Development for NASA Intelligent Power Control
EnergyTech2015.com
Track 2 Session 3
HYBRID ELECTRIC POWER FOR AERONAUTIC PROPULSION PANEL
Moderator: Michael Heil, Ohio Aerospace Institute
This panel will explore benefits and technology challenges associated with distributed, hybrid electric propulsion for future subsonic aeronautic vehicles. Panel members will include aeronautics propulsion industry, NASA, and the DoD.
James Felder, NASA Glenn Research Center
John Nairus, Air Force Research Lab, Chief Engineer Power & Controls Division
Neil Garrigan, GE Aviation
Meyer Benzakein, OSU - Aeronautic
Neil Garrigan: Electric Drive Technology Considerations for Aircraft Propulsion EnergyTech2015
EnergyTech2015.com
Track 2, Session 3 HYBRID ELECTRIC POWER FOR AERONAUTIC PROPULSION PANEL Monday, November 30
Moderator: Michael Heil, Ohio Aerospace Institute
This panel explored benefits and technology challenges associated with distributed, hybrid electric propulsion for future subsonic aeronautic vehicles. Panel members included aeronautics propulsion industry, NASA, and the DoD.
James Felder, NASA Glenn Research Center
John Nairus, Air Force Research Lab, Chief Engineer Power & Controls Division
Neil Garrigan, GE Aviation
Meyer Benzakein, OSU - Aeronautic
Track Two: New Technologies for Solving the Energy Puzzle Where are the breakthroughs? How will new and emerging technologies provide solutions for society energy needs? How can these be effectively integrated with existing legacy systems?
The EnergyTech conference series began in 2010 through productive dialog and interaction between technology and systems engineers / professionals within INCOSE, IEEE, and NASA GRC. The 2015 conference addresses the changing dynamics and emerging technologies in Energy, and also deals with some of the most significant, consequential risks and issues in our critical infrastructure, posing major threats to civilized existence.
A review on techniques and modelling methodologies used for checking electrom...nooriasukmaningtyas
The proper function of the integrated circuit (IC) in an inhibiting electromagnetic environment has always been a serious concern throughout the decades of revolution in the world of electronics, from disjunct devices to today’s integrated circuit technology, where billions of transistors are combined on a single chip. The automotive industry and smart vehicles in particular, are confronting design issues such as being prone to electromagnetic interference (EMI). Electronic control devices calculate incorrect outputs because of EMI and sensors give misleading values which can prove fatal in case of automotives. In this paper, the authors have non exhaustively tried to review research work concerned with the investigation of EMI in ICs and prediction of this EMI using various modelling methodologies and measurement setups.
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODELgerogepatton
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Low power architecture of logic gates using adiabatic techniquesnooriasukmaningtyas
The growing significance of portable systems to limit power consumption in ultra-large-scale-integration chips of very high density, has recently led to rapid and inventive progresses in low-power design. The most effective technique is adiabatic logic circuit design in energy-efficient hardware. This paper presents two adiabatic approaches for the design of low power circuits, modified positive feedback adiabatic logic (modified PFAL) and the other is direct current diode based positive feedback adiabatic logic (DC-DB PFAL). Logic gates are the preliminary components in any digital circuit design. By improving the performance of basic gates, one can improvise the whole system performance. In this paper proposed circuit design of the low power architecture of OR/NOR, AND/NAND, and XOR/XNOR gates are presented using the said approaches and their results are analyzed for powerdissipation, delay, power-delay-product and rise time and compared with the other adiabatic techniques along with the conventional complementary metal oxide semiconductor (CMOS) designs reported in the literature. It has been found that the designs with DC-DB PFAL technique outperform with the percentage improvement of 65% for NOR gate and 7% for NAND gate and 34% for XNOR gate over the modified PFAL techniques at 10 MHz respectively.
2. The presenter,
Loyd Baker, is VP for Technology with 3SL Inc., with extensive
experience teaching automated MBSE methods to major US
corporations and government agencies such as NASA, FAA, and
DoE.
Provides training for Cradle (https://www.threesl.com) the systems
engineering tool selected by NASA as their primary requirements
management tool.
Past president of the Huntsville Chapter of International Council on
Systems Engineering (INCOSE)
NASA Silver Snoopy Award winner for support of the Apollo
missions, including Apollo 13.
3. Systems Engineers utilize a large number of different “pieces of information”
to design, develop, analysis, and validate a new system or modifications to
an existing system
Examples of the ‘pieces of information’:
• Stakeholder Needs
• Use Cases
• Operational Scenarios
• Stakeholder Requirements
• System Requirements
• Interfaces
• System Architectures
• Verification Objectives
• Test Cases
• etc
Pieces of information
4. Category Value
Picklist
Image
Binary Frame
Linked Items
Requirement
Statement
Each dot has specific kinds of ‘attributes/properties’ that capture details
such as the requirement statement, type of requirement, etc
5. Connect the dots together to tell a story, or describe an architecture
6. A Piece of Information by itself has limited value, but when associated
with one or more other pieces of information via relationships (i.e., cross
reference links), the information has more value to the project
relationship relationship
built from
satisfies
derived req
has test
plan
consist of
has result
verified by has test
Product
(PBS)
1
System
Element
2
System
Requirement
3
Stakeholder
Requirement
4
Test Plan
5
Test Case
6
Test
Result
7
Verification
Objective
10
7. • System engineers build models to better understand problems, develop
candidate solutions, and validate design decisions.
• Models are used to tell a story or describe a concept
• Models improve communication between team members, and with the
customer.
• Ask me about an actual experence on a DOE/SRS Summer Study
Some Concepts / Stories are best communicated by a Diagram (i.e.,
conceptual model)
Cradle eFFBD
8. The Problem … In the past, projects would create Documents and
Drawings using the “pieces of information” but failed to keep and
manage the “pieces of information and their connections”.
Problem:
When project information is spread
across multiple documents, the lack
of quick access and consistency
traceability can cause issues when
project data is examined.
Difficult to assess:
• Project Completeness
• Requirement Consistency
• Architecture Integration
• Change Impacts
• Verification
• Validation
• End-to-end traceability
=
9. Today’s Model-Based Systems Engineering (MBSE) Movement is
promoting Data-Model Centric processes rather than the traditional
Document Centric processes.
Document Centric (past) Model-Based Centric (future)
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
Constraining
RequirementConstraining
Requirement
Cradle
ISSUE
Verification
SBS
Trade Study
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
Constraining
RequirementConstraining
Requirement
Cradle
ISSUE
Verification
SBS
Trade Study
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
C
R
Cradle
ISSUE
Verificat
SBS
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
C
R
Cradle
ISSUE
Verificat
SBS
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Project Information Repository
maintained and possibility
delivered to the customer
The Project’s Systems Engineering Processes identify the data to be captured.
10. Select the MBSE Process to be used on your project by studying existing
documented processes
Technical Management Processes
• Decision Analysis
• Technical Planning
• Technical Assessment
• Requirements Management
• Architecture Management
• Risk Management
• Configuration Management
• Technical Data Management
• Interface Management
• Traceability Management
Technical Processes
• Requirements Development
• Logical Architecture
• Physical Architecture
• Design Solution
• Implementation
• Integration
• Verification
• Validation
• Transition
11. Based on your projects SE process, and project deliverables, define the
set of “dots” and their “connections” to be captured for your project. An
example database structure for a large NASA project is as follows.
12. 1. “Foundational Concepts for Model Driven System Design,” white paper, INCOSE Model
Driven System Design Interest Group, International Council on Systems Engineering,
Jul. 15, 2000, by Loyd Baker, Paul Clemente, Bob Cohen, Larry Permenter, Byron
Purves, and Pete Salmon
2. Engineering Complex Systems with Models and Objects, by David W. Oliver, Timothy
P. Kelliher, and James G. Keegan
3. Streamlining Requirements Development through Model-based Systems Engineering,
by Robert Bayt, Ann Christian, Philip Nerren, and Rich DeLoof, NASA PM Challenge
2010
4. A Practical Guide to SysML, by Sanford Friedenthal, Alan Moore, and Rick Steiner
5. SysML Distilled, A Brief Guide To The Systems Modeling Language, by Lenny Delligatti
6. Requirements Definition and Management Using Cradle, by Loyd Baker, 2014,
https://www.threesl.com/pages/news/webletter-November14/REQ-Cradle-white-paper-
v8-1.pdf
Model-Based Systems Engineering References
13. Features Model-Based System Engineering Document Centered System
Design
Information Repository Models (Data & Diagrams) Documents
Reviews (SDR, PDR,
CDR)
By interrogating data & diagrams
(automated)
Read & interpret text then compare
Verification Implicit, incremental, automated, built
into the process
Human audit process
Communication Reproducible and consistent Answers may depend on readers
perspective
Validation Execute in different contexts (e.g.
customer’s context, end-users context,
etc)
Walk-through, reviews of paper
Traceability Integral Accuracy is labor intensive
•Expressiveness. The ability to express complex information in ways that are easily
understood. Models can achieve this expressive power through logical and physical
representations.
•Rigor. Compared with textual representations, executable models provide clear and
unambiguous definitions of behavior, capability or design.
Benefits of MBSE over document centric approaches accrue from two
essential features of a good model:
This information taken from reference 1 on the previous slide.
14. These PrimaryConcurrent/Iterative Activities Are Performed ForEach
Product/System Architecture DesignLayer
RequirementsDefinition
•Identify Stakeholders and Source Material
•Identify OperationalContext and Use cases
•OperationalScenarios, Info Exchange
•Establish StakeholderRequirements Set
•Establish MOEs, Design Constraints
•Capture Issues / Risks / Decisions
LogicalArchitecture
Analysis
•Develop System FunctionalModels
•Establish Traceability Between the Functions
and Requirements
•Define Logical I/O
•Allocate Functions to Architecture Entities
•Allocate Logical I/O to Interfaces
PhysicalArchitecture
Analysis
•Identify Architecture Structure (i.e.,
Hierarchy of Architecture Entities) and
PhysicalInterfaces
•Analyze Allocated Functions and I/O
•Allocate Constraining Requirements to
Architecture Entities
•Risk Assessment
•Compliance & Cost Assessment
•Design Verification & Validation
ProductEvaluation & DocumentGeneration
AnalysisResults
Specifications
•Configuration Management
•Test Planning
•Metrics
Functional Models Physical Architecture Views
Architecture Entity List
TechnicalRules,Standards,and Conventions
R1-1
R1 R2
R
Issue
Risk
F1 F5
F2 F3
F4
System of Systems
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Example Model-Based Systems Engineering Process
15. Apply Project Processes in Layers to Reduce Risk
Product Architecture Design activities are used to transform agreed-upon source
requirements and constraints into a design solution with a proper balance between
performance, risk, cost, and schedule.
Requirements Definition Logical Architecture
Analysis
Physical Architecture
Analysis
Product
Evaluation
&
Document
Generation
Stakeholder
Needs
&
Source
Material
System
Functional
Models
Allocate
Functions
to System
and next
level
System
Interfaces
Design
Layer
“1” Design
Constraints
System
Structure
Operational
Context,
Use Cases,
Scenarios
System
Requirements
Physical Architecture
Analysis
Product
Evaluation
&
Document
Generation
Subsystem
Functional
Models
Subsystem
Interfaces
Design
Layer
“n” Subsystem
Structure
Requirements Definition
Subsystem
Requirements
Design
Constraints
Design
in Layers
System
Spec
Subsystem
Spec
Analyze
Allocated
Functions
&
Interfaces
Allocate
Functions
to
Subsystem
and next
level
Analyze
Allocated
Functions
&
Interfaces
Operational
Context,
Use Cases,
Scenarios
Logical Architecture
Analysis
16. Integrate Models & Requirements at each Level of the Architecture
Structure
Architecture Level 1 Models
Child Child Child
Requirement
Child Child Child
Requirement
Subsys X.3 Functional Model
System Breakdown Structure (SBS)
Architecture Level 2 Models
Parent
to child
traces
Parent
to child
traces
Horizontal Traceability
Vertical Traceability
Equip X.3
Equip X.3.1 Equip X.3.2 EquipX.3.3
Subsys X.3
Subsys X.3.1 Subsys X.3.2 SubsysX.3.3
SBS 1.3.1 SBS 1.3.2 SBS1.3.3
SBS 1
SBS1.1 SBS1.3SBS 1.2
Child Child Child
Requirement
Child Child Child
Requirement
System X Functional Model
Equip X
Equip X.1 Equip X.2 EquipX.3
System X
Subsys X.1 Subsys X.2 SubsysX.3
operation 1
Data
operation 2operation 1
DataData
operation 2
Operational Scenarios
operation 1
Data
operation 2operation 1
DataData
operation 2
Operational Scenarios
17. • The Modeling Notations used to support each process activity are identified. The
Cradle systems engineering support tool was used.
• Cradle did not support SysML at the time the project was going on so traditional
eFFBDs (enhanced Function Flow Block Diagrams) and PADs (Physical
Architecture Diagrams) were used. Cradle SysML support will be available in the
1QT 2016 allowing future projects to choose which notations best satisfy their
project needs.
• The project performed timeline analyses of the mission events using the Cradle-
Excel Timeline Analysis Tool.
• The actual NASA Models are not shown because they have not been approved
for public release.
MBSE Activities Used Successfully on one NASA Project are Presented
on the Following Slides
18. The MBSE activities were grouped into eight stages as shown in the following figure.
The Iterate nodes (circles with embedded I symbol inside) in the above process
diagram indicates that all stages between the two Iterate nodes are repeated for each
level in the system architecture hierarchy.
The Parallel nodes (circles with embedded AND symbol inside) indicate that the
stages (3, 4, and 5) between the two ‘AND’ nodes can be performed concurrently.
MBSE Activities Used Successfully on one NASA Project
19. Stage 1- Define Concept of Operations & Stakeholder Requirements
The activities in this stage are performed at project start-up to define the project scope, prepare
a concept of operations (ConOps), and then develop the set of stakeholder requirements and
publish in a Stakeholder Requirements Document (SRD).
20. Cradle Process Flow Diagrams (PFDs) are used to identify the operations needed to
accomplish a use case. These PFDs are known as Operational Scenario Diagrams. The
identified operations aid the user in deriving the necessary stakeholder requirements.
Stage 1- Define Concept of Operations & Stakeholder Requirements :2
21. The following example Cradle traceability table shows the Stakeholder Requirements derived
from Scenario Operations which describe a specific use case. Scenario Operations were
identified on the PFD shown on the previous slide.
Stage 1- Define Concept of Operations & Stakeholder Requirements :3
22. Stage 2 - Define System/System Element Context
The activities in this stage will develop a System Context Diagram for a primary system element
to identify all external entities that must interact with the system element and the required
external interfaces. These external interfaces must be identified prior to beginning stages 3
through 7.
23. Stage 3 - Define System Elements
The activities in this stage are for defining physical characteristics for the specified system
element and then derive the appropriate system requirements for that element, then break-down
the system element into its component parts (one level down the hierarchy), and identify a draft
set of physical characteristics for each subordinate element.
Primary “System Element” for
which Requirements are being
defined during current design
cycle
Always go one level deeper in
hierarchy and identify candidate
draft Child “System Elements”.
Next cycle each Child Element
becomes the primary and the
process is repeated.
24. A System Element’s Structure (its component parts one level down the hierarchy) are
identified in order to allocate functions and requirements to the component parts. This Cradle
diagram is also known as a Physical Architecture Diagram (PAD).
Stage 3 - Define System Elements :2
25. Stage 4 - Define Functional Behavior
Identify system functions and their inputs and outputs that satisfy the system element functional
requirements identified in the previous design cycle. These functions, when integrated together,
describe the desired behavior the system element must exhibit. In stage 5, the functions /
interfaces will be allocated to specific system elements (i.e., the things that must perform the
functions).
ANDFunction2
Function3
Function4
Data
Sub-Function
ofFunction4
Sub-Function
Of Function4
Data
Functional
System
Requirement
Functional
System
Requirement
Satisfy
Satisfy
Derived Req
Functional
System
Requirement
Satisfy
26. The Cradle enhanced Functional Flow Block Diagram (eFFBD) describes the desired behavior
the system element must exhibit. This diagram is also known as a Behavior Diagram. It is
used to define system functions from which Functional Requirements are derived.
Stage 4 - Define Functional Behavior :2
27. The following Cradle traceability table shows the Functional Requirements derived from the
system functional behavior described on the eFFBD shown on the previous slide.
Stage 4 - Define Functional Behavior :3
28. Stage 5 -Allocate Functions & Interfaces to System Elements
In this stage, the functions and I/O (identified in stage 4) are assigned to different system
elements and interfaces.
1. Functional allocation assigns desired behavior to the different system elements.
SystemElement SystemElement
System
INTERFACE
Derived
Nonfunctional System
Requirements
Derived
FunctionalSystem
Requirements
Derived
InterfaceSystem
Requirements
allocate
satisfy
satisfy
allocate
satisfy
Data
ANDFunction1 Function2
Function3
Function4
Data
satisfy
29. Stage 5 -Allocate Functions & Interfaces to System Elements :2
2. Based on the I/O produced and consumed by the functions being allocated to system
elements, candidate physical interfaces between the system elements are identified.
Derived
Nonfunctional System
Requirements
Derived
Interface
Requirements
30. 3. Because each allocated function and interface has traceability links to requirements being
satisfied, those requirements are indirectly being allocated to the system elements and
interfaces.
SystemElement SystemElement
System
INTERFACE
Derived
Nonfunctional System
Requirements
Derived
FunctionalSystem
Requirements
Derived
InterfaceSystem
Requirements
allocate
satisfy
satisfy
allocate
satisfy
Data
ANDFunction1 Function2
Function3
Function4
Data
satisfy
Stage 5 -Allocate Functions & Interfaces to System Elements :3
31. The following Cradle traceability table shows the Functional and Non-Functional Requirements
allocated to the System Elements. (i.e., Equipment items in Cradle).
Stage 5 -Allocate Functions & Interfaces to System Elements :4
32. The following Cradle traceability table shows the Interface Requirements allocated to the Data
Definition (DD) interfaces identified on the Physical Architecture Diagram (PAD).
Stage 5 - Allocate Functions & Interfaces to System Elements :5
33. Stage 6 - System RequirementsAnalysis & Verification Planning
The system requirements derived in stages 3-5 are analyzed for clarity, completeness,
consistency, traceability to the stakeholder or system requirements baselined at the end of the
previous design cycle. Also, verification and test planning activities should be performed for the
newly created system requirements and appropriate traceability established..
built from
satisfies
derived req
has test
plan
consist of
has result
verified by
identifies
has test
Product
(PBS)
1
System
Element
2
System
Requirement
3
Stakeholder
Requirement
4
Test Plan
5
Test Case
6
Test
Result
7
Use Case
(Specification)
8
Verification
Objective
10
34. Assign Times (durations and optionally fixed start times) to the Functions and dynamically
execute them. To verify functions are executed in the desired time ordered sequence.
Simulation Times (Days / HH : MM : SS)
Perform TimeLine Analysis of Specified Behavior (i.e., Functional Models)
36. Timeline Setup Sheet Lists the Functions and Times downloaded from Cradle
These values (Fixed Start Time, Duration, and Fixed End
Time) are read from the function specifications in the Cradle
database associated with the exported models
This Decomposition flag is read from the
Diagram’s Group attribute in the Cradle
database. It is set to 1 in the database to
indicate that the function’s decomposition is to
be included in the analysis
37. Results of the simulation are displayed on the “Timeline Results Sheet”
Computed Simulation Times (function start and end times)
Verify functions executed in the desired order with correct I/O
38. Stage 7 - Generate Documentation for System/System Elements
Whether for review and approval, reference documentation, training or other uses; producing
documentation is a vital and often time consuming activity for a project. Cradle’s ability to
produce reports and Word documents in an automated and customized fashion supports the
project’s documentation needs while saving time and ensuring consistency with documentation
formats and standards.
Master Test Plan
System
Requirements
Document (SRD)
System Architecture
Description
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
Constraining
RequirementConstraining
Requirement
Cradle
ISSUE
Verification
SBS
Trade Study
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
Constraining
RequirementConstraining
Requirement
Cradle
ISSUE
Verification
SBS
Trade Study
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
Constraining
RequirementConstraining
Requirement
Cradle
ISSUE
Verification
SBS
Trade Study
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Reference
DocumentReference
Document
System
Performance
Requirement
Performance
Requirement
Constraining
RequirementConstraining
Requirement
Cradle
ISSUE
Verification
SBS
Trade Study
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Mission 1
Mission 2
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Pre-Launch Launch On-orbit
Operation Scenario #3Pre-Launch Launch On-orbit
Operational Scenario #1
Pre-Launch Launch On-orbit
-Point
Camera
Take
picture
Operational Scenario #2
Store
picture
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
Data
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Func 1 Func 2
Func 3
Func 4
DataData
Analysis
Cradle Information Repository
39. Stage 8 – System Verification & Validation (V&V)Traceability
Capture the status of each V&V activity in the database with traceability back to the impacted
requirement and operational scenarios.
• Verification Traceability. The purpose of the Verification Process is to confirm that the specified
design requirements (i.e., System Requirements) are fulfilled by the system.
• Validation Traceability. The purpose of the Validation Process is to provide objective evidence
that the services provided by a system when in use comply with stakeholders’ requirements,
achieving its intended use in its intended operational environment.
40. Is Model Based Systems Engineering (MBSE) something new? No, MBSE
methods and techniques have been individually practiced by many good
engineers and analyst over the years. The MBSE process presented in this
presentation was about “Connecting the Dots”.
The problem has been that project management has been obsessed with
‘deliverable documents’ rather than delivering an engineering data-model that
can be used to support analyses, end-to-end traceability, and automatically
produce the deliverable documents from the data-model.
• The engineering data-model usually consists of entities, attributes,
relationships, and diagrams that specify the system architecture.
• Remember a diagram (graphical model) is worth a thousand words. These
diagrams aid in communicating ideas/concepts among project personnel and
the customer.
• What is new is the SysML modeling language. It should help with
communication issues by having a common way to describe system
architectures.
Please contact me at loyd.baker@threesl.com to discuss MBSE processes
In Summary