Goals of the presentation:
* to analyze the AutomotiveSPICE process scopes and measurement purposes
* to discuss the measures that can be adopted in an Automotive project
* to propose a possible \'top metrics\' scope and boundary for SPICE-compliant projects
[See also www.automotive-spin.it]
Mapping Automotive SPICE: Achieving Higher Maturity & Capability LevelsLuigi Buglione
As usual, when planning to improve a process, an organization needs to compare the current version (‘as-is’) with the new, desired one (‘to-be’). The possible content for such improvement comes from comparisons and mappings with similar processes kept from different sources. In the ICT arena such kind of studies are quite frequent but not always done for covering all models, for instance in the Automotive field. Again, often such comparisons have been done between not directly comparable elements (e.g. any management system standard as ISO 9001 is a requirement model, while maturity models such as CMMI or ISO/IEC 15504 represent process meta-models, with a different aim and contents). The aim of this presentation is to provide a new mapping between AutomotiveSPICE (A-SPICE) and the ISO 9001 norm for the Automotive sector (ISO/TS 16494:2009). This new mapping could be to provide tips for giving contents to ISO clauses but directly from A-SPICE, for more valuable improvement projects.
Automotive SPICE® 3.0 - What is new and what has changed?Dominik Strube
With our presentation "Automotive SPICE® 3.0 - What is new and what has changed?" you will know the changes implemented in the new version of Automotive SPICE® v3.0. This is provided free of charge.
This presentation has been created by leading intacsTM SPICE principal assessors. Please feel free to share this documentation among your colleagues, as long as the content is not altered.
Hirschmann: Automotive SPICE Requirements for development process and tools Intland Software GmbH
The document discusses requirements for development processes and tools based on Automotive SPICE standards. It describes how an automotive company uses various tools like Doors, Trackers, CMDB categories, Wikis and document management to establish bidirectional traceability between requirements, designs, code and tests. URLs and hyperlinks are used to link related artifacts across different tools while maintaining the information in the original tools.
ASPICE – Automotive Software Process improvement and capability determination
This is a domain specific version of ISO / IEC 15504
Purpose: To evaluate the efficiency of development processes of ECU suppliers in the automotive industry.
SIA Journée d'étude : NORME ISO 26262 Sécurité fonctionnelle électronique automobile , 04-03-2018
Cédric Heller, DQI/DSEE, French Delegate of TC22/SC32/WG8
An approach towards sotif with ansys medini analyzeBernhard Kaiser
This presentation motivates what's so different about safety for automated vehicles and introduces the concept of SOTIF (Safety of the Intended Functionality) and the upcoming first industry standard PAS 21448 on SOTIF. After that, some ideas are given how the lessons from this new discipline can be put into an industry-applicable development process for automated driving functions, and how the safety engineering tool medini analyze can help engineers succeeding in their practical work. After the first set of intended safety analysis realisations in medini analyze has been presented, the slide show concludes with an outlook on possible future extensions, also involving a close integration of medin analyze with ANSYS' simulation capabilities for automated driving functions.
This document provides an overview of ISO 26262 and functional safety standards. It discusses key aspects of ISO 26262 including its structure, vocabulary, safety lifecycle, roles and responsibilities, and requirements for managing functional safety. ISO 26262 adapts IEC 61508 for automotive and aims to avoid faults and control failures through technical safety measures applied throughout the product lifecycle from concept to decommissioning. Management of functional safety is required to plan, coordinate, and track all safety activities.
Mapping Automotive SPICE: Achieving Higher Maturity & Capability LevelsLuigi Buglione
As usual, when planning to improve a process, an organization needs to compare the current version (‘as-is’) with the new, desired one (‘to-be’). The possible content for such improvement comes from comparisons and mappings with similar processes kept from different sources. In the ICT arena such kind of studies are quite frequent but not always done for covering all models, for instance in the Automotive field. Again, often such comparisons have been done between not directly comparable elements (e.g. any management system standard as ISO 9001 is a requirement model, while maturity models such as CMMI or ISO/IEC 15504 represent process meta-models, with a different aim and contents). The aim of this presentation is to provide a new mapping between AutomotiveSPICE (A-SPICE) and the ISO 9001 norm for the Automotive sector (ISO/TS 16494:2009). This new mapping could be to provide tips for giving contents to ISO clauses but directly from A-SPICE, for more valuable improvement projects.
Automotive SPICE® 3.0 - What is new and what has changed?Dominik Strube
With our presentation "Automotive SPICE® 3.0 - What is new and what has changed?" you will know the changes implemented in the new version of Automotive SPICE® v3.0. This is provided free of charge.
This presentation has been created by leading intacsTM SPICE principal assessors. Please feel free to share this documentation among your colleagues, as long as the content is not altered.
Hirschmann: Automotive SPICE Requirements for development process and tools Intland Software GmbH
The document discusses requirements for development processes and tools based on Automotive SPICE standards. It describes how an automotive company uses various tools like Doors, Trackers, CMDB categories, Wikis and document management to establish bidirectional traceability between requirements, designs, code and tests. URLs and hyperlinks are used to link related artifacts across different tools while maintaining the information in the original tools.
ASPICE – Automotive Software Process improvement and capability determination
This is a domain specific version of ISO / IEC 15504
Purpose: To evaluate the efficiency of development processes of ECU suppliers in the automotive industry.
SIA Journée d'étude : NORME ISO 26262 Sécurité fonctionnelle électronique automobile , 04-03-2018
Cédric Heller, DQI/DSEE, French Delegate of TC22/SC32/WG8
An approach towards sotif with ansys medini analyzeBernhard Kaiser
This presentation motivates what's so different about safety for automated vehicles and introduces the concept of SOTIF (Safety of the Intended Functionality) and the upcoming first industry standard PAS 21448 on SOTIF. After that, some ideas are given how the lessons from this new discipline can be put into an industry-applicable development process for automated driving functions, and how the safety engineering tool medini analyze can help engineers succeeding in their practical work. After the first set of intended safety analysis realisations in medini analyze has been presented, the slide show concludes with an outlook on possible future extensions, also involving a close integration of medin analyze with ANSYS' simulation capabilities for automated driving functions.
This document provides an overview of ISO 26262 and functional safety standards. It discusses key aspects of ISO 26262 including its structure, vocabulary, safety lifecycle, roles and responsibilities, and requirements for managing functional safety. ISO 26262 adapts IEC 61508 for automotive and aims to avoid faults and control failures through technical safety measures applied throughout the product lifecycle from concept to decommissioning. Management of functional safety is required to plan, coordinate, and track all safety activities.
A recent regulation approved by the European Parliament laid out the requirements for type approvals of motor vehicles on their safety aspects calls for the introduction of these new safety features as a prerequisite. As such, the need for an internationally recognized standard for safety critical systems becomes more crucial to measure how safe a system is.
MISRA C provides guidelines for using the C programming language in safety-critical systems. The document discusses how MISRA C relates to ISO 26262, which specifies functional safety standards for automotive systems. Key points include that MISRA C addresses many criteria specified in ISO 26262 for suitable programming languages, such as enforcing low complexity, using a language subset, strong typing, and defensive implementation techniques. The document also discusses how to achieve and demonstrate compliance with the MISRA C guidelines.
Find out about the requirement for ISO 26262 unit testing for car item improvement. Our Functional Safety experts additionally share with you the unit testing techniques and suggestion table, as characterized by ISO 26262 standard.
https://www.embitel.com/blog/embedded-blog/iso-26262-compliant-unit-testing-strategies-achieving-functional-safety-in-automotive
Exemple Radio-réveil en Capella / ArcadiaPascal Roques
Dans mes formations SysML, j'utilise depuis pas mal d'années déjà un exemple simple de système : le radio-réveil. C'est même l'exemple principal de mon livre d'initiation à SysML, paru chez Eyrolles.
Du coup, j'ai voulu faire l'exercice également avec le nouvel outil open-source Capella en utilisant la démarche et les concepts ARCADIA.
Cette version intègre les niveaux Operational Analysis, System Analysis, et Logical Architecture. Une version ultérieure intégrera la Physical Architecture.
The document discusses embedded software development for Eclipse. It provides an overview of Eclipse and how it offers a customizable development platform through a plug-in architecture. Model-driven development approaches are described that can help reduce development costs by catching defects earlier through visual modeling and design-level debugging integrated within the Eclipse environment. Team collaboration is also facilitated through Eclipse and Rational Team Concert plug-ins.
Greg Tierney of Avid presented on their experiences using SystemC for design verification. Some key points:
1) Avid chose SystemC to enhance their existing C++ verification code and take advantage of its built-in verification capabilities like randomization and multi-threading.
2) SystemC helped Avid solve problems like connecting entire HDL modules to their testbench and monitoring foreign signals.
3) While SystemC provided benefits, Avid also encountered issues with its compile/link performance and large library size. Overall, Avid found SystemC reliable for design verification over three years of use.
The document describes the software development life cycle (SDLC) process. There are typically six stages in the SDLC: analysis, planning, design, coding, testing, and implementation & maintenance. The analysis stage involves identifying requirements, feasibility studies, and evaluating possible solutions. The design stage then further develops the logical and physical design based on requirements. Finally, the coding, testing, and implementation stages produce the final software product.
Functional hazard analysis is the first step in the process of ensuring functional safety. For safety-critical product developers, this step is fundamental as it helps identify and assess the potential hazardous situations that could lead to accidents. A systematic and structured approach to hazards analysis is crucial to identify Safety Goals and their related ASILs as an input for the development of safety related products.
Watch video recording: https://intland.com/on-demand-webinar/hazard-analysis-and-functional-safety-compliance/
Automotive functional safety iso 26262 training bootcamp 2019Tonex
Tonex offers an Automotive Functional Safety ISO 26262 Training Bootcamp course to teach participants about ISO 26262. The course covers all aspects of ISO 26262 including functional safety management, hazard analysis, safety requirements, software and hardware development processes, auditing and more. It is intended for engineers, managers, suppliers and others in the automotive industry. The hands-on training aims to help participants understand and implement ISO 26262 in their work.
A software system is more than the code; it is a set of related artifacts; these may contain defects or problem areas that should be reworked or removed; quality-related attributes of these artifacts should be evaluated
Reviews allow us to detect and eliminate errors/defects early in the software life cycle (even before any code is available for testing), where they are less costly to repair
Most problems have their origin in requirements and design; requirements and design artifacts can be reviewed but not executed and tested
A code review usually reveals directly the location of a bug, while testing requires a debugging step to locate the origin of a bug
Adherence to coding standards cannot be checked by testing
RA TechED 2019 - SY07- Next-Gen Device Library of Preconfigured ObjectsRockwell Automation
The document discusses Rockwell Automation's next-generation device library of preconfigured objects. It provides an overview of the library's benefits, including speeding up development times and improving manufacturing competitiveness by facilitating the gathering of plant floor data from smart devices. The library includes object faceplates for devices like drives and I/O, as well as configuration steps. Customers can access and download device libraries from Rockwell Automation's website.
The Rockwell Automation® Library of Process Objects helps
you quickly develop process solutions with rich functionality
and known performance. In this session, how to build a control
strategy using Library objects will be demonstrated. The Library
objects and their functions within a typical control system will
be presented, highlighting features for operators, maintainers
and engineers. Walk away understanding the value of using the
Library to develop process solutions.
THE NEW IEEE STANDARD FOR SOFTWARE QUALITY ASSURANCE PROCESSES – AN ESSENTIA...Bakul Banerjee, Ph.D.
The presentation explores the application of the new IEEE Standard for Software Quality Assurance in the context of PMI's project management standards.
A common need in system architecture design is to verify that if the architect is correct and can satisfy its requirements.
Execution of system architect model means to interact with state machines to test system’s control logic. It can verify if the logical sequences of functions and interfaces in different scenarios are desired.
However, only sequence itself is not enough to verify its consequence or output. So we need each function to do what it is supposed to do during model execution to verify its output, and that is what we called “simulation”.
This presentation introduced how to embed Python or MATLAB® codes inside functions to do “simulation” within Capella.
This document discusses considerations for reusing components in automotive systems designed according to ISO 26262 functional safety standards. It begins with an overview of ISO 26262 and its requirements for reusable components called Safety Elements Out of Context (SEooCs). Suppliers often deliver SEooCs to customers, with documentation like a safety manual describing proper deployment. For non-SEooC components, a Development Interface Agreement is required. While ISO 26262 does not directly address open source software, some argue it could be qualified for safety-critical use if specified, tested, and documented rigorously. In general, component reuse aims to increase quality and efficiency if managed carefully according to ISO 26262 processes.
The document discusses the "Step Wise" approach to planning software projects. It involves 10 main steps: 1) establish project scope and objectives, 2) establish project infrastructure, 3) analyze project characteristics, 4) identify products and activities, 5) estimate effort for each activity, 6) identify activity risks, 7) allocate resources, 8) review and publicize the plan, 9) execute the plan, and 10) create lower level plans. Each step is then explained in more detail with examples provided for clarification.
Exploring the Functionality of the Rockwell Automation® Library of Process Ob...Rockwell Automation
The Rockwell Automation® Library of Process Objects lets you
quickly develop process solutions with rich functionality and
known performance. In this session, objects in the library and
their functions within a typical process control system will be
presented, common library features such as modes, alarms, and features for operations, maintenance and engineering personnel will be explained and new features for the 3.5 library release will be highlighted. Walk away knowing how to more effectively develop, operate and maintain process systems.
Intland Software's Functional Safety Expert Szabolcs Agai presented this talk at MethodPark Process Insights USA 2020 about managing ASPICE and ISO 26262 compliance in automotive systems engineering using Application Lifecycle Management.
The document provides an introduction to model based development for automotive engineers. It discusses that model based design uses system models at the center of the development process from requirements to testing. It describes the key benefits of model based design as integrating testing with design, automatically generating code and documentation, and reusing designs across hardware targets. It then outlines the main steps of the model based design process as defining the system, identifying components, modeling with equations, building a Simulink block diagram, running simulations, and validating results.
Auto Code Generation and Rapid Brewery/Distillery AutomationDMC, Inc.
This presentation details how the Siemens Brewing template, a TIA Portal based auto code generation tool created developed in partnership by DMC and Siemens, can be used to create complete automation in rapid brewing and distillery.
I apologize, upon reviewing the document I do not feel comfortable rating or assessing any organization's software processes without their consent or more detailed information.
A recent regulation approved by the European Parliament laid out the requirements for type approvals of motor vehicles on their safety aspects calls for the introduction of these new safety features as a prerequisite. As such, the need for an internationally recognized standard for safety critical systems becomes more crucial to measure how safe a system is.
MISRA C provides guidelines for using the C programming language in safety-critical systems. The document discusses how MISRA C relates to ISO 26262, which specifies functional safety standards for automotive systems. Key points include that MISRA C addresses many criteria specified in ISO 26262 for suitable programming languages, such as enforcing low complexity, using a language subset, strong typing, and defensive implementation techniques. The document also discusses how to achieve and demonstrate compliance with the MISRA C guidelines.
Find out about the requirement for ISO 26262 unit testing for car item improvement. Our Functional Safety experts additionally share with you the unit testing techniques and suggestion table, as characterized by ISO 26262 standard.
https://www.embitel.com/blog/embedded-blog/iso-26262-compliant-unit-testing-strategies-achieving-functional-safety-in-automotive
Exemple Radio-réveil en Capella / ArcadiaPascal Roques
Dans mes formations SysML, j'utilise depuis pas mal d'années déjà un exemple simple de système : le radio-réveil. C'est même l'exemple principal de mon livre d'initiation à SysML, paru chez Eyrolles.
Du coup, j'ai voulu faire l'exercice également avec le nouvel outil open-source Capella en utilisant la démarche et les concepts ARCADIA.
Cette version intègre les niveaux Operational Analysis, System Analysis, et Logical Architecture. Une version ultérieure intégrera la Physical Architecture.
The document discusses embedded software development for Eclipse. It provides an overview of Eclipse and how it offers a customizable development platform through a plug-in architecture. Model-driven development approaches are described that can help reduce development costs by catching defects earlier through visual modeling and design-level debugging integrated within the Eclipse environment. Team collaboration is also facilitated through Eclipse and Rational Team Concert plug-ins.
Greg Tierney of Avid presented on their experiences using SystemC for design verification. Some key points:
1) Avid chose SystemC to enhance their existing C++ verification code and take advantage of its built-in verification capabilities like randomization and multi-threading.
2) SystemC helped Avid solve problems like connecting entire HDL modules to their testbench and monitoring foreign signals.
3) While SystemC provided benefits, Avid also encountered issues with its compile/link performance and large library size. Overall, Avid found SystemC reliable for design verification over three years of use.
The document describes the software development life cycle (SDLC) process. There are typically six stages in the SDLC: analysis, planning, design, coding, testing, and implementation & maintenance. The analysis stage involves identifying requirements, feasibility studies, and evaluating possible solutions. The design stage then further develops the logical and physical design based on requirements. Finally, the coding, testing, and implementation stages produce the final software product.
Functional hazard analysis is the first step in the process of ensuring functional safety. For safety-critical product developers, this step is fundamental as it helps identify and assess the potential hazardous situations that could lead to accidents. A systematic and structured approach to hazards analysis is crucial to identify Safety Goals and their related ASILs as an input for the development of safety related products.
Watch video recording: https://intland.com/on-demand-webinar/hazard-analysis-and-functional-safety-compliance/
Automotive functional safety iso 26262 training bootcamp 2019Tonex
Tonex offers an Automotive Functional Safety ISO 26262 Training Bootcamp course to teach participants about ISO 26262. The course covers all aspects of ISO 26262 including functional safety management, hazard analysis, safety requirements, software and hardware development processes, auditing and more. It is intended for engineers, managers, suppliers and others in the automotive industry. The hands-on training aims to help participants understand and implement ISO 26262 in their work.
A software system is more than the code; it is a set of related artifacts; these may contain defects or problem areas that should be reworked or removed; quality-related attributes of these artifacts should be evaluated
Reviews allow us to detect and eliminate errors/defects early in the software life cycle (even before any code is available for testing), where they are less costly to repair
Most problems have their origin in requirements and design; requirements and design artifacts can be reviewed but not executed and tested
A code review usually reveals directly the location of a bug, while testing requires a debugging step to locate the origin of a bug
Adherence to coding standards cannot be checked by testing
RA TechED 2019 - SY07- Next-Gen Device Library of Preconfigured ObjectsRockwell Automation
The document discusses Rockwell Automation's next-generation device library of preconfigured objects. It provides an overview of the library's benefits, including speeding up development times and improving manufacturing competitiveness by facilitating the gathering of plant floor data from smart devices. The library includes object faceplates for devices like drives and I/O, as well as configuration steps. Customers can access and download device libraries from Rockwell Automation's website.
The Rockwell Automation® Library of Process Objects helps
you quickly develop process solutions with rich functionality
and known performance. In this session, how to build a control
strategy using Library objects will be demonstrated. The Library
objects and their functions within a typical control system will
be presented, highlighting features for operators, maintainers
and engineers. Walk away understanding the value of using the
Library to develop process solutions.
THE NEW IEEE STANDARD FOR SOFTWARE QUALITY ASSURANCE PROCESSES – AN ESSENTIA...Bakul Banerjee, Ph.D.
The presentation explores the application of the new IEEE Standard for Software Quality Assurance in the context of PMI's project management standards.
A common need in system architecture design is to verify that if the architect is correct and can satisfy its requirements.
Execution of system architect model means to interact with state machines to test system’s control logic. It can verify if the logical sequences of functions and interfaces in different scenarios are desired.
However, only sequence itself is not enough to verify its consequence or output. So we need each function to do what it is supposed to do during model execution to verify its output, and that is what we called “simulation”.
This presentation introduced how to embed Python or MATLAB® codes inside functions to do “simulation” within Capella.
This document discusses considerations for reusing components in automotive systems designed according to ISO 26262 functional safety standards. It begins with an overview of ISO 26262 and its requirements for reusable components called Safety Elements Out of Context (SEooCs). Suppliers often deliver SEooCs to customers, with documentation like a safety manual describing proper deployment. For non-SEooC components, a Development Interface Agreement is required. While ISO 26262 does not directly address open source software, some argue it could be qualified for safety-critical use if specified, tested, and documented rigorously. In general, component reuse aims to increase quality and efficiency if managed carefully according to ISO 26262 processes.
The document discusses the "Step Wise" approach to planning software projects. It involves 10 main steps: 1) establish project scope and objectives, 2) establish project infrastructure, 3) analyze project characteristics, 4) identify products and activities, 5) estimate effort for each activity, 6) identify activity risks, 7) allocate resources, 8) review and publicize the plan, 9) execute the plan, and 10) create lower level plans. Each step is then explained in more detail with examples provided for clarification.
Exploring the Functionality of the Rockwell Automation® Library of Process Ob...Rockwell Automation
The Rockwell Automation® Library of Process Objects lets you
quickly develop process solutions with rich functionality and
known performance. In this session, objects in the library and
their functions within a typical process control system will be
presented, common library features such as modes, alarms, and features for operations, maintenance and engineering personnel will be explained and new features for the 3.5 library release will be highlighted. Walk away knowing how to more effectively develop, operate and maintain process systems.
Intland Software's Functional Safety Expert Szabolcs Agai presented this talk at MethodPark Process Insights USA 2020 about managing ASPICE and ISO 26262 compliance in automotive systems engineering using Application Lifecycle Management.
The document provides an introduction to model based development for automotive engineers. It discusses that model based design uses system models at the center of the development process from requirements to testing. It describes the key benefits of model based design as integrating testing with design, automatically generating code and documentation, and reusing designs across hardware targets. It then outlines the main steps of the model based design process as defining the system, identifying components, modeling with equations, building a Simulink block diagram, running simulations, and validating results.
Auto Code Generation and Rapid Brewery/Distillery AutomationDMC, Inc.
This presentation details how the Siemens Brewing template, a TIA Portal based auto code generation tool created developed in partnership by DMC and Siemens, can be used to create complete automation in rapid brewing and distillery.
I apologize, upon reviewing the document I do not feel comfortable rating or assessing any organization's software processes without their consent or more detailed information.
This document discusses Software Process Improvement and Capability Determination (SPICE). SPICE is an international standard for software process assessments that identifies best practices and provides an improvement path. The Automotive SPICE model was developed for the automotive industry. SPICE assessments evaluate organizations across two dimensions - processes and capability levels. This helps identify strengths, weaknesses, and targets for improvement. The assessment data can then be used to plan process improvements and increase an organization's software development capabilities.
This document provides an overview of ISO/IEC 15504 (SPICE) and its current and future directions. It discusses the parts and concepts of ISO/IEC 15504, including capability levels, process assessment models, organizational maturity, and standards-based and sector-based models. It also outlines the ISO study group revision from 2009-2011, the evolution and transition of SPICE, and the formation of the SPICE Academy.
ISO/IEC 15504, also known as SPICE, is an international standard for software process assessment. It defines a framework for assessing processes based on a process reference model and capability levels. Processes are divided into categories and each process is assessed against attributes to determine its capability level on a scale of 0 to 5. ISO/IEC 15504 provides guidelines for conducting assessments through steps like planning, data collection, and reporting results. Assessors require training and experience to perform assessments competently. The standard can be used for both process improvement and determining a supplier's process capabilities.
A proposal for a new common process scope for AutomotiveSPICE: Six reasons fo...Luigi Buglione
The presentation introduced the rationale by six reasons why adding the MAN.6 process in an ISO/IEC 15504 assessment could bring several advantages to an organization, whatever the application domain
MASP (Metrics in Automotive Software Projects) - Purpose, Scope & ResultsLuigi Buglione
The purpose of this presentation is to propose a balanced set of measures to be used in a
measurement plan conforming to the ISO/IEC 15504 Process Reference Model (PRM). Such
measures are defined and described using a template derived from the Measurement Information
Model (MIM) proposed in Appendix A of ISO/IEC 15939 standard. This document is the first
outcome of the MASP (Metrics in Automotive Software Projects) working group of Automotive
SPIN Italy (www.automotive-spin.it).
Internal Audits and Assessments with help of Enterprise SPiCEErnest Wallmueller
Internal audits and assessments were conducted at SVOX using Enterprise SPICE to help drive process improvements. Enterprise SPICE provided practices that could be used to assess processes at Capability Level 1 and monitor work products and process performance at Level 2. First experiences found Enterprise SPICE useful for many areas but weak in sales, marketing, finance, and portfolio management. Some processes required more granularity and clearly defined relationships. The assessments identified improvement actions and provided a means for continual process updates beyond external audits alone.
Light Maturity Models (LMM): An Agile ApplicationLuigi Buglione
This presentation shows an easier possible way for starting the aplication of maturity models (light), coming back to the original Crosby\'s idea. It presents some possible ways to apply LMM to Agile projects/organizations
This document discusses how ABB used a Notes application developed by FoCul to implement their risk-based inspection (RBI) process. The application standardized processes, improved efficiency, and helped ABB win over £3 million in new contracts. It provided benefits like improved collaboration, consistency, and flexibility. The application was successful due to individual user benefits, improved organizational efficiency, and enhanced sales opportunities. Lessons learned include the importance of configurability and a modular approach. The application demonstrates how Notes can effectively support knowledge-intensive business processes.
The Metrics Cards. A Balanced Set of Measures ISO/IEC 15504 compliantLuigi Buglione
the presentation aims to: 1) recap the balancing principles for quantitatively managing a project; 2) show a possible top10 metrics for Automotive SPICE; 3) discuss the attention points for applying such metrics
In Information and Communication Technology (ICT) a ‘deliverable’ may be either software (perceived as an ‘output’) or a service (perceived as an ‘outcome’). On the one hand, the differences between software and service have led to the design of parallel models and lifecycles with more commonalities than differences, thereby not supporting the adoption of different frameworks. For instance, a software project could be managed applying best practices for services (e.g. ITIL), while some processes (e.g. Verification & Validation) are better defined in models of the Software Management domain. Thus, this paper aims at reconciling these differences and provides suggestions for a better joint usage of models/frameworks. To unify existing models we use the LEGO approach, which aims at keeping the element of interest from any potential model/framework for being inserted in the process architecture of the target Business Process Model (BPM) of an organization, strengthening the organizational way of working. An example of a LEGO application is presented to show the benefit from the joint view of the ‘software + service’ sides as a whole across the project lifecycle, increasing the opportunity to have many more sources for this type of improvement task.
Software or service that's the question luigi buglioneIWSM Mensura
The document discusses knowledge management (KM) in the context of maturity and capability models (MCMs) for software and services. It presents CMMI-DEV/SVC and ISO 15504-2 as examples of horizontal MCMs that reference KM. CMMI-DEV/SVC only mention KM practices in GP 2.5, while ISO 15504-2 defines a knowledge management process (RIN.3) with specific base practices. The document also reviews other KM frameworks like APQC KMMM, Siemens KMMM, ONTOKNOM, and G-KMMM that provide staged representations for assessing KM maturity levels.
Linda Biglow has 18 years of experience in the automotive industry focusing on continuous improvement, new product introduction, and front line supervision. She has a variety of technical skills including lean manufacturing, ergonomics certification, failure mode and effects analysis, and ISO and TS auditing. Some of her accomplishments include creating a repetitive strain injury reduction program and implementing training centers. Currently she is the Corporate Continuous Improvement Coordinator at Guelph Manufacturing Group, coordinating all continuous improvement activities across multiple facilities.
This document provides details on Doungporn Chintanaphan's experience as a senior consultant specializing in SAP enterprise applications, particularly financial and controlling modules. It outlines 9 projects Doungporn led or contributed to between 2003-2015, implementing and supporting SAP systems for companies in various industries like manufacturing, automotive, retail and public sector. The document demonstrates Doungporn's expertise in areas like financial process design, system configuration, testing, training and post go-live support.
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...Luigi Buglione
“Tracking & Control” activities in software projects are most often based, in industry, on just two dimensions of analysis: time and cost. Most often, ‘tracking & control’ excludes other dimensions (such as quality, risks & impact on society, stakeholders’ viewpoint in a broader sense) taken into account in Performance Management models such as EFQM or the Malcolm Baldridge model. How can balancing those multiple concurrent control mechanisms across several dimensions of analysis be done? Balancing Multiple Perspective (BMPs) is a procedure designed to help project managers choose a set of project indicators from several concurrent viewpoints. This paper also presents the related questionnaire with a list of 14 candidate measures helping to compare the “as-is” situation and to figure out what will be the desired one, including cost figures to be possibly considered in the budget for next projects.
This document summarizes a presentation on measuring and evaluating software sustainability from both a product and process perspective. It discusses defining sustainability indicators using an Entity-Attribute-Measure approach and proposes a measurement framework that is compliant with ISO/IEC 33000 standards for assessing process sustainability. The presentation aims to further understanding of how to measure sustainability as an additional attribute to evaluate software processes.
This document contains the resume of V.B. Engels summarizing his work experience, education, skills, and personal details. He has over 7 years of work experience in quality control and engineering roles at Isuzu Motors India, BMW India, and AMREP. He holds a Diploma in Mechanical Engineering and Bachelor of Engineering Technology. His skills include AutoCAD, CATIA V5, UNIGRAPHICS NX, and he has received internal auditor and problem solving training certifications.
Kuldip Narayain is a management professional with over 25 years of experience in production planning and control. He is currently seeking new assignments in this area. His career highlights include serving as General Manager of Operations for Power Mech Industries and holding various production management roles at other companies such as Leak Proof Engineering, Gtech Rebar Technology, UT Pumps & Systems, and D.B. Engineering Co. He has expertise in areas like production administration, product development, strategic planning, and production operations.
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...Luigi Buglione
ICT can provide a definitive contribution in reducing CO2 emissions and, in general, in the environment preservation. Because its pervasiveness in today’s life, software in particular plays an important role in achieving such a goal. Software process is the combination of those practices, directly or indirectly involved in software development, operation, and maintenance.
In previous papers the authors addressed the topic of evaluating the sustainability of software products. In this paper the focus is on the evaluation of the sustainability of the software process, i.e. the measurement of the extent the process is performed by having care of the environment and by minimizing its impact on the environment. To do that, a sustainability measurement framework for software process is defined. Such a framework is composed by Sustainability Levels, Sustainability Process Attributes and being compliant with the requirements stated in the new ISO/IEC 33000 series standard for software process assessment.
Iwsm2014 measurement process - improving the iso 15939 standard (luigi bugl...Nesma
This document summarizes a presentation on improving the ISO 15939 standard for software measurement processes. The presentation discusses refining the Measurement Information Model (MIM) to better represent the measurement process lifecycle. It also proposes using a "5Ws+2H" template and Balancing Multiple Perspectives (BMP) technique for developing measurement plans. The goal is to provide more guidance in the standard for effectively planning measurement activities and using measurement results. Suggested improvements could be considered for inclusion in a future revision of ISO 15939.
Byron Pang is an Industrial Engineering professional with over 15 years of experience in various roles. He is currently an IE Manager at Infineon Technologies where he leads a team and is responsible for maintaining manufacturing KPIs and driving productivity improvements. Some of his past accomplishments include receiving various achievement awards and improving OEE, setup times, and cycle times through projects applying IE tools and methodologies.
Some thoughts on Productivity in ICT Projects: measurable entities, requireme...Luigi Buglione
WSPM/SGPS 2008 - Madrid, Sept 25 2008
Goals of the presentation:
* to look at the entities to be measured and to be related against stated information goals (project vs product)
* to enlarge the possible project\'s requirement taxonomy from ISO/IEC 14143-1
* from requirements to WBS: a process-oriented view
* some thoughts on the \'productivity\' definition
This document discusses measurement practices for Lean and Agile approaches. It presents an agenda covering introduction topics on Lean, Agile and measurement; best practices including requirements elicitation and management, sizing units, estimation, monitoring and control; and conclusions. The goal is to analyze common measurement practices, discuss potential issues, and propose countermeasures to strengthen measurement in Lean-Agile teams and projects.
Thailand SPIN Day 2014: มิตร ศัตรู หรือความไม่รู้ต่างหากที่หลอกเรา (29/5/2557...Apple Taton
1. RSTL is a software development company in Thailand with over 1,000 employees that develops products for Thomson Reuters.
2. In 2011, RSTL started adopting Agile methods like Scrum and Kanban to improve their software development process, guided by the CMMI framework.
3. A 2013 appraisal found RSTL achieving a CMMI Level 3 in key process areas like requirements management, development, verification, and validation, showing that Agile and CMMI can work well together when the Agile practices address the specific goals.
The document provides an industrial training report submitted by Suyash Trivedi during their internship at Lumax Mannoh Allied Technologies from June 15th to July 15th, 2016. It includes sections on the company profile, customers, product details like the gear shifter, research and development processes, advanced quality planning (APQP), potential failure modes and effects analysis, inspection methods used, work allotted to the author, product components, and conclusions from the training. The report summarizes the author's learning experience during their internship focused on quality planning, failure analysis, and manufacturing processes at Lumax Mannoh.
Improving the User Story Agile Technique Using the INVEST CriteriaLuigi Buglione
Although the Agile Software Development (ADS) approach has been around for the last 15 years, it is only recently that attention has moved towards Agile Software Management (ASM) for tackling some of the management-related weaknesses, such as estimating on the basis of User Story points. This paper presents an application of the INVEST criteria (Independent – Negotiable – Valuable – Estimable – Small –Testable) for improving the measurement technique of User Stories, introducing sizing units and a technique to negotiate requirements. It includes a discussion on an approach to balancing the six criteria used to evaluate a set of User Stories in a Sprint.
There is a growing interest during last years in a better understanding of the inner meaning of ‘product value’ as perceived from the final customer, looking at possible techniques and new ways to anticipate and better capturing requirements from early stages. But even if more and more professionals and IT organizations achieve certifications on their personal knowledge or organizational maturity that should go in that direction, few attention is paid to the project closure phase and to the historicization of project data. If planned and gathered at the right level of granularity, effort data could explain and represent a valuable knowledge base – jointly with some requirement metrics - about how to create and reinforce the value to deliver to customer. This paper provides a list of possible improvement actions derived from practical experience that can bring more value to software products moving from better and more accurate project management and measurement processes.
Similar to Top Metrics for SPICE-compliant projects (20)
Obiettivi della presentazione: (1) Presentare una breve storia dell’ITSM degli ultimi anni; (2) Illustrare i tratti caratteristici dei principali framework e modelli nell’ITSM, tra cui ITIL e DevOps; (3) Proporre la giusta sintesi di diversi approcci ITSM, ricordando sempre che tali approcci rimangono sempre strumento, non obiettivo.
The missing links in software estimation: Work, Team Loading and Team PowerLuigi Buglione
This presentation investigates the theoretical foundation of the basic concepts used in software effort estimation, productivity measurement and benchmarking. By elaborating on how similar concepts are defined and used in well-established engineering fields, we aim to shed light on some inconsistent and fallacious use of concepts and units of measure, resulting misconceptions and their consequences in project planning. Particularly, we focus on ‘Work’, ‘Team Power’ and ‘Team Loading’, analyzing the way many studies from the ‘70s on faced such issue. Too often projects fail for being late and not always adding new resources allows respecting established milestones as well as the established quality levels. After setting the theoretical layout, we present the results of an empirical investigation we made using the data in the International Software Benchmarking Standards Group (ISBSG) dataset D&E (Development & Enhancement) v13, using both COSMIC and IFPUG data for Business and Real-Time applications. The results indicate that a considerable number of projects might have been poorly planned and utilized human resources inefficiently, and hence paid much higher costs. Hence, we suggest software companies to revisit the productivity data of the past projects as well as evaluating the new ones by measuring Team Power, Team Loading and comparing to Team Size utilized.
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...Luigi Buglione
A common challenge in life is to evaluate and deal with risks. Even though Risk management is fundamental to any activity, it is too often evaluated and managed from a qualitative rather than a quantitative perspective. In order to improve, too often organizations are seeking compliance against a single model/approach, forgetting that most often ‘one model doesn’t fit all’ and that the target process model is the organizational one, strengthened by external best practices. An approach to process improvement that takes this into consideration is LEGO (Living EnGineering prOcess). LEGO extracts the most useful Elements of Interest (EoI) from several types of maturity models into an organizational Business Process Model (BPM) in order to facilitate to the achievement of higher organizational maturity and capability levels, that’s the definitive intended target to be improved. This paper applies the LEGO approach to Risk Management, analyzing several Risk Management Maturity Models and unifying their practices in order to come up with a more comprehensive process model on risk management integrating multiple views.
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...Luigi Buglione
‘Agile’ risks to be a very (ab)used term in the ICT (and not) community during last years. Agile means – as in the Agile Manifesto – to be responsive, working in team and be ready to change. But what do we need for really being agile? The answer is simple: start to be (before) LEAN in order to be (after) AGILE. Too often these two terms risk to be meant as synonyms, but they are different and complementary to each other. The presentation will show a possible path to do that, adopting Lean techniques as suggested by Six Sigma for reducing wastes (the seven ‘muda’) and only then adopting Agile ones, also applied to Functional (and not) Sizing Methods, such as Function Points and SNAP. Note from the conference organizers: “Muda” is a Japanese word meaning “waste”. The Toyota Production System identified seven types of “muda”.
From Software to Service Sustainability: a still Broader PerspectiveLuigi Buglione
This paper proposes an approach to enlarge the view from software (products) to services, because a service is a broader container than a project and can include software as well as other assets to be managed from an Asset Management perspective. Hybridizing typical software and service management models and frameworks could help organizations in a better management of their assets, stressing more the (inner) value of intangibles and of a good mid-long term strategy, passing for a valuable proposition of MVVs (Mission-Vision-Values).
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...Luigi Buglione
This document presents an empirical study on using different IFPUG base functionality types (BFCs) like external inputs, external outputs, external queries, internal logical files, and external interface files in effort estimation. The study uses project data from the ISBSG repository containing information on functional size, effort, application type, development type, and other attributes. Statistical analysis is performed on various subsets of the data based on filters. The results show that using multiple BFCs together in estimation, instead of just total function points, increases the correlation with effort significantly. This implies BFC types should be considered to obtain better estimation accuracy.
A Murphological View on Software Measurement: a serious joke or a funny seri...Luigi Buglione
The 30-year experience from the Software Measurement field explains that a strong resistance usually comes from project team members, supposing the real objective is a personal evaluation on their performance and not a neutral measurement for a concrete process improvement. Concurrently, from the middle ‘80s a series of SPI models - such as the Software Capability Maturity Model (Sw-CMM) and nowadays its evolution, the CMMI –provided a guide for realizing a real improvement, where measurement played an important role, before as a Common Feature, then as a separate process (MA – Measurement and Analysis) at Level 2. But a certain resistance still remain alive also after these years.
Recently, in the Management field (and also in ICT) more than “serious” books and reference guides it seems that (apparent) semi-serious publications such as the Dilbert strips by Scott Adams are referenced in technical presentations and papers as a starting point for commenting daily ICT malpractices. If so, another good source for “joking” with such serious things are some of the most know laws, the “Murphy’s laws”, originally written by Arthur Block and after created/modified by plenty of people worldwide and published over the Internet in a sort of “GNU licence for humour”.
This paper tries to propose a “murphological view” on Software Measurement issues, commenting some related measurement-related laws and providing links with main SPI practices at the aim to reduce the percentage of failures in application of Software Measurement programs, as noted by H.Rubin some years ago.
Do we really re-use our knowledge (or not)?Luigi Buglione
Looking back to the last 25 years in IT, one of the most used, practical IT ‘inventions’ has been the ‘cut & paste’ mechanism, that’s a reuse of a previous artefact. But looking to ICT organizations in these turbulent years – no matter if they deal with software and/ services – many of them seem to do not be designed for resilience. From a root-cause analysis (RCA), one of the main ‘bones’ for improvement is the lack of reuse of organizations’ experience, in terms of historical data, artefacts, processes, etc.
Thus, re-using the ‘internal knowledge’ (before thinking to software reuse) is – as many Process Improvement models like MPS.BR (both the SW and the SV constellations) affirm – one of the real ‘wheels’ driving an organization to achieve success, measured not only by ROI but also by VOI (Value on Investment), because the more and more relevance in understanding the role and value of intangibles in our business.
The keynote presentation will move from evidences and well-known industrial stories for discussing and understanding where knowledge has (or not) been the key driver for organizational success, which possible barriers to that and how multi-model approaches as LEGO (Living EnGineering prOcess) could help an organization in achieving such goals in an easier way, betting mostly on people knowledge, as the ‘building perspective’ also looking to the Balanced Scorecard (BSC) schema and logical flow.
Balanced Measurement Sets: Criteria for Improving Project Management PracticesLuigi Buglione
The availability of a measurement framework right at the early stage of a project can have a very positive impact in the management of software development process. In this paper, we cope with this problem proposing a methodology that can allow an early adoption of balanced measurement sets, which will be iteratively refined at each iteration of the process. The proposed methodology can be implemented and supported by open source tools like the Spago4Q platform.
PIF or SNAP? That's the Question! Or maybe it's not? - A panelLuigi Buglione
The presentation introduced a panel organized at IWSM-MENSURA 2014 by MAIN (Metrics Associations' International Network - www.mai-net.org) about the value and way to deal with NFRs in a software project, using a series of PIF (Productivity Impact Factors) for calibrating your project effort or a specific sizing unit? That's the (discussed) question!
Software Sustainability: a Broader PerspectiveLuigi Buglione
In this presentation the approach to address software sustainability evaluation is discussed. We believe that software sustainability is a complex business to be addressed by including the largest set of indicators from software development, use, maintenance and disposal.
Measurement Process: Improving the ISO 15939 StandardLuigi Buglione
Over the past few years ISO has published a number of specific standards detailing processes included in a generic form in software development life cycle models. ISO 15939 on the Measurement process itself is an example of such specific ISO standard. This paper presents some suggestions for improvements to its Measurement Information Model and to the measurement plan within the planning process of ISO 15939.
This document discusses measuring and evaluating productivity for both functional and non-functional requirements (NFRs). It describes SNAP (Software Non-functional Assessment Process), a new NFR sizing method developed by IFPUG. SNAP divides NFRs into categories and sub-categories to assign size in SNAP Points. The document advocates measuring both functional size units (FSUs) and non-functional size units (NFSUs) to more accurately evaluate overall productivity. It provides an example of how to incorporate NFR-related tasks into work breakdown structures and schedules.
The LEGO Strategy: Guidelines for a Profitable DeploymentLuigi Buglione
When dealing with improvements, organizations seek to find a break-even point for their applications as early as possible in order to maximize the return from their investment. However, in some cases such a strategy can lead to a long term failure by not realizing the full benefits, when focusing only on a short term. The LEGO (Living EnGineering prOcess) approach – a method for building your own process meta-model based on multiple inputs – is a way to make an organization more efficient and effective, optimizing resources, as well as time and costs through looking at its entire Business Process Model. This paper introduces the elements for designing a strategy for a more valuable deployment of a process improvement initiative, in order to optimize the choice of the models and elements to be considered as an input to the LEGO approach
ICEBERG: a different look at Software Project ManagementLuigi Buglione
Every project – whatever the application field – should be managed taking into account at least four dimensions: Time, Cost, Quality and Risk. To manage these dimensions, a key tool for a Project Manager is to increase project visibility, defined as the amount of information about the project associated with its probability of occurrence. This paper uses the “iceberg” metaphor to introduce the ICEBERG (Improvement after Control and Evaluation-BasEd Rules and Guidelines) approach that can help Project Managers through the use of standard (de jure and de facto) ICT methods and techniques. This approach focuses not only on the management, and measurement, of resources, process and product, but also of the project and the organization itself. A list of candidate measures related to these 5 entities is suggested for a comprehensive software measurement plan in order to reduce project risk.
During the past 20 years Maturity & Capability Models (MCMs) become a buzzword in the ICT world. Since the initial Crosby’s idea in 1979, plenty of models have been created in the Software & Systems Engineering domains, addressing various perspectives. By analyzing the content of the Process Reference Models (PRM) in many of them, it can be noticed that reuse-related issues have unfortunately often little importance in the appraisals of the capabilities of software organizations while in practice they are considered as significant contributors in traditional process and organizational performance appraisals. While MCMs represent a good mean for assessing the status of a set of processes, integrating two or more models with a common area of focus can offer more information and value for an organization. The aim of this paper is to present some information about Reuse best practices and models, keep the best components from each model and – using the LEGO (Living EnGineering prOcess) approach to process improvement - merge those best practices from several types of maturity models into an organizational Business Process Model (BPM) in order to achieve in an easier and faster way higher organizational maturity and capability levels.
The document proposes deriving green metrics for software by systematically mapping sustainability assets, direct effects, green factors, and an entity-attribute-measure taxonomy. It presents sustainability assets like people, infrastructure, processes, and products that influence direct effects like power waste, effort waste, and material waste. Green factors that impact direct effects are then identified. Finally, example green metrics are defined using the entity-attribute-measure structure and mapped to green factors to allow monitoring of software sustainability performance. The metrics provide a starting point to help organizations deploy and control sustainability-related processes.
Software Architects’ Experiences of Quality Requirements: What we Know and ...Luigi Buglione
Abstract. [Context/motivation] Quality requirements (QRs) are a concern of both requirement engineering (RE) specialists and software architects (SAs). However, the majority of empirical studies on QRs take the RE analysts’/clients’ perspectives, and only recently very few included the SAs’ perspective. As a result, (i) relatively little is known about SAs’ involvement in QRs engineering and their coping strategies, and (ii) whatever is known mostly comes from small and midsized projects. [Question/problem] The question in this exploratory study is how SAs cope with QRs in the context of large and contract-based software system delivery projects. [Principal ideas/results] We executed an exploratory case study with 20 SAs in the context of interest. The key results indicate the role SAs play in QRs engineering, the type of requirements communication processes SAs are involved in, the ways QRs are discovered, documented, quantified, validated and negotiated. Our most important findings are that in contract-based contexts: (1) the QRs are approached with the same due diligence as the functional requirements and the architecture design demand, (2) the SAs act proactively and embrace responsibilities over the QRs, (3) willingness to pay and affordability seem as important QRs prioritization criteria as cost and benefits do, and (4) QRs engineering is perceived as a social activity and not as much as a tool and method centric activity.[Contribution] The main contributions of the paper are (i) the explication of the QRs process from SAs’ perspective, and (ii) the comparison of our findings with previously published results
The GP 2.8 Game - – Deploying a Balanced Measurement Plan by the ‘Play’n’Lear...Luigi Buglione
Workshop goals:
G1. Understand the main purpose for a measure and its value and “return on information” to projects
G2. Be able to properly define the basic elements for a measure, according to ISO/IEC 15939 MIM
G3. Balance a set of measures by concurrent perspectives, in order to create a balanced measurement plan
G4. Select and prioritize measures for a measurement plan taking care of budget constraints