While the V-model provides the necessary quality orientation, agile methods stand for calculated openness and flexibility. Agile development makes for a vital cooperation between automation specialist and customer – both parties benefit from their continuous interaction by gaining valuable additional knowledge about the application.

The right process model for the project

As an expert for the development of automation hardware and software, Eckelmann implements innovative projects in mechanical and plant engineering. Our engineers create functional, safe and long-term reliable automation solutions that meet customers’ requirements.

The spectrum of tasks ranges from small projects with limited functionality and safety requirements through many intermediate steps up to large-scale safety-related automation systems with complex functionalities. The appropriate development process model is selected according to the principles of suitability and efficiency. The applicable tandards and guidelines are, of course, taken into account in the selection.

The precise tailoring of the selected model to the features and needs of the project ensures both the compliance with all quality management requirements and the efficiency of the development. 

Classic and agile process models

Classic process models for development are divided into phases for which it is imperative that they are executed consecutively (waterfall model). In order to start any one phase, the result of the preceding phase needs to be documented and released. At the end of the project, the development result is available together with a standardised and consistent documentation.

One of the well-known classic process models is the V-model. It is required by a number of standards and makes the ideal assumption that all requirements, at the outset of the project, are capable of being completely defined through requirements analysis and can, then, be refined, implemented and tested, consecutively.

In the V-model, changing the requirements or the technical implementation during project execution involves considerable effort, especially in the later project phases. Results in the form of useful functions are only available towards the close of the project. Errors resulting from early phases and detected later make a substantial correction effort necessary.

In practice, however, making changes and supplements to requirements is as much a necessary reality as introducing amendments to the technical implementation and dividing developments into sub-functions to be implemented consecutively.

V-model-based development process
V-model-based development process

Generating values for our customers

Certified and quality-oriented development and production methods are by no means an end in themselves. Rather, they are the basis for the optimal realisation of the customer’s explicit and implicit requirements at the end of the development process, that is to say, the basis for the validity of results.

The principles of certified quality orientation are the subject of regular training courses. All staff commit themselves to a methodological, transparent, responsible, risk-conscious and targeted proceeding. Depending on the complexity of the task, the instruments needed are tailored in a cost-conscious and targeted manner.

Agile development based on Scrum, an iterative, incremental framework for project management (Copyright: Lakeworks, Sebastian Wallroth, Original und Lizenzen unter: commons.wikimedia.org/wiki/File:Scrum_process-de.svg)
Agile development based on Scrum, an iterative, incremental framework for project management (Copyright: Lakeworks, Sebastian Wallroth, Original und Lizenzen unter: commons.wikimedia.org/wiki/File:Scrum_process-de.svg)

Using process models appropriately, involving customers

In automation technology, neither the classic V-model nor agile models optimally meet the project-related demands placed on the process model. Eckelmann therefore combines the two process models with each other. Depending on the specific need, the focus can be shifted to either of them.

As a result, efficient and quality-oriented solutions are achieved which uncompromisingly meet the customer’s requirements and the applicable standards and guidelines.

While the V-model provides the necessary quality orientation, agile methods stand for calculated openness and flexibility. Agile development makes for a vital cooperation between automation specialist and customer – both parties benefit from their continuous interaction by gaining valuable additional knowledge about the application.

V-model and agile development combined
V-model and agile development combined

Contact

Dipl.-Wirtsch.-Ing. Philipp Eckelmann
Vorstand
Tel.: +49 611 7103-0


Cookies help us in providing our services. By using our services, you agree that we set cookies.

More