Search NASASearch

SEARCH · Search NASA

Results for “data lifecycle”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 73 records · Page 4

Recommendations on Evidence and Process for Certification of Learning-enabled Components in Aerospace Systems

This report primarily identifies a collection of relevant and necessary evidence for assurance of machine learnt components (MLCs)—also known as learning-enabled components—integrated into aircraft systems, and gives preliminary suggestions on the elements of a certification process that invoke the identified evidence. The main focus is on feedforward neural networks that are static and trained offline through supervised learning. A brief background on the generic elements of the lifecycle of an MLC is given to contextualize the assurance considerations and, consequently, the evidence that is relevant and necessary to support certification. At the level of an MLC, those considerations relate to: (i) the consistency and correctness of MLC contributions to system functions in the context of a validated functional intent; and (ii) the absence of MLC contributions to aircraft-level failure conditions. At an ML model level, confidence in model and data properties contribute to assurance of the containing MLC, in particular: (a) generalizability and robustness of models, in the presence of inputs not previously seen during training, disturbances to inputs, and unexpected inputs; and (b) valid data, i.e., data that are at least representative, relevant, complete, and accurate. Evidence for the above span the elements of the ML lifecycle, and includes, at a minimum, lifecycle artifacts that pertain to: (1) properties of requirements capturing functional intent, safety constraints, and aspects of the intended use and operating environment; (2) model performance, model complexity and design, and algorithm choice; (3) achievement of required performance at the levels of a trained model during model development, a trained model after model development is complete, and a trained model that is transformed into an executable equivalent; (4) model implementation aspects necessary for transforming a trained model into the executable equivalent; (5) integration of the executable trained model into the containing MLC, and eventually the larger system; and, (6) lastly, the verification and validation (V&V) of each of the above. Such V&V lifecycle artifacts themselves include: aspects of coverage, e.g., of various levels of requirements by the input space of the model and the data; traceability (where applicable); application of formal methods for property specification, analysis, and checking. Examples of evidence generation methods and tools further ground the discussion on what constitutes evidence, and the contribution to assurance during certification. The identified assurance considerations and supporting evidence is not a comprehensive set. Additionally, neither what should be considered as sufficient evidence relative to the assigned criticality of an MLC, nor how criticality ought to be determined and adjusted, have been considered in this report. However, suggestions are made for potential activities of the ML lifecycle that are aimed at providing confidence that an MLC can be relied upon when integrated into its containing (aircraft) system. Those activities are proposed as candidate elements of a certification process for MLCs. The main purpose of this report to inform regulatory guidance and consensus standards that may be used to meet the safety intent of the applicable regulations.

Aviation safety

The Dark Target aerosol retrieval algorithm applied to Low Earth Orbit and GEOstationary imagers: progress towards an integrated LEO-GEO view of global aerosol

The relatively simple dark-target (DT) aerosol retrieval algorithm provides products of spectral aerosol optical depth (AOD) from measurements of multi-spectral reflectance in visible, near-infrared and shortwave infrared wavelength bands. Originally developed for Moderate-resolution Imaging Spectroradiometer (MODIS aboard Terra and Aqua) in Low-Earth Orbit (LEO), DT has been ported to Visible Infrared Imaging Suite (VIIRS aboard Suomi-NPP and NOAA-20, also in LEO), to enhanced-MODIS Airborne Simulator (eMAS, on an airborne platform), and now to sensors in GEOstationary orbit (Advanced Himawari Imager - AHI aboard Himawari-8 and Advanced Baseline Imagers – ABI aboard GOES-16 and 17). Together, these new datasets not only extend upon the 20+ year MODIS aerosol record, but also expand the temporal sampling and/or spatial resolution. Between July and October of 2019, NASA participated in two field experiments on opposite sides of the globe. These included FIREX-AQ which focused on fire and smoke in the Western U.S., and then CAMP2EX which targeted aerosol/cloud interactions around the Philippines. We have performed DT aerosol retrievals on all images from all sensors during these three months, validated against ground observations from stationary and mobile sunphotometer sites, and have begun to develop a synergy that represents semi-global observations every half hour. The resulting aerosol products are being used as context and for model assimilation, thus providing the framework for more complete characterization of global aerosol transport and lifecycle. Here, we report on progress, as well as remaining challenges such as data management, computer processing, and accounting for differences between GEO and LEO observation geometry and surface reflectance parameterization.

