The document discusses an architecture modeling methodology for model-based systems engineering projects. It involves developing hierarchical architecture models, using the models to derive requirements, and tracing requirements to model elements. The methodology includes context diagrams to illustrate physical elements outside the system, decomposing physical and operational/functional elements, and using operational scenarios to develop mission operations and system functions. The modeling approach aims to generate a complete picture of the architecture and stakeholder problem.
This document introduces the concept of projective analysis (PAN) and discusses its use in enterprise modeling. PAN elicits clients' models of their ecosystems and analyzes the sustainability of their strategies while illustrating risks. It is based on the idea that enterprises are sociotechnical systems composed of autonomous components that collaborate voluntarily. Modeling such systems requires accounting for their open nature and interactions with the environment. PAN models demand as arising from actors' self-models and anticipation of needs within their context of use. The technique aims to capture both predictable and emergent behaviors.
Integration of a Regular Application into a User Interface Adaptation Engine ...icchp2012
Virtual User Models for Designing and Using Inclusive Products - Integration of a Regular Application into a User Interface Adaptation Engine in the MYUI Project - Sanchez, Victor (s)
R&M Technologies provides reliability, maintainability and logistics support analysis services. It developed RamLog software in 1992 to manage lifecycle logistics data. RamLog includes capabilities like FMECA, RCM analysis, maintenance task analysis, technical manual authoring, and a simulation edition to model system operations and support over the lifecycle. RamLog integrates with RAMLOG.NET for transactional database support.
Model Runway Part 2 Design Best Practices at Blue Cross BlueShieldRoger Snook
This document provides an overview and agenda for a webinar on system modeling with M3, an IBM Rational software framework. The webinar will recap the previous session, walk through an example RSA (Rational Software Architect) construction, and summarize the M3 modeling framework. The framework uses models at different levels - computation independent (CIM), platform independent (PIM), and platform specific (PSM) - with defined workflows, components, and UML diagrams. The example models an online shopping system to demonstrate the CIM, PIM and PSM levels.
The document discusses architectural UML and provides information on:
1) The elements of a software architecture including views, models, and diagrams.
2) How UML can be used to represent different architectural views including design, process, development, and physical views.
3) An example of using UML models and diagrams to represent different views of a chess game architecture.
Reliability based approach for structural design and assessment performance c...StroNGER2012
This document discusses reliability-based approaches for structural design and assessment based on performance criteria and indicators in current European codes and guidelines. It is organized into three parts that discuss general aspects of structural design, performance indicators for assessing existing structures, and the concepts of robustness and dependability in structural systems. The document advocates for a system engineering approach to structural design that considers structures as complex systems and decomposes them into interconnected elements and components. Key concepts discussed include performance-based design, structural system quality management, and reliability-based design criteria.
1) The document discusses various software and hardware for copying and converting DVDs and VHS tapes, including DVD copying software, DVD burning software, and devices like the Dazzle Video Creator Platinum that allow converting VHS tapes to DVD format.
2) It explains different DVD formats like DVD-R, DVD+R, dual-layer DVDs, and differences between burning, copying, and dubbing video formats.
3) Instructions are provided on labeling home-copied DVDs using template software and blank labels.
The 5 principles of Model Based Systems Engineering (MBSE)James Towers
The document outlines the 5 principles of model-based systems engineering (MBSE):
1. Each model view has a defined purpose and scope.
2. Modeling adds value by being more accessible and useful than real-world systems.
3. Models must be of sufficient quality by being concise, consistent, coherent, and correct.
4. Models are constructed from appropriate elements like languages, paradigms and topologies.
5. Architectural frameworks, process frameworks, competent people, and appropriate tools enable effective MBSE.
This document introduces the concept of projective analysis (PAN) and discusses its use in enterprise modeling. PAN elicits clients' models of their ecosystems and analyzes the sustainability of their strategies while illustrating risks. It is based on the idea that enterprises are sociotechnical systems composed of autonomous components that collaborate voluntarily. Modeling such systems requires accounting for their open nature and interactions with the environment. PAN models demand as arising from actors' self-models and anticipation of needs within their context of use. The technique aims to capture both predictable and emergent behaviors.
Integration of a Regular Application into a User Interface Adaptation Engine ...icchp2012
Virtual User Models for Designing and Using Inclusive Products - Integration of a Regular Application into a User Interface Adaptation Engine in the MYUI Project - Sanchez, Victor (s)
R&M Technologies provides reliability, maintainability and logistics support analysis services. It developed RamLog software in 1992 to manage lifecycle logistics data. RamLog includes capabilities like FMECA, RCM analysis, maintenance task analysis, technical manual authoring, and a simulation edition to model system operations and support over the lifecycle. RamLog integrates with RAMLOG.NET for transactional database support.
Model Runway Part 2 Design Best Practices at Blue Cross BlueShieldRoger Snook
This document provides an overview and agenda for a webinar on system modeling with M3, an IBM Rational software framework. The webinar will recap the previous session, walk through an example RSA (Rational Software Architect) construction, and summarize the M3 modeling framework. The framework uses models at different levels - computation independent (CIM), platform independent (PIM), and platform specific (PSM) - with defined workflows, components, and UML diagrams. The example models an online shopping system to demonstrate the CIM, PIM and PSM levels.
The document discusses architectural UML and provides information on:
1) The elements of a software architecture including views, models, and diagrams.
2) How UML can be used to represent different architectural views including design, process, development, and physical views.
3) An example of using UML models and diagrams to represent different views of a chess game architecture.
Reliability based approach for structural design and assessment performance c...StroNGER2012
This document discusses reliability-based approaches for structural design and assessment based on performance criteria and indicators in current European codes and guidelines. It is organized into three parts that discuss general aspects of structural design, performance indicators for assessing existing structures, and the concepts of robustness and dependability in structural systems. The document advocates for a system engineering approach to structural design that considers structures as complex systems and decomposes them into interconnected elements and components. Key concepts discussed include performance-based design, structural system quality management, and reliability-based design criteria.
1) The document discusses various software and hardware for copying and converting DVDs and VHS tapes, including DVD copying software, DVD burning software, and devices like the Dazzle Video Creator Platinum that allow converting VHS tapes to DVD format.
2) It explains different DVD formats like DVD-R, DVD+R, dual-layer DVDs, and differences between burning, copying, and dubbing video formats.
3) Instructions are provided on labeling home-copied DVDs using template software and blank labels.
The 5 principles of Model Based Systems Engineering (MBSE)James Towers
The document outlines the 5 principles of model-based systems engineering (MBSE):
1. Each model view has a defined purpose and scope.
2. Modeling adds value by being more accessible and useful than real-world systems.
3. Models must be of sufficient quality by being concise, consistent, coherent, and correct.
4. Models are constructed from appropriate elements like languages, paradigms and topologies.
5. Architectural frameworks, process frameworks, competent people, and appropriate tools enable effective MBSE.
The document introduces the artITecture Architecture Method for documenting solution level architecture. It describes the method's primary and secondary deliverables for describing different aspects of the architecture. The primary deliverables are software, infrastructure, integration, and data architectures. Architectural thinking considers all phases of the system lifecycle and links to project management. Principles of the method include considering all lifecycle phases and project management implications.
Model Runway: Design Best Practices at BlueCross BlueShieldRoger Snook
From the developerWorks series, Good Design is Good Business: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/model_runway_see_the_latest_design_best_practices_at_bluecross_blueshield24?lang=en
Software Architecture: views and viewpointsHenry Muccini
This is an introductory lecture to Software Architecture Views and Viewpoints, part of the Advanced Software Engineering course, at the University of L'Aquila, Italy (www.di.univaq.it/muccini/SE+/2012)
The document discusses Model-driven Architecture building for constrained systems using the ARCADIA method. ARCADIA is a model-based architecture engineering approach that starts from standards like DoDAF and IEEE 1471, and integrates and enriches them with additional viewpoints and non-functional analysis capabilities. It allows collaborative validation of architectures through standards. The method involves formalizing and sharing operational and system needs models, and then developing logical and physical architecture models. These models can then be automatically analyzed using multiple viewpoints like safety, performance, and cost to validate and optimize the solution architecture.
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
The document outlines an approach to architecture development that involves:
1. Defining objectives, inputs, steps and outputs for developing the architecture.
2. Developing business, information systems, data, application and technology architectures through baseline descriptions, target descriptions, gap analysis and roadmaps.
3. Identifying opportunities and solutions which includes consolidating gaps, reviewing objectives and migration strategies, and defining transition architectures.
This document presents a model for evaluating the availability of automotive software architectures. The model is implemented as a reasoning framework in the ArchE architecture expert system. The model analyzes how effective watchdog mechanisms are in improving system availability when failures occur. A watchdog is a separate processor that monitors the main CPU and triggers a reset if the CPU fails. The model allows architects to quantitatively analyze how well their design meets availability requirements and identifies improvements to better handle failures.
This document discusses different techniques for extracting architecture from code, including clustered-based and pattern-based techniques. Clustered-based techniques like FOCUS and ROMANTIC group components using hierarchical clustering. Pattern-based techniques use a top-down approach with human guidance to identify architectural patterns in code. The document also covers motivation for architecture extraction, including handling legacy code and system evolution.
This document discusses using patterns to guide architecture evolution in service-driven systems. It proposes identifying recurring architecture change patterns from logs, formally specifying patterns in a catalogue, and reusing patterns to support evolution. An example evolution case integrating a new component is presented. A pattern-based evolution process involves specifying changes, retrieving relevant patterns, and instantiating patterns to implement the changes. The approach is experimentally analyzed using evaluation scenarios and a prototype for automated pattern-based evolution. Maintaining a pattern library could help discover, specify and reuse patterns to guide architecture-centric software evolution.
The document discusses pattern-driven reuse for architecture evolution in service-driven systems. It proposes using change patterns to specify recurring architecture changes. Patterns are specified as graphs and stored in a graph database. Evolution is guided by a 3-step process: 1) specifying the change context, 2) retrieving relevant patterns, and 3) instantiating patterns to evolve the architecture. Change patterns provide a reusable abstraction to support architecture evolution.
This document summarizes a presentation about identifying patterns in architecture change logs. It discusses analyzing change logs to discover recurring patterns that can guide future architecture evolution. The key points are: 1) Change logs provide a history of architectural changes over time; 2) Graph-based modeling of change instances enables formal analysis to identify operationalization patterns and dependencies; 3) Identifying patterns from past changes allows potential reuse in guiding future architecture evolution.
The document discusses software architecture documentation. It provides goals for architecture documentation, including presenting common views, defining stakeholders, identifying their concerns, and defining what and how to document. It also discusses the scope of the documentation. Finally, it discusses different approaches to software architecture documentation, including the Rational Unified Process (RUP) and Software Engineering Institute (SEI) methods. The document aims to provide guidance on effective software architecture documentation.
The document discusses two popular enterprise architecture frameworks - TOGAF and Zachman. It provides an overview of what enterprise architecture is, its key drivers and benefits. It then describes the major components of TOGAF including the Architecture Development Method (ADM) and supporting artifacts. Next, it outlines the Zachman Framework and how it classifies architectures based on perspectives and communication questions. Finally, it summarizes the benefits architectures provide including standardized processes, reduced complexity and improved decision making.
The document presents the "4+1" view model for describing software architectures. It consists of five views: the logical view, process view, physical view, development view, and use case scenarios. Each view addresses different stakeholder concerns and can be described using its own notation. The logical view describes the object-oriented decomposition. The process view addresses concurrency and distribution. The physical view maps software to hardware. The development view describes module organization. Together these views provide a comprehensive architecture description that addresses multiple stakeholder needs.
The document presents the "4+1" view model for describing software architectures. It consists of five views: the logical view, process view, physical view, development view, and use case scenarios. Each view addresses different stakeholder concerns and can be described using its own notation. The logical view describes the object-oriented decomposition. The process view addresses concurrency and distribution. The physical view maps software to hardware. The development view describes module organization. Together these views provide a comprehensive architecture description that addresses multiple stakeholder needs.
This document discusses business analysis methodologies and frameworks. It defines a methodology as describing who performs what tasks using what inputs to produce what outputs, when, how, and why. A framework is described as a partially completed solution with options for completion. The document outlines the Unified Methodology Architecture (UMA) components of roles, tasks, inputs, outputs, processes, and guidance. It presents a business analysis framework that maps requirements from business objectives to technical requirements. Finally, it discusses how methodologies and frameworks can be customized based on factors like competency levels and technique complexity.
The document outlines the steps and outputs involved in establishing an architecture capability and practice within an organization. It describes establishing the business, data, application, and technology architectures required to define the architecture practice. It then provides detailed steps and outputs for various architecture activities like developing the architectural vision, business architecture, data architecture, and transition planning.
A classification framework for component modelsIvica Crnkovic
In the last decade a large number of different software component models have been developed, with different aims and using different principles and technologies. This has resulted in a number of models which have many similarities, but also principal differences, and in many cases unclear concepts. Component-based development has not succeeded in providing standard principles, as has, for example, object-oriented development. In order to increase the understanding of the concepts, and to differentiate component models more easily, this paper identifies, discusses and characterises fundamental principles of component models, and provides a Component Model Classification Framework based on these principles. Further, the paper classifies a large number of component models using this framework.
The document compares the operational complexity and costs of the Space Shuttle versus the Sea Launch Zenit rocket. [1] The Space Shuttle was designed for performance but not operational efficiency, resulting in costly ground, mission planning, and flight operations. [2] In contrast, the Zenit rocket was designed from the start to have automated and robust processes to keep operations simple and costs low. [3] The key lesson is that designing a launch system with operational requirements in mind from the beginning leads to much more efficient operations long-term.
The document provides an overview of project management and procurement at NASA. It discusses the key skills required for project managers, including acquisition management. It notes that 80-85% of NASA's budget is spent on contracts, and procurement processes are complex and constantly changing. The document outlines some common contract types and how they allocate risk between the government and contractor. It also discusses the relationship between contracting officers and project managers, and how successful procurement requires effective communication rather than direct control or authority.
The document introduces the artITecture Architecture Method for documenting solution level architecture. It describes the method's primary and secondary deliverables for describing different aspects of the architecture. The primary deliverables are software, infrastructure, integration, and data architectures. Architectural thinking considers all phases of the system lifecycle and links to project management. Principles of the method include considering all lifecycle phases and project management implications.
Model Runway: Design Best Practices at BlueCross BlueShieldRoger Snook
From the developerWorks series, Good Design is Good Business: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/model_runway_see_the_latest_design_best_practices_at_bluecross_blueshield24?lang=en
Software Architecture: views and viewpointsHenry Muccini
This is an introductory lecture to Software Architecture Views and Viewpoints, part of the Advanced Software Engineering course, at the University of L'Aquila, Italy (www.di.univaq.it/muccini/SE+/2012)
The document discusses Model-driven Architecture building for constrained systems using the ARCADIA method. ARCADIA is a model-based architecture engineering approach that starts from standards like DoDAF and IEEE 1471, and integrates and enriches them with additional viewpoints and non-functional analysis capabilities. It allows collaborative validation of architectures through standards. The method involves formalizing and sharing operational and system needs models, and then developing logical and physical architecture models. These models can then be automatically analyzed using multiple viewpoints like safety, performance, and cost to validate and optimize the solution architecture.
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
The document outlines an approach to architecture development that involves:
1. Defining objectives, inputs, steps and outputs for developing the architecture.
2. Developing business, information systems, data, application and technology architectures through baseline descriptions, target descriptions, gap analysis and roadmaps.
3. Identifying opportunities and solutions which includes consolidating gaps, reviewing objectives and migration strategies, and defining transition architectures.
This document presents a model for evaluating the availability of automotive software architectures. The model is implemented as a reasoning framework in the ArchE architecture expert system. The model analyzes how effective watchdog mechanisms are in improving system availability when failures occur. A watchdog is a separate processor that monitors the main CPU and triggers a reset if the CPU fails. The model allows architects to quantitatively analyze how well their design meets availability requirements and identifies improvements to better handle failures.
This document discusses different techniques for extracting architecture from code, including clustered-based and pattern-based techniques. Clustered-based techniques like FOCUS and ROMANTIC group components using hierarchical clustering. Pattern-based techniques use a top-down approach with human guidance to identify architectural patterns in code. The document also covers motivation for architecture extraction, including handling legacy code and system evolution.
This document discusses using patterns to guide architecture evolution in service-driven systems. It proposes identifying recurring architecture change patterns from logs, formally specifying patterns in a catalogue, and reusing patterns to support evolution. An example evolution case integrating a new component is presented. A pattern-based evolution process involves specifying changes, retrieving relevant patterns, and instantiating patterns to implement the changes. The approach is experimentally analyzed using evaluation scenarios and a prototype for automated pattern-based evolution. Maintaining a pattern library could help discover, specify and reuse patterns to guide architecture-centric software evolution.
The document discusses pattern-driven reuse for architecture evolution in service-driven systems. It proposes using change patterns to specify recurring architecture changes. Patterns are specified as graphs and stored in a graph database. Evolution is guided by a 3-step process: 1) specifying the change context, 2) retrieving relevant patterns, and 3) instantiating patterns to evolve the architecture. Change patterns provide a reusable abstraction to support architecture evolution.
This document summarizes a presentation about identifying patterns in architecture change logs. It discusses analyzing change logs to discover recurring patterns that can guide future architecture evolution. The key points are: 1) Change logs provide a history of architectural changes over time; 2) Graph-based modeling of change instances enables formal analysis to identify operationalization patterns and dependencies; 3) Identifying patterns from past changes allows potential reuse in guiding future architecture evolution.
The document discusses software architecture documentation. It provides goals for architecture documentation, including presenting common views, defining stakeholders, identifying their concerns, and defining what and how to document. It also discusses the scope of the documentation. Finally, it discusses different approaches to software architecture documentation, including the Rational Unified Process (RUP) and Software Engineering Institute (SEI) methods. The document aims to provide guidance on effective software architecture documentation.
The document discusses two popular enterprise architecture frameworks - TOGAF and Zachman. It provides an overview of what enterprise architecture is, its key drivers and benefits. It then describes the major components of TOGAF including the Architecture Development Method (ADM) and supporting artifacts. Next, it outlines the Zachman Framework and how it classifies architectures based on perspectives and communication questions. Finally, it summarizes the benefits architectures provide including standardized processes, reduced complexity and improved decision making.
The document presents the "4+1" view model for describing software architectures. It consists of five views: the logical view, process view, physical view, development view, and use case scenarios. Each view addresses different stakeholder concerns and can be described using its own notation. The logical view describes the object-oriented decomposition. The process view addresses concurrency and distribution. The physical view maps software to hardware. The development view describes module organization. Together these views provide a comprehensive architecture description that addresses multiple stakeholder needs.
The document presents the "4+1" view model for describing software architectures. It consists of five views: the logical view, process view, physical view, development view, and use case scenarios. Each view addresses different stakeholder concerns and can be described using its own notation. The logical view describes the object-oriented decomposition. The process view addresses concurrency and distribution. The physical view maps software to hardware. The development view describes module organization. Together these views provide a comprehensive architecture description that addresses multiple stakeholder needs.
This document discusses business analysis methodologies and frameworks. It defines a methodology as describing who performs what tasks using what inputs to produce what outputs, when, how, and why. A framework is described as a partially completed solution with options for completion. The document outlines the Unified Methodology Architecture (UMA) components of roles, tasks, inputs, outputs, processes, and guidance. It presents a business analysis framework that maps requirements from business objectives to technical requirements. Finally, it discusses how methodologies and frameworks can be customized based on factors like competency levels and technique complexity.
The document outlines the steps and outputs involved in establishing an architecture capability and practice within an organization. It describes establishing the business, data, application, and technology architectures required to define the architecture practice. It then provides detailed steps and outputs for various architecture activities like developing the architectural vision, business architecture, data architecture, and transition planning.
A classification framework for component modelsIvica Crnkovic
In the last decade a large number of different software component models have been developed, with different aims and using different principles and technologies. This has resulted in a number of models which have many similarities, but also principal differences, and in many cases unclear concepts. Component-based development has not succeeded in providing standard principles, as has, for example, object-oriented development. In order to increase the understanding of the concepts, and to differentiate component models more easily, this paper identifies, discusses and characterises fundamental principles of component models, and provides a Component Model Classification Framework based on these principles. Further, the paper classifies a large number of component models using this framework.
The document compares the operational complexity and costs of the Space Shuttle versus the Sea Launch Zenit rocket. [1] The Space Shuttle was designed for performance but not operational efficiency, resulting in costly ground, mission planning, and flight operations. [2] In contrast, the Zenit rocket was designed from the start to have automated and robust processes to keep operations simple and costs low. [3] The key lesson is that designing a launch system with operational requirements in mind from the beginning leads to much more efficient operations long-term.
The document provides an overview of project management and procurement at NASA. It discusses the key skills required for project managers, including acquisition management. It notes that 80-85% of NASA's budget is spent on contracts, and procurement processes are complex and constantly changing. The document outlines some common contract types and how they allocate risk between the government and contractor. It also discusses the relationship between contracting officers and project managers, and how successful procurement requires effective communication rather than direct control or authority.
The document introduces the NASA Engineering Network (NEN), which was created by the Office of the Chief Engineer to be a knowledge management system connecting NASA's engineering community. The NEN integrates various tools like a content management system, search engine, and collaboration tools. It provides access to key knowledge resources like NASA's Lessons Learned database and engineering databases. The NEN is working to expand by adding more communities, engineering disciplines, and knowledge repositories.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, tracking satellites, inventory management, procedures viewing, and videoconferencing. Managing laptops in space presents challenges around cooling, power, and software/hardware compatibility in the harsh space environment.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, planning rendezvous and proximity operations, inventory management, procedure reviews, and communication between space and ground via software like WorldMap and DOUG. Managing laptops in space presents challenges around hardware durability, cooling, and software/data management in the space environment.
This document discusses the use of market-based systems to allocate scarce resources for NASA missions and projects. It provides examples of how market-based approaches were used for instrument development for the Cassini mission, manifesting secondary payloads on the space shuttle, and mission planning for the LightSAR Earth imaging satellite project. The document finds that these applications of market-based allocation benefited or could have benefited from a decentralized, incentive-based approach compared to traditional centralized planning methods. However, it notes that resistance to new approaches and loss of managerial control are barriers to adoption of market-based systems.
The Stardust mission collected samples from comet Wild 2 and interstellar dust particles. It launched in February 1999 and encountered Wild 2 in January 2004, collecting dust samples in aerogel. It returned the samples to Earth safely in January 2006. The spacecraft used an innovative Whipple shield to protect itself from comet dust impacts during the encounter. Analysis of the Stardust samples has provided insights about comet composition and the early solar system.
This document discusses solutions for integrating schedules on NASA programs. It introduces Stuart Trahan's company, which provides Earned Value Management (EVM) solutions using Microsoft Office Project that comply with OMB and ANSI requirements. It also introduces a partner company, Pinnacle Management Systems, that specializes in enterprise project management solutions including EVM, project portfolio management, and enterprise project resource management, with experience in the aerospace, defense, and other industries. The document defines schedule integration and describes some methods including importing to a centralized Primavera database for review or using Primavera ProjectLink for updates, and challenges including inconsistent data formats and levels of detail across sub-schedules.
The document discusses NASA's implementation of earned value management (EVM) across its Constellation Program to coordinate work across multiple teams. It outlines the organizational structure, current target groups, and an EVM training suite. It also summarizes lessons learned and the need for project/center collaboration to integrate schedules horizontally and vertically.
This document summarizes a presentation about systems engineering processes for principle investigator (PI) mode missions. It discusses how PI missions face special challenges due to cost caps and lower technology readiness levels. It then outlines various systems engineering techniques used for PI missions, including safety compliance, organizational communication, design tools, requirements management, and lessons learned from past missions. Specific case studies from NASA's Explorers Program Office are provided as examples.
This document discusses changes to NASA's business practices for managing projects, including adopting a new acquisition strategy approach and implementing planning, programming, and budget execution (PPBE). The new acquisition strategy involves additional approval meetings at the strategic planning and project levels to better integrate acquisition with strategic and budgetary planning. PPBE focuses on analyzing programs and infrastructure to align with strategic goals and answer whether proposed programs will help achieve NASA's mission. The document also notes improvements in funds distribution and inter-center transfers, reducing the time for these processes from several weeks to only a few days.
Spaceflight Project Security: Terrestrial and On-Orbit/Mission
The document discusses security challenges for spaceflight projects, including protecting space assets from disruption, exploitation, or attack. It highlights national space policy principles of protecting space capabilities. It also discusses trends in cyber threats, including the increasing capabilities of adversaries and how even unskilled attackers can compromise terrestrial support systems linked to space assets if defenses are not strong. Protecting space projects requires awareness of threats, vulnerabilities, and strategies to defend, restore, and increase situational awareness of space assets and supporting systems.
Humor can positively impact many aspects of project management. It can improve communication, aid in team building, help detect team morale issues, and influence leadership, conflict management, negotiation, motivation, and problem solving. While humor has benefits, it also has risks and not all uses of humor are positive. Future research is needed on humor in multicultural teams, its relationship to team performance, how humor is learned, and determining optimal "doses" of humor. In conclusion, humor is a tool that can influence people and projects, but must be used carefully and spontaneously for best effect.
The recovery of Space Shuttle Columbia after its loss in 2003 involved a massive multi-agency effort to search a wide debris field, recover crew remains and evidence, and compensate local communities. Over 25,000 people searched over 680,000 acres, recovering 38% of Columbia's weight. Extensive engineering investigations were conducted to identify the causes of failure and implement changes to allow the safe return to flight of Discovery in 2005.
This document summarizes research on enhancing safety culture at NASA. It describes a survey developed to assess NASA's safety culture based on principles of high reliability organizations. The survey was tailored specifically for NASA and has been implemented to provide feedback and identify areas for improvement. It allows NASA to benchmark its safety culture within and across other industries pursuing high reliability.
This document summarizes a presentation about project management challenges at NASA Goddard Space Flight Center. The presentation outlines a vision for anomaly management, including establishing consistent problem reporting and analysis processes across all missions. It describes the current problem management approach, which lacks centralized information sharing. The presentation aims to close this gap by implementing online problem reporting and trend analysis tools to extract lessons learned across missions over time. This will help improve spacecraft design and operations based on ongoing anomaly experiences.
This document discusses leveraging scheduling productivity with practical scheduling techniques. It addresses scheduling issues such as unwieldy schedule databases and faulty logic. It then discusses taming the schedule beast through using a scheduler's toolkit, schedule templates, codes to manipulate MS Project data, common views/filters/tables, limiting constraints, and other best practices. The document provides examples of using codes and custom views/filters to effectively organize and display schedule information.
This document describes Ball Aerospace's implementation of a Life Cycle and Gated Milestone (LCGM) process to improve program planning, execution, and control across its diverse portfolio. The LCGM provides a standardized yet flexible framework that maps out program activities and products across phases. It was developed through cross-functional collaboration and introduced gradually across programs while allowing flexibility. Initial results showed the LCGM supported improved planning and management while aligning with Ball Aerospace's entrepreneurial culture.
This document discusses the importance of situation awareness (SA) for project team members. It defines SA as having three levels: perception of elements in the current situation, comprehension of the current situation, and projection of the future status. Good team SA is achieved by turning individual SAs into shared SA through communication. Teams with strong SA prepare more, focus on comprehending and projecting, and maintain awareness through techniques like questioning assumptions and seeking additional information.
This document discusses theories of leadership and how a project manager's leadership style may impact project success depending on the type of project. It outlines early hypotheses that a PM's competence, including leadership style, is a success factor on projects. It presents a research model linking PM leadership competencies to project success, moderated by factors like project type. Initial interviews found that leadership style is more important on complex projects, and different competencies are needed depending on if a project is technical or involves change. Certain competencies like communication skills and cultural sensitivity were seen as important for different project types and contexts.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdfTechgropse Pvt.Ltd.
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
Jeff.robinson
1. MBSE ARCHITECTURE
MODELING METHODOLOGY
Project Management
Challenge 2010
Jeff Robinson
Special thanks to
Scott Lukens
Used with Permission
2. Agenda
A. Overview
Arcitecture Modeling Methodology
B. Architecture Methodology (Physical)
1. Context Diagram
2. Decompose Physical Elements
C. Architecture Methodology (Operational & Functional)
1. Architecture Modeling Activities (with examples)
D. Use Models to Help Derive Requirements
1. Architecture Methodology Requirement Types
2. Characterization List
3. Derive Operational and Performance Requirements
4. Interface Requirements
5. Trace Derived Requirements to Model Elements
E. Model-Based Output
2
4. Model-Based Systems Engineering
(MBSE)
Requirements Gathering & Functional Behavior Analysis System Architecture
Analysis
Arcitecture Modeling Methodology
Operational Analysis
• Identify Source Material, Operational • Operational Scenarios • System Structure (i.e., Hierarchy of
Context, Use Cases, Scenarios, • Integrated Behavior Models System Elements)
Information Exchange • Derive Functional / Performance • Interfaces between System
• Establish Initial Requirements Set Requirements Elements
• Establish Design Constraints • Define I/O • Allocate Functional Behavior and
• Capture Issues / Risks / Decisions • Define Effectiveness Measures Non-Functional Requirements
Requirements Model Functional Models System Architectures
R1
F3 F4 System of Systems
R1.1 R1.2
F1 F5
Trade
F2
R1.2.1
Issue
Equipment List
Advantages of MBSE over Document Centric Approach
Shows Complete full picture of Architecture/Stakeholder Problem.
Generates executable artifacts.
MBSE Allows requirements conformance and consistency checking to be
assessed and validated. Document
Approach Centric
Orchestrates understanding of a design in all phases of the
development lifecycle. Approach
4
5. Part 1 – Develop Hierarchical Architecture
Model
(1) Identify Life (5) Develop
Arcitecture Modeling Methodology
Cycle Phase Mission
Operation for
Each Scenario
(6) Decompose
Mission
(2) Identify DRM Operation
Mission Phase
(ConOps)
(7) Develop Top-
(3) Develop Level System
Mission Sub- Functions
phases
(4) Model Nominal (8) Decompose
& Off-Nominal Functions
Activities
(Operational
Scenarios)
5
6. Part 2 – Use Architecture Models to Help
Derive Requirements
Model Characterize Requirement(s)
Arcitecture Modeling Methodology
Complete Model Develop Requirements
Characterization List for using Characterization List 3
Each Model Element
2
Operational/ Capability
Requirements
External Interface
Perform Hierarchal Requirements
1
Architecture Modeling
Trace/Link
Requirements to
4
Model Element
Use Model Element (with
Output
5 linked requirements) to
generate Requirements Model-Based
Systems
Document Engineering
6
11. (1) Identify Lifecycle Phase
The ‘System Lifecycle Phase’ may be modeled
as a Process Flow Diagram (PFD).
Arcitecture Modeling Methodology
SoS Level II System Level III Element Level IV
Integrate Integrate Manufacture
Each Lifecycle phase will have a Operational Transport Transport
Test System Test Component Test
unique set of missions, stakeholders, Train Sustain
Train
interfaces and constraints Operate Dispose
Applicable to
Integrate Operational Train -
SoS Level - SoS Test SoS Operate
AND AND
*4*
1 2 3
Input Input
Applicable to
Integrate Transport System Train -
System Level - System - System Test System
5 6 7 8
Input Input
Applicable to
Transport Component
Element Level Manufacture Sustain Dispose
- Element Test
9 12 13
10 11
11
12. (2) Identify DRM Mission Phase
(ConOps)
The ‘DRM Mission Phase (ConOps)’ PFD is decomposed
from the ‘DRM Mission Phase’
Arcitecture Modeling Methodology
DRM-1 ISS
OR OR
1
Lunar
DRM-2
Surface
*2*
Lunar
DRM-3 Habitat
3
DRM-4 Mars
4
‘Operate’ Lifecycle Phase
12
14. (4) Model Nominal & Off-Nominal
Activities (Operational Scenarios)
The ‘Nominal & Off-Nominal Activities (Operational
Arcitecture Modeling Methodology
Scenarios)’ PFD is decomposed from the ‘Mission Sub-
Phase’.
Scenario 1 LS Explore
OR OR
Operations
Activities modeled
Scenario 2 for the Scenario
Lunar Golf
Scenario 3 LS Mining
Operations
‘Lunar Surface Operations’
14
15. (5) Develop Mission Operation for
Each Scenario
The ‘Mission Operations for Each Scenario’ PFD is
Arcitecture Modeling Methodology
decomposed from the ‘Nominal & Off-Nominal Activities
(Operational Scenarios)’
Define a Swim Lane
(row) for each
system component.
CxP Exit Transition to Hit Golf Return to Enter
AND AND
Habitat Driving Range Balls Habitat Habitat
Define Operations
for that system
component. Start Stop
Video Feed Video Feed
Elementary
Video Feed
Schools
Define the Data
Flows (interface ‘Lunar Golf’
messages) for that
system component.
15
16. Mission Operation Swim Lanes
The Swim Lanes (‘CxP’ and ‘Elementary Schools’) represent the
internal or external elements of the Physical Architecture that the PFD
Arcitecture Modeling Methodology
operations are associated to for the current level (SoS Level).
Elem. Schools
CxP System(s)
(External Sys.) Current Level
CTN Mission Crew
Habitat EVA Rover Crew
(Comm) Systems Equipment Next Level
CxP Exit Transition to
AND
Habitat Driving Range
Start
Video Feed
Elementary
Vid
Schools
16
17. (6) Decompose Mission Operation
The ‘Mission Operation’ PFD is
Arcitecture Modeling Methodology
decomposed from the ‘Mission
Operations for Each Scenario’.
Crew Enter Turn Power Drive to Golf Turn Power
AND Exit Rover AND
Rover On Range Off
Rover On Maneuver Rover Off
Command Commands Command
Rover Rover Power Maneuver Rover
On Rover Power Off
‘Transition to Driving Range’
17
18. Decomposed Mission Operation Swim
Lanes
The Swim Lanes (‘Crew’ and ‘Rover’) represent the internal and
external elements of the Physical Architecture that the PFD operations
Arcitecture Modeling Methodology
are associated to at the current level (System Level).
Elem. Schools
CxP System(s)
(External Sys.)
CTN Mission Crew
Habitat EVA Rover Crew
(Comm) Systems Equipment Current Level
Crew Enter
AND
Rover
R
C
Rover
18
19. (7) Develop Top-Level System
Functions
The ‘Top-Level System Functions’ enhanced Functional
Arcitecture Modeling Methodology
Flow Block Diagram (eFFBD) is decomposed from the
‘Mission Operation’ PFD.
Until Destination Reached
Disengage Engage
Accelerate
Brake I AND OR OR AND I Brake
Vehicle
System System
Rover Move
Distance Accelerator
Release Apply
(Odometer) Pedal
Brake Brake
Decelerate
Vehicle
Move
Brake Pedal
Change Vehicle
Direction
Move
Steering
System
‘Maneuver Rover’ 19
20. (8) Decompose Functions
The ‘Decompose Functions” FFBD is decomposed from
Arcitecture Modeling Methodology
the Top-Level System Functions’ FFBD.
Translate
Change
Rotation to
Motor RPM
Wheels
Move Rover
Accelerator Distance
Pedal (Odometer)
‘Accelerate Vehicle’
20
22. Architecture Methodology
Requirement Types
Various types of requirements are represented in this
architecture methodology.
Arcitecture Modeling Methodology
Mode Architecture Modeling
l No. Activity Requirement Types
System of System (SoS) Level
1. Identify Lifecycle Phase Operational/Capability Requirements
2. Identify DRM Mission Phase
External Interface Requirements
(ConOps)
3. Develop Mission Sub-Phases
4. Model Nominal & Off-Nominal
Activities (Operational Scenarios)
1 5 5. Develop Mission Operation for Each
Scenario
System Level
2 6 6. Decompose Mission Operation Operational/Capability Requirements
7. Develop Top-Level System Functions
Functional/Performance Requirements
3 7 Internal Interface Requirements (System to
System)
4 8 Element Level
8. Decompose Functions Functional/Performance Requirements
External Interface Requirements
Internal Interface Requirements (Element to
Element)
Physical Architecture (All Levels)
~ Define Physical Architecture Physical Interface Requirements
22
23. Characterization List
Complete a standard Characterization List for each of the modeled
element which assists in developing associated system requirements.
Arcitecture Modeling Methodology
For Operational Models For Functional Models
Description of each Operation Description of each Function
<Describe the operation for the model element.> <Describe the model element’s function.>
Inputs/Outputs Inputs/Outputs
<Identify the operational inputs and outputs for the <Identify the functional inputs and outputs for the
model element.> model element.>
Desired Capability (level across scenarios) Desired Performance (level across scenarios)
<Describe operation capability> Describe the performance required for the function
(rate, time, weight, etc.)>
Pre Conditions
<Describe condition needed to enter/activate Pre Conditions
operation.> <Describe condition needed to enter/activate
function.>
Post Conditions
<Describe condition when operation complete.> Post Conditions
<Describe condition when function complete.>
Operating Context (Environment)
<Identify the environmental conditions that the Operating Context (Environment)
modeled element sees during its operation. > <Identify the environmental conditions that the
modeled element sees during its function. >
Off-Nominal Behavior and Recovery
<Identify credible off-nominal behaviors or scenarios Off-Nominal Behavior and Recovery
and suggested recovery operations to mitigate the <Identify credible off-nominal behaviors or scenarios
behavior. Identify a worst case scenario and 2 to 3 and suggested recovery operations to mitigate the
lesser severe behaviors.> behavior. Identify a worst case scenario and 2 to 3
lesser severe behaviors.>
23
24. (1) Derive Operational Requirements
Example - Derive Operational Requirement using Characterization List
Arcitecture Modeling Methodology
for ‘Transition to Driving Range’ operational model element.
Operational
No. Characterization Item Characterization Text
Requirement
1. Operation Description Transition two crew members and Transition to Driving
golf equipment between lunar Range
habitat and lunar golf driving range. Lunar Rover shall safely
2. Inputs ~ secure two crew members
and crew equipment for
3. Outputs ~ transit between lunar
habitat and the lunar golf
4. Pre and Post Conditions Decision authority.
driving range with a TBD
5. Operating Context 24 hr weather predicted. maximum travel distance
(Environment) and a TBD maximum
Desired Capability(level TBD maximum travel distance. continuous operation time.
6.
across scenarios) Safe travel speed of TBD mph.
7. Off-Nominal Behavior Rover fails to operate.
8. Off-Nominal Recovery Don’t not use rover;
Attempt to repair rover;
Contingency return to habitat (limit
rover distance to safe EVA walk).
24
25. (2) Derive Performance Requirements
Example - Derived Performance Requirement using Characterization
Arcitecture Modeling Methodology
List for the ‘Accelerate Vehicle’ functional model element.
Performance
No. Characterization Item Characterization Text
Requirement
1. Function Description Able to change rover acceleration. Change Vehicle
Acceleration
2. Inputs Move Accelerator Pedal
Lunar Rover acceleration
Outputs ~ changes shall be manually
3.
controlled by EVA crew so
4. Pre and Post Conditions Decision authority. that associated crew
member physical effort
5. Operating Context 24 hr weather predicted.
does not exceed human
(Environment)
factors as defined in TBD
6. Desired Performance (level TBD maximum rover acceleration. document.
across scenarios) Any crew EVA manual control not
to exceed human factors per TBD
document.
7. Off-Nominal Behavior (1) Acceleration fails Off.
(2) Acceleration fails On
8. Off-Nominal Recovery (1a) Don’t not use rover;
(1b) Attempt to repair rover;
(2a) Enable contingency
acceleration override;
(2b) Then purse contingency return
to habitat (walk) (limit rover
distance to safe EVA walk).
25
26. (3) Interface Requirements - Example
Identify the interface items in the architecture models
Use the “Catcher-Pitcher-Ball” approach to develop the interface requirements
Arcitecture Modeling Methodology
for each interface.
Interface
‘Pitcher’ ‘Ball’ ‘Catcher’
Requirement
Set (Send Data) (Data Characteristics) (Receive Data)
Example FS Provides H&S Data 10. H&S Data US Receives H&S Data
The 1st Stage shall provide The H&S message shall The US shall receive H&S
H&S data to the US in consist of Z data across data from the US in and do
accordance with US / 1st interface 295. something in accordance with
Stage IRD 10. US / 1st Stage IRD 10.
Description <Include Interface <Provide the <Include Interface Requirement
Requirement in the SRD for characteristics of the data in the SRD for the second
the first physical system being sent in the IRD physical system specifying that
specifying that data is being between the two physical data is being received from the
provided to the second systems.> first physical system.>
physical system.>
The single Interface item in the sample eFFBD Sample eFFBD
reflects a common set of Interface First Stage Upper Stage
Function X Function Z
Requirements in the following three
documents:
1) First Physical System SRD (Ex.: First Stage) Upper Stage
H&S Function Y
2) Second Physical System SRD (Ex.: Upper Stage)
External Interface
3) Common Interface IRD
26
27. Trace Derived Requirements to Model
Elements
Trace/link the derived requirements (operational, functional, interface)
back to the associated modeled elements
Arcitecture Modeling Methodology
Use the projects requirements management tool (Cradle, CORE, etc.) for
linking.
This linking activity close the loop for Model-Based Systems Engineering
(MBSE).
Accelerate
OR
Vehicle
Move
Accelerator
Requirement Item Functional Model Item Pedal
Disengage Brake System Disengage Brake System
Decelerate
Accelerate Vehicle Accelerate Vehicle Vehicle
Decelerate Vehicle Decelerate Vehicle
Change Vehicle Direction Change Vehicle Direction Move
Engage Brake System Engage Brake System Brake Pedal
Change Vehicle
Direction
‘Maneuver Rover’ Top-Level FFBD Move
Steering
System
27
29. Model-Based Systems Engineering
(MBSE) Output
Generate a resulting MBSE
requirements document:
Arcitecture Modeling Methodology
Where the SRD (and IRD) document
headers are the actual model element
names.
Where the requirements text
traced/linked to that model element are
output under the header.
Models
PFD & FFBD Model “Names”
become Requirement Document
“Section Headers”
Diagrams (PFD, FFBD, etc.)
Requirements
Requirement “Text” under each
header derived from modeling
characterization list.
29
32. Benefits of Models (Why?)
Provides Visual representation of system characteristics
Arcitecture Modeling Methodology
(easier to “see” what is going on).
The primary means of communication with
Stakeholders, Users, and Builders
Guiding and recording aggregation and decomposition
of system functions, components, and solution
characteristics.
Maintenance of system integrity through coordination of
design activities.
Assisting design by providing templates and recording
decisions.
Bridges the gap between customers problem space and
designers solution space.
32
33. Hierarchical Considerations
in Modeling
The of the architect depends upon where you are in
the hierarchy
Arcitecture Modeling Methodology
Stakeholders Mission Scenarios
Level 2
Operational Test
SoS External Interfaces
Operate Operational Needs
Train
System Boundaries
Integrate
Stakeholders
Level 3
System Test Acquisition Decisions
System
Transport Lifecycle Considerations
1
Train Technology Options
Integrate
Stakeholders
Component Test Trade Studies
Level 4
Element
Manufacture 1.1 Risk Mitigations
Sustain Technology Maturity
Transport
Dispose
Each level of the hierarchy follows the same basic process but with a Different Focus
33
34. A Side-Track into Breakdown
Structures
Product System Work
Arcitecture Modeling Methodology
Breakdown Structure Breakdown Structure Breakdown Structure
(PBS) (SBS) (WBS)
An exhaustive, A hierarchical tree A hierarchical tree
hierarchical tree structure structure of PBS structure used for
of components that make components and defining and organizing
up a system, arranged in Implementing systems, the total scope of a
whole-part relationship. arranged in whole-part project.
relationship.
Products PBS + Other Systems PBS + Services
34
35. The Boundary Diagram
-Onion Model-
SBS = PBS + Other Systems WBS = PBS + Services
Arcitecture Modeling Methodology
Training
Transport
System
System
Crew
PBS
Comm Sustain
?
Manufacture System
System
PBS = Products
Test
System Other
Ext
35
36. Swim Lanes Using Onion Model
Onion Model used to help identify PFD Swim Lanes depending on
Project Level and Mission Phase.
Arcitecture Modeling Methodology
SoS Mission Phases System Mission Phases SoS Mission Phases System Mission Phases
NA Operational Test Manufacture
Operate System Test
Integrate Transport
Train Sustain
Swim Lanes
SoS
External
External
36
37. Operation and Physical Element
Association (System Level)
The table below illustrates the association of the System
Level Operations to the applicable System Level Physical
Arcitecture Modeling Methodology
Element(s).
Operation Allocation to System Level
System Level Trans. to Hit Return
Physical Exit Driving Golf To Enter
Element Habitat Range Balls Habitat Habitat
Habitat
Swim Lanes Crew
used for the Rover
“Transition to Crew Equip
Driving Range” EVA
operation CTN (Comms)
The “Crew” and “Rover” physical elements are involved in the ‘Transition
to Drive Range’ operations, so they become the respective Swim Lanes in
the associated Process Flow Diagram.
37
38. Transition from Operational to
Functional Modeling
The model transition from “Operational” (using PFDs) to
“Functional” (using FFBDs) may vary depending on the
Arcitecture Modeling Methodology
physical element involved.
SoS Level SoS Mission / Operational Model
System to Element Level (see table below) (see table below)
Ground Systems Mission Systems Crew Module Launch System
Operational Operational Operational Operational
System
Functional
Elem SubSys
Operational Operational Functional Functional
Functional Functional Functional Functional
38
39. Decompose Function Until Uniquely
Allocated to a Single Element
The decomposition should continue
Constraints System Performance until the function can be allocated
Arcitecture Modeling Methodology
Function
C1, C2, C3 20 sec uniquely to a single physical element.
Yellow Boxes (Leaf Nodes)
7s
1s 12 s Represent functions that will be used
C1,C2,
C1 C1,C3
C3 to specify Element Requirements
(System 3.7 allocations).
4s 2s 1s 10 s
Gray Boxes
2s Represent interim steps in the
C1,C2 C1 C3 C1,C3
functional analysis.
They DO NOT have associated
3s 1s 3s 4s 3s Element Requirements.
C1,C2 C2 C3 C1,C3 C3 Ensure Performance and Constraints
are properly carried down to leaf
functions.
2s
1s Define Element Interface needs and
C3
allocations.
Deriving Element Functions Stop When Only Leaf Nodes specify requirements
39