Getting a grip on the complexities of the development process requires a planning- and process model to be in place. For that, the common distinction is that between classic and agile process models.

Basics

Generally, a process model subdivides the development process into clearly assessable phases, limited both in terms of duration and content, and organizes the individual development steps. These steps are subsequently matched with methods and techniques. Throughout the entire development process, the goal is to bring related tasks and process models into a clear logical order. With its specifications, a process model serves as an organizational tool, which is later on adapted for a specific project through tailoring.

Classic process models

As “classic process models” we understand detailed approaches which provide the project members with precise working instructions. Classic process models differ from agile process models by being “static” and setting particularly specific guidelines as to when and how artifacts are to be created. The two best-known “classics” are probably the V-model XT, an agency-specific, process-oriented standard for planning and executing projects, e.g. system development, and RUP®. RUP® (Rational Unified Process) was developed by the company Rational and is a method-dependent process model that is closely connected to UML. First developed in 1997, the standard has since been continuously updated and improved.

RE in classic process models

Requirements Engineering (RE) is an integral part of every classic process model. Its goal is to define all requirements as completely as possible within the initial phase of a project. This is intended to provide the best-possible basis for all subsequent phases. Since this is difficult to achieve at times, revisions (Rücksprünge) are a constant possibility. Nevertheless, it remains an essential goal of the analysis phase. Consequently, the formulation of a set of high-quality requirements usually entails a great deal (Umfang) of elicitation, documentation and validation techniques of Requirements Engineering.

Implementation strategies

Whether you plan on implementing Requirements Engineering within a pre-existing process model or introducing an entirely new process model yourself, you will need an elaborate, comprehensive implementation strategy. This strategy must specify, among other things, the persons responsible to assist with and promote the change; the specific internal marketing plans; the techniques used to pass on new knowledge/methods to the employees; the ways in which the current implementation status is being supervised etc.; all the many small building blocks that need to be accounted for in order to successfully facilitate change within an organization. However, the most important thing is: an implementation project is not a sprint, but a marathon, which has to be endured!

Do you have any questions?

If you have any questions to the consulting and project work of SOPHIST, we are at your disposal: from the organization and preparation to implementation and follow-up. We will be happy to help you.

Your contact person:

vertrieb[at]sophist[dot]de

+49 (0)9 11 40 900 63

Your contact person:

vertrieb[at]sophist[dot]de

+49 (0)9 11 40 900 78

Your contact person:

vertrieb[at]sophist[dot]de

+49 (0)9 11 40 900 62

FROM OUR SOPHIST BLOG

(we feel sorry, but our BLOG posts are in German)

Neue Geschichten für Altbekanntes – unsere Firmenphilosophie

Seit einigen Monaten haben wir es uns zur Aufgabe gemacht, unsere Firmenphilosophie nicht nur zu leben, sondern durch unser Handeln auch mit Leben zu füllen. Dazu war es aber nötig, uns diese wieder präsenter zumachen. Wie genau wir das gemacht …

Scaled Agile Frameworks- Teil 4: More with LeSS.

Zwischen der Entstehung des Agilen Manifests 2001 und heute hat das Thema Agilität nichts an Aktualität eingebüßt. Ja, sogar noch zugenommen. Nach wie vor wird an dem Problem der Umsetzung dieses Manifests gearbeitet. Im Besonderen, wie ein agiles Konzept in einem größeren Maßstab verwirklicht werden kann. Bereits in der Frühphase 2001 …

Von SOPHIST Werbemitteln, die auf Festivals rocken

Ich liebe kreative, lustige und bunte Werbemittel. Gerne nehme ich sie mit, verwahren sie in Schubladen oder Kisten und freue mich immer wieder über meinen Werbemittelschatz. Doch außer Stifte und Blöcke nutze ich kaum etwas davon. Ich habe leider auch …

SOPHIST präsentiert: Den RE-Exit-Room

Welche Folgen können unzufriedene, jähzornige Stakeholder haben? Arme REler werden in einen Raum gesperrt und nur herausgelassen, wenn sie es schaffen, innerhalb einer Stunde alle Hinweise zusammenzutragen, um eine Spezifikation zu vervollständigen. Acht Besucher der SOPHIST DAYS 2019 befanden sich …

Gesunde SOPHISTen durch ihre Hilfe – Doris Dischner stellt sich vor

Gesundheit wird bei SOPHIST groß geschrieben. Ein Schritt um Nachhaltig für ein gesünderes und besseres Arbeitsklima war die Entscheidung für regelmäßige Sessions mit der Heilpraktikerin Doris Dischner. Wer das ist, und was genau sie tut, erfahren Sie in diesem Beitrag …

Copyright 2018

SOPHIST GmbH

Do you need more information?

Just give us a Call  and let us direct you to the right contact person?

Tel:      +49 (0)9 11 40 90 00

E-Mail: heureka[at]sophist[dot]de

Our office hours:                   Monday to Thursday:                              Friday:
                                              08:00 - 12:00 Uhr                                    08:00 - 12:00 Uhr
                                              13:00 - 18:00 Uhr                                    13:00 - 17:00 Uhr



Of course you are also welcome to reach various departments directly by e-mail:

All about Trainings:

training[at]sophist[dot]de

 



All about projects or consulting activities:

vertrieb[at]sophist[dot]de

 



All about our job offers and your career opportunities at SOPHIST:

DeineZukunft[at]sophist[dot]de


 

All about our events, marketing activities and publications:

marketing[at]sophist[dot]de


 

 

Legal disclaimer

Privacy Policy