dark target

Safety Expertise and the Perils of Novelty

Emerging aviation markets such as urban air mobility are giving rise to new technologies and means of operation. However, novelty may hide ‘unknown unknowns,’ raising new hazards. This paper examines how expertise and safety techniques enable transformative technologies such as reduced crew operations, hybrid wing-borne and rotor-born flight, federated air traffic services, and urban operations. We explore how analysts use expertise to address common-cause failures, collect and interpret safety data, and perform exacting tradeoffs between dissimilarity, redundancy, independence, and diversity (human, process lifecycle, or otherwise) to ensure safety. When novelty is present, analysts might not possess the expertise needed to fully understand the implications of design decisions and tradeoffs being made, especially in early lifecycle phases, on emergent properties such as safety. Safety expertise must be carefully cultivated. The conflicting views of safety experts must be unpacked to identify the divergence in fundamental assumptions, models, means, and methods that may be causing them. Once systems venture beyond the basis of what safety expertise can reliably guarantee, projects take on risk that must be managed. The paper contains key takeaways and actionable recommendations for novel OEMs and regulators touching on topics such as robust monitoring; clear and transparent reporting; incremental approaches to fielding novel systems in hazard-rich, risk-tolerant environments; the cultivation of safety culture and expertise in an organization; and the use of scientific study to reduce epistemic uncertainty in novel operations with new technologies. Since excessive novelty in aviation can undermine the current foundation of safety, humility and incrementalism are necessary to enable emerging aviation markets safely.

safety expertise

Safety Expertise and the Perils of Novelty

Emerging aviation markets such as urban air mobility are giving rise to new technologies and means of operation. However, novelty may hide ‘unknown unknowns,’ raising new hazards. This paper examines how expertise and safety techniques enable transformative technologies such as reduced crew operations, hybrid wing-borne and rotor-born flight, federated air traffic services, and urban operations. We explore how analysts use expertise to address common-cause failures, collect and interpret safety data, and perform exacting tradeoffs between dissimilarity, redundancy, independence, and diversity (human, process lifecycle, or otherwise) to ensure safety. When novelty is present, analysts might not possess the expertise needed to fully understand the implications of design decisions and tradeoffs being made, especially in early lifecycle phases, on emergent properties such as safety. Safety expertise must be carefully cultivated. The conflicting views of safety experts must be unpacked to identify the divergence in fundamental assumptions, models, means, and methods that may be causing them. Once systems venture beyond the basis of what safety expertise can reliably guarantee, projects take on risk that must be managed. The paper contains key takeaways and actionable recommendations for novel OEMs and regulators touching on topics such as robust monitoring; clear and transparent reporting; incremental approaches to fielding novel systems in hazard-rich, risk-tolerant environments; the cultivation of safety culture and expertise in an organization; and the use of scientific study to reduce epistemic uncertainty in novel operations with new technologies. Since excessive novelty in aviation can undermine the current foundation of safety, humility and incrementalism are necessary to enable emerging aviation markets safely.

safety expertise

From Here to There - Bird's Eye Perspective on Grant Lifecycle and Administration

“What gets measured gets done ”or “measure it to manage it”. The statements have become matter of fact. However, measurement (and even metrics) alone cannot fully communicate an organization’s story without the point of accountability. As a dynamic org, we must measure what is necessary, using the appropriate lenses to analyze the most relevant information that allows robust decision-making. A key function of Program Planning and Control (PP&C) is to assist HRP in the development of such strategy that ensures the proper execution of program research goals. With introspection of the Technical Officer role as defined by 2 CFR(i.e., Part 200, Part 1800)and subsequent governance under the NASA Grant and Cooperative Agreement Manual (GCAM), we’ve realized an obvious disconnect among Principal Investigator’s (PI),technical communication with the elements and some of the administrative/fiduciary requirements that should run parallel to the science work. This find has introduced new program risks as evidenced through incomplete deliverables or other less-than-successful requirements through the lifecycle for work we fund. One solution the Grants Technical Officer proposes is for PP&C to share in the communication with stakeholders of grants administration much earlier in the award process in attempt to reduce programmatic risks; particularly in data, reporting and performance management. As such, the planned IWS 2022 session will focus on(plenary) topics that include (1) definition of the grant lifecycle, (2) anatomy of a grant(NF1687 the award document), and (3)performance measurement/post-award monitoring. As HH&P pursues its strategic objectives to evolve the directorate into a data rich and knowledge rich organization, it has become increasingly important to develop the multiple levels of insight across the program to ensure data and other reporting(qualitative/quantitative), alongside proper administration. And the desired outcome is to make certain HRP meets/exceeds the accountability standard that our research information is received, maintained and accessible in posterity.

