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.
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]
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.
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.
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
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.
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]
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.
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.
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
As the intricacy of Electronic Control Units (ECU) in present day vehicles has expanded, the requirement for automotive functional safety standard has turned out to be more goal. ISO 26262 standard tends to the all inclusive security hones required for planning basic car segments. We take a gander from an optimistic standpoint rehearses that will help you to plan ISO 26262-agreeable ECU programming.
An integrative solution towards SOTIF and AV safetyBernhard Kaiser
Slide set from this year's SOTIF conference in Austin, Texas, Oct 1 and 2, 2019. Shows intermediate pragmatic ideas on how to handle SOTIF in combination with ISO 26262 safety, and how to integrate SOTIF analysis with simulation and driving verification. Terminology may still change as ISO 21448 is evolving.
Get Answers to the most asked questions for ISO26262 compliant automotive Functional Safety consulting services. Check out the FAQs for Functional safety in automotive.
https://www.embitel.com/product-engineering-2/iso-26262functional-safety/
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.
Most industrial safety-critical systems are developed and validated following safety standards. However even though all safety standards address similar concerns with similar objectives, they are also domain-specific standards. The presentation results from the activity of a working group (formerly CG2E, now part of the recently set-up Embedded France) gathering industrial safety experts from aeronautics, automotive, industrial automation, nuclear, railway and space. The lecture will combine a presentation focused on one industry specific standard (the recent ISO 26262 for automotive), and complementary perspective in comparison with the standards in the other five mentioned domains. After the presentation of the history and position and the various regulation regimes, we will highlight some more technical topics e.g., integrated or external safety systems, fault prevention vs. fault tolerance, objectives vs. means prescription, probabilistic vs. deterministic arguments and the notion of criticality, integrity or assurance levels.
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.
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
Scenario-Based Development & Testing for Autonomous DrivingYu Huang
Formal Scenario-Based Testing of Autonomous Vehicles: From Simulation to the Real World, 2020
A Scenario-Based Development Framework for Autonomous Driving, 2020
A Customizable Dynamic Scenario Modeling and Data Generation Platform for Autonomous Driving, 2020
Large Scale Autonomous Driving Scenarios Clustering with Self-supervised Feature Extraction, 2021
Generating and Characterizing Scenarios for Safety Testing of Autonomous Vehicles, 2021
Systems Approach to Creating Test Scenarios for Automated Driving Systems, Reliability Engineering and System Safety (215), 2021
Automotive Functional Safety ISO 26262 Training Bootcamp : Tonex TrainingBryan Len
Price: $3,999.00
Length: 4 Days
Automotive functional safety ISO 26262 training covers the background of ISO 26262 standard, its scope, the main differences from IEC 61508 (the general safety standard), and how the scope varies with adding new systems.
What is ISO 26262?
ISO 26262 is a Functional Safety standard that is a modification of the general safety standard IEC 61508 for the specifics of Automotive Electric/Electronic Systems.
Learn About:
ISO 26262 requirements
The challenges of implementing ISO 26262
The formal safety management processes and the recommended supporting processes
Risk assessment and the functional safety concept
Technical safety concept and system design
Safety-oriented hardware and software development
A methodical approach to safety analysis
Skills required for effective auditing of the ISO 26262 requirements
Skills to review the Safety Case
Functional Safety Audit and Functional Safety Assessment
Confirmation Measures including Confirmation Reviews, Functional Safety Audit and Functional Safety Assessment
Hazard analysis and risk assessment (H&R / HARA)
Parts 2,3,4,5,6,7,8, and 9
FMEA
FTA
ISO 26262 hardware architectural metrics
Dependent failure analysis (DFA)
DRBFM
Why Do You Need ISO 26262 Training?
ISO 26262 is the new automotive application standard for functional safety IEC 61508 that impacts the whole product lifecycle. However, applying and implementing ISO 26262 in an effective, efficient way can be challenging.
Learning Objectives:
Upon the completion of automotive functional safety ISO 26262 training, the attendees are able to:
Understand the details of ISO 26262
Identify how the scope of ISO 26262 applies to their system
Develop a Safety Case plan complying ISO 26262
Respond to Development Interface Agreement compliant to ISO
Define the safety goals and Automotive Safety Integrity Level (ASIL)
Determine the HW requirements based on ASIL
Determine the SW requirements based on ASIL
Course Outline:
Overview of the ISO 26262
Functional Safety Management (Part 2)
Project-Independent Functional Safety Management Activities
Requirements of Safety Management
Work Products, Part 2
Concept Phase (Part 3)
Work Products, Part 3
Product Development, System Level (Part 4)
Work Products, Part 4
Product Development: Hardware Level (Part 5)
Assessing Possibility of Violation of A Safety Goal
Work Products, Part 5
Product Development: Software Level (Part 6)
Work Products, Part 7
Production and Operation (Part 7)
Work Products, Part 7
Supporting Processes (part 8)
Work Products, Part 8
ASIL-Oriented and Safety-Oriented Analyses (Part 9)
Work Products, Part 9
ISO 26262 Tools
ISO 26262 Auditing
TONEX Sample Hands-On Workshop
Request more information.Visit Tonex training link below
https://www.tonex.com/training-courses/automotive-functional-safety-iso-26262-training/
ISO26262-6 Software development process (Ver 3.0)Hongseok Lee
ISO26262-6 Software Development Process in the automotive domain. Planning(Coding Guideline. MISRA guideline), Requirement, Design, Safety Analysis, Testing
As the intricacy of Electronic Control Units (ECU) in present day vehicles has expanded, the requirement for automotive functional safety standard has turned out to be more goal. ISO 26262 standard tends to the all inclusive security hones required for planning basic car segments. We take a gander from an optimistic standpoint rehearses that will help you to plan ISO 26262-agreeable ECU programming.
An integrative solution towards SOTIF and AV safetyBernhard Kaiser
Slide set from this year's SOTIF conference in Austin, Texas, Oct 1 and 2, 2019. Shows intermediate pragmatic ideas on how to handle SOTIF in combination with ISO 26262 safety, and how to integrate SOTIF analysis with simulation and driving verification. Terminology may still change as ISO 21448 is evolving.
Get Answers to the most asked questions for ISO26262 compliant automotive Functional Safety consulting services. Check out the FAQs for Functional safety in automotive.
https://www.embitel.com/product-engineering-2/iso-26262functional-safety/
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.
Most industrial safety-critical systems are developed and validated following safety standards. However even though all safety standards address similar concerns with similar objectives, they are also domain-specific standards. The presentation results from the activity of a working group (formerly CG2E, now part of the recently set-up Embedded France) gathering industrial safety experts from aeronautics, automotive, industrial automation, nuclear, railway and space. The lecture will combine a presentation focused on one industry specific standard (the recent ISO 26262 for automotive), and complementary perspective in comparison with the standards in the other five mentioned domains. After the presentation of the history and position and the various regulation regimes, we will highlight some more technical topics e.g., integrated or external safety systems, fault prevention vs. fault tolerance, objectives vs. means prescription, probabilistic vs. deterministic arguments and the notion of criticality, integrity or assurance levels.
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.
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
Scenario-Based Development & Testing for Autonomous DrivingYu Huang
Formal Scenario-Based Testing of Autonomous Vehicles: From Simulation to the Real World, 2020
A Scenario-Based Development Framework for Autonomous Driving, 2020
A Customizable Dynamic Scenario Modeling and Data Generation Platform for Autonomous Driving, 2020
Large Scale Autonomous Driving Scenarios Clustering with Self-supervised Feature Extraction, 2021
Generating and Characterizing Scenarios for Safety Testing of Autonomous Vehicles, 2021
Systems Approach to Creating Test Scenarios for Automated Driving Systems, Reliability Engineering and System Safety (215), 2021
Automotive Functional Safety ISO 26262 Training Bootcamp : Tonex TrainingBryan Len
Price: $3,999.00
Length: 4 Days
Automotive functional safety ISO 26262 training covers the background of ISO 26262 standard, its scope, the main differences from IEC 61508 (the general safety standard), and how the scope varies with adding new systems.
What is ISO 26262?
ISO 26262 is a Functional Safety standard that is a modification of the general safety standard IEC 61508 for the specifics of Automotive Electric/Electronic Systems.
Learn About:
ISO 26262 requirements
The challenges of implementing ISO 26262
The formal safety management processes and the recommended supporting processes
Risk assessment and the functional safety concept
Technical safety concept and system design
Safety-oriented hardware and software development
A methodical approach to safety analysis
Skills required for effective auditing of the ISO 26262 requirements
Skills to review the Safety Case
Functional Safety Audit and Functional Safety Assessment
Confirmation Measures including Confirmation Reviews, Functional Safety Audit and Functional Safety Assessment
Hazard analysis and risk assessment (H&R / HARA)
Parts 2,3,4,5,6,7,8, and 9
FMEA
FTA
ISO 26262 hardware architectural metrics
Dependent failure analysis (DFA)
DRBFM
Why Do You Need ISO 26262 Training?
ISO 26262 is the new automotive application standard for functional safety IEC 61508 that impacts the whole product lifecycle. However, applying and implementing ISO 26262 in an effective, efficient way can be challenging.
Learning Objectives:
Upon the completion of automotive functional safety ISO 26262 training, the attendees are able to:
Understand the details of ISO 26262
Identify how the scope of ISO 26262 applies to their system
Develop a Safety Case plan complying ISO 26262
Respond to Development Interface Agreement compliant to ISO
Define the safety goals and Automotive Safety Integrity Level (ASIL)
Determine the HW requirements based on ASIL
Determine the SW requirements based on ASIL
Course Outline:
Overview of the ISO 26262
Functional Safety Management (Part 2)
Project-Independent Functional Safety Management Activities
Requirements of Safety Management
Work Products, Part 2
Concept Phase (Part 3)
Work Products, Part 3
Product Development, System Level (Part 4)
Work Products, Part 4
Product Development: Hardware Level (Part 5)
Assessing Possibility of Violation of A Safety Goal
Work Products, Part 5
Product Development: Software Level (Part 6)
Work Products, Part 7
Production and Operation (Part 7)
Work Products, Part 7
Supporting Processes (part 8)
Work Products, Part 8
ASIL-Oriented and Safety-Oriented Analyses (Part 9)
Work Products, Part 9
ISO 26262 Tools
ISO 26262 Auditing
TONEX Sample Hands-On Workshop
Request more information.Visit Tonex training link below
https://www.tonex.com/training-courses/automotive-functional-safety-iso-26262-training/
ISO26262-6 Software development process (Ver 3.0)Hongseok Lee
ISO26262-6 Software Development Process in the automotive domain. Planning(Coding Guideline. MISRA guideline), Requirement, Design, Safety Analysis, Testing
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
20161115 Agile in Automotive: "Balanceability is the new 'Agile'"Alexander Much
These are the slides from a keynote given on the Agile in Automotive 2016 in Stuttgart. It tries to place "Agile" and especially scrum where it belongs: a consultant hype and just one of many possible methods for automotive software development.
20160706 Automotive SYS: "Evolving Needs for Software Systems - Demonstrated"Alexander Much
A workshop on Automotive SYS 2016 which details current software architectures for safety systems, secure automotive Ethernet communication and how to build dynamically reconfigurable systems with AUTOSAR.
An overview presentation of the IAG Requirements Maturity Model with description of the key capability areas and characteristics of the maturity levels.
The automotive industry has grown to rely on software more than many other, traditionally software-focused industries. Software development expertise is increasingly becoming the currency in automotive development. To cut costs and time to market, the adoption of Agile is on the rise in this highly regulated industry. Our webinar helps you to learn how to ensure compliance with ISO 26262 and other automotive regulations (IEC 61508, Automotive SPICE, CMMI, etc) in an Agile development environment. The webinar also gives you practical knowledge about continuous compliance with ISO 26262 and other relevant automotive regulations.
The essence of an IT strategic plan is to align the IT department with the organization’s strategic intent, vision and business objectives in concert with the senior executive team. The goal is to develop a road map of initiatives and activities that will enable the organization to achieve the vision, and optimize the IT resource capability to deliver on the promised benefits and outcomes needed to accomplish the firm’s mission. The purpose of this webinar is to review the maturity levels of an organization’s Project Portfolio Management practice that will help the firm accomplish this mission.
To learn more: http://developingaculturethatworks.com/
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).
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
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
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.
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
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.
Sneak peek na15 agl01 leading construction industry to lean-agile (leagile)...Iram hasan
Sneak Peek; Leading Construction Industry to Lean-Agile (LeAgile) Project Management
Agility Conference 2015
PMI Global Congress North America 2015
Orlando, Florida (11-13 Oct 2015)
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).
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!
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.
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.
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.
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.
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.
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.
Sustainability of software depends on several factors including the processes deployed to develop, operate, maintain and dispose software systems. To make such sustainability-related processes actually deployable and controllable, specific green metrics and indicators are necessary. In this paper we propose a sound methodological approach to derive green metrics and we provide also a significant set of metrics, derived according to such an approach, able to address different aspects of software sustainability.
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