201108 qz systematisches_re

•

0 gefällt mir•227 views

Arnold Rudorfer

Technologie

Weitere ähnliche Inhalte

Mehr von Arnold 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.

Nih ce-presentation-05272016(for approval)

Arnold Rudorfer

Configuration Engineering for Invitro-Diagnostic (IVD) Product Development

Arnold Rudorfer

Configuration Engineering for Invitro-Diagnostic Product Development

Arnold Rudorfer

Ein Requirements Engineering Referenzmodell

Arnold 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.

S Ra P A Concurrent, Evolutionary Software Prototyping Process

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.

People And Project Management Issues In Highly Time Pressured Rapid Prototypi...

Arnold 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.

Using Evolutionary Prototypes To Formalize Product Requirements

Arnold Rudorfer

Scrum Med02232011 V4

Arnold Rudorfer

Lean Re Pres Rudorfer Vector Forum V1

Arnold Rudorfer

Visure Solutions Keynote06222009 V3

Arnold Rudorfer

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.

Incose Sweden Model Management01292011 V8

Arnold Rudorfer

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.

Refsq 2011 03 29 V3

Arnold Rudorfer

Lean Re Pres Ebert Rudorfer Re Conf2011 V8

Arnold Rudorfer

SYNGO TFS Program InfoTeam Keynote

Arnold Rudorfer

Mehr von Arnold Rudorfer (14)

Nih ce-presentation-05272016(for approval)

Configuration Engineering for Invitro-Diagnostic (IVD) Product Development

Configuration Engineering for Invitro-Diagnostic Product Development

Ein Requirements Engineering Referenzmodell

S Ra P A Concurrent, Evolutionary Software Prototyping Process

People And Project Management Issues In Highly Time Pressured Rapid Prototypi...

Using Evolutionary Prototypes To Formalize Product Requirements

Scrum Med02232011 V4

Lean Re Pres Rudorfer Vector Forum V1

Visure Solutions Keynote06222009 V3

Incose Sweden Model Management01292011 V8

Refsq 2011 03 29 V3

Lean Re Pres Ebert Rudorfer Re Conf2011 V8

SYNGO TFS Program InfoTeam Keynote

201108 qz systematisches_re

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Mehr von Arnold Rudorfer

Mehr von Arnold Rudorfer (14)