[system architecture] - what are MDA architecture, ADL and DSSA

MDA

MDA yes Model Driven Architecture Abbreviation , Also called model driven architecture , It originated from the idea of separating system specification and platform implementation ,MDA The main objectives of ：Portability（ Portability ）,Interoperability（ Interoperability ）,Reusability（ Reusability ）

First there is a platform independent model （PIM）, Use tools to map platform independent models to platform dependent models （PSM）, Then generate code from platform related models .

MDA And core model ：

• Platform independent model （PIM）： With a high level of abstraction , A model independent of any implementation technology
• Platform related models （PSM）： Tailored to a particular implementation technology , Let you use the implementation constructs available in this technology to describe the model of the system .PIM Will be transformed into one or more PSM
• Code Code： Use the source code to describe the system （ Statute ）, Every PSM Will be turned into code .

It is to be able to generate another set of programs or applications through a set of general programs

ADL

ADL Is a formal language , It is supported by the underlying semantic model , It provides concrete syntax and conceptual framework for conceptual architecture modeling of software systems .

ADL Three basic elements ：
artifacts ： A computing or data storage unit
Connections ： Architecture building blocks for modeling interactions between components and their rules governing these interactions
Architecture configuration ： Connection diagrams describing the components and connectors of the architecture

ADL For modeling , Some pseudo code

DSSA

DSSA(Domain Specific Software Architecture) Domain specific software architecture , It can be seen as a method or theory for developing product lines , The goal is to support the generation of multiple applications in a specific domain .
Ideal Characteristics ：

• A strictly defined problem domain or solution domain
• It's universal , So that it can be used for the development of a specific application in the field
• An abstraction of the appropriate program for the entire domain
• Have a fixed in this field 、 Typical reusable elements in the development process

Domain analysis mechanism ：

• Domain expert ： Experienced users 、 Engaged in system requirements analysis in this field 、 Design 、 Experienced software engineer in implementation and project management, etc . The main tasks of domain experts include providing knowledge about the requirements specification and implementation of systems in the domain .
• Domain analysts ： Domain analysts should be experienced system analysts with knowledge engineering background
• Domain designers ： Domain designers should be experienced software designers
• Domain implementer ： Field implementers should be experienced programmers

Three level model ：

---

Author's popular article recommends ：

Java Interview questions special column ：

《 from Java Interview questions look at the source code 》-LongAdder、LongAccumulator What is it ？
《 from Java Interview questions to see the source code 》-LinkedBlockingQueue Source code analysis
《 from Java Interview questions look at the source code 》- What concurrent queues are there ? And ConcurrentLinkedQueue Source code analysis
《 from Java Interview questions look at the source code 》- After watching Kafka performance optimization - Let you hang the interviewer
《 from Java Interview questions look at the source code 》- Why is the default thread pool blocking queue used LinkedBlockingQueue