The document discusses requirements engineering (RE) challenges at large scales and within Siemens Healthcare. It describes Siemens Healthcare's global presence and divisions. The Requirements Engineering Global Technology Field (RE GTF) was created to address RE challenges through a reference approach and centers of competence. The RE GTF provides best practices, Siemens-specific assets, and high productivity technologies to manage complexity and help projects succeed.
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Establishing Testing Knowledge and Experience Sharing at Siemens by Peter Zimmerer. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Quality Re Pres Ebert Rudorfer Med Conf2011 V4Arnold Rudorfer
This document summarizes a presentation on quality requirements engineering for medical systems. It discusses the challenges of developing safety and security critical medical devices. It provides an overview of quality requirements engineering and examples of how it was applied to a large medical device project at Siemens Healthcare involving thousands of requirements and hundreds of developers. The presentation outlines issues addressed through solutions like a feature model, forced ranking, architecture mapping, and a quality tree. It discusses positive results like improved reliability and reduced review efforts.
This document discusses model-based engineering approaches used by Siemens Healthcare in developing medical device software. It identifies challenges such as ambiguous specifications, complex architectures, and lack of verification and validation efficiency. Siemens addresses these issues through solutions like a requirements engineering meta-model to provide structure and traceability between business needs and technical specifications. They also use feature models and graphical clinical workflow models to improve understanding, scoping, and impact analysis for large projects. The aim is to increase efficiency, quality and productivity in medical device development.
Sascha Seifert, Siemens Healthcare, pour la journée e-health 2013Thearkvalais
This document discusses the THESEUS-MEDICO project, which aims to develop semantic web technologies for medical applications. It summarizes the project's goals of using ontologies and natural language processing to link medical images and text, enabling intelligent search, reporting and disease modeling. Key accomplishments included parsing medical images to understand anatomy, detecting findings in images, and developing semantic search of radiology reports. The work seeks to formalize medical knowledge for more comprehensive clinical decision support.
The document discusses challenges in product development at Siemens Healthcare and lessons learned for managing people and projects. It emphasizes the importance of multi-disciplinary teams, closed-loop communication, performance evaluations, training, and setting miniature milestones to help ensure on-time delivery of projects. Concurrent rapid prototyping is presented as an agile approach for developing products to meet tight deadlines.
This document provides details for planning the Siemens CT DC Excellence Awards 2013-14 event. It outlines the goals of celebrating nominees from 9 countries and 25 locations. It then describes various touchpoints and elements of the event including the theme, pre-event activities, main event components like the venue, entrance, registration process, and entertainment options. It presents two theme options for the event and provides additional event flow and design details.
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Establishing Testing Knowledge and Experience Sharing at Siemens by Peter Zimmerer. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Quality Re Pres Ebert Rudorfer Med Conf2011 V4Arnold Rudorfer
This document summarizes a presentation on quality requirements engineering for medical systems. It discusses the challenges of developing safety and security critical medical devices. It provides an overview of quality requirements engineering and examples of how it was applied to a large medical device project at Siemens Healthcare involving thousands of requirements and hundreds of developers. The presentation outlines issues addressed through solutions like a feature model, forced ranking, architecture mapping, and a quality tree. It discusses positive results like improved reliability and reduced review efforts.
This document discusses model-based engineering approaches used by Siemens Healthcare in developing medical device software. It identifies challenges such as ambiguous specifications, complex architectures, and lack of verification and validation efficiency. Siemens addresses these issues through solutions like a requirements engineering meta-model to provide structure and traceability between business needs and technical specifications. They also use feature models and graphical clinical workflow models to improve understanding, scoping, and impact analysis for large projects. The aim is to increase efficiency, quality and productivity in medical device development.
Sascha Seifert, Siemens Healthcare, pour la journée e-health 2013Thearkvalais
This document discusses the THESEUS-MEDICO project, which aims to develop semantic web technologies for medical applications. It summarizes the project's goals of using ontologies and natural language processing to link medical images and text, enabling intelligent search, reporting and disease modeling. Key accomplishments included parsing medical images to understand anatomy, detecting findings in images, and developing semantic search of radiology reports. The work seeks to formalize medical knowledge for more comprehensive clinical decision support.
The document discusses challenges in product development at Siemens Healthcare and lessons learned for managing people and projects. It emphasizes the importance of multi-disciplinary teams, closed-loop communication, performance evaluations, training, and setting miniature milestones to help ensure on-time delivery of projects. Concurrent rapid prototyping is presented as an agile approach for developing products to meet tight deadlines.
This document provides details for planning the Siemens CT DC Excellence Awards 2013-14 event. It outlines the goals of celebrating nominees from 9 countries and 25 locations. It then describes various touchpoints and elements of the event including the theme, pre-event activities, main event components like the venue, entrance, registration process, and entertainment options. It presents two theme options for the event and provides additional event flow and design details.
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.
This document discusses integrating user-centered design (UCD) and software engineering (SE) processes. It proposes combining the strengths of both approaches by using a single artifact, like a storyboard, to focus on client requirements, design the user interface, and shorten test cycles. The authors describe their experience developing a hospital administration software using an integrated UCD-SE process that employed a storyboard to capture requirements and verify functionality throughout development. They argue this approach can develop software faster while continually aligning with user needs.
Feature-Oriented Requirements Engineering (FORE) offers a solution to meet the challenges of engineering efficiency and cost effectiveness for medical device software development at Siemens Healthcare. FORE structures requirements according to marketable features to provide a business perspective throughout the product lifecycle. Integrating FORE provides benefits like more effective testing, transparency of requirements, reduced complexity through variability modeling, and simplified tracing. A business case found the net present value to be 15-20% of the annual R&D budget with a two year payback period, resulting in a return on investment of approximately 1:3. Testing benefits most from applying FORE.
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.
Quality Re Pres Ebert Rudorfer Med Conf2011 V5Arnold Rudorfer
This document discusses quality requirements engineering for medical systems. It provides an overview of quality requirements engineering challenges for medical device projects. It then discusses Siemens and Vector Consulting, the business environment for medical devices, and examples of applying quality requirements engineering for security. The document outlines some case studies and results, concluding that quality requirements engineering can improve system reliability and availability while reducing engineering effort.
The document discusses applying lean approaches to requirements engineering for the syngo.via medical platform project at Siemens. It aimed to address challenges of large project scope, tight regulations and costs, and complexity growth. The project involved over 5,000 requirements, millions of lines of code, and hundreds of developers. Lean requirements engineering techniques were used to help cope with these challenges and improve results and benefits.
The document discusses applying lean approaches to requirements engineering for the syngo.via medical platform project at Siemens. It aimed to address challenges of developing a large software project with thousands of requirements across many locations within tight budgets and regulations. The project sought to introduce lean requirements engineering techniques to help cope with these challenges and improve results.
This document summarizes an presentation on agile requirements engineering for a large platform project. It discusses the challenges of traditional requirements engineering for large projects. It then describes solutions implemented at Siemens Healthcare including using a feature model to group requirements, value-based prioritization of features, and incremental requirements engineering. Graphical modeling of clinical workflows was also used to improve specification clarity and reduce review times. The changes resulted in reduced effort for tracing, testing and other activities with an estimated positive net present value.
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.
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.
The document describes a presentation given by Siemens Healthcare SYNGO on their experiences using Microsoft Team Foundation Server (TFS). The presentation covered SYNGO's rationale for adopting TFS, how they set up their TFS program, initial experiences with project and change management using TFS, best practices for usability when customizing TFS, and the pros and cons they have identified with using TFS. The presentation was intended to provide an overview of SYNGO's TFS program and lessons learned from their experience transitioning to TFS for development project management.
The document discusses requirements engineering challenges in the healthcare industry. It covers business trends like increasing innovation rates, pressure for efficiency, and global engineering challenges. It also presents two healthcare IT case studies and best practices from industry projects to effectively address requirements engineering challenges.
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.
This document discusses integrating user-centered design (UCD) and software engineering (SE) processes. It proposes combining the strengths of both approaches by using a single artifact, like a storyboard, to focus on client requirements, design the user interface, and shorten test cycles. The authors describe their experience developing a hospital administration software using an integrated UCD-SE process that employed a storyboard to capture requirements and verify functionality throughout development. They argue this approach can develop software faster while continually aligning with user needs.
Feature-Oriented Requirements Engineering (FORE) offers a solution to meet the challenges of engineering efficiency and cost effectiveness for medical device software development at Siemens Healthcare. FORE structures requirements according to marketable features to provide a business perspective throughout the product lifecycle. Integrating FORE provides benefits like more effective testing, transparency of requirements, reduced complexity through variability modeling, and simplified tracing. A business case found the net present value to be 15-20% of the annual R&D budget with a two year payback period, resulting in a return on investment of approximately 1:3. Testing benefits most from applying FORE.
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.
Quality Re Pres Ebert Rudorfer Med Conf2011 V5Arnold Rudorfer
This document discusses quality requirements engineering for medical systems. It provides an overview of quality requirements engineering challenges for medical device projects. It then discusses Siemens and Vector Consulting, the business environment for medical devices, and examples of applying quality requirements engineering for security. The document outlines some case studies and results, concluding that quality requirements engineering can improve system reliability and availability while reducing engineering effort.
The document discusses applying lean approaches to requirements engineering for the syngo.via medical platform project at Siemens. It aimed to address challenges of large project scope, tight regulations and costs, and complexity growth. The project involved over 5,000 requirements, millions of lines of code, and hundreds of developers. Lean requirements engineering techniques were used to help cope with these challenges and improve results and benefits.
The document discusses applying lean approaches to requirements engineering for the syngo.via medical platform project at Siemens. It aimed to address challenges of developing a large software project with thousands of requirements across many locations within tight budgets and regulations. The project sought to introduce lean requirements engineering techniques to help cope with these challenges and improve results.
This document summarizes an presentation on agile requirements engineering for a large platform project. It discusses the challenges of traditional requirements engineering for large projects. It then describes solutions implemented at Siemens Healthcare including using a feature model to group requirements, value-based prioritization of features, and incremental requirements engineering. Graphical modeling of clinical workflows was also used to improve specification clarity and reduce review times. The changes resulted in reduced effort for tracing, testing and other activities with an estimated positive net present value.
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.
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.
The document describes a presentation given by Siemens Healthcare SYNGO on their experiences using Microsoft Team Foundation Server (TFS). The presentation covered SYNGO's rationale for adopting TFS, how they set up their TFS program, initial experiences with project and change management using TFS, best practices for usability when customizing TFS, and the pros and cons they have identified with using TFS. The presentation was intended to provide an overview of SYNGO's TFS program and lessons learned from their experience transitioning to TFS for development project management.
The document discusses requirements engineering challenges in the healthcare industry. It covers business trends like increasing innovation rates, pressure for efficiency, and global engineering challenges. It also presents two healthcare IT case studies and best practices from industry projects to effectively address requirements engineering challenges.