From games to automotive, from web to embedded, ABSE models can handle it.
ABSE was created with the goal of laying out a foundation and support for all the processes involved in software engineering, as well as supporting all domains. So, ABSE is domain-agnostic by design.
ABSE is a methodology that supports the generic human problem-solving process, with a strong support for the software engineering discipline. This genericity gives developers the power to translate any of his/her specific views of any given domain into actionable, configurable metamodels.
ABSE has built-in genericity. The developer adds specificity. |
Cross-Domain Development?
Any imaginable domain can be modeled with ABSE. ABSE's genericity may however come with a cost: there could be approaches that are more suitable to model a specific domain than ABSE. However, today we see that domains cross over all the time. For instance:
- Automotive has built-in entertainment (a problem domain cross-over)
- Entertainment devices have web access (a problem-solution domain cross-over)
- Web applications use databases (a solution domain cross-over)
So, in a world where domains mix and cooperate most of the time, a development approach that supports any domain stands a better chance of evolution and long-term stability. |
