Christian Dirschl | The Unified Governance Use Case - Using semantic web technologies for improved software development processes
Using seman*c web technologies for
improved so7ware development processes
The Uniﬁed Governance Use Case
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 644055.
This communication reflects only the author’s view and the Commission is not responsible for any use that may be made of the information it contains.
1. A methodology for combined so7ware and data engineering based on a meta-model describing the complete
soIware and data lifecycles, domain models and design inten<ons.
2. Tools to produce so7ware development models from the meta-model, including transforma<ons that generate
or conﬁgure soIware applica<ons
3. Tools to produce data development models from the meta-model, incorpora<ng data quality and integrity
constraints, data cura<on workﬂows, and data transforma<ons.
4. Methods to use the meta-model and tools as part of a uniﬁed so7ware and data engineering process, with an
emphasis on techniques for ensuring data quality and integrity, as well as soIware security and reliability.
5. Evidence that the ALIGNED methodology and tools produce greater development produc<vity and agility in
realis<c enterprise and web scale data intensive systems.
Overview Uniﬁed Governance
• Improve the governance of combined soIware and
data engineering projects
– Many diﬀerent systems are in use
– Diﬀerent jargon is used within and across systems
– Keeping informa<on in sync is <me consuming
• Create uniﬁed views of soIware and data
engineering tasks and projects
– Provide ability to access data across systems
– Find related informa<on and provide improved analy<cs capabili<es
– Feedback informa<on into individual systems
SoIware Development – Challenges
• Support Requirements engineering (Planning, Analysis &
– Provide feedback from customers (Maintenance)
– Inform about relevant informa<on from support team and previous
• Support Implementa<on Phase
– Reduce overhead of duplica<ng informa<on
– Inform about relevant informa<on from customers and planning
• Support Maintenance
– Show related informa<on that already may provide solu<ons
– Point to similar improvement sugges<ons
Overview DIO ontology
The purpose of the DIO
ontology is to model the
design intent or design
undertaking the design
of any ar<fact. A design
intent or design
ra<onale is an explicit
documenta<on of the
decisions made when
designing a system or
More informa<on can be found at: hap://purl.org/dio/