Downloads

Das Prozessmodell "Hardware SPICE" ist ein noch recht junges Modell zur Bewertung der Hardware-Engineering-Prozesse. Es ist stark angelehnt an das bekannte Automotive SPICE® und ergänzt die darin enthaltenen Prozesse um die Hardware-Aspekte. "Hardware SPICE" wird im Rahmen der intacs™ Arbeitsgruppe "Hardware Process Assessment Model" entwickelt und gepflegt. Im Dezember 2020 erschien die aktuell gültige Version 2.0. Das Modell wird zur Zeit noch selten implementiert oder assessiert. Da es in Zukunft aber an Bedeutung gewinnt, möchten wir einen Blick hinein werfen: · Wie ist das Modell aufgebaut?

Das Prozessmodell "Hardware SPICE" ist ein noch recht junges Modell zur Bewertung der Hardware-Engineering-Prozesse. Es ist stark angelehnt an das bekannte Automotive SPICE® und ergänzt die darin enthaltenen Prozesse um die Hardware-Aspekte. "Hardware SPICE" wird im Rahmen der intacs™ Arbeitsgruppe "Hardware Process Assessment Model" entwickelt und gepflegt. Im Dezember 2020 erschien die aktuell gültige Version 2.0. Das Modell wird zur Zeit noch selten implementiert oder assessiert.

2011 trat die erste Ausgabe der ISO 26262 „Road Vehicles – Functional Safety“ in Kraft. Seitdem wurden in der Automobilindustrie viele Anstrengungen unternommen, um bestehende Entwicklungsprozesse an die neuen Anforderungen anzupassen. Berechtigterweise hat sich in den letzten Jahren immer wieder die Frage gestellt, ob sich die Anforderungen der ISO 26262 mit Automotive SPICE® vereinbaren lassen und wie Entwicklungsprozesse gestaltet werden müssen, die beide Standards erfüllen.

Choosing the "right" development platform is one of the most important decisions in the development of software products. In the recent past there have been a number of new developments that help to avoid the common pitfalls of software development. One of them is the open source platform .NET Core 3 from Microsoft. This article starts by describing the most common pitfalls when deciding on a suitable development platform. It uses illustrative case studies to show how .NET Core 3 deals with these challenges. This article was published on the website of the DevInsider (online since 23.09.2020) and is available under the keyword Solution Stack.

Software developing organizations are increasingly under pressure to have assessments conducted to demonstrate their process capability to their OEM customers. The reaction to impending audits differs greatly between organizations. Organizations that fixate on passing the assessment instead of focussing the software process improvement activities on the organization's business goals can suffer inefficiencies. In this paper, we outline an approach for a systematic analysis of practicioners' experiences: Cases from professional experience were collected and condensed in scenarios that constrast potential influencing factors.Maria Eckey, senior consultant and team lead at the Method Park office in Stuttgart, presented this approach on this year's meeting of EuroSPI in Edinburgh. It was published in the conference transcript (p. 392-401). The download below contains links to the volume and the first two pages of Mrs Eckey's paper.

Many companies use both process management tools to ensure standard compliance for instance, and ALM tools to control the development of software components in the entire product lifecycle. However, the interface between these two tools often is undefined and gaps are only closed step by step by in-house developments. This approach leads to a confusing tool landscape. How to efficiently interlink ALM and process tools and which advantages result from this approach? These topics are described step by step in this technical article. In: HANSER automotive, Special Connected Cars (Edition 6/2019)

Manual testing of complex graphical user interfaces (GUI) requires high effort. With GUI testing tools, detailed test scenarios can be defined, their execution automated, and documented with screenshots. One of these GUI testing tools is Squish. Its basic principle is derived from the familiar concept of Behavior Driven Development (BDD). This article describes and evaluates Squish in the context of testing an application, written with Qt/QML, for the medical technology environment. In: German Testing Magazin (Insert of JavaSPEKTRUM 3/2019 and OBJEKTspektrum 4/2019)

This article describes typical challenges and risks arising from migrations of ALM data. These are often down to stakeholders but also to technical risks. Moreover, mapping the data model of an existing tool to a new tool is generally nontrivial. In addition to do’s and don’ts or patterns and anti-patterns, the author presents a procedure model he developed, based on agile principles, which enables a successful implementation of data migrations. In: OBJEKTspektrum (edition 3/2019)