Lucy D Barnes-Moten

Reusable Rocket Engine Advanced Health Management System. Architecture and Technology Evaluation: Summary

In this study, we proposed an Advanced Health Management System (AHMS) functional architecture and conducted a technology assessment for liquid propellant rocket engine lifecycle health management. The purpose of the AHMS is to improve reusable rocket engine safety and to reduce between-flight maintenance. During the study, past and current reusable rocket engine health management-related projects were reviewed, data structures and health management processes of current rocket engine programs were assessed, and in-depth interviews with rocket engine lifecycle and system experts were conducted. A generic AHMS functional architecture, with primary focus on real-time health monitoring, was developed. Fourteen categories of technology tasks and development needs for implementation of the AHMS were identified, based on the functional architecture and our assessment of current rocket engine programs. Five key technology areas were recommended for immediate development, which (1) would provide immediate benefits to current engine programs, and (2) could be implemented with minimal impact on the current Space Shuttle Main Engine (SSME) and Reusable Launch Vehicle (RLV) engine controllers.

Pettit, C. D.

Non-Turbulent Liquid-Bearing Polar Clouds: Observed Frequency of Occurrence and Simulated Sensitivity to Gravity Waves

A common feature of polar liquid-bearing clouds (LBCs) is radiatively-driven turbulence, which may variously alter cloud lifecycle via vertical mixing, droplet activation, and subsequent feedbacks. However, polar LBCs are commonly initiated under stable, non-turbulent conditions. Using long-term data from the North Slope of Alaska and McMurdo, Antarctica, we show that non-turbulent conditions prevail in ~25% of detected LBCs, surmised to be preferentially early in their lifecycle. We conclude that non-turbulent LBCs are likely common over the polar regions owing primarily to atmospheric temperature and stability. Such stable environments are known to support gravity wave activity. Using large-eddy simulations we find that short to intermediate period gravity waves may catalyze turbulence formation when aerosol particles available for activation are sufficiently small. We posit that the frequent occurrence of non-turbulent LBCs over the polar regions has implications for polar aerosol-cloud interactions and their parameterization in large-scale models.

Clouds

Trustworthy Autonomy for Gateway Vehicle System Manager

The Vehicle System Manager (VSM) is the highest-level software control system in the Gateway hierarchical Autonomous System Management Architecture. The VSM provides four function categories: Mission Management and Timeline Execution, Resource Management, Fault Management, Vehicle Control and Operation. VSM provides various levels of automation ranging from fully autonomous operations with no flight crew and minimal ground monitoring to advisory automation when Gateway is crewed and has full ground monitoring. Trustworthiness is achieved via verified specification, comprehensive development verification, and real-time verification using assume-guarantee contracts. Development verification includes semantic verification of the data model via peer review and testing and assume-guarantee contracts implemented using the PlusCal/TLA+ environment. VSM also uses runtime assume-guarantee contracts, implemented in R2U2 via a runtime monitor that feeds the necessary telemetry data to R2U2 and which receives and responds to the R2U2 verdict stream. The full lifecycle verification approach and use of assume-guarantee contracts provides increased trustworthiness to VSM. Preliminary results provide encouragement that VSM can be both autonomous and trustworthy.

Assume-guarantee contracts

A 20 Year Lifecycle Study for Launch Facilities at the Kennedy Space Center

The lifecycle cost analysis was based on corrosion costs for the Kennedy Space Center's Launch Complexes and Mobile Launch Platforms. The first step in the study involved identifying the relevant assets that would be included. Secondly, the identification and collection of the corrosion control cost data for the selected assets was completed. Corrosion control costs were separated into four categories. The sources of cost included the NASA labor for civil servant personnel directly involved in overseeing and managing corrosion control of the assets, United Space Alliance (USA) contractual requirements for performing planned corrosion control tasks, USA performance of unplanned corrosion control tasks, and Testing and Development. Corrosion control operations performed under USA contractual requirements were the most significant contributors to the total cost of corrosion. The operations include the inspection of the pad, routine maintenance of the pad, medium and large scale blasting and repainting activities, and the repair and replacement of structural metal elements. Cost data was collected from the years between 2001 and 2007. These costs were then extrapolated to future years to calculate the 20 year lifecycle costs.

