Question

Answer

Enterprise Analyst works on the analysis abstraction level (domain). It will be of the greatest help for the problem formalization tasks, requirements capturing, before switching to system design.

Question

Why do we execute conceptual models?

Answer

Because it is the only way we can efficiently assure the analysis model quality and avoid the misunderstandings in this early project phase.
By executing our early models, we are actually “simulating” our future implemented system execution far before design, implementation and especially testing activities. During the analysis phase, it is still relatively “cheap” to find and fix any kind of error.

Question

How does Enterprise Analyst relate to source code of any programming language (C#, Java, VB, etc)?

Answer

Enterprise Analyst is absolutely independent of any platform or programming language, but its models make solid base for all types of target designs.

Question

How does Enterprise Analyst relate to UML?

Answer

Enterprise Analyst is based on the parts of UML’s meta-model related to classes and objects. It adds an additional semantics layer to be able to simulate model execution.

Question

How does Enterprise Analyst relate to MDA?

Answer

Enterprise Analyst has been built under basic MDA’s principles: platform independency and model oriented development. Enterprise Analyst shifts the developer’s focus from the source code to model.

Question

How does Enterprise Analyst relate to Object Orientation?

Answer

Enterprise Analyst is based on the concepts of class and object, so it naturally supports the object oriented paradigms, principles and its “way of thinking”.

Question

How does Enterprise Analyst relate to software architecture?

Answer

Because of its high abstraction level, Enterprise Analyst simply OBLIDGES the modeler to think of architecture aspects (of at least system’s domain) and it DOES NOT LET him to put his attention to a low level details before it becomes necessary.

Question

How does Enterprise Analyst impacts software development process?

Answer

Enterprise Analyst shifts a software development process’s center of gravity from implementation to analysis phase. This causes some efforts to be moved from the design/implementation/testing to early analysis.

Question

Does Enterprise Analyst generates some code to be able to execute the models?

Answer

No, it doesn’t. Enterprise Analyst has its own virtual machine, independent of any source code or platform, current or future one. However, the models are executed and validated can be easily transformed to a code.

Question

Why Enterprise Analyst does not permit some algorithmic details, calculations and operations to be executed?

Answer

Because Enterprise Analyst’s docus is on the architectonic elements of the model, its central concepts and their relationships. Resolving well enough those aspects, it is relatively easy to add some low level details.

Question

What are inconsistencies in Enterprise Analyst?

Answer

Inconsistencies are potential problems in the model’s execution. Those problems represent the reflections of the future code level problems. To detect and resolve them on the model level means to avoid them at some lower level (source code) and probably save great amount of efforts lately in the project.

Question

What are the future plans of Enterprise Analyst?

Answer

Some other UML diagram support will be included: sequence, state machines, use cases and OCL. We also plan to implement some design model generation in the future.