Skip to content

Commit f54de40

Browse files
authored
Merge pull request #63 from cyberskye/main
Add Constraints sub-section to Current State of MLOps
2 parents 2f0504e + 1750199 commit f54de40

File tree

1 file changed

+34
-3
lines changed

1 file changed

+34
-3
lines changed

roadmap/2024/MLOpsRoadmap2024.md

Lines changed: 34 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,14 +62,45 @@ In the next section, we will discuss the key drivers for MLOps and expand upon t
6262

6363
As we shall see, this can result in large conceptual gaps between what is involved in creating a viable proof of concept of a trained ML model on a Data Scientist’s laptop vs what it subsequently takes to be able to safely transition that asset into a commercial product in production environments. MLOps in practice is still on the early path towards maturity and it is likely that many practices that are commonly seen today, will be abandoned for better approaches over the next few years as teams get more exposure to the full scope of this problem domain.
6464

65-
Compounding this challenge, Machine Learning solutions tend to be decision-making systems rather than just data processing systems and thus will be required to be held accountable to much higher standards than those applied to the best quality software delivery projects. The bar for quality and governance processes is therefore very high, in many cases representing legal compliance processes mandated by regional legislation.
65+
<!-- Compounding this challenge, Machine Learning solutions tend to be decision-making systems rather than just data processing systems and thus will be required to be held accountable to much higher standards than those applied to the best quality software delivery projects. The bar for quality and governance processes is therefore very high, in many cases representing legal compliance processes mandated by regional legislation. -->
6666

67-
As these decision-making solutions increasingly displace human decision-makers in commerce and government, we encounter a new class of governance problems, collectively known as ‘Responsible AI’. These introduce a range of challenges around complex issues such as ethics, fairness and bias in ML models and often fall under government regulation requiring interpretability and explainability of models, often to a standard higher than that applied to human staff.
67+
<!-- As these decision-making solutions increasingly displace human decision-makers in commerce and government, we encounter a new class of governance problems, collectively known as ‘Responsible AI’. These introduce a range of challenges around complex issues such as ethics, fairness and bias in ML models and often fall under government regulation requiring interpretability and explainability of models, often to a standard higher than that applied to human staff. -->
6868

69-
As a result, it will be necessary for MLOps to develop in a manner that facilitates complex and sensitive governance processes that are of a standard appropriate to what is expected to become a highly regulated area.
69+
<!-- As a result, it will be necessary for MLOps to develop in a manner that facilitates complex and sensitive governance processes that are of a standard appropriate to what is expected to become a highly regulated area. -->
70+
71+
72+
### Constraints
73+
74+
<!-- NOTES: Constraints evolving in tandem with both the current state of MLOps outlined above, and the Driving forces listed below. -->
75+
76+
#### Machine Learning solutions as decision-making systems:
77+
78+
Machine Learning solutions tend to be decision-making systems, rather than just data processing systems, and thus are increasingly required to be held accountable to much higher standards than those applied to the best quality software delivery projects. The bar for quality and governance processes is therefore very high, in many cases representing legal compliance processes mandated by legislation spanning various levels of governmental and intergovernmental entities.
79+
80+
In addition, this is a space of rapidly changing legal compliance; therefore, in order to maintain deployment frequency and lead-time metrics, it will be necessary for MLOps to develop in a manner that facilitates automation of governance processes within release processes.
81+
82+
83+
#### Current and future governance and legal risks associated with producing decision-making systems:
84+
85+
As MLOps decision-making solutions increasingly displace human decision-makers in commerce and government, we encounter a new class of governance problems, collectively known as ‘Responsible AI’. These governance problems introduce a range of challenges around complex issues such as ethics, fairness and bias in ML models. They often fall under government regulation that requires interpretability and explainability of models, often to a standard higher than that applied to human staff.
86+
87+
It is therefore necessary for MLOps to develop in a manner that:
88+
89+
* Facilitates Responsible AI governance in areas such as ethics, fairness and bias.
90+
91+
* Facilitate existing and future complex governance processes mandated by legislation that potentially spans multiple levels of government, including intergovernmental entities.
92+
93+
#### Current and future governance and legal risks associated with security and data privacy:
94+
95+
Legal compliance processes exist at various levels of government and intergovernmental oversight. These processes may include ethics, fairness, bias, data privacy, and security. It is therefore necessary for MLOps to develop in a manner that:
96+
97+
* Facilitates both existing and expected future requirements of oversight, transparency audits, privacy, and security.
98+
99+
* Facilitates the complex array of both existing governance processes and potential future governance processes. This may require high level, complex, interpretability and explainability of models.
70100

71101
<br>
72102

103+
73104
## Drivers
74105

75106
<!--NOTES: Driving forces for the current snapshot of the roadmap.-->

0 commit comments

Comments
 (0)