Kolody, Mark R.

A Method for Calculating the Probability of Successfully Completing a Rocket Propulsion Ground Test

Propulsion ground test facilities face the daily challenges of scheduling multiple customers into limited facility space and successfully completing their propulsion test projects. Due to budgetary and schedule constraints, NASA and industry customers are pushing to test more components, for less money, in a shorter period of time. As these new rocket engine component test programs are undertaken, the lack of technology maturity in the test articles, combined with pushing the test facilities capabilities to their limits, tends to lead to an increase in facility breakdowns and unsuccessful tests. Over the last five years Stennis Space Center's propulsion test facilities have performed hundreds of tests, collected thousands of seconds of test data, and broken numerous test facility and test article parts. While various initiatives have been implemented to provide better propulsion test techniques and improve the quality, reliability, and maintainability of goods and parts used in the propulsion test facilities, unexpected failures during testing still occur quite regularly due to the harsh environment in which the propulsion test facilities operate. Previous attempts at modeling the lifecycle of a propulsion component test project have met with little success. Each of the attempts suffered form incomplete or inconsistent data on which to base the models. By focusing on the actual test phase of the tests project rather than the formulation, design or construction phases of the test project, the quality and quantity of available data increases dramatically. A logistic regression model has been developed form the data collected over the last five years, allowing the probability of successfully completing a rocket propulsion component test to be calculated. A logistic regression model is a mathematical modeling approach that can be used to describe the relationship of several independent predictor variables X(sub 1), X(sub 2),..,X(sub k) to a binary or dichotomous dependent variable Y, where Y can only be one of two possible outcomes, in this case Success or Failure. Logistic regression has primarily been used in the fields of epidemiology and biomedical research, but lends itself to many other applications. As indicated the use of logistic regression is not new, however, modeling propulsion ground test facilities using logistic regression is both a new and unique application of the statistical technique. Results from the models provide project managers with insight and confidence into the affectivity of rocket engine component ground test projects. The initial success in modeling rocket propulsion ground test projects clears the way for more complex models to be developed in this area.

Messer, Bradley P.

Integrated testing and verification system for research flight software design document

The NASA Langley Research Center is developing the MUST (Multipurpose User-oriented Software Technology) program to cut the cost of producing research flight software through a system of software support tools. The HAL/S language is the primary subject of the design. Boeing Computer Services Company (BCS) has designed an integrated verification and testing capability as part of MUST. Documentation, verification and test options are provided with special attention on real time, multiprocessing issues. The needs of the entire software production cycle have been considered, with effective management and reduced lifecycle costs as foremost goals. Capabilities have been included in the design for static detection of data flow anomalies involving communicating concurrent processes. Some types of ill formed process synchronization and deadlock also are detected statically.

Taylor, R. N.

Orbit Determination and Navigation Software Testing for the Mars Reconnaissance Orbiter

During the extended science phase of the Mars Reconnaissance Orbiter's lifecycle, the operational duties pertaining to navigation primarily involve orbit determination. The orbit determination process utilizes radiometric tracking data and is used for the prediction and reconstruction of MRO's trajectories. Predictions are done twice per week for ephemeris updates on-board the spacecraft and for planning purposes. Orbit Trim Maneuvers (OTM-s) are also designed using the predicted trajectory. Reconstructions, which incorporate a batch estimator, provide precise information about the spacecraft state to be synchronized with scientific measurements. These tasks were conducted regularly to validate the results obtained by the MRO Navigation Team. Additionally, the team is in the process of converting to newer versions of the navigation software and operating system. The capability to model multiple densities in the Martian atmosphere is also being implemented. However, testing outputs among these different configurations was necessary to ensure compliance to a satisfactory degree.

Deep Space Network

Polarimetric Retrievals of Cloud Droplet Number Concentrations

