Abstraction Methodology is a Model-based method of driving software-centered Projects, Programs and Enterprise IT. With the exception of writing actual software code and running manual tests, the work is performed by producing, discussing and investigating interconnected Models.
On the top level we separate Modelling Space into several Views.
Projects View will consist of individual Projects. The content of an individual Project Package will depend on a scope that range from changing hardly anything to changing practically everything. The Modelling conducted for a Project is also affected by availability of Enterprise level re-usable models, as the first Model-Driven Project may need to produce some of those re-usable artifacts. As a result no Model present in the Enterprise View can be ruled out.
Please refer to the Enterprise View for definitions of the individual models that can be present in an individual Project.
Enterprise View is a set of Enterprise-level models and re-usable artifacts. Enterprise View is usually owned by a lead Enterprise Architect. In addition to Enterprise-specific models, it contains artifacts originally created by individual Projects that are identified as reusable by the Enterprise Architects
Process View models the Project itself rather than the object of the Project's activities. The Modellers are expected to consult Process View for guidelines and definitions.