CXperf is a parallel application analysis tool that helps developers improve the performance of applications on Exemplar parallel servers. It analyzes applications, supports multiple parallel programming models, and interprets results visually. CXperf gathers performance measurements during application execution and then provides graphical analysis to help identify optimization opportunities. This helps developers fine-tune applications to more efficiently utilize complex HPC architectures.
Kaushik Kumar Dash is a technical lead at Honeywell with 9 years of experience developing safety critical software for avionics projects. He has extensive skills in C, C++, Ada83 and experience across the SDLC from requirements to testing. Some of his achievements include receiving individual and team excellence awards for his work on flight management systems and user interfaces. He is seeking new opportunities to further his career and expand his technical knowledge.
The document discusses IBM's Rational solution for model-based systems and software engineering. It provides an overview of IBM tools that can be used together as part of a solution to help organizations develop safe and compliant software, including Rational Team Concert for project planning and collaboration, DOORS for requirements management, Rhapsody for architecture and design, and Quality Manager for quality management and testing. The solution supports processes like DO-178C and provides customizable process guidance, tool integration, and process enactment capabilities.
With around two decades of existence, the community of Software Product Line (SPL) researchers and practitioners is thriving as can be attested by the extensive research output and the numerous successful industrial projects. Education has a key role to support the next generation of engineers to build highly complex SPLs. Yet, it is unclear how SPLs are taught, what are the possible missing gaps and difficulties faced, what are the benefits, or what is the material available. In this paper, we carry out a survey with over 30 respondents with the purpose of capturing a snapshot of the state of teaching in our community. We report and discuss quantitative as well as qualitative results of the survey. We build upon them and sketch six concrete actions to continue improving the state of practice of SPL teaching.
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Presentation for bcs citp assessment interviewmarkvard
A 10 minute presentation referencing IT works I have been personally responsible for. It was presented as part of an assessment interview to become Chartered IT Professional (CITP) Sep 2019.
The document introduces the Open-DO initiative, which aims to promote openness and cooperation in the DO-178 certification community for avionics software. It discusses the benefits of open source communities and applying agile principles. Open-DO would provide shared certification workflows, templates, tools and educational materials to help lower costs and foster innovation. Success will depend on engaging certification authorities, industry leaders, tool providers and academics around open governance and certification of example projects.
Open-DO: Towards a Lean Approach for Certification (Cyrille Comar)AdaCore
In this series of talks, our panel of experts present real world examples that illustrate how Lean Production concepts are being successfully applied to software development. In particular to applications that have to meet the highest levels of safety and security.
CXperf is a parallel application analysis tool that helps developers improve the performance of applications on Exemplar parallel servers. It analyzes applications, supports multiple parallel programming models, and interprets results visually. CXperf gathers performance measurements during application execution and then provides graphical analysis to help identify optimization opportunities. This helps developers fine-tune applications to more efficiently utilize complex HPC architectures.
Kaushik Kumar Dash is a technical lead at Honeywell with 9 years of experience developing safety critical software for avionics projects. He has extensive skills in C, C++, Ada83 and experience across the SDLC from requirements to testing. Some of his achievements include receiving individual and team excellence awards for his work on flight management systems and user interfaces. He is seeking new opportunities to further his career and expand his technical knowledge.
The document discusses IBM's Rational solution for model-based systems and software engineering. It provides an overview of IBM tools that can be used together as part of a solution to help organizations develop safe and compliant software, including Rational Team Concert for project planning and collaboration, DOORS for requirements management, Rhapsody for architecture and design, and Quality Manager for quality management and testing. The solution supports processes like DO-178C and provides customizable process guidance, tool integration, and process enactment capabilities.
With around two decades of existence, the community of Software Product Line (SPL) researchers and practitioners is thriving as can be attested by the extensive research output and the numerous successful industrial projects. Education has a key role to support the next generation of engineers to build highly complex SPLs. Yet, it is unclear how SPLs are taught, what are the possible missing gaps and difficulties faced, what are the benefits, or what is the material available. In this paper, we carry out a survey with over 30 respondents with the purpose of capturing a snapshot of the state of teaching in our community. We report and discuss quantitative as well as qualitative results of the survey. We build upon them and sketch six concrete actions to continue improving the state of practice of SPL teaching.
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Presentation for bcs citp assessment interviewmarkvard
A 10 minute presentation referencing IT works I have been personally responsible for. It was presented as part of an assessment interview to become Chartered IT Professional (CITP) Sep 2019.
The document introduces the Open-DO initiative, which aims to promote openness and cooperation in the DO-178 certification community for avionics software. It discusses the benefits of open source communities and applying agile principles. Open-DO would provide shared certification workflows, templates, tools and educational materials to help lower costs and foster innovation. Success will depend on engaging certification authorities, industry leaders, tool providers and academics around open governance and certification of example projects.
Open-DO: Towards a Lean Approach for Certification (Cyrille Comar)AdaCore
In this series of talks, our panel of experts present real world examples that illustrate how Lean Production concepts are being successfully applied to software development. In particular to applications that have to meet the highest levels of safety and security.
This document summarizes a technical paper that discusses the use of design for manufacture (DFM) and design for assembly (DFA) tools in modern manufacturing. It describes how DFM and DFA aim to reduce costs by integrating design and manufacturing considerations. Software tools are presented that help with tasks like estimating part costs, assembly times, and evaluating design alternatives. The principles and approaches of DFM, DFA, and integrated design tools are outlined.
Track A- The convergence of fabless - primesenschiportal
This document discusses the convergence of fabless semiconductor companies towards application-driven product design and complete solutions. It notes that original equipment manufacturers now look for holistic solutions from partners rather than just chips. This has driven fabless companies to take on more roles in system design, software development, and manufacturing to remain competitive in delivering qualified reference designs, full bills of materials, and end-to-end solutions to OEMs. The key takeaway is that fabless companies must expand beyond chip design and sales to provide more complete solutions driven by applications and user experience in order to meet OEM demands.
Track A- The convergence of fabless - primesenschiportal
This document discusses the convergence of fabless semiconductor companies towards application-driven product design and complete solutions. It notes that original equipment manufacturers now look for holistic solutions from partners rather than just chips. This has driven fabless companies to take on more roles in system design, software development, and manufacturing to remain competitive in delivering qualified, cost-effective reference designs to OEMs. The key takeaway is that fabless companies must expand beyond chip design and do "more than Moore" to succeed in this new model where end user experience and applications are the driving factors over just chip performance and cost.
This document summarizes a technical paper about design for manufacture (DFM) and design for assembly (DFA) tools. It discusses how DFM and DFA principles were developed to improve manufacturability and reduce costs. Software tools that integrate DFM and DFA analysis are presented, including the Boothroyd-Dewhurst software. The paper concludes by examining decision models for selecting DFM/DFA software based on required functions, supported processes, interfaces, and operating systems.
The document outlines the objectives and key concepts covered in Chapter 14 of the textbook "Accounting Information Systems, 6th edition". The objectives include the in-house development phase of the SDLC, tools used such as CASE and PERT/Gantt charts, structured vs object-oriented design approaches, documentation types, and the commercial software option. It then covers the phases of SDLC in more detail including in-house development, commercial packages, and maintenance. Design approaches like structured and object-oriented are defined. Documentation, testing, training and post-implementation review are discussed as part of system delivery.
Deployment Automation for Hybrid Cloud and Multi-Platform EnvironmentsIBM UrbanCode Products
This document discusses how IBM's UrbanCode Deploy product can be used to automate application deployments across hybrid cloud and multi-platform environments. It provides examples of how UrbanCode Deploy supports deploying applications to systems like IBM z/OS, distributed systems, private clouds, public clouds and PaaS platforms in an automated and unified manner using patterns and templates. The document also discusses reference architectures and case studies for implementing continuous delivery pipelines spanning both on-premise and cloud infrastructures.
Continuous Delivery: Fly the Friendly CI in Pivotal Cloud Foundry with ConcourseVMware Tanzu
This document provides an overview of continuous integration (CI) and continuous delivery (CD) using Concourse. It introduces Concourse and discusses why containers and pipelines are useful for CI/CD. It then demonstrates how to use Concourse in practice with examples and explains how to get started using Concourse for CI/CD workflows. The key aspects covered are Concourse's simple and scalable pipeline model using resources, tasks, and jobs, how containerization provides dependable and isolated executions, and how pipelines allow flexible yet efficient software testing and deployment.
Oracle OpenWorld 2009 AIA Best PracticesRajesh Raheja
Oracle OpenWorld 2009 Session S311197
Jedi Masters Reveal
Oracle Application Integration Architecture (AIA) Foundation Pack Best Practices
Building Process Integrations
The software management and engineering in the AI-oriented projects tutorialrpietruszkiewicz
This document discusses software project management techniques that can be applied to AI-oriented software projects. It begins with an introduction to AI projects and software project management. It then covers topics like software design methodologies, programming languages, libraries, testing, and examples of AI software implemented using different technologies. The overall message is that AI projects require specialized software and can benefit from established project management practices to help deal with their unpredictable nature.
The document discusses new product development and competitive advantage through products and services. It covers key aspects of the product development process including design, quality, issues like robust and modular design, and computer-aided design and manufacturing. It also discusses defining the product for manufacturing through engineering drawings, bills of materials, group technology, and production documents. Service design is briefly covered as well. The objective is to develop a product strategy that meets market demands and provides a competitive advantage.
The document discusses various topics related to the social, ethical and legal environment of software development including responsibilities of developers, quality processes, copyright and licensing issues, commercial requirements, and development approaches and methodologies. Specifically, it covers developer responsibilities to ensure quality, virus-free solutions and be responsive to users, as well as potential legal ramifications. It also discusses copyright laws, software licensing types, and preventing software piracy. Various software development approaches and methodologies are outlined such as waterfall, prototyping, RAD and JAD. Design documentation and techniques like flowcharts, data flow diagrams, screen designs and storyboards are also summarized.
How to Scale Operations for a Multi-Cloud Platform using PCFVMware Tanzu
What’s in a cloud platform? Turns out, often several clouds! Companies automate operations in a cloud by treating all components as commodities. However, at enterprise- scale, different business requirements dictate deploying multiple clouds including:
- Hybrid infrastructures and multiple cloud providers
- Compliance with country privacy laws and different security standards
- Specialization requests
The most advanced Pivotal Cloud Foundry (PCF) customers engineer their entire cloud platform, including their multitude of PCF instances, as a product. They create pervasive automation, treat their infrastructure as code, and continuously test and update their platform with delivery pipelines.
In this webinar we’ll discuss how companies are scaling operations of their multi-cloud platforms with Pivotal Cloud Foundry.
We’ll cover:
- Why enterprises deploy multiple clouds
- What operational challenges this causes
- How PCF customers are applying DevOps techniques and tools to platform automation
- An idealized tool stack for a engineering a multi-cloud platform at scale
- How to improve your platform engineering
We thank you in advance for joining us.
The Pivotal Team
Presenter : Greg Chase, James Ma, Caleb Washburn, Pivotal
This document discusses strategies for modernizing applications and moving workloads to Kubernetes and container platforms like Pivotal Container Service (PKS). It recommends identifying candidate applications using buckets based on factors like programming language, dependencies, and access to source code. It outlines assessing applications' business value and technical quality using Gartner's TIME methodology to prioritize efforts. The document provides an overview of PKS and how it can provide benefits like increased speed, stability, scalability and cost savings. It recommends starting projects by pushing a few applications to production on PKS to measure ROI metrics.
This document discusses strategies for modernizing applications and moving workloads to Kubernetes and container platforms like Pivotal Container Service (PKS). It recommends identifying candidate applications using buckets based on factors like programming language, dependencies, and access to source code. It outlines assessing applications' business value and technical quality using Gartner's TIME methodology to prioritize efforts. The document provides an overview of PKS and how it can provide benefits like increased speed, security, scalability and cost savings. It recommends starting projects by pushing a few applications to production on PKS to measure ROI metrics.
IBM's Problem Determination Tools have evolved since their introduction in 2000 to become more robust and functionally superior through ongoing releases. Customers are migrating to the tools due to issues with older products, demands for more sophisticated development and testing tools, and rising maintenance fees for other solutions. The Problem Determination Tools suite features capabilities for supporting SOA/composite applications, optimizing performance, debugging applications, managing and testing data, and conducting various types of testing.
What’s new in Rational collaborative lifecycle management 2011?IBM Danmark
Jan Ekstrøm, Rational Solution Architect - What’s new in Rational Collaborative Lifecycle Management 2011?
Præsentationen er fra Jazz Roadshow 2011.
Se mere på: http://www.smarterbusiness.dk
Building Scalable Development EnvironmentsShahar Evron
The document provides guidelines for building scalable development environments in 3 main areas:
1. Establish standard programming styles and coding practices to reduce bugs and improve readability. This includes using source control, peer review, and coding standards.
2. Implement a multi-tier environment with separate development, staging, and production servers to allow for testing at each stage.
3. Employ practices like unit testing, functional testing, and benchmarking to ensure quality and performance as the system grows.
Rhapsody's model-driven development environment allows developers to work how they want through model and code synchronization. It supports software asset reuse and visualizing legacy code for clarity. Model-driven testing helps improve quality and productivity. Rhapsody provides an open environment to continue using existing tools.
This document summarizes a technical paper that discusses the use of design for manufacture (DFM) and design for assembly (DFA) tools in modern manufacturing. It describes how DFM and DFA aim to reduce costs by integrating design and manufacturing considerations. Software tools are presented that help with tasks like estimating part costs, assembly times, and evaluating design alternatives. The principles and approaches of DFM, DFA, and integrated design tools are outlined.
Track A- The convergence of fabless - primesenschiportal
This document discusses the convergence of fabless semiconductor companies towards application-driven product design and complete solutions. It notes that original equipment manufacturers now look for holistic solutions from partners rather than just chips. This has driven fabless companies to take on more roles in system design, software development, and manufacturing to remain competitive in delivering qualified reference designs, full bills of materials, and end-to-end solutions to OEMs. The key takeaway is that fabless companies must expand beyond chip design and sales to provide more complete solutions driven by applications and user experience in order to meet OEM demands.
Track A- The convergence of fabless - primesenschiportal
This document discusses the convergence of fabless semiconductor companies towards application-driven product design and complete solutions. It notes that original equipment manufacturers now look for holistic solutions from partners rather than just chips. This has driven fabless companies to take on more roles in system design, software development, and manufacturing to remain competitive in delivering qualified, cost-effective reference designs to OEMs. The key takeaway is that fabless companies must expand beyond chip design and do "more than Moore" to succeed in this new model where end user experience and applications are the driving factors over just chip performance and cost.
This document summarizes a technical paper about design for manufacture (DFM) and design for assembly (DFA) tools. It discusses how DFM and DFA principles were developed to improve manufacturability and reduce costs. Software tools that integrate DFM and DFA analysis are presented, including the Boothroyd-Dewhurst software. The paper concludes by examining decision models for selecting DFM/DFA software based on required functions, supported processes, interfaces, and operating systems.
The document outlines the objectives and key concepts covered in Chapter 14 of the textbook "Accounting Information Systems, 6th edition". The objectives include the in-house development phase of the SDLC, tools used such as CASE and PERT/Gantt charts, structured vs object-oriented design approaches, documentation types, and the commercial software option. It then covers the phases of SDLC in more detail including in-house development, commercial packages, and maintenance. Design approaches like structured and object-oriented are defined. Documentation, testing, training and post-implementation review are discussed as part of system delivery.
Deployment Automation for Hybrid Cloud and Multi-Platform EnvironmentsIBM UrbanCode Products
This document discusses how IBM's UrbanCode Deploy product can be used to automate application deployments across hybrid cloud and multi-platform environments. It provides examples of how UrbanCode Deploy supports deploying applications to systems like IBM z/OS, distributed systems, private clouds, public clouds and PaaS platforms in an automated and unified manner using patterns and templates. The document also discusses reference architectures and case studies for implementing continuous delivery pipelines spanning both on-premise and cloud infrastructures.
Continuous Delivery: Fly the Friendly CI in Pivotal Cloud Foundry with ConcourseVMware Tanzu
This document provides an overview of continuous integration (CI) and continuous delivery (CD) using Concourse. It introduces Concourse and discusses why containers and pipelines are useful for CI/CD. It then demonstrates how to use Concourse in practice with examples and explains how to get started using Concourse for CI/CD workflows. The key aspects covered are Concourse's simple and scalable pipeline model using resources, tasks, and jobs, how containerization provides dependable and isolated executions, and how pipelines allow flexible yet efficient software testing and deployment.
Oracle OpenWorld 2009 AIA Best PracticesRajesh Raheja
Oracle OpenWorld 2009 Session S311197
Jedi Masters Reveal
Oracle Application Integration Architecture (AIA) Foundation Pack Best Practices
Building Process Integrations
The software management and engineering in the AI-oriented projects tutorialrpietruszkiewicz
This document discusses software project management techniques that can be applied to AI-oriented software projects. It begins with an introduction to AI projects and software project management. It then covers topics like software design methodologies, programming languages, libraries, testing, and examples of AI software implemented using different technologies. The overall message is that AI projects require specialized software and can benefit from established project management practices to help deal with their unpredictable nature.
The document discusses new product development and competitive advantage through products and services. It covers key aspects of the product development process including design, quality, issues like robust and modular design, and computer-aided design and manufacturing. It also discusses defining the product for manufacturing through engineering drawings, bills of materials, group technology, and production documents. Service design is briefly covered as well. The objective is to develop a product strategy that meets market demands and provides a competitive advantage.
The document discusses various topics related to the social, ethical and legal environment of software development including responsibilities of developers, quality processes, copyright and licensing issues, commercial requirements, and development approaches and methodologies. Specifically, it covers developer responsibilities to ensure quality, virus-free solutions and be responsive to users, as well as potential legal ramifications. It also discusses copyright laws, software licensing types, and preventing software piracy. Various software development approaches and methodologies are outlined such as waterfall, prototyping, RAD and JAD. Design documentation and techniques like flowcharts, data flow diagrams, screen designs and storyboards are also summarized.
How to Scale Operations for a Multi-Cloud Platform using PCFVMware Tanzu
What’s in a cloud platform? Turns out, often several clouds! Companies automate operations in a cloud by treating all components as commodities. However, at enterprise- scale, different business requirements dictate deploying multiple clouds including:
- Hybrid infrastructures and multiple cloud providers
- Compliance with country privacy laws and different security standards
- Specialization requests
The most advanced Pivotal Cloud Foundry (PCF) customers engineer their entire cloud platform, including their multitude of PCF instances, as a product. They create pervasive automation, treat their infrastructure as code, and continuously test and update their platform with delivery pipelines.
In this webinar we’ll discuss how companies are scaling operations of their multi-cloud platforms with Pivotal Cloud Foundry.
We’ll cover:
- Why enterprises deploy multiple clouds
- What operational challenges this causes
- How PCF customers are applying DevOps techniques and tools to platform automation
- An idealized tool stack for a engineering a multi-cloud platform at scale
- How to improve your platform engineering
We thank you in advance for joining us.
The Pivotal Team
Presenter : Greg Chase, James Ma, Caleb Washburn, Pivotal
This document discusses strategies for modernizing applications and moving workloads to Kubernetes and container platforms like Pivotal Container Service (PKS). It recommends identifying candidate applications using buckets based on factors like programming language, dependencies, and access to source code. It outlines assessing applications' business value and technical quality using Gartner's TIME methodology to prioritize efforts. The document provides an overview of PKS and how it can provide benefits like increased speed, stability, scalability and cost savings. It recommends starting projects by pushing a few applications to production on PKS to measure ROI metrics.
This document discusses strategies for modernizing applications and moving workloads to Kubernetes and container platforms like Pivotal Container Service (PKS). It recommends identifying candidate applications using buckets based on factors like programming language, dependencies, and access to source code. It outlines assessing applications' business value and technical quality using Gartner's TIME methodology to prioritize efforts. The document provides an overview of PKS and how it can provide benefits like increased speed, security, scalability and cost savings. It recommends starting projects by pushing a few applications to production on PKS to measure ROI metrics.
IBM's Problem Determination Tools have evolved since their introduction in 2000 to become more robust and functionally superior through ongoing releases. Customers are migrating to the tools due to issues with older products, demands for more sophisticated development and testing tools, and rising maintenance fees for other solutions. The Problem Determination Tools suite features capabilities for supporting SOA/composite applications, optimizing performance, debugging applications, managing and testing data, and conducting various types of testing.
What’s new in Rational collaborative lifecycle management 2011?IBM Danmark
Jan Ekstrøm, Rational Solution Architect - What’s new in Rational Collaborative Lifecycle Management 2011?
Præsentationen er fra Jazz Roadshow 2011.
Se mere på: http://www.smarterbusiness.dk
Building Scalable Development EnvironmentsShahar Evron
The document provides guidelines for building scalable development environments in 3 main areas:
1. Establish standard programming styles and coding practices to reduce bugs and improve readability. This includes using source control, peer review, and coding standards.
2. Implement a multi-tier environment with separate development, staging, and production servers to allow for testing at each stage.
3. Employ practices like unit testing, functional testing, and benchmarking to ensure quality and performance as the system grows.
Rhapsody's model-driven development environment allows developers to work how they want through model and code synchronization. It supports software asset reuse and visualizing legacy code for clarity. Model-driven testing helps improve quality and productivity. Rhapsody provides an open environment to continue using existing tools.
Kunskapsbaren 2011 Stockholm - Mobila trender & strategier
Kunskapsbaren 2011 Linköping - Att produktifiera mjukvara
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15. Basic components of a SPL architecture PL Basics Source: On Software Engineering, http://sftweng.wcorona.com
16.
17. Check-out Compile Execute Product Line repository %Source code pragma if alpha then good else bad endif 010011010 0110010 010110 000101011 1100010 0100010 0 SW Build Software production / build process
18.
19.
20.
21. Binding Time overview SW Build Binding at Aspect Check-out-time Compile-time Run-time Creates Different source code variants Different object code variants Different instances Used for Reliable configuration Implementation oriented configuration Fast reconfiguration Example When security / IRP aspects is important Target / platform variation Reconfiguration at end-user site
22.
23.
24. Organizational changes when adopting software product lines The three essentialls Source: www.sei.cmu.edu Organization
25. Organization for and ordinary production without software product lines Source: www.biglever.com Organization