Cloud droplet number concentration (Nd) is an important parameter of liquid clouds and is crucial to understanding aerosol-cloud interactions. It couples boundary layer aerosol composition, size and concentration with cloud reflectivity. It affects cloud evolution, precipitation, radiative forcing, global climate and, through observation, can be used to partially monitor the first indirect effect. With its unique combination of multi-wavelength, multi-angle, total and polarized reflectance measurements, the Research Scanning Polarimeter (RSP) retrieves Nd with relatively few assumptions. The approach involves measuring cloud optical thickness, mean droplet extinction cross-section and cloud physical thickness. Polarimetric observations are capable of measuring the effective variance, or width, of the droplet size distribution. Estimating cloud geometrical thickness is also an important component of the polarimetric Nd retrieval, which is accomplished using polarimetric measurements in a water vapor absorption band to retrieve the amount of in-cloud water vapor and relating this to physical thickness. We highlight the unique abilities and quantify uncertainties of the polarimetric approach. We validate the approach using observational data from the North Atlantic and Marine Ecosystems Study (NAAMES). NAAMES targets specific phases in the seasonal phytoplankton lifecycle and ocean-atmosphere linkages. This study provides an excellent opportunity for the RSP to evaluate its approach of sensing Nd over a range of concentrations and cloud types with in situ measurements from a Cloud Droplet Probe (CDP). The RSP and CDP, along with an array of other instruments, are flown on the NASA C-130 aircraft, which flies in situ and remote sensing legs in sequence. Cloud base heights retrieved by the RSP compare well with those derived in situ (R=0.83) and by a ceilometer aboard the R.V. Atlantis (R=0.79). Comparing geometric mean values from 12 science flights throughout the NAAMES-1 and NAAMES-2 campaigns, we find a strong correlation between Nd retrieved by the RSP and CDP (R=0.96). A linear least squares fit has a slope of 0.92 and an intercept of 0.3 cm−3. Uncertainty in this comparison can be attributed to cloud 3D effects, nonlinear liquid water profiles, multilayered clouds, measurement uncertainty, variation in spatial and temporal sampling, and assumptions used within the method. Radiometric uncertainties of the RSP measurements lead to biases on derived optical thickness and cloud physical thickness, but these biases largely cancel out when deriving Nd for most conditions and geometries. We find that a polarimetric approach to sensing Nd is viable and the RSP is capable of accurately retrieving Nd for a variety of cloud types and meteorological conditions.

Droplet concentration

Application of Lidar-Radar Combined Data Products during the IMPACTS 2020 Field Campaign

The Investigation of Microphysics and Precipitation for Atlantic Coast-Threatening Snowstorms (IMPACTS) is a three-year field campaign investigating the formation and lifecycle of banded, precipitation structures within intense wintertime cyclones impacting the highly-populated northeast United States. Unlike previous campaigns in the region, IMPACTS mission scientists have access to and coordinate the NASA ER-2 and P-3 aircraft to collect observations from both a remote sensing and in-situ perspective, respectively. For IMPACTS, the ER-2 aircraft was equipped with lidar (CPL), radar (CRS, HIWRAP, EXRAD), microwave radiometer (CoSMIR, AMPR) instruments, each with their own unique capabilities and limitations. Our on-going work effort aims to develop IMPACTS lidar and radar merged data products, which can be used to supplement the raw data sources, tease out additional aspects of the mechanisms underpinning wintertime cyclones, and enhance our understanding of microphysical properties in sensor overlap regions. Preliminary merged data products combine CPL lidar with any one of the NASA High Altitude Radar (HAR) radar products (CRS, HIWRAP, EXRAD) and represent these data as both normalized values and translated to reflectivity signal (dB). Continuing work will further refine our merged data product algorithm to provide additional information on hydrometeor species identification, ice crystal habit, and ice-water content, which will help IMPACTS achieve its mission goal of improving microphysical properties retrievals from both airborne and spaceborne platforms.

Stephen D. Nicholls

A Novel Framework for Multi-Path Data Fusion in Earth Observation and New Observing Strategies: Applications to Predicting Forest Canopy Height

