EMPROSS Business Sectors
Business Development | more
Technology Development & Digitization | more
Green Development | more
Governmental Development | more
Strategic Development | more
Project Management and Innovation Services | more
Technocratic Enterprise Engineering | more
Research and Development | more



The ΕMPPROS (Evangelos Markopoulos Personalized PROject System) Matrix is based in a significantly logical interpretation of the ARIADNE process transformation and integration.  

It is actually an innovative practice developed by EMPROSS specifically to support the adjustability process on such fuzzy process model interpretations.

The EMPPROS MATRIX is the absolute mechanism for adjusting the ARIADNE process into every organizational or project environment and needs.   The MATRIX takes one level further down the results of the ASPAM assessment by integrating all the required processes and organization needs in order to perform successful project management on a technological investment or initiative.

The Matrix defines not only the structure of the adjusted methodology but primarily the way the processes work among themselves, especially the heterogynous ones, that come from the ARIADNE-SE and ARIADNE-PM methodologies.  The EMPPROS MATRIX clearly defines when and how a process model will be used independent from the others as well as when and how another process model will be used upon another process model.

The EMPPROS MATRIX  has two dimensions.

The Horizontal dimension (X-axis) presents the systems acquisition processes that have been selected for the specific methodology, while the Vertical dimension (Y-axis) presents the systems development processes ( figure 1 ).


Having placed on the Matrix the process models (acquisition and development) that have been selected for the methodology by either the organization itself or ASPAM, the Matrix is then filled up with the binary characters ‘0’ and ‘1’ as shown in figure 2 .

The ‘0’ indicates that the coordinates of the specific matrix cell does not create any relation between the two process models that compose this specific coordinate (Xi, Yi).  On the other hand the ‘1’ indicates that the coordinates of the specific matrix cell, which is a set of processes (Xj, Yj), have a specific impact among each other.

Figure 2 : Filling the EMPROSS MATRIX

 As the Matrix is completed with the ‘0’ and ‘1’ the methodology parameterization appears clearly.


If we select the process of System Analysis, which is the second development process in the vertical axis of the matrix, we can then define using a series of questions, the process relationship between this specific vertical process with all the horizontal ones, such as:

Do I (the project manager) need to perform Project Tracking (Project tracking is the fist process in the horizontal axis of the matrix) on the Analysis of the system?  

If the project is critical enough for example, and my answer is ‘YES’, that is I need to track down the progress of this development process, then  place an  ‘1’ in that specific coordinate (X Project Tracking, Y Systems Analysis), and I automatically define the relationship between those two processes as well as the way they will be managed.

If the project is not quite critical and not much time is available for detailed project tracking then the answer to the same question will be ‘NO’  and a ‘0’ will be placed in that specific coordinate indicating that Project Tracking will not be applied on the System Analysis process.

It should be mentioned at this point that the EMPPROSS Μatrix can be read by both dimensions giving a totally different meaning and methodological approach from each one.

If someone reads and interprets the Matrix elements of each coordinate from left to right, then the reading is based on the development processes which affects the elements of the X axis, the acquisition processes.  So we have a reading of the development processes on the aquisition processes.  This is an Engineering based reading.  Reading the matrix from the system developers point of view who wants to see which development processes will has pass through project management activities in order to assure that they are performed properly, and not to assure that the acquisition is done properly.  This is not a developer’s problem to solve. 

On the other hand, reading the matrix and interpreting the matrix elements from the top to the bottom, is a reading based on the processes of the Y axis which are the systems acquisition management processes.  That is the matrix is being read by the customer / buyer who defines which project management and acquisition management processes will be used on the development process in order to support the acquisition process and not the development process.  Figure 3 presents a graphical interpretation of this reading concept.

Giving a practical reading of the matrix of the previous figure the following methodological approach will derive if the reading is being done from left to right (reading as an engineer / developer):

The requirements management process needs to be tracked as well are contract execution process that has to be aligned with the requirements evolution or completion.

The systems analysis process needs to be tracked down but also to control and manage the changes that take place in the analysis and probably affect the contract of the project. 

In the coding phase only the code changes need to be managed, while the testing phase of the system needs to be tracked down and relate every tracking activity with the projects contractual responsibilities or changes that might be necessary.

On the other hand if the matrix is being read from the top to the bottom, the reading reflects the project management activities that a buyer project manager needs to take in managing the acquisition of a technology.  In this case the following methodological approach derives from this interpretation:

Tracking will be performed on all requirements management, systems analysis and systems testing activities.  Changes will be managed only if they come from the analysis and coding phases, while quality assurance will be performed on all development phases with no exception and conditions.  The contract will not be managed unless issues derive from the analysis phase or the testing phase.

Figure 3 : Interpretation of EMPROSS MATRIX based on Roles

In the case that a development process, for example, needs to be applied on all acquisition processes then the coordinate right after this specific process is marked with an ‘1’ which has the same meaning as placing an ‘1’ in each acquisition process related with the specific development process (figure 4).

That is … The ‘1’ that appears in the first row of the matrix under thequality assurance process, indicates that the quality assurance stages will be performed on every development process listed in the vertical (X) axis of the matrix.  On the other hand a ‘0’ in the first row of any acquisition process indicated that this process will be used selectively to specific development processes.

The same concept is used for the vertical processes of the matrix, the development processes.  In this case the requirements management process will be affected by all acquisition management processes, while the other development processes will be affected selectively by the acquisition processes (figure 5).

 Figure 4 : Column Filling Technique on the EMPROSS MATRIX

In general the use of the of the EMPPROS Matrix can not be considered as a difficult task if the organization has a clear understanding of the organizational constraints at the given time, and the project management goals for the specific project.  If this in not known, or difficult to be known, then the organization can use the ASPAMassessment methodology that will help towards the identification of the organizational constraints and project management goals.

Figure 5 : Row Filling Technique on the EMPROSS MATRIX

With this at hand, the proper development and acquisition processes can be selected initially and interpreted then in the most suitable way towards the generation of the specific methodology for the specific project.