This page describes documented MDriven capabilities that may be relevant when building applications that process personal data. It does not establish GDPR compliance.
GDPR compliance and MDriven
GDPR compliance depends on an organisation's processing activities, application design, operational procedures, and legal decisions. Do not treat use of MDriven as a GDPR certification or as evidence that an application meets GDPR requirements.
MDriven uses UML models as the blueprint for applications and can turn those models into executable software. Its documented features include business-logic and validation-rule automation, state-machine modeling, automatic UI and database generation, data management, and cloud integration and hosting.
Capabilities relevant to application design
| Design area | Documented MDriven capability | Example use |
|---|---|---|
| Define application data | MDriven automatically generates database structures from models and supports database synchronization as models evolve. | Model the classes and attributes used by an application, including any attributes that contain personal data. |
| Apply application rules | Business logic and validation rules can be integrated into models and are enforced when the system executes. | Define validation rules for the application's records and processes. |
| Model controlled workflows | State-machine modeling represents business workflows as states and transitions. | Model a record that progresses through defined handling states. |
| Prototype and test | MDriven supports rapid prototyping and live execution of models. | Test the model through prototyping and live execution. |
| Select an operating environment | MDriven documents cloud integration and hosting, including Azure and AWS. | Select and assess an environment appropriate for the organisation's requirements. |
Model and review application behavior
Use the model to define the application's data structures, business rules, and workflows.
- Identify the classes and attributes used to hold personal data.
- Define validation and business rules for the application's intended behavior.
- Use state machines where records must move through defined workflow stages.
- Test the model through prototyping and live execution.
- Review the deployed application's data handling, operational procedures, and environment against the organisation's requirements.
Organisational responsibilities
The documented MDriven capabilities do not define an organisation's GDPR programme. The organisation remains responsible for determining its processing purposes, the personal data used by its application, its operational procedures, and the controls required for its deployment.