Exponential growth of data from Earth Observation (EO) assets has necessitated the development of sophisticated methods for data interpretation and management. NASA’s New Observing Strategy (NOS) approach aims to coordinate operations among complex heterogenous systems of constellations, requiring advanced Artificial Intelligence and Machine Learning (AI/ML) techniques. Despite significant advancements in AI/ML across various domains, the EO and machine learning for satellite (SatML) fields remain fragmented, often relying on adapted techniques rather than domain-specific solutions. We present a novel end-to-end data fusion framework tailored specifically for EO and SatML, addressing this gap by facilitating rapid development of AI/ML applications. This framework, called, Multimodal Earth Observation Workflow for Machine Learning (MEOW-ML), sup- ports the entire AI/ML lifecycle, from dataset manipulation, to model training, evaluation, and logging, and is designed to expedite the development of next-generation NOS deployments and SOTA in EO. We apply our framework to predict canopy height model (CHM) derived from lidar data. We integrate multiple data modalities through a hierarchical, multi-path model architecture, effectively identifying and leveraging the unique strengths of each data source to enhance predictive accuracy. Our experiments demonstrate that the multi-path architecture outperforms traditional single-path models and provides significant advantages in both accuracy and computational efficiency.

Mark Moussa

Evaluation of Cirrus Cloud Simulations Using ARM Data - Development of a Case Study Data Set

Cloud-resolving models (CRMs) provide an effective linkage in terms of parameters and scales between observations and the parametric treatments of clouds in global climate models (GCMs). They also represent the best understanding of the physical processes acting to determine cloud system lifecycle. The goal of this project is to improve state-of-the-art CRMs used for studies of cirrus clouds and to establish a relative calibration with GCMs through comparisons among CRMs, single column model (SCM) versions of the GCMs, and observations. This project will compare and evaluate a variety of CRMs and SCMs, under the auspices of the GEWEX Cloud Systems Study (GCSS) Working Group on Cirrus Cloud Systems (WG2), using ARM data acquired at the Southern Great Plains (SGP) site. This poster will report on progress in developing a suitable WG2 case study data set based on the September 26, 1996 ARM IOP case - the Hurricane Nora outflow case. The environmental data (input) will be described as well as the wealth of validating cloud observations. We plan to also show results of preliminary simulations. The science questions to be addressed derive significantly from results of the GCSS WG2 cloud model comparison projects, which will be briefly summarized.

O'C.Starr, David

Collaborative Systems Engineering in the Ascent Abort-2 Crew Module/Separation Ring Project

Generally speaking, systems engineering (SE) tool-sets face a dilemma balancing power and accessibility. High-powered SE tools (MagicDraw, Cradle, Core, etc.) tend to be specialized and are available only to highly trained Systems Engineers, and/or through the use of a 'back room' developer team making the output products available to the broader team. On the other hand, highly accessible tools (MS Word, Excel, etc.) do not have the power to implement SE in a rigorous manner. NASA has to test all aspects of the new human-rated Orion Multi-Purpose Crew Vehicle spacecraft prior to its first crewed mission. The test program includes uncrewed launch abort flight tests to demonstrate the capability to save the crew in the event that a launch failure occurs. Orion's second abort flight test will be a low-altitude flight test known as "Ascent Abort 2 (AA-2)." This test is currently scheduled to be carried out at Cape Canaveral Air Force Station's Space Launch Complex 46 (SLC-46) in Florida in 2019. NASA's in-house AA-2 Crew Module and Separation Ring (CSR) Team is producing the crew module and separation ring. Operating jointly as both an Advanced Exploration Systems (AES) Project and an Orion Project, the CSR project charter includes development of innovative, streamlined and generally more efficient practices for creation of flight hardware and software. One result of this tasking has been development of a collaborative and data-centric systems engineering environment within the team's shared web environment (Microsoft SharePoint). Through the use of built-in, 'out of the box capabilities' present in MS SharePoint, the CSR Systems Engineering team has created (with some limited developer support) a data-centric architecture for the project's SE implementation, including functional and interface analysis, requirements development and management, risk management, verification planning and management, test results, and end item management. Data elements are linked between data structures so as to define and control relationships between item types, link requirements to parents and children, and link tests to the requirements that they verify. The overall project team integration is increased by also linking SE content to project management content over the project life cycle, including team communication, action items, configuration management, decisional and meeting materials, and life cycle reviews. This presentation will provide an overview of the collaborative SE environment, showing how it provides the power for a number of SE tasks while still providing the accessibility and transparency to allow the full project team to collaborate and succeed. Given the project phase, we'll be able to present a nearly full lifecycle discussion, from concept through verification and approaching delivery.

Systems Engineering environments