We present the use of Dynamic Condition Response Graphs (www.DCRGraphs.net) developed at Exformatics.com and researchers in the Process and System Models Group at IT University of Copenhagen (www.itu.dk/research/models) for modelling and implementing an Adaptive Case Management system for a grant application process.
A small talk on specification of regulatory rules for processes as Dynamic Condition Response graphs given at a Continuous Delivery Meetup at Delta in Denmark. The talk uses an example of a healthcare workflow provided in the excellent book by Reichert and Weber: Enabling Flexibility in Process-aware Information Systems.
This document discusses adapting to case management and the challenges of predefined processes, constant change, and fitting business needs into process models. It proposes adapting by:
1) Predefining only necessary/repeatable aspects and giving guidance for unpredictable work.
2) Empowering users to adjust solutions for ad hoc work and change over time.
3) Moving beyond only process maps to identify core business entities and describe relationships to provide a foundation for various solutions.
Adopting adaptive case management strategies can be successful by centering on describing a business in its own terms rather than changing how the business thinks. The tool then adapts to fit the business needs.
My keynote on Flexible, Adaptable & Compliant Business Systems with Dynamic Condition Response (DCR) Graphs given at the ForMABS 2016 workshop on Formal Methods for Analysis of Business Systems affiliated to ASE 2016 (ase2016.org).
My presentation on how to infer Concurrency & Asynchrony in Declarative Workflow just given at the BPM 2015 conference. The technique allows from analysing compliance rules specified in DCRGraphs.net for business and workflow processes to find out which activities can be carried out independently and thus in parallel or distributed across different actors. The technique is demonstrated on a healthcare workflow.
Towards Flexible, Adaptable & Compliant Process-Aware Information Systems wit...Thomas Hildebrandt
Slides for talk given at the ZISC Institute, ETH Zurich, November 27th, 2015.
Abstract of talk:
Software systems today support complex processes and interactions between humans and
machines in many different variants, from the embedded controllers in cars to workflow
systems in hospitals and case management systems in banks. On the one hand, such
process-aware information systems often operate in unpredictable and changing contexts
which calls for both flexibility and adaptability. On the other hand, it is getting more
and more critical that the software system behaves correctly and is compliant with safety,
security and legal regulations.
In the talk we will address the short-comings of the state-of-the-art industrial standards
for process-aware information systems, in particular the process notations employed in
business process management systems. We then present and demonstrate a new event-based and
declarative process notation and modelling approach for the design of flexible, adaptable
and compliant process-aware information systems called Dynamic Condition Response (DCR)
graphs. DCR Graphs have been developed at IT University of Copenhagen in collaboration
with the danish company Exformatics and has been implemented in an industrial process
design tool, DCRGraphs.net and the Exformatics Enterprise Content and Adaptive Case
Management solution. The talk will contain examples of applications of the DCR Graphs
approach to case management, emergency management and security and will be concluded with
an overview of ongoing work and challenges.
The work is supported by the The Danish Council for Strategic Research, the Royal Danish
Defence College, IT University of Copenhagen, the Velux Foundation, Resultmaker and
Exformatics.
Adaptive Case Management as a Process of Construction of and Movement in a St...Ilia Bider
Despite having a number of years of experience, adaptive case management (ACM) still does not have a theory that would differentiate it from other paradigms of business process management and support. The known attempts to formalize Case Management do not seem to help much in creating an approach that could be useful in practice. This paper suggests an approach to building such a theory based on generalization of what is used in practice on one hand and the state-oriented view on business processes on the other. In practice, ACM systems use a number of ready-made templates that are picked up and filled as necessary for the case. State-oriented view considers a process instance/case as a point moving in a specially constructed state space. The paper suggests to consider a case template as a definition of a sub-space and piking different template on the fly as constructing the state space along with moving in it when filling the template. The result is similar to what in control theory is considered a state space with variable numbers of dimensions. Beside suggestions to building a theory, the paper demonstrates the usage of the theory on an example.
Distribute Process Knowledge in Adaptive Case management through MentoringAdaPro GmbH
1) The document discusses how to distribute process knowledge in organizations through mentoring and adaptive case management (ACM).
2) It describes a case study of an engineer, Leona, who feels overwhelmed by being the only person with knowledge to resolve critical tickets. She decides to mentor her colleague, Steve, by delegating some testing tasks to him and documenting the test procedures.
3) Over multiple iterations, Leona refines her knowledge sharing approach. She creates templates for common testing tasks, documents the procedures, and assigns the tasks to the role of "Test Assistant" in her workflow template, allowing others to take on those tasks. This helps distribute her workload while establishing living, evolving knowledge within the organization
This document provides an overview of Reactive Extensions (Rx) for .NET, which is a new API that enables "LINQ over Events". It introduces key Rx concepts like Observables, Observers, pushing vs pulling data, and dualizing interfaces like IEnumerable/IEnumerator to provide a standard way to work with pushed data. It also demonstrates how to create Observables from different sources and use important Rx operators like Merge, Zip, GroupBy. Overall it serves as an introduction to understanding and working with the Rx framework for .NET.
A small talk on specification of regulatory rules for processes as Dynamic Condition Response graphs given at a Continuous Delivery Meetup at Delta in Denmark. The talk uses an example of a healthcare workflow provided in the excellent book by Reichert and Weber: Enabling Flexibility in Process-aware Information Systems.
This document discusses adapting to case management and the challenges of predefined processes, constant change, and fitting business needs into process models. It proposes adapting by:
1) Predefining only necessary/repeatable aspects and giving guidance for unpredictable work.
2) Empowering users to adjust solutions for ad hoc work and change over time.
3) Moving beyond only process maps to identify core business entities and describe relationships to provide a foundation for various solutions.
Adopting adaptive case management strategies can be successful by centering on describing a business in its own terms rather than changing how the business thinks. The tool then adapts to fit the business needs.
My keynote on Flexible, Adaptable & Compliant Business Systems with Dynamic Condition Response (DCR) Graphs given at the ForMABS 2016 workshop on Formal Methods for Analysis of Business Systems affiliated to ASE 2016 (ase2016.org).
My presentation on how to infer Concurrency & Asynchrony in Declarative Workflow just given at the BPM 2015 conference. The technique allows from analysing compliance rules specified in DCRGraphs.net for business and workflow processes to find out which activities can be carried out independently and thus in parallel or distributed across different actors. The technique is demonstrated on a healthcare workflow.
Towards Flexible, Adaptable & Compliant Process-Aware Information Systems wit...Thomas Hildebrandt
Slides for talk given at the ZISC Institute, ETH Zurich, November 27th, 2015.
Abstract of talk:
Software systems today support complex processes and interactions between humans and
machines in many different variants, from the embedded controllers in cars to workflow
systems in hospitals and case management systems in banks. On the one hand, such
process-aware information systems often operate in unpredictable and changing contexts
which calls for both flexibility and adaptability. On the other hand, it is getting more
and more critical that the software system behaves correctly and is compliant with safety,
security and legal regulations.
In the talk we will address the short-comings of the state-of-the-art industrial standards
for process-aware information systems, in particular the process notations employed in
business process management systems. We then present and demonstrate a new event-based and
declarative process notation and modelling approach for the design of flexible, adaptable
and compliant process-aware information systems called Dynamic Condition Response (DCR)
graphs. DCR Graphs have been developed at IT University of Copenhagen in collaboration
with the danish company Exformatics and has been implemented in an industrial process
design tool, DCRGraphs.net and the Exformatics Enterprise Content and Adaptive Case
Management solution. The talk will contain examples of applications of the DCR Graphs
approach to case management, emergency management and security and will be concluded with
an overview of ongoing work and challenges.
The work is supported by the The Danish Council for Strategic Research, the Royal Danish
Defence College, IT University of Copenhagen, the Velux Foundation, Resultmaker and
Exformatics.
Adaptive Case Management as a Process of Construction of and Movement in a St...Ilia Bider
Despite having a number of years of experience, adaptive case management (ACM) still does not have a theory that would differentiate it from other paradigms of business process management and support. The known attempts to formalize Case Management do not seem to help much in creating an approach that could be useful in practice. This paper suggests an approach to building such a theory based on generalization of what is used in practice on one hand and the state-oriented view on business processes on the other. In practice, ACM systems use a number of ready-made templates that are picked up and filled as necessary for the case. State-oriented view considers a process instance/case as a point moving in a specially constructed state space. The paper suggests to consider a case template as a definition of a sub-space and piking different template on the fly as constructing the state space along with moving in it when filling the template. The result is similar to what in control theory is considered a state space with variable numbers of dimensions. Beside suggestions to building a theory, the paper demonstrates the usage of the theory on an example.
Distribute Process Knowledge in Adaptive Case management through MentoringAdaPro GmbH
1) The document discusses how to distribute process knowledge in organizations through mentoring and adaptive case management (ACM).
2) It describes a case study of an engineer, Leona, who feels overwhelmed by being the only person with knowledge to resolve critical tickets. She decides to mentor her colleague, Steve, by delegating some testing tasks to him and documenting the test procedures.
3) Over multiple iterations, Leona refines her knowledge sharing approach. She creates templates for common testing tasks, documents the procedures, and assigns the tasks to the role of "Test Assistant" in her workflow template, allowing others to take on those tasks. This helps distribute her workload while establishing living, evolving knowledge within the organization
This document provides an overview of Reactive Extensions (Rx) for .NET, which is a new API that enables "LINQ over Events". It introduces key Rx concepts like Observables, Observers, pushing vs pulling data, and dualizing interfaces like IEnumerable/IEnumerator to provide a standard way to work with pushed data. It also demonstrates how to create Observables from different sources and use important Rx operators like Merge, Zip, GroupBy. Overall it serves as an introduction to understanding and working with the Rx framework for .NET.
Total Quality Management (TQM) aims to meet customer needs through continuous quality improvement involving the entire organization. While TQM was effective for linear systems, modern organizations exhibit nonlinear complexity. To better address this, TQM could integrate principles from chaos theory and view organizations as complex adaptive systems. This would involve statistical tools to analyze variation, methods to promote systemic thinking and dialogue, and experimenting with different quality approaches to advance the field.
IT and Business Process Modelling course at IT University of Copenhagen (Lect...Thomas Hildebrandt
First and second lecture for the IT and Business Process Modelling course at IT University of Copenhagen.
The course has focus on flexibility in business processes and introduces to DCR Graphs business process constraint mapping (using www.dcrgraphs.net) and BPMN modelling (using www.academic.signavio.com).
It is based on the book "Enabling Flexibility in Process-Aware Information Systems - Challenges, Methods, Technologies" by Manfred Reichert and Barbara Weber. (http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-3-642-30408-8)
AwwStruck is an Indian website that aggregates and sells handicrafts from across India in order to showcase the country's cultural diversity. Indian handicrafts have a long history and tradition and represent the cultural brilliance of India. AwwStruck offers a wide variety of handicrafts for home decor, weddings, and gifts that demonstrate the vast variety produced by India's large handicraft industry. Producers of handicrafts are encouraged to connect with AwwStruck to sell their products.
Case Management: Where Rules Meet Process And ContentSandy Kemsley
This document discusses case management systems and how they can help knowledge workers. It defines case management as a combination of process, content, rules, and events to support knowledge work in a flexible way. The document outlines how case management provides benefits like improved decision making through contextual information, enforcement of policies and rules, and visibility into work in progress. It provides examples of how case management helps with tasks like loan exception handling, customer support, and insurance claims processing.
Os2 Erfa-møde - Fleksibel og Agil Digitalisering ved hjælp af DCR graferThomas Hildebrandt
OS2 Erfa-seminar om fleksibel digitalisering. Københavns Kommune, koncernservice. Præsenterer DCR Grafer, digitalisering af lovgivning og sammenligner med BPMN.
The document defines case management and provides examples. It then describes a reference architecture for case management with five domains: Collaboration and Social, Deliver, Manage, Create, and Support. Each domain contains specific capabilities for case management. The Manage domain capabilities include information management, business rules management, process and activity management, and content management. The Create domain capabilities include modeling, content creation, and case initiation.
The document discusses the management theories of Taylorism and Fayolism. It provides examples of how Frederick Taylor's scientific management principles were applied through experiments and case studies. It also explains Henri Fayol's 14 principles of management. The key differences between Taylor and Fayol are discussed, with Taylor focusing on workers as machines and Fayol treating workers as capital assets. An example is given of how Tata Consultancy Services applied Fayol's principles to become a leading technology company.
scientific management by taylor and fayolism- Administrative management(theor...Reon Zedval
The document discusses different perspectives on scientific management approaches proposed by Taylor and Fayol. Taylor focused on improving worker efficiency from the bottom up through careful analysis of tasks. Fayol took a top-down perspective, emphasizing educating managers first to improve processes and then workers. While Taylor viewed work scientifically and objectively, Fayol considered more human and behavioral factors, focusing on training management and ensuring fair treatment of employees.
This document discusses system architecture and provides examples. It defines system architecture as the conceptual model that defines a system's structure, behavior, and views. System architecture can refer to the architecture of a system itself, the process of architecting a system, or the body of knowledge for designing systems. An effective system architecture depicts the system's elements, properties, relationships, behaviors, and multiple views in an overall model. The document also provides examples of system architectures and things to consider when developing an architecture, such as key parts, elements, relationships, and techniques. It emphasizes that the architecture should represent the overall research topic.
Business Process Management and Case ManagementSandy Kemsley
This document discusses the differences between business process management (BPM) and case management (CM). BPM focuses on optimizing routine, repeatable business processes, while CM handles more dynamic, knowledge-based work. The document proposes that few real-world processes are fully structured or unstructured, so CM and BPM often work together, with structured processes sometimes spawning case management exceptions and cases invoking structured process fragments when needed.
This document discusses Oracle's Siebel case management software and its applications across various industries. It provides an agenda that covers Siebel CRM and case management, case management in different institutions, complementary solutions, analytical approaches, and pricing. It then discusses challenges organizations face around siloed infrastructure and legacy systems. The rest of the document focuses on how Siebel provides a unified case management approach, centralized data repository, and transforms delivery of customer services through integrated customer service and case management. It provides examples of how Siebel supports benefits case management, investigative case management, and social services case management.
Talk given by Robert Maxwell, Lead Incident Handler and Kelly McCracken, Director, CSIRT at Salesforce, at Techno Security, in June 2016
Effective IR Communication & Coordination using a Case Management System Description: Too often IR teams are left to managing incidents from email, personal folders, and shared drive. Salesforce's CSIRT will demonstrate how they have developed an effective case management system to increase the team's ability to effectively track, respond, manage, measure, and report on incidents from detection through the lessons learned phase of the incident response lifecycle.
The document provides an introduction to business process management (BPM). It defines BPM as both a management methodology and enabling technology. The goals of BPM include improving efficiency, compliance, agility, and visibility of business processes. Benefits include process improvement, increased business agility, and self-documenting processes. The document discusses the evolution of BPM technology and trends, including the emergence of BPMN standards and model-driven development. It also outlines how BPM relates to service-oriented architecture.
Taming The Unpredictable: Real-World Adaptive Case ManagementKeith Swenson
The document discusses the shift from deterministic "push" models of work to non-deterministic "pull" models driven by goals and outcomes. It argues that as knowledge work becomes more important, management needs to move from Newtonian to quantum views that embrace unpredictability. Case management and adaptive case management (ACM) are presented as tools to support goal-driven, event-based work that allows knowledge workers flexibility.
26 topline marketing strategies to launch a new brand, product or service. Includes a 1 page summary outlining the pros and cons of each approach as well as best in class examples. Designed as flashcards so that it can be printed out to help stimulate brainstorm sessions.
Thomas Hildebrandt gives a presentation on business process management (BPM) and adaptive case management. He discusses how BPM can be used to describe "as-is" and "to-be" processes as flow diagrams, configure a standard BPM system to implement the processes, and analyze operational processes to improve them. Hildebrandt also outlines his background researching collaborative processes and process-oriented IT systems.
The document discusses systems analysis and design (SAD), which refers to the process of examining a business situation with the intent of improving it through better procedures and methods. SAD involves defining problems, requirements, and specifications, as well as designing solutions and implementations. It discusses the various phases of system development like planning, analysis, design, development, testing, implementation, and maintenance. It also describes different approaches to system development like process-oriented, object-oriented, and data-oriented. Finally, it discusses different system development life cycle (SDLC) models like waterfall, spiral, and agile models.
An Assessment Model Study for Lean and Agile (Leagile) Index by Using Fuzzy AHPDr. Lutfi Apiliogullari
This document describes a study that develops an assessment model to evaluate companies on their level of implementing lean and agile principles and strategies. The study uses fuzzy analytic hierarchy process (fuzzy AHP) and decision making trial and evaluation laboratory (DEMATEL) methods to determine the important lean and agile criteria and their relationships. Lean and agile criteria are identified from literature and expert opinions. Fuzzy AHP is used to assign weights to the criteria. The model is applied to a company to calculate their initial lean/agile index. Improvements are then made and the index is recalculated to test the model. The goal is to help companies assess their situation regarding lean and agile implementation and identify areas for improvement.
Change Management for ERP implementations - 101Luc Galoppin
Learning
Stream
Communica6ons
Stream
Performance
Stream
1. The document discusses organizational change and ERP projects, covering topics like managing resistance to change, predicting resistance, and approaches to change management.
2. It describes four "workstreams" for managing organizational change: communication, learning, organization, and performance. The communication stream involves managing expectations, the learning stream upgrades skills/knowledge, the organization stream defines new roles/responsibilities, and the performance stream translates strategies into new ways of working.
3. Models and approaches to change management are presented, including the change cycle, ingredients for successful change, common illusions about
TUW-ASE-Summer 2014: Advanced service-based data analytics: concepts and designsHong-Linh Truong
This document discusses concepts and designs for advanced service-based data analytics. It begins by outlining principles of elasticity for data analytics and discussing data analytics within a single system. Data analytics within a single system is complex but has limitations as it operates within a single domain and infrastructure. The document goes on to discuss performing data analytics across multiple systems and composable cost evaluation.
From Model-based to Model and Simulation-based Systems ArchitecturesObeo
Achieving quality engineering through descriptive and analytical models
Systems architecture design is a key activity that affect the
overall systems engineering cost. It is hence fundamental
to ensure that the system architecture reaches a proper quality.
In this paper, we leverage on MBSE approaches and complement them
with simulation techniques, as a prom-ising way to improve the quality of the system architecture definition, and to come up with inno-vative solutions while securing the systems engineering process.
Total Quality Management (TQM) aims to meet customer needs through continuous quality improvement involving the entire organization. While TQM was effective for linear systems, modern organizations exhibit nonlinear complexity. To better address this, TQM could integrate principles from chaos theory and view organizations as complex adaptive systems. This would involve statistical tools to analyze variation, methods to promote systemic thinking and dialogue, and experimenting with different quality approaches to advance the field.
IT and Business Process Modelling course at IT University of Copenhagen (Lect...Thomas Hildebrandt
First and second lecture for the IT and Business Process Modelling course at IT University of Copenhagen.
The course has focus on flexibility in business processes and introduces to DCR Graphs business process constraint mapping (using www.dcrgraphs.net) and BPMN modelling (using www.academic.signavio.com).
It is based on the book "Enabling Flexibility in Process-Aware Information Systems - Challenges, Methods, Technologies" by Manfred Reichert and Barbara Weber. (http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-3-642-30408-8)
AwwStruck is an Indian website that aggregates and sells handicrafts from across India in order to showcase the country's cultural diversity. Indian handicrafts have a long history and tradition and represent the cultural brilliance of India. AwwStruck offers a wide variety of handicrafts for home decor, weddings, and gifts that demonstrate the vast variety produced by India's large handicraft industry. Producers of handicrafts are encouraged to connect with AwwStruck to sell their products.
Case Management: Where Rules Meet Process And ContentSandy Kemsley
This document discusses case management systems and how they can help knowledge workers. It defines case management as a combination of process, content, rules, and events to support knowledge work in a flexible way. The document outlines how case management provides benefits like improved decision making through contextual information, enforcement of policies and rules, and visibility into work in progress. It provides examples of how case management helps with tasks like loan exception handling, customer support, and insurance claims processing.
Os2 Erfa-møde - Fleksibel og Agil Digitalisering ved hjælp af DCR graferThomas Hildebrandt
OS2 Erfa-seminar om fleksibel digitalisering. Københavns Kommune, koncernservice. Præsenterer DCR Grafer, digitalisering af lovgivning og sammenligner med BPMN.
The document defines case management and provides examples. It then describes a reference architecture for case management with five domains: Collaboration and Social, Deliver, Manage, Create, and Support. Each domain contains specific capabilities for case management. The Manage domain capabilities include information management, business rules management, process and activity management, and content management. The Create domain capabilities include modeling, content creation, and case initiation.
The document discusses the management theories of Taylorism and Fayolism. It provides examples of how Frederick Taylor's scientific management principles were applied through experiments and case studies. It also explains Henri Fayol's 14 principles of management. The key differences between Taylor and Fayol are discussed, with Taylor focusing on workers as machines and Fayol treating workers as capital assets. An example is given of how Tata Consultancy Services applied Fayol's principles to become a leading technology company.
scientific management by taylor and fayolism- Administrative management(theor...Reon Zedval
The document discusses different perspectives on scientific management approaches proposed by Taylor and Fayol. Taylor focused on improving worker efficiency from the bottom up through careful analysis of tasks. Fayol took a top-down perspective, emphasizing educating managers first to improve processes and then workers. While Taylor viewed work scientifically and objectively, Fayol considered more human and behavioral factors, focusing on training management and ensuring fair treatment of employees.
This document discusses system architecture and provides examples. It defines system architecture as the conceptual model that defines a system's structure, behavior, and views. System architecture can refer to the architecture of a system itself, the process of architecting a system, or the body of knowledge for designing systems. An effective system architecture depicts the system's elements, properties, relationships, behaviors, and multiple views in an overall model. The document also provides examples of system architectures and things to consider when developing an architecture, such as key parts, elements, relationships, and techniques. It emphasizes that the architecture should represent the overall research topic.
Business Process Management and Case ManagementSandy Kemsley
This document discusses the differences between business process management (BPM) and case management (CM). BPM focuses on optimizing routine, repeatable business processes, while CM handles more dynamic, knowledge-based work. The document proposes that few real-world processes are fully structured or unstructured, so CM and BPM often work together, with structured processes sometimes spawning case management exceptions and cases invoking structured process fragments when needed.
This document discusses Oracle's Siebel case management software and its applications across various industries. It provides an agenda that covers Siebel CRM and case management, case management in different institutions, complementary solutions, analytical approaches, and pricing. It then discusses challenges organizations face around siloed infrastructure and legacy systems. The rest of the document focuses on how Siebel provides a unified case management approach, centralized data repository, and transforms delivery of customer services through integrated customer service and case management. It provides examples of how Siebel supports benefits case management, investigative case management, and social services case management.
Talk given by Robert Maxwell, Lead Incident Handler and Kelly McCracken, Director, CSIRT at Salesforce, at Techno Security, in June 2016
Effective IR Communication & Coordination using a Case Management System Description: Too often IR teams are left to managing incidents from email, personal folders, and shared drive. Salesforce's CSIRT will demonstrate how they have developed an effective case management system to increase the team's ability to effectively track, respond, manage, measure, and report on incidents from detection through the lessons learned phase of the incident response lifecycle.
The document provides an introduction to business process management (BPM). It defines BPM as both a management methodology and enabling technology. The goals of BPM include improving efficiency, compliance, agility, and visibility of business processes. Benefits include process improvement, increased business agility, and self-documenting processes. The document discusses the evolution of BPM technology and trends, including the emergence of BPMN standards and model-driven development. It also outlines how BPM relates to service-oriented architecture.
Taming The Unpredictable: Real-World Adaptive Case ManagementKeith Swenson
The document discusses the shift from deterministic "push" models of work to non-deterministic "pull" models driven by goals and outcomes. It argues that as knowledge work becomes more important, management needs to move from Newtonian to quantum views that embrace unpredictability. Case management and adaptive case management (ACM) are presented as tools to support goal-driven, event-based work that allows knowledge workers flexibility.
26 topline marketing strategies to launch a new brand, product or service. Includes a 1 page summary outlining the pros and cons of each approach as well as best in class examples. Designed as flashcards so that it can be printed out to help stimulate brainstorm sessions.
Thomas Hildebrandt gives a presentation on business process management (BPM) and adaptive case management. He discusses how BPM can be used to describe "as-is" and "to-be" processes as flow diagrams, configure a standard BPM system to implement the processes, and analyze operational processes to improve them. Hildebrandt also outlines his background researching collaborative processes and process-oriented IT systems.
The document discusses systems analysis and design (SAD), which refers to the process of examining a business situation with the intent of improving it through better procedures and methods. SAD involves defining problems, requirements, and specifications, as well as designing solutions and implementations. It discusses the various phases of system development like planning, analysis, design, development, testing, implementation, and maintenance. It also describes different approaches to system development like process-oriented, object-oriented, and data-oriented. Finally, it discusses different system development life cycle (SDLC) models like waterfall, spiral, and agile models.
An Assessment Model Study for Lean and Agile (Leagile) Index by Using Fuzzy AHPDr. Lutfi Apiliogullari
This document describes a study that develops an assessment model to evaluate companies on their level of implementing lean and agile principles and strategies. The study uses fuzzy analytic hierarchy process (fuzzy AHP) and decision making trial and evaluation laboratory (DEMATEL) methods to determine the important lean and agile criteria and their relationships. Lean and agile criteria are identified from literature and expert opinions. Fuzzy AHP is used to assign weights to the criteria. The model is applied to a company to calculate their initial lean/agile index. Improvements are then made and the index is recalculated to test the model. The goal is to help companies assess their situation regarding lean and agile implementation and identify areas for improvement.
Change Management for ERP implementations - 101Luc Galoppin
Learning
Stream
Communica6ons
Stream
Performance
Stream
1. The document discusses organizational change and ERP projects, covering topics like managing resistance to change, predicting resistance, and approaches to change management.
2. It describes four "workstreams" for managing organizational change: communication, learning, organization, and performance. The communication stream involves managing expectations, the learning stream upgrades skills/knowledge, the organization stream defines new roles/responsibilities, and the performance stream translates strategies into new ways of working.
3. Models and approaches to change management are presented, including the change cycle, ingredients for successful change, common illusions about
TUW-ASE-Summer 2014: Advanced service-based data analytics: concepts and designsHong-Linh Truong
This document discusses concepts and designs for advanced service-based data analytics. It begins by outlining principles of elasticity for data analytics and discussing data analytics within a single system. Data analytics within a single system is complex but has limitations as it operates within a single domain and infrastructure. The document goes on to discuss performing data analytics across multiple systems and composable cost evaluation.
From Model-based to Model and Simulation-based Systems ArchitecturesObeo
Achieving quality engineering through descriptive and analytical models
Systems architecture design is a key activity that affect the
overall systems engineering cost. It is hence fundamental
to ensure that the system architecture reaches a proper quality.
In this paper, we leverage on MBSE approaches and complement them
with simulation techniques, as a prom-ising way to improve the quality of the system architecture definition, and to come up with inno-vative solutions while securing the systems engineering process.
This document summarizes reasons why Cisco management hesitated to engage in an ERP implementation project. The key reasons included:
- Fear of decentralization and large "mega-projects" that ERP implementations can become.
- Disruption to existing business processes and operations.
- Need for a strong internal team and partners to lead the project given its complexity.
- Balancing standardization with maintaining some proprietary functionality.
- High costs associated with large ERP projects.
Cisco's approach was to implement the ERP system quickly to minimize disruption to the business.
Integrated Analysis of Traditional Requirements Engineering Process with Agil...zillesubhan
In the past few years, agile software development approach has emerged as a most attractive software development approach. A typical CASE environment consists of a number of CASE tools operating on a common hardware and software platform and note that there are a number of different classes of users of a CASE environment. In fact, some users such as software developers and managers wish to make use of CASE tools to support them in developing application systems and monitoring the progress of a project. This development approach has quickly caught the attention of a large number of software development firms. However, this approach particularly pays attention to development side of software development project while neglects critical aspects of requirements engineering process. In fact, there is no standard requirement engineering process in this approach and requirements engineering activities vary from situation to situation. As a result, there emerge a large number of problems which can lead the software development projects to failure. One of major drawbacks of agile approach is that it is suitable for small size projects with limited team size. Hence, it cannot be adopted for large size projects. We claim that this approach can be used for large size projects if traditional requirements engineering approach is combined with agile manifesto. In fact, the combination of traditional requirements engineering process and agile manifesto can also help resolve a large number of problems exist in agile development methodologies. As in software development the most important thing is to know the clear customer’s requirements and also through modeling (data modeling, functional modeling, behavior modeling). Using UML we are able to build efficient system starting from scratch towards the desired goal. Through UML we start from abstract model and develop the required system through going in details with different UML diagrams. Each UML diagram serves different goal towards implementing a whole project.
Continuity in the development of seamless mobility: An approach for a system-...IRJET Journal
This document discusses approaches to enable continuity and traceability in interdisciplinary product development for systems-of-systems (SoS) environments. It addresses the challenges of developing complex, interconnected systems where independent teams use various tools and methods.
The document presents three approaches: 1) A classification of four dimensions of continuity in product engineering to address consistency across levels of detail, temporal changes, different projects, and partial models. 2) The KaRDF and Vitruvius methods for consistently modeling heterogeneous development artifacts using semantic technologies. 3) A methodology based on SPALTEN problem-solving processes to support management of changes in distributed development.
Integrating these approaches would support distributed development of seamless mobility systems with high consistency
towards a model-based framework for development of engineering1 (1)Jinzhi Lu
This document proposes a model-based framework for developing engineering tool-chains that support cyber-physical systems modeling and simulation. It presents the SPIT framework, which takes a systems approach to support MBSE tool-chain development. The framework addresses functionalities of MBSE tool-chains from a systems engineering perspective. Demo tool-chains are developed to support co-simulation of CPS using MBSE. Future work includes extending tool integration languages to formalize co-simulation tool-chains and analyzing the functional dynamics of MBSE enterprise transitioning.
This document discusses the design of a hospital management system project for a university course. It includes an introduction to the project motivation and requirements. It also includes UML diagrams - use case, entity relationship, activity, class, and sequence diagrams - to design the solution for the hospital management system. The diagrams identify the key entities, activities, classes, and sequence of interactions involved in the system.
This document proposes applying kanban scheduling techniques to systems engineering activities in rapid response environments. It describes how systems engineering could be modeled as a set of continuous and taskable services that flow through a kanban scheduling system. This approach aims to improve integration and use of scarce SE resources, provide flexibility and predictability, enable visibility and coordination across projects, and reduce governance overhead. The document defines key aspects of a kanban scheduling system for SE, including work items, activities, resources, queues, and flow metrics. It argues this approach could better support SE in rapid response compared to traditional methods.
1) How will managers of a monopolistically competitive firm de.docxLynellBull52
1) How will managers of a monopolistically competitive firm decide on the optimal level of production? Elucidate.
2) Describe market forces that come into play in the short run if a monopolistically competitive firm is making a positive economic profit. How would this compare to the typical long-run equilibrium? Explain.
3) True, False Uncertain and Explain: “Happy hour” pricing by bars and restaurants (i.e., lower prices at the close of the business day) is not a logical outcome. The increase in demand for food and beverages around 5:00 p.m. should actually result in higher prices.
4) Mary and Sam are the only two growers who provide organically grown corn to a local grocery store. They know that if they cooperated and produced less corn, they could raise the price of the corn. If they work independently, they will each earn $100. If they decide to work together and both lower their output, they can each earn $150. If one person lowers output and the other does not, the person who lowers output will earn $0 and the other person will capture the entire market and will earn $200. {The table below represents the choices available to Mary and Sam.}
*What is the best choice for Sam if he is sure that Mary will cooperate?
*If Mary thinks Sam will cheat, what should Mary do and why?
*What is the prisoner’s dilemma result?
Mary
A
B
A
($100, $100)
($200, $0)
Sam
B
($0, $200)
($150, $150)
Note: A = Work independently; B = Cooperate and Lower Output. Each table entry lists Sam's earnings first, and Mary's earnings second.
Optimising agile development practices
for the maintenance operation: nine heuristics
Lise Tordrup Heeager & Jeremy Rose
# Springer Science+Business Media New York 2014
Abstract Agile methods are widely used and successful in many development situations and
beginning to attract attention amongst the software maintenance community – both researchers
and practitioners. However, it should not be assumed that implementing a well-known agile
method for a maintenance department is therefore a trivial endeavour - the maintenance operation
differs in some, important respects from development work. Classical accounts of software
maintenance emphasise more traditional software engineering processes, whereas recent re-
search accounts of agile maintenance efforts uncritically focus on benefits. In an action research
project at Aveva in Denmark we assisted with the optimisation of SCRUM, tailoring the standard
process to the immediate needs of the developers. We draw on both theoretical and empirical
learning to formulate seven heuristics for maintenance practitioners wishing to go agile.
Keywords Software maintenance . Agile methods . SCRUM . Action research
1 Introduction
Software developers have for more than a decade been concerned with a change of perspective in
favour of the lightweight flexible approaches incorporated in agile.
Lecture in the iMinds-SMIT VUB Service Science Lecture SeriesGeert Poels
The document discusses conceptualizing service science through conceptual modeling. It aims to facilitate interdisciplinary research and achieve a shared understanding of service concepts. The problem is that service research is fragmented without a clear understanding of the domain. The solution proposed is to build a conceptual model that clarifies concepts using descriptive service theories and identifies relationships between concepts from different theories. This conceptual framework would help analyze the domain and provide common definitions without fully integrating existing theories.
This document discusses a nursing homework assignment that involves analyzing a healthcare information technology (HIT) project. It describes a hypothetical example of a nurse leader proposing a new alarm and monitoring system for a children's hospital wing that was initially rejected due to budget constraints. After a child was abducted, the new system was approved. The key takeaway is the importance of getting stakeholder and decision maker support for HIT projects. Students are asked to discuss a real HIT project from their organization and how stakeholders helped move it forward.
Overview Of System Development Life Cycle (SDLC)Nicole Savoie
The document discusses the system development life cycle (SDLC), which is a process used for developing systems from planning through implementation. It contains four main steps: analysis, planning, design, and implementation. During analysis, data flow diagrams are used to model the system's processes. Consistency between context and lower-level data flow diagrams is important for an easy-to-follow process model. SDLC is also used to determine how an information system can support business needs by designing, building, and delivering the system to users through the analysis, design, implementation, and testing phases. Procedure models created during analysis help define requirements graphically. Reliability of the process model is key to improving later SDLC stages.
The document provides an overview of IT project management. It discusses systems development, understanding business needs through business process modeling, the roles of various participants in system development including users and specialists. It also covers the systems analysis and design process, guidelines for systems development including developing accurate cost and benefit information, and maintaining flexibility. Project management tasks like defining, planning, scheduling, monitoring and controlling, and reporting are also summarized.
This is my College Project Documentation on Hospital Management System. Which includes mainly Problem Definition, Existing System, Proposed System, Requirement Analysis, Scope of the System, Feasibility Study, Hardware & Software Requirement, ER Diagram, DFD Diagram, Data Dictionary for Project, Sample Output Screenshots, Conclusion
An Approach of Improve Efficiencies through DevOps AdoptionIRJET Journal
This document discusses adopting DevOps practices to improve organizational efficiencies. It begins with an abstract discussing how organizations waste resources and how DevOps aims to address this through lean principles and continuous feedback. It then discusses the history and concepts of DevOps, proposing a DevOps adoption model. It outlines factors that affect IT performance and cultural transformation. The document also describes the research design of a study conducted through interviews with DevOps professionals. It identifies four main challenges to DevOps adoption: lack of awareness, lack of support, implementing technologies, and adapting processes. The analysis focuses on the lack of awareness challenge, noting confusion around DevOps definitions and resistance to "buzzwords".
Similar to A Case for Declarative Process Modelling - Slides on Adaptive Case Managment from AdaptiveCM 2014 workshop (20)
B2B payments are rapidly changing. Find out the 5 key questions you need to be asking yourself to be sure you are mastering B2B payments today. Learn more at www.BlueSnap.com.
IMPACT Silver is a pure silver zinc producer with over $260 million in revenue since 2008 and a large 100% owned 210km Mexico land package - 2024 catalysts includes new 14% grade zinc Plomosas mine and 20,000m of fully funded exploration drilling.
How MJ Global Leads the Packaging Industry.pdfMJ Global
MJ Global's success in staying ahead of the curve in the packaging industry is a testament to its dedication to innovation, sustainability, and customer-centricity. By embracing technological advancements, leading in eco-friendly solutions, collaborating with industry leaders, and adapting to evolving consumer preferences, MJ Global continues to set new standards in the packaging sector.
At Techbox Square, in Singapore, we're not just creative web designers and developers, we're the driving force behind your brand identity. Contact us today.
How to Implement a Strategy: Transform Your Strategy with BSC Designer's Comp...Aleksey Savkin
The Strategy Implementation System offers a structured approach to translating stakeholder needs into actionable strategies using high-level and low-level scorecards. It involves stakeholder analysis, strategy decomposition, adoption of strategic frameworks like Balanced Scorecard or OKR, and alignment of goals, initiatives, and KPIs.
Key Components:
- Stakeholder Analysis
- Strategy Decomposition
- Adoption of Business Frameworks
- Goal Setting
- Initiatives and Action Plans
- KPIs and Performance Metrics
- Learning and Adaptation
- Alignment and Cascading of Scorecards
Benefits:
- Systematic strategy formulation and execution.
- Framework flexibility and automation.
- Enhanced alignment and strategic focus across the organization.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
❼❷⓿❺❻❷❽❷❼❽ Dpboss Matka Result Satta Matka Guessing Satta Fix jodi Kalyan Final ank Satta Matka Dpbos Final ank Satta Matta Matka 143 Kalyan Matka Guessing Final Matka Final ank Today Matka 420 Satta Batta Satta 143 Kalyan Chart Main Bazar Chart vip Matka Guessing Dpboss 143 Guessing Kalyan night
[To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
This presentation is a curated compilation of PowerPoint diagrams and templates designed to illustrate 20 different digital transformation frameworks and models. These frameworks are based on recent industry trends and best practices, ensuring that the content remains relevant and up-to-date.
Key highlights include Microsoft's Digital Transformation Framework, which focuses on driving innovation and efficiency, and McKinsey's Ten Guiding Principles, which provide strategic insights for successful digital transformation. Additionally, Forrester's framework emphasizes enhancing customer experiences and modernizing IT infrastructure, while IDC's MaturityScape helps assess and develop organizational digital maturity. MIT's framework explores cutting-edge strategies for achieving digital success.
These materials are perfect for enhancing your business or classroom presentations, offering visual aids to supplement your insights. Please note that while comprehensive, these slides are intended as supplementary resources and may not be complete for standalone instructional purposes.
Frameworks/Models included:
Microsoft’s Digital Transformation Framework
McKinsey’s Ten Guiding Principles of Digital Transformation
Forrester’s Digital Transformation Framework
IDC’s Digital Transformation MaturityScape
MIT’s Digital Transformation Framework
Gartner’s Digital Transformation Framework
Accenture’s Digital Strategy & Enterprise Frameworks
Deloitte’s Digital Industrial Transformation Framework
Capgemini’s Digital Transformation Framework
PwC’s Digital Transformation Framework
Cisco’s Digital Transformation Framework
Cognizant’s Digital Transformation Framework
DXC Technology’s Digital Transformation Framework
The BCG Strategy Palette
McKinsey’s Digital Transformation Framework
Digital Transformation Compass
Four Levels of Digital Maturity
Design Thinking Framework
Business Model Canvas
Customer Journey Map
Understanding User Needs and Satisfying ThemAggregage
https://www.productmanagementtoday.com/frs/26903918/understanding-user-needs-and-satisfying-them
We know we want to create products which our customers find to be valuable. Whether we label it as customer-centric or product-led depends on how long we've been doing product management. There are three challenges we face when doing this. The obvious challenge is figuring out what our users need; the non-obvious challenges are in creating a shared understanding of those needs and in sensing if what we're doing is meeting those needs.
In this webinar, we won't focus on the research methods for discovering user-needs. We will focus on synthesis of the needs we discover, communication and alignment tools, and how we operationalize addressing those needs.
Industry expert Scott Sehlhorst will:
• Introduce a taxonomy for user goals with real world examples
• Present the Onion Diagram, a tool for contextualizing task-level goals
• Illustrate how customer journey maps capture activity-level and task-level goals
• Demonstrate the best approach to selection and prioritization of user-goals to address
• Highlight the crucial benchmarks, observable changes, in ensuring fulfillment of customer needs
Building Your Employer Brand with Social MediaLuanWise
Presented at The Global HR Summit, 6th June 2024
In this keynote, Luan Wise will provide invaluable insights to elevate your employer brand on social media platforms including LinkedIn, Facebook, Instagram, X (formerly Twitter) and TikTok. You'll learn how compelling content can authentically showcase your company culture, values, and employee experiences to support your talent acquisition and retention objectives. Additionally, you'll understand the power of employee advocacy to amplify reach and engagement – helping to position your organization as an employer of choice in today's competitive talent landscape.
How are Lilac French Bulldogs Beauty Charming the World and Capturing Hearts....Lacey Max
“After being the most listed dog breed in the United States for 31
years in a row, the Labrador Retriever has dropped to second place
in the American Kennel Club's annual survey of the country's most
popular canines. The French Bulldog is the new top dog in the
United States as of 2022. The stylish puppy has ascended the
rankings in rapid time despite having health concerns and limited
color choices.”
Industrial Tech SW: Category Renewal and CreationChristian Dahlen
Every industrial revolution has created a new set of categories and a new set of players.
Multiple new technologies have emerged, but Samsara and C3.ai are only two companies which have gone public so far.
Manufacturing startups constitute the largest pipeline share of unicorns and IPO candidates in the SF Bay Area, and software startups dominate in Germany.
The 10 Most Influential Leaders Guiding Corporate Evolution, 2024.pdfthesiliconleaders
In the recent edition, The 10 Most Influential Leaders Guiding Corporate Evolution, 2024, The Silicon Leaders magazine gladly features Dejan Štancer, President of the Global Chamber of Business Leaders (GCBL), along with other leaders.
How to Implement a Real Estate CRM SoftwareSalesTown
To implement a CRM for real estate, set clear goals, choose a CRM with key real estate features, and customize it to your needs. Migrate your data, train your team, and use automation to save time. Monitor performance, ensure data security, and use the CRM to enhance marketing. Regularly check its effectiveness to improve your business.
Event Report - SAP Sapphire 2024 Orlando - lots of innovation and old challengesHolger Mueller
Holger Mueller of Constellation Research shares his key takeaways from SAP's Sapphire confernece, held in Orlando, June 3rd till 5th 2024, in the Orange Convention Center.
Structural Design Process: Step-by-Step Guide for BuildingsChandresh Chudasama
The structural design process is explained: Follow our step-by-step guide to understand building design intricacies and ensure structural integrity. Learn how to build wonderful buildings with the help of our detailed information. Learn how to create structures with durability and reliability and also gain insights on ways of managing structures.
Dpboss Matka Guessing Satta Matta Matka Kalyan Chart Satta Matka
A Case for Declarative Process Modelling - Slides on Adaptive Case Managment from AdaptiveCM 2014 workshop
1. September 1, 2014
A Case for Declarative Process Modelling:
Agile Development of a Grant Application System
IT
UNIVERSITY
OF
COPENHAGEN
Morten Marquard &
Thomas Hildebrandt
joint work with
Tijs Slaats, & Søren Debois
2. 2012-: EU COST Action IC1201 - Behavioural Types
for Reliable Large-Scale Software Sy stems
IT
UNIVERSITY
OF
COPENHAGEN
CSCW in Healthcare, University of Copenhagen, 27 June, 2014
Foundational Process Models &
Theoretical Computer Science
PhD, Aarhus University, 2000
a’ b’
BRICS Basic Research in Computer Science
2
CSCW d
c’
Categorical Models for Concurrency:
Independence, Fairness and Dataflow
Thomas Troels Hildebrandt
BRICS Dissertation Series DS-00-1
ISSN 1396-7002 February 2000
2000-2003: Head of Study Program on
Internet Technology
2012: Head of Process & System Models Group
Thomas Hildebrandt - hilde@itu.dk
2010: Case Studies of
Best Practice
Workflow and
Workflow in Practice
(Innovation Network)
A
single
slide
about
me
2
2
1
b
b
d’
a’ b’
N’
1
2 1
BRICS DS-00-1 T. T. Hildebrandt: Categorical Models for Concurrency: Independence, Fairness and Dataflow
labelled nets N and N′ that are HP bisimilar but not HHP bisimilar. The
by the actions {a, b, c, d} as the names suggest, e.g. a1 is labelled by
notion of bisimulation with the requirement, that any two related runs
causal dependency between actions, that is the same history. Heredi-tary
imposes a backtracking condition: for any two related runs, the runs
backtracking a pair of related transitions, must be related, too. We allow back-tracking
the order which is laid down by the related runs; as long as no other
a particular transition, it can be backtracked. Thereby it is ensured
not dependent on the order in which independent actions are linearized.
we expect from a bisimulation for concurrency.
the standard example from [95] of two systems that are plain but not
bisimilar. Both systems have an a-action (b-action) that can be followed by
d-action) or an independent (not competing on any places) b-action
have an a-action (a b-action) which can be followed by an independent
Consequently, the two systems are HP bisimilar. However, observe that
find, the matching of the parallel a- and b-transitions depends on the
appear in the runs to match. So, the systems are not hereditary HP
the c transition dictates that we have to match a1 to a′1, and so a1.b1
backtracking condition requires that and b′are related. But from this
Interdisciplinary research
projects with industry
www.itu.dk/research/models
2007-11: Computer Supported
Mobile Adaptive Business
Processes (Foundations of
Technology and Production)
2008-2012: Trustworthy
Pervasive Healthcare
Processes (Strategic Research)
2011-2014: Flexible Cross-organizational
Case
2004-2011: Director of FIRST PhD School Management (Industrial PhD)
2014-17: Computational Artifacts: Design Oriented Theory
of Computational Artifacts in Cooperati ve Work Practices
(Velux, www.COMPART.ku.dk)
3. Agile Development of a Grant Application System September 1st, 2014
IT
Supported
Flexible
Processes
Process 3
IT
UNIVERSITY
OF
COPENHAGEN
In this article, we showed that PAISs support operational However, the focus is not on data but on process-related information ordering of activities). Process mining is also related to monitoring intelligence [41].
8 Conclusion
Process-aware information systems (PAISs) follow a characteristic 13 shows the four phases of such a life-cycle [7]. In the processes are (re)designed. In the configuration phase, designs by configuring a PAIS (e.g., a WFMS). After configuration, the starts where the operational business processes are executed using In the diagnosis phase, the operational processes are analyzed problems and to find things that can be improved. The focus of management (systems) is on the lower half of the life-cycle. is little support for the diagnosis phase. Moreover, support in limited to providing an editor while analysis and real design support Figure 13: PAIS life-cycle.
enactment
4. Agile Development of a Grant Application System September 1st, 2014
Let
us
look
at
the
process..
IT
UNIVERSITY
OF
COPENHAGEN
4
5. Agile Development of a Grant Application System September 1st, 2014
Let
us
look
at
the
process..
Only the “happy” path is described
IT
UNIVERSITY
OF
COPENHAGEN
4
6. Agile Development of a Grant Application System September 1st, 2014
Let
us
look
at
the
process..
Only the “happy” path is described
Other patient conditions or on-going treatments are
IT
UNIVERSITY
OF
COPENHAGEN
not taken into account
4
7. Agile Development of a Grant Application System September 1st, 2014
Let
us
look
at
the
process..
Only the “happy” path is described
Other patient conditions or on-going treatments are
IT
UNIVERSITY
OF
COPENHAGEN
not taken into account
Only describes how not why
4
8. Agile Development of a Grant Application System September 1st, 2014
Let
us
look
at
the
process..
Only the “happy” path is described
Other patient conditions or on-going treatments are
Typically introduces unnecessary dependencies
IT
UNIVERSITY
OF
COPENHAGEN
not taken into account
Only describes how not why
4
9. Agile Development of a Grant Application System September 1st, 2014
Model
all
routes?
IT
UNIVERSITY
OF
COPENHAGEN
5
10. Agile Development of a Grant Application System September 1st, 2014
Model
all
routes?
A complex “Spaghetti” diagram
- that still only describes how and not why
IT
UNIVERSITY
OF
COPENHAGEN
5
11. Agile Development of a Grant Application System September 1st, 2014
Model
all
routes?
A complex “Spaghetti” diagram
- that still only describes how and not why
and describes only the anticipated events
IT
UNIVERSITY
OF
COPENHAGEN
5
12. Agile Development of a Grant Application System September 1st, 2014
Flexibility
vs
Support
• Flexibility: ability to defer, change,
Already in 1983, researchers in
Computer Supported Cooperative
Work (CSCW) concluded that office
automation systems “do not deal
well with unanticipated
conditions” (Barber) & “were
automating a fiction” (Sheil)
and deviate
• support: provide analysis and
guidance
• unstructured: do what ever you
want, but get no support
• structured: support, but no
IT
UNIVERSITY
OF
COPENHAGEN
Motivation
Flexibility versus Support in workflows
Classical trade-off between flexibility and support1 flexibility
[1] W.M.P. van der Aalst et al. Declarative workflows: Balancing between flexibility and support
6
Sunday, March 14, 2010
Motivation
Flexibility versus Support in workflows
• Flexibility: ability to defer, change,
and deviate
• support: provide analysis and
guidance
• unstructured: do what ever you
want, but get no support
• structured: support, but no
Classical trade-off between flexibility and support1 flexibility
[1] W.M.P. van der Aalst et al. Declarative workflows: Balancing between flexibility and support
Sunday, March 14, 2010
[Schmidt & Bannon: Taking CSCW Seriously: Supporting Articulation Work, 1992]
“Good standards for business process
modelling are still missing and even today’s
WFMSs are too rigid”
Process-Aware Information Systems:
Design, Enactment, and Analysis
Wil M.P. van der Aalst
Department of Mathematics and Computer Science, Eindhoven University of P.O. Box 513, NL-5600 MB Eindhoven, w.m.p.v.d.aalst@tue.nl
Abstract. Process-aware information systems support operational business by combining advances in information technology with recent insights
from management science. Workflow management systems are typical examples
13. Agile Development of a Grant Application System September 1st, 2014
AdapKve
Case
Management
IT
UNIVERSITY
OF
COPENHAGEN
http://www.xpdl.org/nugen/WfMC p/adaptive-case-management/public.htm
“Adaptive Case Management (ACM) is information technology that
exposes structured and unstructured business information (business
data and content) and allows structured (business) and unstructured
(social) organizations to execute work (routine and emergent
processes) in a secure but transparent manner.”
7
14. Agile Development of a Grant Application System September 1st, 2014
AdapKve
Case
Management
IT
UNIVERSITY
OF
COPENHAGEN
http://www.xpdl.org/nugen/WfMC p/adaptive-case-management/public.htm
“Adaptive Case Management (ACM) is information technology that
exposes structured and unstructured business information (business
data and content) and allows structured (business) and unstructured
(social) organizations to execute work (routine and emergent
processes) in a secure but transparent manner.”
7
from BPM
15. Agile Development of a Grant Application System September 1st, 2014
AdapKve
Case
Management
IT
UNIVERSITY
OF
COPENHAGEN
http://www.xpdl.org/nugen/WfMC p/adaptive-case-management/public.htm
“Adaptive Case Management (ACM) is information technology that
exposes structured and unstructured business information (business
data and content) and allows structured (business) and unstructured
(social) organizations to execute work (routine and emergent
processes) in a secure but transparent manner.”
from BPM to ACM
7
(record)
16. Agile Development of a Grant Application System September 1st, 2014
AdapKve
Case
Management
IT
UNIVERSITY
OF
COPENHAGEN
http://www.xpdl.org/nugen/WfMC p/adaptive-case-management/public.htm
“Adaptive Case Management (ACM) is information technology that
exposes structured and unstructured business information (business
data and content) and allows structured (business) and unstructured
(social) organizations to execute work (routine and emergent
processes) in a secure but transparent manner.”
from BPM to ACM
7
(record)
Process
“snippets”
or
“fragments”
17. Agile Development of a Grant Application System September 1st, 2014
What
could
we
have
done?
IT
UNIVERSITY
OF
COPENHAGEN
8
18. Physician Check
Discharge
Patient
Agile Development of a Grant Application System September 1st, 2014
Events
&
Compliance
Rules
IT
UNIVERSITY
OF
COPENHAGEN
Surgery Report
9
Suite
Surgical discharge letter
for referring phys.
Surgical Ward Nurse Patient Record
Admit
Patient
Write
Discharge Letter
Create
Make
Lab Rest
Provide
Postsurgical Care
Transport
Patient to Ward
Perform
Surgery
Prepare
Patient
Send Patient
to Surgical Suite
Fig. 10.1 Prespecified process model Smed
Table 10.1 Examples of compliance rules for medical processes
c1 Before a surgery may be performed the patient must be prepared for it and be sent to
the surgical suite.
c2 After examining the patient a decision must be made. However, this must not be done
before the examination.
c3 After the examination, the patient must be informed about the risks of the (planned)
surgery.
c4 Before scheduling the surgery the patient has to be informed about anesthesia.
c5 If a surgery has not been scheduled it must not be performed.
c6 After a patient is discharged a discharge letter must be written.
19. Physician Check
Discharge
Patient
Agile Development of a Grant Application System September 1st, 2014
Events
&
Compliance
Rules
IT
UNIVERSITY
OF
COPENHAGEN
Surgery Report
10
Suite
Surgical discharge letter
for referring phys.
Surgical Ward Nurse Patient Record
Admit
Patient
Write
Discharge Letter
Create
Make
Lab Rest
Provide
Postsurgical Care
Transport
Patient to Ward
Perform
Surgery
Prepare
Patient
Send Patient
to Surgical Suite
Fig. 10.1 Prespecified process model Smed
Table 10.1 Examples of compliance rules for medical processes
c1 Before a surgery may be performed the patient must be prepared for it and be sent to
the surgical suite.
c2 After examining the patient a decision must be made. However, this must not be done
before the examination.
c3 After the examination, the patient must be informed about the risks of the (planned)
surgery.
c4 Before scheduling the surgery the patient has to be informed about anesthesia.
c5 If a surgery has not been scheduled it must not be performed.
c6 After a patient is discharged a discharge letter must be written.
20. Agile Development of a Grant Application System September 1st, 2014
SimulaKon
of
Process
IT
UNIVERSITY
OF
COPENHAGEN
11
21. Agile Development of a Grant Application System September 1st, 2014
SimulaKon
of
Process
IT
UNIVERSITY
OF
COPENHAGEN
12
22. Agile Development of a Grant Application System September 1st, 2014
SimulaKon
of
Process
IT
UNIVERSITY
OF
COPENHAGEN
13
23. Agile Development of a Grant Application System September 1st, 2014
SimulaKon
of
Process
IT
UNIVERSITY
OF
COPENHAGEN
14
24. Agile Development of a Grant Application System September 1st, 2014
SimulaKon
of
Process
IT
UNIVERSITY
OF
COPENHAGEN
15
25. Agile Development of a Grant Application System September 1st, 2014
SimulaKon
of
Process
IT
UNIVERSITY
OF
COPENHAGEN
16
26. Agile Development of a Grant Application System September 1st, 2014
Agile
to
IT
UNIVERSITY
OF
COPENHAGEN
Live
Development?
• When to involve the users ?
Requirement Specification
Implementation
Test
Configure
Go-Live
17
27. Agile Development of a Grant Application System September 1st, 2014
Agile
to
IT
UNIVERSITY
OF
COPENHAGEN
Live
Development?
• When to involve the users ?
Requirement Specification
Implementation
Test
Configure
Go-Live
17
Chaos
28. Agile Development of a Grant Application System September 1st, 2014
Agile
to
IT
UNIVERSITY
OF
COPENHAGEN
Live
Development?
• When to involve the users ?
Requirement Specification
Implementation
Test
Configure
Go-Live
17
Chaos
Depression
30. Agile Development of a Grant Application System September 1st, 2014
CollaboraKve
Modelling
IT
UNIVERSITY
OF
COPENHAGEN
19
31. Agile Development of a Grant Application System September 1st, 2014
AdapKve
Case
Management
&
DCR
• A
Case
for
Declara/ve
Process
Modelling:
Agile
Development
of
a
Grant
Applica/on
System
Flexibility is the default
with
S.
Debois,
M.
Marquard
&
T.
Slaats,
Adap/veCM,
2014,
Germany
• Collaborative Modeling & Execution
• Process Fragments can be added & removed
during simulation and execution
• Underlying formal model supports
verification (also after dynamic adaptation)
• Events can come from many sources
IT
UNIVERSITY
OF
COPENHAGEN
20
Towards
Trustworthy
Adap/ve
Case
Management
with
Dynamic
Condi/on
Response
Graphs
with
R.
R.
Mukkamala
&
T.
Slaats,
EDOC
2013,
Canada
Dynamic
Condi/on
Response
Graphs
for
Trustworthy
Adap/ve
Case
Management
with
R.
R.
Mukkamala,
M.
Marquard
&
T.
Slaats,
Adap/veCM,
2013,
Austria
Hierarchical
Declara/ve
Modelling
with
Sub-‐processes
and
Refinement
with
S.
Debois
&
T.
Slaats,
BPM,
2013,
The
Netherlands
32. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
IT
UNIVERSITY
OF
COPENHAGEN
21
33. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
IT
UNIVERSITY
OF
COPENHAGEN
21
34. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
• (Live) Expert end-user co-development
IT
UNIVERSITY
OF
COPENHAGEN
21
35. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
• (Live) Expert end-user co-development
• Communication - with and between users
IT
UNIVERSITY
OF
COPENHAGEN
21
36. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
• (Live) Expert end-user co-development
• Communication - with and between users
• Usability test (at run-time)
IT
UNIVERSITY
OF
COPENHAGEN
21
37. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
• (Live) Expert end-user co-development
• Communication - with and between users
• Usability test (at run-time)
• Process mining & uncertainty
IT
UNIVERSITY
OF
COPENHAGEN
21
38. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
• (Live) Expert end-user co-development
• Communication - with and between users
• Usability test (at run-time)
• Process mining & uncertainty
• Reliable & adaptable protocols for communication
IT
UNIVERSITY
OF
COPENHAGEN
21
with external systems
39. Agile Development of a Grant Application System September 1st, 2014
Ongoing
Research
• How can we make ACM useful in practice?
• (Live) Expert end-user co-development
• Communication - with and between users
• Usability test (at run-time)
• Process mining & uncertainty
• Reliable & adaptable protocols for communication
IT
UNIVERSITY
OF
COPENHAGEN
21
with external systems
• Case studies
40. Agile Development of a Grant Application System September 1st, 2014
Flow-‐chart
based
guidance....
IT
UNIVERSITY
OF
COPENHAGEN
22
41. Agile Development of a Grant Application System September 1st, 2014
Constraint
based
guidance
IT
UNIVERSITY
OF
COPENHAGEN
23