NASA has implemented CMMI models to improve software engineering processes. Key impacts include reduced risk, more accurate cost estimates, and finding defects earlier. NASA requires a minimum CMMI level for contractors depending on software class. Lessons learned are that preparation is critical, tools help achieve compliance, and cultural changes have significantly improved practices. CMMI provides a proven approach to manage performance if defined processes are used, results measured, and continuous improvements made.
LDAC-1 developed a minimum functionality lunar lander design using a risk-informed approach to meet basic mission requirements. LDAC-2 then focused on reducing risks to crew safety by adding redundancy and reliability upgrades. The goal was to design a lander that provided adequate safety for crew with a design optimized for mass.
The document discusses the use of probabilistic risk assessment (PRA) in decision making for the Space Shuttle program. It provides background on the development of the Shuttle PRA since 1987. Key information for management includes clearly presenting the PRA analysis and assumptions, limitations, and estimates of uncertainty to support risk-informed decisions.
The document discusses the development of requirements for a vehicle through model-based systems engineering. It provides examples of models that can be used to capture a vehicle's operational concept, including a design reference mission diagram, a phase model, and an activity model. The models aim to depict how the vehicle and crew interact during different mission activities and phases to achieve objectives. They are used to identify vehicle capabilities and functions needed to implement the operational concept.
1) Det Norske Veritas (DNV) is a classification society established in 1864 that identifies, assesses, and manages risk, particularly for maritime industries.
2) DNV has a large global presence with over 9,000 employees in 300 offices across 100 countries.
3) DNV has the largest market share for classification of floating production storage and offloading (FPSO) vessels at 40%, focusing on risk assessment and certification of new FPSO builds and conversions.
This document introduces the new release of CADISON R13 software. Some key improvements in R13 include 3D equipment layouts linked to models for clash detection, automatic cable routing, automatic creation of terminal drawings, and enhancements to electric design and pipe support modeling to save engineering time. CADISON aims to continuously improve project engineering efficiency for customers. The document discusses CADISON's direction, its 15-year history, and goals for future releases.
This document provides a final report on rail operations and technology for a Brazil high-speed rail (TAV) project. It includes 3 parts: an overview of the TAV project, an introduction to key aspects of high-speed rail technology, and a volume on rail operations and technology. The volume analyzes high-speed rail networks, infrastructure, operations and rolling stock in multiple countries to identify best practices for the Brazil TAV project.
The document discusses test-driven PL/SQL development and best practices for error management. It covers defining requirements, writing unit tests, handling exceptions, and logging errors consistently. Key aspects include using pre-defined exception types and handlers, avoiding direct error raising/handling in application code, and following standards for error messaging.
Developed Studies, Business DevelopmentJoaquim Leao
Joaquim Leão has extensive experience in developing strategies for companies operating in Brazil. Some of the key projects and roles mentioned in the document include:
- Developing a strategy plan for Larsen & Toubro to expand their operations in Brazil.
- Presenting business opportunities and challenges for companies in various sectors such as offshore oil/gas, petrochemicals, and biofuels.
- Creating a business plan to improve Baker Hughes' operations in Brazil.
- Holding leadership roles in swimming and volleyball clubs in Brazil.
LDAC-1 developed a minimum functionality lunar lander design using a risk-informed approach to meet basic mission requirements. LDAC-2 then focused on reducing risks to crew safety by adding redundancy and reliability upgrades. The goal was to design a lander that provided adequate safety for crew with a design optimized for mass.
The document discusses the use of probabilistic risk assessment (PRA) in decision making for the Space Shuttle program. It provides background on the development of the Shuttle PRA since 1987. Key information for management includes clearly presenting the PRA analysis and assumptions, limitations, and estimates of uncertainty to support risk-informed decisions.
The document discusses the development of requirements for a vehicle through model-based systems engineering. It provides examples of models that can be used to capture a vehicle's operational concept, including a design reference mission diagram, a phase model, and an activity model. The models aim to depict how the vehicle and crew interact during different mission activities and phases to achieve objectives. They are used to identify vehicle capabilities and functions needed to implement the operational concept.
1) Det Norske Veritas (DNV) is a classification society established in 1864 that identifies, assesses, and manages risk, particularly for maritime industries.
2) DNV has a large global presence with over 9,000 employees in 300 offices across 100 countries.
3) DNV has the largest market share for classification of floating production storage and offloading (FPSO) vessels at 40%, focusing on risk assessment and certification of new FPSO builds and conversions.
This document introduces the new release of CADISON R13 software. Some key improvements in R13 include 3D equipment layouts linked to models for clash detection, automatic cable routing, automatic creation of terminal drawings, and enhancements to electric design and pipe support modeling to save engineering time. CADISON aims to continuously improve project engineering efficiency for customers. The document discusses CADISON's direction, its 15-year history, and goals for future releases.
This document provides a final report on rail operations and technology for a Brazil high-speed rail (TAV) project. It includes 3 parts: an overview of the TAV project, an introduction to key aspects of high-speed rail technology, and a volume on rail operations and technology. The volume analyzes high-speed rail networks, infrastructure, operations and rolling stock in multiple countries to identify best practices for the Brazil TAV project.
The document discusses test-driven PL/SQL development and best practices for error management. It covers defining requirements, writing unit tests, handling exceptions, and logging errors consistently. Key aspects include using pre-defined exception types and handlers, avoiding direct error raising/handling in application code, and following standards for error messaging.
Developed Studies, Business DevelopmentJoaquim Leao
Joaquim Leão has extensive experience in developing strategies for companies operating in Brazil. Some of the key projects and roles mentioned in the document include:
- Developing a strategy plan for Larsen & Toubro to expand their operations in Brazil.
- Presenting business opportunities and challenges for companies in various sectors such as offshore oil/gas, petrochemicals, and biofuels.
- Creating a business plan to improve Baker Hughes' operations in Brazil.
- Holding leadership roles in swimming and volleyball clubs in Brazil.
The document outlines various organizations' plans to contribute to the SAIC Crisis Management integrated knowledge environment (HIKE) in year 2. It discusses Stanford KSL enhancing explanation capabilities for the ATP reasoner and merging additional knowledge bases. SRI will help with ontology merging and load information extracted by Textwise. MIT START plans to link to other HIKE systems and expand coverage areas. NWU and CMU did not provide details on their year 2 plans.
Vol1 Demand & Revenue Forecast Final ReportFabio Alves
This document is the final report of Volume 1 of the Brazil TAV Project demand and revenue forecast. It was prepared by Halcrow-Sinergia Consortium in June 2009. The report provides an executive summary that includes ridership forecasts for the TAV express service between Rio de Janeiro and São Paulo, as well as regional services. It also benchmarks the forecasts against other high-speed rail projects internationally. The full report then details the background of the study, existing transport systems, surveys conducted, development of the demand model, assumptions used in the analysis, and ridership forecasts for express and regional services through 2044.
The document provides an overview of NASA's Software Engineering Initiative from 2002 to 2008. The initiative aimed to advance software engineering practices across NASA to improve schedule, cost, quality and delivered functionality. It established groups and policies to improve processes, provide training, infuse new technologies, and increase collaboration. Key impacts included improved planning, use of best practices by contractors, and a foundation for disciplined software development through shared process assets.
Auto-Scaling to Minimize Cost and Meet Application Deadlines in Cloud Workflowsmingtemp
http://www.cs.virginia.edu/~mm5bw/papers/WorkflowAutoScaling.pdf
The presentation for SC 2011
http://dl.acm.org/citation.cfm?id=2063449
www.mingmao.org
This document provides a summary of Divahar Jayaraman's professional portfolio, including expertise in aerospace engineering fields like aerodynamics and structural dynamics, as well as programming languages and software. It also lists professional experience conducting aircraft loads analysis and developing various computational fluid dynamics and structural analysis programs. Projects developed include panel codes, finite element method codes, and computational fluid dynamics solvers.
2005* ApresentaçãO Sobre AviaçãO Executiva Paris Air ShowEmbraer RI
This presentation discusses Embraer's business aviation market and the Legacy jet.
Embraer sees opportunities for growth in the business aviation market which is estimated to reach $33.6 billion by 2014. The Legacy jet gives Embraer competitive advantages through its ability to operate from short runways and high altitude airports. Embraer has enhanced the Legacy's performance and capabilities over time.
Embraer's goal is to become a major player in the business aviation market within 10 years by providing innovative products and services that create value for customers and shareholders. To achieve this, Embraer is conducting in-depth research to understand the business aviation market.
This document summarizes a research study examining a non-hierarchical approach to air tasking in joint air operations using agent-based modeling. The study builds an agent-based air campaign model called ABACUS to test if decentralized execution can achieve the goals of an air campaign in a reasonable way. The model finds that targets are killed over time in simulations with decentralized tasking. While further validation is needed, the results indicate decentralized execution may be a feasible alternative to current hierarchical approaches under certain conditions like a target-rich environment with good intelligence sharing. The next steps are to improve the model and compare decentralized and centralized approaches using efficiency metrics.
CommunityOneEast 09 - Dynamic Languages: the next big thing for the JVM or an...Chris Richardson
Dynamic languages have many benefits but static languages with compile-time checking can also be expressive. The document discusses the rise of dynamic languages on the Java Virtual Machine like Groovy and how they provide benefits like concise syntax and runtime programmability while static languages provide safety through compile-time checking. It then outlines Chris Richardson's presentation agenda on dynamic languages, favorite Groovy features, frustrations with Groovy, and the Scala language which aims to provide both expressiveness and compile-time checking.
Architecture is a foundational element of complex system design. Upfront analysis and architecting helps understand essential requirements and reduce incidental complexity through a well-designed structure. This recommendation promotes investing in system-level thinking to establish a solid foundation addressing the problem, rather than its symptoms.
Image Processing and Cartography with the NASA Vision WorkbenchMatt Hancher
These are the slides from a talk I gave about the NASA Vision Workbench at the FOSS4G conference at the end of 2007. For a more up-to-date discussion of the Vision Workbench, see this presentation instead: http://www.slideshare.net/mdhancher/the-nasa-vision-workbench-reflections-on-image-processing-in-c-presentation
NASA has facilitated the commercialization of over 40 years of technology development. This document lists the top 20 NASA spinoff technologies from the past 5 years that have been successfully transferred to the private sector. They include a water filtration system developed for the ISS that provides clean drinking water worldwide, remote-controlled tractors with precision from GPS technology originally developed for a Mars probe, and a bacterial detection system for spacecraft now used to detect anthrax. Many of the technologies improve healthcare, agriculture, aviation safety, law enforcement, and environmental remediation.
A NASA desenvolveu tecnologias para reciclar urina de astronautas e purificar água no espaço. Uma empresa usou esses conceitos para desenvolver bebidas probióticas à base de água de coco, vendendo mais de 1 milhão de garrafas em 2011. Outra empresa usou bactérias para fermentar chás probióticos.
NASA's Space Technology Program aims to advance technologies from low to mid readiness levels for future NASA missions and other government/commercial applications. It includes elements for early-stage innovation, game-changing technology development, and crosscutting capability demonstrations. The program will employ a portfolio approach across the technology readiness scale and sponsor research at universities, industry, and NASA centers. It will help enable NASA's human spaceflight goals by developing technologies like in-orbit propellant transfer and storage, lightweight modules, and autonomous docking.
A powerpoint summary of technologies highlighted in NASA's 2010 edition of Spinoff, which features recent significant research and development activities across NASA and the successful transfer of NASA technologies to the marketplace. This presentation summarizes the commercial technologies profiled in Spinoff 2010; the full text is available for download at http://spinoff.nasa.gov, and print copies can be requested by calling (301) 286-0561 or through spinoff@sti.nasa.gov.
NASA technology related to 3D imaging, microsystems, and high-resolution imagery was licensed to develop the world's first 3D endoscope for brain surgery. The MARVEL endoscope provides surgeons with a 3D image in close quarters, allowing for improved visibility and understanding of an object's proximity during surgery. It was developed through a partnership between a neurosurgeon and JPL under a Space Act Agreement to improve safety and reduce costs of brain surgeries.
On NASA Space Shuttle Program Hardware and SoftwareMartin Dvorak
This document discusses the history and development of the software used in NASA's Space Shuttle program. It describes how the software evolved from the Apollo guidance computer to the general purpose computers used on the shuttles. It highlights the focus on reliability through redundancy of hardware and software. The development process emphasized statistical analysis, incremental improvements, extensive testing, and maintaining high quality through careful processes and adequate resources.
User Centered Agile Development at NASA - One Groups Path to Better SoftwareBalanced Team
The group at NASA iteratively adopted agile practices over two years to improve their software development process. They started with six month development cycles and shortened this to six weeks and then three weeks. This allowed for more frequent customer feedback and prioritization of work. Daily builds and testing ensured progress was always visible. Their measure of success became working code delivered in frequent iterations rather than presentations or documentation.
Agile Leadership – Is a Servant Leader always the Right Approach?IvanaTerrorBull
There is an accepted wisdom within the Agile community that the right management style is that of the Servant Leader, one who is there to serve the team as a ‘first among equals’. They are not the manager of the team, as the team is self-organising, but rather removes impediments and coaches the team in agile best practices. However, just blindly following this approach in every circumstance can be catastrophic.
This talk is aimed at Scrum Masters, their managers and team members. After the talk attendees will understand:
• the definition of a servant leader and what this means in practice
• the difference between management and leadership
• how to assess the current situation in order to decide the most appropriate leadership style
• when to change leadership style for maximum results
• that a true servant leader is about giving the team what they need, not necessarily what they want
This document provides information on CoreAVI's graphics certification process and products. It discusses their DO-178B/C and DO-254 certification methodology, which involves a 6-phase development process. It also describes their OpenGL SC graphics driver, which has a modular design and over 2000 test procedures to achieve certification. The document addresses topics from CAST-29 and EASA on using COTS graphics processors in safety-critical systems. CoreAVI provides certification packages for their graphics drivers up to DO-178C Level A and DO-254 Level C.
Career Education & Work Gov Inst 2008 Project TemplateSue Fox
The presentation is the scaffolding that all school district teams attending the institute used to develop their Career Education and Work plan for the 2008-2009 school year.
The document outlines requirements for a community marketplace called BeatNik that connects students and instructors. It describes features like user profiles, class listings, forums, contests, payments, and dashboards for students and instructors. Key points are:
- Students can search, enroll in, and review classes while instructors can add classes and manage students.
- Users include students, instructors, guests, and admins. Instructors require approval to add classes.
- The navigation includes sections for home, teaching, learning, community, contests, and user profiles.
- Dashboards allow users to manage profiles, classes, goals, and engagement. Instructors can add classes and view analytics.
The document outlines various organizations' plans to contribute to the SAIC Crisis Management integrated knowledge environment (HIKE) in year 2. It discusses Stanford KSL enhancing explanation capabilities for the ATP reasoner and merging additional knowledge bases. SRI will help with ontology merging and load information extracted by Textwise. MIT START plans to link to other HIKE systems and expand coverage areas. NWU and CMU did not provide details on their year 2 plans.
Vol1 Demand & Revenue Forecast Final ReportFabio Alves
This document is the final report of Volume 1 of the Brazil TAV Project demand and revenue forecast. It was prepared by Halcrow-Sinergia Consortium in June 2009. The report provides an executive summary that includes ridership forecasts for the TAV express service between Rio de Janeiro and São Paulo, as well as regional services. It also benchmarks the forecasts against other high-speed rail projects internationally. The full report then details the background of the study, existing transport systems, surveys conducted, development of the demand model, assumptions used in the analysis, and ridership forecasts for express and regional services through 2044.
The document provides an overview of NASA's Software Engineering Initiative from 2002 to 2008. The initiative aimed to advance software engineering practices across NASA to improve schedule, cost, quality and delivered functionality. It established groups and policies to improve processes, provide training, infuse new technologies, and increase collaboration. Key impacts included improved planning, use of best practices by contractors, and a foundation for disciplined software development through shared process assets.
Auto-Scaling to Minimize Cost and Meet Application Deadlines in Cloud Workflowsmingtemp
http://www.cs.virginia.edu/~mm5bw/papers/WorkflowAutoScaling.pdf
The presentation for SC 2011
http://dl.acm.org/citation.cfm?id=2063449
www.mingmao.org
This document provides a summary of Divahar Jayaraman's professional portfolio, including expertise in aerospace engineering fields like aerodynamics and structural dynamics, as well as programming languages and software. It also lists professional experience conducting aircraft loads analysis and developing various computational fluid dynamics and structural analysis programs. Projects developed include panel codes, finite element method codes, and computational fluid dynamics solvers.
2005* ApresentaçãO Sobre AviaçãO Executiva Paris Air ShowEmbraer RI
This presentation discusses Embraer's business aviation market and the Legacy jet.
Embraer sees opportunities for growth in the business aviation market which is estimated to reach $33.6 billion by 2014. The Legacy jet gives Embraer competitive advantages through its ability to operate from short runways and high altitude airports. Embraer has enhanced the Legacy's performance and capabilities over time.
Embraer's goal is to become a major player in the business aviation market within 10 years by providing innovative products and services that create value for customers and shareholders. To achieve this, Embraer is conducting in-depth research to understand the business aviation market.
This document summarizes a research study examining a non-hierarchical approach to air tasking in joint air operations using agent-based modeling. The study builds an agent-based air campaign model called ABACUS to test if decentralized execution can achieve the goals of an air campaign in a reasonable way. The model finds that targets are killed over time in simulations with decentralized tasking. While further validation is needed, the results indicate decentralized execution may be a feasible alternative to current hierarchical approaches under certain conditions like a target-rich environment with good intelligence sharing. The next steps are to improve the model and compare decentralized and centralized approaches using efficiency metrics.
CommunityOneEast 09 - Dynamic Languages: the next big thing for the JVM or an...Chris Richardson
Dynamic languages have many benefits but static languages with compile-time checking can also be expressive. The document discusses the rise of dynamic languages on the Java Virtual Machine like Groovy and how they provide benefits like concise syntax and runtime programmability while static languages provide safety through compile-time checking. It then outlines Chris Richardson's presentation agenda on dynamic languages, favorite Groovy features, frustrations with Groovy, and the Scala language which aims to provide both expressiveness and compile-time checking.
Architecture is a foundational element of complex system design. Upfront analysis and architecting helps understand essential requirements and reduce incidental complexity through a well-designed structure. This recommendation promotes investing in system-level thinking to establish a solid foundation addressing the problem, rather than its symptoms.
Image Processing and Cartography with the NASA Vision WorkbenchMatt Hancher
These are the slides from a talk I gave about the NASA Vision Workbench at the FOSS4G conference at the end of 2007. For a more up-to-date discussion of the Vision Workbench, see this presentation instead: http://www.slideshare.net/mdhancher/the-nasa-vision-workbench-reflections-on-image-processing-in-c-presentation
NASA has facilitated the commercialization of over 40 years of technology development. This document lists the top 20 NASA spinoff technologies from the past 5 years that have been successfully transferred to the private sector. They include a water filtration system developed for the ISS that provides clean drinking water worldwide, remote-controlled tractors with precision from GPS technology originally developed for a Mars probe, and a bacterial detection system for spacecraft now used to detect anthrax. Many of the technologies improve healthcare, agriculture, aviation safety, law enforcement, and environmental remediation.
A NASA desenvolveu tecnologias para reciclar urina de astronautas e purificar água no espaço. Uma empresa usou esses conceitos para desenvolver bebidas probióticas à base de água de coco, vendendo mais de 1 milhão de garrafas em 2011. Outra empresa usou bactérias para fermentar chás probióticos.
NASA's Space Technology Program aims to advance technologies from low to mid readiness levels for future NASA missions and other government/commercial applications. It includes elements for early-stage innovation, game-changing technology development, and crosscutting capability demonstrations. The program will employ a portfolio approach across the technology readiness scale and sponsor research at universities, industry, and NASA centers. It will help enable NASA's human spaceflight goals by developing technologies like in-orbit propellant transfer and storage, lightweight modules, and autonomous docking.
A powerpoint summary of technologies highlighted in NASA's 2010 edition of Spinoff, which features recent significant research and development activities across NASA and the successful transfer of NASA technologies to the marketplace. This presentation summarizes the commercial technologies profiled in Spinoff 2010; the full text is available for download at http://spinoff.nasa.gov, and print copies can be requested by calling (301) 286-0561 or through spinoff@sti.nasa.gov.
NASA technology related to 3D imaging, microsystems, and high-resolution imagery was licensed to develop the world's first 3D endoscope for brain surgery. The MARVEL endoscope provides surgeons with a 3D image in close quarters, allowing for improved visibility and understanding of an object's proximity during surgery. It was developed through a partnership between a neurosurgeon and JPL under a Space Act Agreement to improve safety and reduce costs of brain surgeries.
On NASA Space Shuttle Program Hardware and SoftwareMartin Dvorak
This document discusses the history and development of the software used in NASA's Space Shuttle program. It describes how the software evolved from the Apollo guidance computer to the general purpose computers used on the shuttles. It highlights the focus on reliability through redundancy of hardware and software. The development process emphasized statistical analysis, incremental improvements, extensive testing, and maintaining high quality through careful processes and adequate resources.
User Centered Agile Development at NASA - One Groups Path to Better SoftwareBalanced Team
The group at NASA iteratively adopted agile practices over two years to improve their software development process. They started with six month development cycles and shortened this to six weeks and then three weeks. This allowed for more frequent customer feedback and prioritization of work. Daily builds and testing ensured progress was always visible. Their measure of success became working code delivered in frequent iterations rather than presentations or documentation.
Agile Leadership – Is a Servant Leader always the Right Approach?IvanaTerrorBull
There is an accepted wisdom within the Agile community that the right management style is that of the Servant Leader, one who is there to serve the team as a ‘first among equals’. They are not the manager of the team, as the team is self-organising, but rather removes impediments and coaches the team in agile best practices. However, just blindly following this approach in every circumstance can be catastrophic.
This talk is aimed at Scrum Masters, their managers and team members. After the talk attendees will understand:
• the definition of a servant leader and what this means in practice
• the difference between management and leadership
• how to assess the current situation in order to decide the most appropriate leadership style
• when to change leadership style for maximum results
• that a true servant leader is about giving the team what they need, not necessarily what they want
This document provides information on CoreAVI's graphics certification process and products. It discusses their DO-178B/C and DO-254 certification methodology, which involves a 6-phase development process. It also describes their OpenGL SC graphics driver, which has a modular design and over 2000 test procedures to achieve certification. The document addresses topics from CAST-29 and EASA on using COTS graphics processors in safety-critical systems. CoreAVI provides certification packages for their graphics drivers up to DO-178C Level A and DO-254 Level C.
Career Education & Work Gov Inst 2008 Project TemplateSue Fox
The presentation is the scaffolding that all school district teams attending the institute used to develop their Career Education and Work plan for the 2008-2009 school year.
The document outlines requirements for a community marketplace called BeatNik that connects students and instructors. It describes features like user profiles, class listings, forums, contests, payments, and dashboards for students and instructors. Key points are:
- Students can search, enroll in, and review classes while instructors can add classes and manage students.
- Users include students, instructors, guests, and admins. Instructors require approval to add classes.
- The navigation includes sections for home, teaching, learning, community, contests, and user profiles.
- Dashboards allow users to manage profiles, classes, goals, and engagement. Instructors can add classes and view analytics.
The document is the owner's manual for a 2011 GMC Terrain. It provides information on operating vehicle features such as the remote keyless entry system, door locks, windows, seat adjustments, safety belts, mirrors, lighting, climate controls, and transmission. The manual is organized into sections covering different vehicle systems and components.
High Level Software Applications for Machine Control was presented by Shannon Krause and covered:
- Her experience developing control system software at several facilities including the Very Large Array Radio Astronomy Observatory, Thomas Jefferson National Accelerator Facility, and MIT Bates Linear Accelerator Center.
- Concepts in high level software applications including how they are the interface between humans and machines and should be designed around user needs.
- Examples of high level software applications developed in Tcl/Tk, LabVIEW, and other languages at various facilities to monitor and control systems.
Several recent accidents involving controlled flight into terrain (CFIT) in visual conditions at night highlight the risks of nighttime visual flight in remote areas. Proper preflight planning and terrain familiarization are critical to avoid CFIT, as darkness can make visual avoidance of terrain nearly impossible. When receiving radar services, pilots should not rely on air traffic controllers to warn of terrain hazards and should advise ATC if unsure of ability to see and avoid terrain. Following instrument flight rules altitude minimums and using technology like terrain awareness systems can help improve safety for nighttime visual flights.
The TAWS is an avionic system installed in aircraft that uses sensors and computing functions to determine if the aircraft is in danger of colliding with terrain. It comprises components like the FLTA, GPWS, and processors that provide audio and video warnings to pilots if the aircraft path will intersect with high terrain. The system advantageously reduces CFIT accidents by alerting pilots with audio warnings and color-coded terrain displays when the aircraft approaches high terrain, though it has the disadvantage of sharing displays with other systems and its warnings occurring within only 1-2 minutes.
The CREW system provides a virtual research environment to support collaborative research events. It allows users to record events, replay and annotate recordings, and conduct faceted searches across recorded content and related resources. The system was developed through a user-centered design process involving three user groups to ensure it meets researchers' needs. Future work will focus on ongoing user requirements gathering, supported evaluation events, and further development based on user feedback.
Thirty months of microservices. Stairway to heaven or highway to hellSander Hoogendoorn
This is the deck of the talks on microservices I did at both Avisi's #ASAS2016 (Arnhem, NL), Microsoft's #TechDaysNL (Amsterdam, NL) and #GeeCon (Prague, Czech Republic) conferences in September and October 2016.
Microservices are the next hype. Websites are full of introducing posts, books are being written and conferences organized. There’s big promises of scalability and flexibility. However, when you are knee deep in mud as an architect, developer or tester, it’s hard to find out how to get there. Sander Hoogendoorn, independent craftsman and CTO of Klaverblad Insurances, discusses the long and winding road his projects, both greenfield and brownfield, have travelled. Sander will e.g. address polyglot persistence, DDD, bounded contexts, modeling HTTP/REST, continuous delivery and many lessons learned, using many real-life examples.
The document provides an overview of the requirements and processes needed to successfully pass Preliminary Design Review (PDR) and Key Decision Point C (KDP C) under NASA Procedural Requirements 7120.5D. It first discusses categorizing a project based on cost and complexity to determine the appropriate decision authority and governing documents. It then outlines the phases of formulation and implementation in the project lifecycle and the major reviews and decision gates including PDR, which provides approval to proceed to implementation phases. Examples from the Juno project are given to demonstrate how to address the requirements to have a successful PDR while still accomplishing the primary work.
This document provides an update from the Chief Master Sergeant of the Air Force to the Chief of Staff of the Air Force on several close air support issues. It discusses the follow up to a recent friendly fire incident involving a B-52, ongoing efforts to improve joint close air support procedures and equipment, and recommendations to fund additional equipment needed by ground forward air controllers to perform their mission safely and effectively.
SS7 and SIGTRAN technologies continue to be important for connecting new and existing networks due to their proven reliability and ability to support legacy infrastructure. They enable critical applications like value-added services, IP Multimedia Subsystem (IMS) adoption, and the rollout of 4G/LTE networks. Vendors offer integrated hardware modules and software solutions using SS7 and SIGTRAN to help telecom providers accelerate development and reduce costs.
This document provides an overview of NASA and JPL's project lifecycle and design practices for flight projects. It describes the phases and key decision points in the project lifecycle. It also outlines JPL's design principles, flight project practices, and processes for managing technical, schedule, and budget margins. Additionally, it introduces the Certification of Flight Readiness process to document adherence to development practices and assess residual risk for mission success.
Qna L6 S Project Aa Cmp Oxide Range Reduction (Oct 08)Norbert Gloser
The document summarizes a Lean Six Sigma project to improve the uniformity of a CMP oxide film thickness process at a wafer fabrication plant. The project team used DMAIC methodology to define the problem, measure current performance, analyze causes of non-uniformity, improve the process, and establish controls. Specifically, the team defined a goal of reducing oxide thickness variation from 550 angstroms to 320 angstroms to close 70% of the gap with a benchmarking site. The project was expected to yield $4.1 million in annual savings through increased chip output and yield.
This document provides a template and outline for an Air Force program review briefing. The template includes sections for a bottom line up front, program description, concept of operations, requirements, affordability, schedule, funding, risks, and recommendations. It emphasizes key information to include in each section, such as decisions being requested of leadership, outstanding issues, cost and schedule drivers, and risk mitigation activities. The template is intended to guide briefers in concisely summarizing essential information about the program under review.
IGARSS 2011 - RCM, The Making of (AC) (Short).pptgrssieee
The document summarizes the RADARSAT Constellation Mission (RCM) which consists of three small SAR satellites to support operational requirements of the Canadian government. Key points are that it provides improved coverage over RADARSAT-1/2 with a responsive ground segment. The design parameters were driven by continuity of C-band SAR data, improved revisit rates, and a more cost efficient and reliable small satellite design. The project involves phases for definition, implementation, and commissioning, with MDA Systems as the prime contractor and support from Canadian industry.
The document discusses the challenges of accurately estimating costs for large NASA facilities projects. It notes that initial estimates for several Constellation Program facilities were significantly lower than actual costs, with estimates being 2-2.4 times lower than final costs. Historical data can help estimate costs but has limitations as requirements often change. More data is needed to better model facility costs and create more accurate estimates.
The document analyzes findings from 47 NASA project reviews conducted between FY2009 and FY2010. It identifies trends in project strengths and weaknesses based on the 7 assessment criteria from NPR 7120.5D (goals, technical, budget, schedule, resources, risk, management). The analysis found the most common strengths were in management, followed by schedule and budget. The top weaknesses were in budget, schedule, and technical areas. Limitations include variability between review teams and subjective interpretation of findings.
SCA To Date and Motivation for Change. These slides will discuss why the JTRS Program Executive Office (JPEO) is aggressively procuring Software Defined Radio (SDR) consortium and industry assistance to spearhead a high impact evolution of the Software Communications Architecture (SCA) intended to deliver better radio performance along with a smaller footprint for waveforms and radio software. The webcast audience will learn about innovative SCA change proposal details and identified opportunities for near term radio performance impact with rapid market availability of these new capabilities via highly motivated COTS SDR software and development tool vendors.
This document provides an overview of dynamic positioning failure mode and effects analysis (DP FMEA) and spatial analysis for a leading offshore company. It introduces C-MAR Group which specializes in DP services and training. Key points covered include DP classification rules, requirements for 600-person DP-3 vessels, how to perform spatial analysis, and examples of C-MAR's experience conducting DP FMEAs and other DP services in Asia and China for various offshore companies and shipyards.
This document provides information about Zeeshan Khan, a manager at the Network Operations Center (NOC) with over 5 years of experience. It includes his educational background of an MBA in supply chain management and project management as well as an electrical engineering degree. It lists his experience working with various telecommunications vendors and providing consulting, presentations and guest lectures. Contact information is provided at the end. The document appears to be introducing Zeeshan Khan and providing his credentials and background to students or others.
This document discusses the oSCJ project for developing safety-critical applications in Java. It describes safety-critical systems and the challenges of developing such systems. It then provides an overview of the Safety-Critical Java (SCJ) specification, the oSCJ implementation including its virtual machine, libraries, and tools. It also presents benchmark results and discusses future work.
Comparative Study of Object Detection AlgorithmsIRJET Journal
This document compares different object detection algorithms that use convolutional neural networks: Single Shot Detector (SSD), Faster R-CNN, and R-FCN. These algorithms are evaluated based on their speed and accuracy when combined with different feature extractors like VGG-16, ResNet-101, Inception ResNet, and MobileNet. The algorithms are trained on the COCO dataset and their performance is measured using mean average precision (mAP). SSD is found to be the fastest since it performs all computations in one network without needing region proposals. However, Faster R-CNN and R-FCN achieve higher accuracy. The best combinations are found to be Faster R-CNN with ResNet-101 and R-FCN with ResNet
The document discusses soldier modernization efforts, including enhancing capabilities for future soldiers to accomplish missions. It outlines five key soldier system capability areas and various projects to modernize equipment like clothing, weapons, sensors and protection. Global development of integrated soldier systems is mentioned, along with challenges of balancing capabilities, technology insertion and performance parameters.
Sri Balasubramanian, P.E., Chief of the Caltrans Office of Asphalt Pavement, and Jack Van Kirk, P.E., Director of Asphalt Technology for George Reed/Basic Resources, and co-chair of the Asphalt Task Group, part of the joinit Caltrans-industry Rock Products Committee, provide an update on Caltrans asphalt pavement specifications and testing issues. at the CalAPA Spring Asphalt Pavement Conference & Equipment Expo, April 12-13, 2017 in Ontario, Calif.
Cutting Edge Predictive Modeling For ClassificationPankaj Sharma
This document provides an overview of gradient boosting machines (GBM) and their implementation in R. It discusses GBM's ability to balance predictive performance and model complexity. It also briefly mentions other predictive modeling techniques and highlights GBM's prevalence in winning data science competitions. The document examines Leo Breiman's philosophy of letting the data determine the appropriate model. It outlines how GBM can handle various data challenges and describes R packages for GBM and other advanced analytics. Finally, it shares one analyst's experience transitioning from SAS to R for predictive modeling.
Scarab: SAT-based Constraint Programming System in Scala / Scala上で実現された制約プログラ...scalaconfjp
This document discusses Scarab, a SAT-based constraint programming system developed in Scala. Scarab provides a domain-specific language and APIs for modeling constraint satisfaction problems and solving them using SAT encodings and SAT solvers like Sat4j. It aims to provide an expressive, efficient and customizable workbench for developing SAT-based systems. The document gives examples of using Scarab to model and solve the graph coloring problem and pandiagonal Latin square problem. It also discusses Scarab's features like efficiency, portability and ability to leverage advanced SAT solving techniques.
Tesla 2009-2013 and beyond. Check out the amazing progress we've made in the past 4 years This is a presentation made by my colleague Sumit Gupta at the NVIDIA investor Day 11 April 2013.
Updates related on Grid since last meeting in December 2008: Service, resourc...Go Iwai
This document summarizes updates related to grid computing since the last meeting in December 2008. It discusses resource upgrades at KEK, including an additional 2.5 million SPECint2000 by December 2009 and another 2.5 million by March 2010. Plans are outlined to deploy a storage service in early 2010 to expose tape storage to the grid. Operational statistics show over 1,000 ILC jobs run, accounting for around 10% of CPU time and over 1 petabyte of storage used. ILC is reported as the heaviest computing resource consumer at KEK in the past 6 months. Several pending items are also noted including FTS deployment and reconstruction of the KEK-1 grid site.
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.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...Fwdays
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
Session 1 - Intro to Robotic Process Automation.pdf
Crumbley.tim
1. 2011 PM Challenge
NASA Experience with
CMM and CMMI
February, 2011
John C. Kelly & Tim Crumbley
Office of Chief Engineer
2. NASA Experience
with CMM and CMMI
• Outline
– NASA’s experience
with CMMI model
– NASA’s CMMI
requirement
– NASA’s lessons
learned and key
impacts from using
CMMI
Atop twin columns of fire, space shuttle Atlantis
roars into the cloudy sky above Launch Pad 39A at NASA's
Kennedy Space Center in Florida on the STS-125 mission.
2
3. The Three Elements of Project
Success
Process:
a defined method involving steps or operations
People: Technology:
Skills, Training, Application domains,
Management tools, languages,
information, environments
Improved Process + Competent Workforce + Appropriate Technology
=
Reduced Risk, Higher Productivity, and Better Quality
4. Timeline 2000 – 2011 Planned for
NASA Software Engineering Initiative – CMM and CMMI Activities FY11
MSFC LaRC*
MSFC (FSW)
(FSSB)
LaRC* LaRC* LaRC*
JPL (FSSB) (SDAB) JPL
CMMI Level 3 (SDAB)
JSC MSFC (SIL)
GSFC GSFC
CMMI Level 2 LaRC* SDAB LaRC KSC ARC
MSFC GSFC
LaRC* ASDC (FSSB) LaRC GRC
MSFC
CMM Level 3 ARC* JSC
CMM Level 2 LaRC GRC JPL *- Implemented
JPL
MSFC JSC ARC JPL JSC part of the model
2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011
Signed: Software 5 Centers had Signed: Software 8 Centers have
Procedural Procedural
Requirement experience Requirement experience
Software Working NPR 7150.2 using the models NPR 7150.2A using the CMMI model
Group Charter
NPR 7150.2 (2004) NPR 7150.2 A (2009)
Started: NASA SW
Eng Improvement Class A and B - CMMI Level 2 or Class A - CMMI Level 3
Initiative CMM Level 3 Class B - CMMI Level 2
Class C - Center Decision Class C - Center Decision
CMM/CMMI Appraisals & Consultations at NASA Centers
Software Engineering Training and SEI Training at NASA Centers 4
5. NASA CMMI Summary
Completed SW Engineering Appraisals from FY07-FY10
CMMI = Capability Maturity Model Integrated (Carnegie Mellon University – SW Engineering Institute)
Center/Organization Rating (SCAMPI A by Date # Type Organizational Software Classes
Certified Appraiser) Projects size Assessed
LaRC- ASDC PP(CL3), CM(CL1) Nov-06 1 Data Center Support 85 Class C
MSFC ML3 Apr-07 3 Development 63 Class A, B and C
JPL ML3 Sep-07 7 Dev & Maintenance 1000 Class A, B and C
GSFC ML2 + RSKM(2) May-08 4 Dev & Maintenance 600 Class A, B and C
LaRC- FSSB ML2 + CL3 Oct-08 3 Services 5 Class B & C
LaRC- SDAB PP(CL3), REQM(CL3), Mar-09 4 Development 21 Class B & C
CM(CL3), MA(CL3)
JSC ML2 Apr-09 4 Development 90 Class A, B, C and D
KSC ML2 Sep-09 1 Development 225 Class A, B and C
MSFC – SIL ML2 + CL3 May-2010 1 Development 50 Class C
ARC –ISD ML2 May-2010 6 Development 63 Class B & C
(Code TI)
GRC-Flt SW ML2 Aug 2010 2 Development 22 Class C & D
MSFC-Flt SW ML3 Aug 2010 1 Development 75 Class A
JPL – Mission SW ML3 Sept 2010 9 Development & 950 Class B and C
Maintenance
5
6. Sample of NASA Industry Partner Ratings
NASA Projects Industry Partners CMMI
Level
Shuttle Primary Avionics Software System (PASS), Shuttle SAIL test United Space Alliance Flight Software Element (FSWE) Level 5
facility, Orion Crew Exploration Vehicle (Orion)
International Space Station (C&DH), Ares Boeing Level 3
Orion Crew Exploration Vehicle (Orion) Lockheed Martin Corporation Level 3
Orion Crew Exploration Vehicle (Orion), Ares Honeywell Level 3
Orion Crew Exploration Vehicle (Orion) ATK Level 3
Ares Draper Level 3
Ares J-2X, Orion Crew Exploration Vehicle (Orion), Space Shuttle Hamilton Sundstrand Rocketdyne / Pratt & Whitney Level 3
Main Engine Rocketdyne
Ares, Deep Impact 1 Ball Level 3
James Webb Space Telescope Northrop Grumman Level 3
GRAIL, Juno Lockheed-Martin Space and Exploration Systems Level 3
Ground Systems Engineering (GSE) Checkout, Assembly and Boeing Level 3
Payload Processing Services (CAPPS) Kennedy Space Center (KSC)
ISS Environmental Control and Life Support Systems, Orion Crew Hamilton Sundstrand Level 3
Exploration Vehicle (Orion)
GOES-R Harris IT Services Corporation Level 3
MSFC Engineering Support Contractor Jacobs Engineering Level 3
STEREO Johns Hopkins University Applied Physics Laboratory Level 3
NASA Software IV&V Services, JSC Support Contractor L-3 STRATIS Level 3
KSC SupportShuttle support United Space Alliance, LLC Level 3
NASA Aircraft Management Information System (NAMIS) software SAIC, Aircraft Operations Support System (AOSS) Level 3
JSC Support Contractor Tietronix Level 2
7. NASA’s Software Engineering Requirements
• Software engineering is a core capability and a key enabling technology for
NASA's missions and supporting infrastructure.
• The NASA Software Engineering Procedural Requirements (NPR 7150.2A)
supports the implementation of the NASA Policy Directive (NPD) 7120.4,
NASA Engineering and Program/Project Management Policy.
• The NASA Software Engineering Requirements provide a minimal set of
requirements established by the Agency for software acquisition,
development, maintenance, retirement, operations, and management.
• The NASA Software Engineering Requirements are intended to support
NASA programs and projects to accomplish their planned goals (e.g.,
mission success, safety, schedule, and budget) while satisfying their
specified requirements.
• The NASA Software Engineering Requirements provide a set of software
engineering requirements in generic terms to be applied throughout NASA
and its contractor community.
7
8. Profile of NPR target audience
Advances
Early Progressive Slow Entrenched
Adopters Users Adopters Resisters
8
9. Purpose of NPRs
Shift target audience to
the left 10 - 25%
Advances
Early Progressive Slow Entrenched
Adopters Users Adopters Resisters
This is our target after putting the NPR in place and after each NPR update cycle
9
10. NASA-wide Software Classification*
Class A Space Flight Human Rated Software Systems
Class B Non-Human Space Rated Software Systems
OCE
Class C Mission Support Software & Facilities
Class D Analysis and Distribution Software
Class E Development Support Software
(e.g., Class A – C is mostly software developed or acquired for Highly Specialized IT systems)
Class F General Purpose Computing Software
(Multi-Center or Multi-Program/Project)
Class G General Purpose Computing Software
(Single Center or Project)
Class H General Purpose Desktop Software
* Established by NPR 7150.2A 10
11. NASA Software Engineering Requirements, NPR 7150.2
CMMI Requirement
• [SWE-032] The project shall ensure that software is acquired, developed and
maintained by an organization with a non-expired Capability Maturity Model
Integration® for Development (CMMI-DEV) rating as measured by a Software
Engineering Institute (SEI) authorized or certified lead appraiser as follows:
– For Class A software: CMMI-DEV Maturity Level 3 Rating or higher for software,
or CMMI-DEV Capability Level 3 Rating or higher in all CMMI-DEV Maturity Level
2 and Maturity Level 3 process areas for software.
– For Class B software: CMMI-DEV Maturity Level 2 Rating or higher for software,
or CMMI-DEV Capability Level 2 Rating or higher for software in the following
process areas:
• a. Requirements Management.
• b. Configuration Management.
• c. Process and Product Quality Assurance.
• d. Measurement and Analysis.
• e. Project Planning.
• f. Project Monitoring and Control.
• g. Supplier Agreement Management (if applicable).
– For Class C software: The required CMMI-DEV Maturity Level for Class C
software will be defined per Center or project requirements.
11
12. CMMI Requirement Notes
• Note: Organizations who have completed Standard CMMI® Appraisal Method for
Process Improvement (SCAMPISM) Class A appraisals against the CMMI-DEV Model
are to maintain their rating and have their results posted on the SEI web site so that
NASA can assess the current maturity/capability rating. Software development
organizations need to be reappraised and keep an active appraisal rating posted on the
SEI web site during the time that they are responsible for the development and
maintenance of the software.
• Note: For Class A software development only, a transition period to obtain a CMMI-
DEV Maturity/Capability Level 3 Rating will be allowed for organizations developing
Class A software per the NASA Headquarters Office of the Chief Engineer approved
Center Software Engineering Improvement Plan as described in SWE-003, SWE-004,
and SWE-108.
• Note: For Class B software, in lieu of a CMMI rating by a development organization,
the project will conduct an evaluation, performed by a qualified evaluator selected
by the Center Engineering Technical Authority, of the seven process areas listed in
SWE-032 and mitigate any risk, if deficient. This exception is intended to be used in those
cases in which NASA wishes to purchase a product from the "best of class provider", but
the best of class provider does not have the required CMMI rating. When this exception
is exercised, the Center Engineering Technical Authority should be notified.
12
13. CMM/CMMI Lessons Learned by NASA
• Preparing for an appraisal is where you get the
measurable process improvement
• CMMI process helped Centers establish a baseline
of where they are
• Develop an extensive set of “tools” (i.e., templates,
spreadsheets) to help projects with CMMI practices
and artifacts
– Use of toolset helped projects reach
compliance much faster
• Mentors can help get Project tool use started and
help Projects tailor the artifacts
• Established sponsorship across departments
– Management Steering Group
– Was difficult to get mid-level managers to
“own” improvement program
• Established early on a relationship with the Lead
Appraiser
The perfectly picturesque spiral galaxy
• PIID development and artifact collection known as Messier 81, or M81
– PIIDs and artifacts were maintained on a
server for ease of access and review
• Importance of interview preparation and training
13
14. CMM/CMMI Lessons Learned by NASA
• Use the workshops to review the processes in
depth and reinforced the tool sets
• Tracking Progress, determine a method for
projects to report progress
• Many of our projects need basic project
management and configuration management
training
• CMMI assessments helped identify areas for
process and project improvement
• Despite initial reluctance, pre-appraisal was a
positive experience for our projects - laid a good
foundation for future involvement
• Projects appreciated systematic and analytical
feedback on what they are doing
• Measurement and analysis is a big challenge
• Improved quality and review of management plan
early in the life cycle and reuse of the plans for
new projects
Mars
• Resource planning and tracking at the individual
Image Credit: NASA/JPL-Caltech
process level provided little additional benefit to
the projects
• Smaller projects need to have light-weight
processes to avoid being smothered (especially
for a one person task)
14
15. CMMI Key Impacts at NASA
• Reduces risk of software failure - Increases mission safety
– Improvement processes based on best practices in Industry and
Government
– Risk management much improved on software subsystems--Previously
there was little monitoring of risks
• More predictable software cost estimates and delivery schedules
– Data showed projects working within CMMI software framework & best
practices had increased accuracy in cost estimates and smaller growth in
resources over the lifecycle
• Smarter buyer of contracted out software
– Educating the NASA workforce on best practices in Software Engineering
• More defects found and removed earlier
• Reduces duplication of efforts between projects
• Increases ability to meet the challenges of evolving software
technology
• Software development planning has been improved across the
Agency
– There is a growing consensus among the practitioners and software
managers that working to a defined process has substantial benefits.
– Vast improvement in planning of software projects and in monitoring
progress
Space Shuttle Launch picture
• NASA’s contractor community has heard the word that the bar
from Disney’s Castle
has been raised with respect to software engineering and is
responding appropriately
– NPR 7150.2A, Software Engineering Requirements (update Nov 2009)
15
16. CMMI Key Impacts at NASA
• A solid foundation and structure is now in place
for developing software in a disciplined manner
– More uniformity in management plans, reviews, test
plans, status reporting Risk management much
improved on software subsystems--Previously there
was little monitoring of risks
– Data management and configuration management has
improved
– Improve the working relationships between Engineering
and Safety and Mission Assurance with respect to
software engineering
• The Agency is better prepared for major
programs and projects than it was 8 years ago
– Software teams and software quality engineers are
working together to assure compliance to standards, to
improve quality
• The knowledge and skills of the NASA software
engineering community has significantly
improved
– We have seen significant cultural changes. Space Shuttle Atlantis Rollout at
• Extensive mentoring program established to Kennedy Space Center
improve software practices April 2010
• Our projects are now better managed –
particularly in the area of progress tracking
– Now we know exactly where we are in the project and
how long it’s likely to take to finish
16
17. Summary of NASA’s Experience
with CMM and CMMI
Why improve processes? Because process is the foundation for all other improvements, and lasting
improvements are not possible without it.
If a performance management system is not in use, leadership is unaware of what is and is not working.
CMMI is a proven approach to performance management – with more than a decade of results showing
it does work.
Simply deciding to “do CMMI” is not enough
to achieve benefits.
Defining good processes, using them, measuring
the results, and making improvements based on
what you learn are all key to reaping the benefits
of process improvement.
The CMMI models are one part of a comprehensive
approach to process improvement that helps
organizations understand
• why they should improve
• what frameworks and tools would best fit their
needs
• how to implement them Apollo 8, the first manned mission to the moon
17
Editor's Notes
10 year effort led out of the NASA Chief Engineers office at HQ. Dr. John C. Kelly is the Program Executive for the Initiative.
Started the initiative in 2002First set of NASA Software Engineering Requirements were signed off in 2004MSFC and Then JPL both reach CMMI ML3, Over the last 10 years 8 of the ten NASA Centers have successfully completed a CMM and or CMMI assessmentUpdated set of NASA Software Engineering Requirements were signed off in 2009
this slide pertains to the time when the NPR was being developed