Abstract
Model-Driven Engineering (MDE) can leverage domain engineering by offering support to complex variability and automatic implementation. However, little attention is given to the process of designing a domain architecture that is well suited to MDE techniques such as domain-specific languages and software transformations. A domain-specific software architecture is normally developed based on a few selected and important requirements, called architectural drivers. This paper presents three types of architectural drivers that can be used to build a software architecture that can take full advantage of the benefits of MDE. It also presents some patterns that can be used to help in the architectural design. An evaluation is also presented, showing that, when used together in a model-driven domain engineering project, these drivers and patterns can lead to some benefits in terms of reusability and complexity, but that in some cases there are drawbacks that need to be considered in a trade-off analysis.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
