The document discusses experiences with lean requirements engineering approaches applied to a large medical platform project between Siemens and Vector. It outlines several business challenges for the project, including controlling a complex architecture and facilitating market valuation. It then describes various lean solutions applied, such as using a feature model to group requirements, value-based ranking of features, mapping features to architecture, modeling clinical workflows visually, and adopting agile development practices. Structure-based tracing of features and requirements is also proposed to reduce tracing efforts and errors.
Medical device development is increasingly under market pressure to reduce deployment in critical care facilities. Further, budget cuts in critical care facilities drive process innovation mostly realized through a holistic integration of IT systems (hospital information systems, PACS and modalities). One important leverage to reduce development cycle time is to introduce learn/ agile requirements engineering approaches. Traditional V-model based development processes cannot cope with the pressure from the market. Given that the content of software in medical device has risen bigger than 60% (compared to 30% by end of the ‘90s), lean/agile RE is becoming a paramount discipline for a development organization to remain competitive. Our own experience and an underlying business case show concrete cost savings in the project planning, testing and complexity reduction of the imaging platform architecture. A comparison of traditional to learn/ agile requirements engineering rounds up the picture including key takeaways.
EDF2013: Keynote Gerhard Kreß: Big Data in Industrial ApplicationsEuropean Data Forum
Keynote talk of Gerhard Kreß, Director Strategic Transformation at Siemens AG, at the European Data Forum 2013, 10 April 2013 in Dublin, Ireland: Big Data in Industrial Applications
Medical device development is increasingly under market pressure to reduce deployment in critical care facilities. Further, budget cuts in critical care facilities drive process innovation mostly realized through a holistic integration of IT systems (hospital information systems, PACS and modalities). One important leverage to reduce development cycle time is to introduce learn/ agile requirements engineering approaches. Traditional V-model based development processes cannot cope with the pressure from the market. Given that the content of software in medical device has risen bigger than 60% (compared to 30% by end of the ‘90s), lean/agile RE is becoming a paramount discipline for a development organization to remain competitive. Our own experience and an underlying business case show concrete cost savings in the project planning, testing and complexity reduction of the imaging platform architecture. A comparison of traditional to learn/ agile requirements engineering rounds up the picture including key takeaways.
EDF2013: Keynote Gerhard Kreß: Big Data in Industrial ApplicationsEuropean Data Forum
Keynote talk of Gerhard Kreß, Director Strategic Transformation at Siemens AG, at the European Data Forum 2013, 10 April 2013 in Dublin, Ireland: Big Data in Industrial Applications
Was macht Projekte erfolgreich? Warum scheitern Projekte und liefern nicht das, was ihre Auftraggeber erwarten? Nach wie vor ist unzureichendes Requirements Engineering der Hauptgrund für abgebrochene Projekte oder solche, die ihre Ziele nicht erreichen. Technologische Herausforderungen sind per se keine wichtigen Projektrisiken, ihr Management dagegen schon. Doch es gibt auch genügend Projekte, die ihre Ziele erreichen. Grund genug, sich mit den Praktiken des Requirements Engineering auseinanderzusetzen und wesentliche Praxistipps zu geben. Dieser Übersichtsbeitrag basiert teilweise auf dem Buch „Systematisches Requirements Engineering“, das im Dpunkt-Verlag erschienen ist [1]. Unsere Erfahrungen in verschiedenen Industrieprojekten aus einer Vielzahl von Systemen und Anwendungen zeigen, dass ein gutes Verständnis sowie eine systematische Behandlung von Anforderungen erfolgskritisch sind. Wir zeigen mit praktischen Beispielen und einem Praxisbeispiel aus ei-ner sicherheitsrelevanten Anwendung z. B. aus der Medizintechnik, wie Requirements Engineering konkret und erfolgreich umgesetzt wird. Damit können die Kosten für Nacharbeiten um ca. 30% gesenkt werden.
Software-intensive medizinische Systeme stehen in einem immensen Marktdruck. Während sie technologisch und hinsichtlich ihrer Sicherheit kompromisslos innovativ sein müssen, fordern die Krankenhäuser und auch Gesundheitskostenreformen eine immer kürzere Zykluszeit bei gleichzeitig angespannten Budgets. Traditionelle Entwicklungsprozesse, die Innovation und Qualität über einen schwerfälligen Prozess erreichten, sind nicht mehr zeitgemäß. Unsere Studien zeigen, dass in der Medizintechnik die Kosten für Nacharbeiten über den Produktlebenszyklus hinweg durch eine Verbesserung des Requirements Engineering um 30-50% gesenkt werden können. Requirements Engineering hat daher eine Schlüsselstelle als Erfolgsfaktor im Gesundheitswesen. Modellbasierte Vorgehensweisen unterstützt die durchgängige Entwicklung von Anforderungen bis zur Validierung. Durch den erhöhten Abstraktionsgrad zu Beginn bei der anforderungsentwicklung und Analyse sind Problembeschreibungen wesentlich klarer, einfacher und weniger redundant. Das erhöht nicht nur die Entwicklungsgeschwindigkeit, sondern sorgt innerhalb des Projektes für klar verstandende Domänenkonzepte. Modelle helfen bei der Durchgängigkeit von den systemanforderungen zu den Softwareanforderungen und dann zu Design und Validierung. Unser Beitrag zeigt Industrieerfahrungen bei Siemens Healthcare und bietet Orientierung bei der Umsetzung modellbasierter Entwicklung mit Fokus auf Requirements Engineering in medizinischen Systemen. Wir zeigen, wie Anforderungen so formalisiert werden, dass einerseits informell formulierte Anforderungen schrittweise in eine formalere Form kommen und während die Verständlichkeit der Anforderungen erhalten bleibt. Damit sind die Anforderungen präzise formuliert und werden zur Konsistenzsicherung und Vervollständigung genutzt, und sie können weiterhin von Stakeholder verschiedenem Hintergrund verstanden und validiert werden.
Medical device development is increasingly under market pressure to reduce deployment time in critical care facilities. Further, budget cuts in critical care facilities drive process innovation mostly realized through a holistic integration of IT systems across departments (hospital information systems, PACS and modalities). One important leverage to reduce development cycle time and to control complexities of software along the life-cycle is to use model-based engineering approaches. Such new technology adoption is still in its early adoption phase. Less than 10 percent of organizations (in the medical device industry) use such approaches. As more and more clinical workflows start to be IT-supported > 60% (end of the ’90 only ~ 30%), model-based engineering brings viable solutions to large software development efforts (> 5000 requirements) in multi product lines. This talk will discuss implemented model-based engineering in Requirements Engineering, Architecture Design as well as outline what is planned for the system test by means of an imaging platform project carried out in Siemens Healthcare. Our own experience and an underlying business case show concrete cost savings in the project planning, testing and complexity reduction of the imaging platform architecture using a model-based requirements engineering approach. Further, the current status and requirements of engineering tools will be discussed. The talk ends with best practices developed as well as key take aways.
USTDA US-ASEAN Hanoi Vietnam 13th November 2012beckwithn
Neil Beckwith - Presentation given to the United States Trade and Development Agency - US-ASEAN Smart Grid Workshop in Hanoi, Vietnam 13th November 2012
Was macht Projekte erfolgreich? Warum scheitern Projekte und liefern nicht das, was ihre Auftraggeber erwarten? Nach wie vor ist unzureichendes Requirements Engineering der Hauptgrund für abgebrochene Projekte oder solche, die ihre Ziele nicht erreichen. Technologische Herausforderungen sind per se keine wichtigen Projektrisiken, ihr Management dagegen schon. Doch es gibt auch genügend Projekte, die ihre Ziele erreichen. Grund genug, sich mit den Praktiken des Requirements Engineering auseinanderzusetzen und wesentliche Praxistipps zu geben. Dieser Übersichtsbeitrag basiert teilweise auf dem Buch „Systematisches Requirements Engineering“, das im Dpunkt-Verlag erschienen ist [1]. Unsere Erfahrungen in verschiedenen Industrieprojekten aus einer Vielzahl von Systemen und Anwendungen zeigen, dass ein gutes Verständnis sowie eine systematische Behandlung von Anforderungen erfolgskritisch sind. Wir zeigen mit praktischen Beispielen und einem Praxisbeispiel aus ei-ner sicherheitsrelevanten Anwendung z. B. aus der Medizintechnik, wie Requirements Engineering konkret und erfolgreich umgesetzt wird. Damit können die Kosten für Nacharbeiten um ca. 30% gesenkt werden.
Software-intensive medizinische Systeme stehen in einem immensen Marktdruck. Während sie technologisch und hinsichtlich ihrer Sicherheit kompromisslos innovativ sein müssen, fordern die Krankenhäuser und auch Gesundheitskostenreformen eine immer kürzere Zykluszeit bei gleichzeitig angespannten Budgets. Traditionelle Entwicklungsprozesse, die Innovation und Qualität über einen schwerfälligen Prozess erreichten, sind nicht mehr zeitgemäß. Unsere Studien zeigen, dass in der Medizintechnik die Kosten für Nacharbeiten über den Produktlebenszyklus hinweg durch eine Verbesserung des Requirements Engineering um 30-50% gesenkt werden können. Requirements Engineering hat daher eine Schlüsselstelle als Erfolgsfaktor im Gesundheitswesen. Modellbasierte Vorgehensweisen unterstützt die durchgängige Entwicklung von Anforderungen bis zur Validierung. Durch den erhöhten Abstraktionsgrad zu Beginn bei der anforderungsentwicklung und Analyse sind Problembeschreibungen wesentlich klarer, einfacher und weniger redundant. Das erhöht nicht nur die Entwicklungsgeschwindigkeit, sondern sorgt innerhalb des Projektes für klar verstandende Domänenkonzepte. Modelle helfen bei der Durchgängigkeit von den systemanforderungen zu den Softwareanforderungen und dann zu Design und Validierung. Unser Beitrag zeigt Industrieerfahrungen bei Siemens Healthcare und bietet Orientierung bei der Umsetzung modellbasierter Entwicklung mit Fokus auf Requirements Engineering in medizinischen Systemen. Wir zeigen, wie Anforderungen so formalisiert werden, dass einerseits informell formulierte Anforderungen schrittweise in eine formalere Form kommen und während die Verständlichkeit der Anforderungen erhalten bleibt. Damit sind die Anforderungen präzise formuliert und werden zur Konsistenzsicherung und Vervollständigung genutzt, und sie können weiterhin von Stakeholder verschiedenem Hintergrund verstanden und validiert werden.
Medical device development is increasingly under market pressure to reduce deployment time in critical care facilities. Further, budget cuts in critical care facilities drive process innovation mostly realized through a holistic integration of IT systems across departments (hospital information systems, PACS and modalities). One important leverage to reduce development cycle time and to control complexities of software along the life-cycle is to use model-based engineering approaches. Such new technology adoption is still in its early adoption phase. Less than 10 percent of organizations (in the medical device industry) use such approaches. As more and more clinical workflows start to be IT-supported > 60% (end of the ’90 only ~ 30%), model-based engineering brings viable solutions to large software development efforts (> 5000 requirements) in multi product lines. This talk will discuss implemented model-based engineering in Requirements Engineering, Architecture Design as well as outline what is planned for the system test by means of an imaging platform project carried out in Siemens Healthcare. Our own experience and an underlying business case show concrete cost savings in the project planning, testing and complexity reduction of the imaging platform architecture using a model-based requirements engineering approach. Further, the current status and requirements of engineering tools will be discussed. The talk ends with best practices developed as well as key take aways.
USTDA US-ASEAN Hanoi Vietnam 13th November 2012beckwithn
Neil Beckwith - Presentation given to the United States Trade and Development Agency - US-ASEAN Smart Grid Workshop in Hanoi, Vietnam 13th November 2012
Presentazione Siemens all' Archibus user conference 2011 siemenseFM srl
Presentazione del progetto Archibus di Siemens Health Care all'International User Conference 2011 che gli fatto vincere l'ambito premio Application Excellence Award graze al progetto di implementazione dell' applicazione unica e innovativa Archibus svolto con il supporto di eFM.
To view the recorded version of the SAP webinar held at Computaris' 2 decade anniversary virtual event, please register here: http://webexpo.computaris.com/webinars/sap
Un año más, Siemens ha estado en una de las ferias tecnológicas más importantes del año: Hannover Messe. Aquí, encontraréis toda la actualidad sobre el sector industrial de la mano de Siegfried Russwurm, CEO de Siemens Industry.
Multi domain product architecture: start integrated, stay integratedObeo
A comprehensive product architecture is critical to cross-domain product development
The electronics industry adage '90% of the components work as designed but 50% fail when you plug them in' is multiplied as you bring together electronics, software, and mechanics in today's complex products.
Preventing these types of cross-product integration problems requires a cross-domain level of thinking supported by integrated Model-Based System Engineering (MBSE)
and architecting solutions that can be continuously verified and validated through simulations to identify issues early.
Based on Capella, and integrated with Teamcenter, System Modeling Workbench provides an integrated multi-domain product architecture that enables a cross-domain digital thread: 'start integrated, stay integrated'.
This webinar was driven by Pascal Vera (Siemens Digital Industries Software):
Pascal Vera is Product Management Director at Siemens Digital Industries Software, responsible for MBSE and ALM, and work in the team managing the partnership with Obeo for Capella integration with Teamcenter.
Holding a doctoral degree in industrial software engineering, he has 20+ years of experience in Systems Engineering, Mechatronics and Embedded Systems across multiple industries.
System Modeling Workbench is a joint development of Obeo and Siemens Digital Industries Software.
Similar to Lean Re Pres Ebert Rudorfer Re Conf2011 V8 (20)
This talk on Configuration Engineering (= Configuration Management for Platform development) will discuss challenges, solution approaches and engineering experiences in invitro-diagnostic (IVD) product development. CE is an emerging discipline in various industries (such as medical devices, automotive, avionics/ space, …) which has developed from Configuration Management practices for single products. Further, examples presented will highlight the underlying CE concepts as well as address tool issues including observed benefits over the introduction.
Configuration Engineering for Invitro-Diagnostic (IVD) Product DevelopmentArnold Rudorfer
This talk on Configuration Engineering (= Configuration Management for Platform development) will discuss challenges, solution approaches and engineering experiences in invitro-diagnostic (IVD) product development. CE is an emerging discipline in various industries (such as medical devices, automotive, avionics/ space, …) which has developed from Configuration Management practices for single products. Further, examples presented will highlight the underlying CE concepts as well as address tool issues including observed benefits over the introduction.
Configuration Engineering for Invitro-Diagnostic Product DevelopmentArnold Rudorfer
This talk on Configuration Engineering (= Configuration Management for Platform development) will discuss challenges, solution approaches and engineering experiences in invitro-diagnostic (IVD) product development. CE is an emerging discipline in various industries (such as medical devices, automotive, avionics/ space, …) which has developed from Configuration Management practices for single products. Further, examples presented will highlight the underlying CE concepts as well as address tool issues including observed benefits over the introduction.
S Ra P A Concurrent, Evolutionary Software Prototyping ProcessArnold Rudorfer
This paper defines a highly concurrent, software rapid prototyping
process that supports a sizable development team to develop a
high-quality, evolutionary software prototype. The process is particularly
aimed at developing user-interface intensive, workflow-centered
software. The Software Engineering Department and User Interface Design
Center at Siemens Corporate Research (SCR) have successfully
practiced this process in prototyping a healthcare information system
over the last year. We have evolved this agile, iterative software development
process that tightly integrates the UI designers and the software
developers with the prototype users (e.g., marketing staff), leading to efficient
development of business application prototypes with mature user
interfaces. We present the details of our process and the conditions that
make it effective. Our experience with this process indicates that prototypes
can be rapidly developed in a highly concurrent fashion given a
stable prototyping software architecture and access to readily available
domain knowledge.
People And Project Management Issues In Highly Time Pressured Rapid Prototypi...Arnold Rudorfer
This paper reports the experiences on people- and project management issues and how they
were successfully addressed to produce successive rapid deliveries of a medical healthcare
software prototype, the Soarian Financial product vision. The key practices of people and project
management are highlighted and concrete examples are provided to indicate how problems could
be resolved. Also, an outlook towards further research on people and project management issues
are presented in the context of evolutionary rapid development.
Using Evolutionary Prototypes To Formalize Product RequirementsArnold Rudorfer
Boundary objects are artifacts that facilitate
communication and interaction between people or groups
functioning in different domains. Software engineers, user
interface designers and usability specialists have different
domain knowledge, different terminologies, and shared
terms with different, distinct meanings. Boundary objects
can help assist the process of designing software by
providing a common interface for communication between
professionals in different domains. The Software
Engineering department and User Interface Design Center
at Siemens Corporate Research used an evolutionary
prototype as a boundary object to help elicit product
requirements from their client, Siemens Medical Solutions.
This enhanced communication with the client and between
groups at SCR. This paper describes how the evolutionary
prototype functioned as a boundary object and how it
allowed software engineering processes and humancomputer
interaction methods to proceed concurrently
without the need for well-defined interaction points.