Classic RE is considered too bureaucratic and unproductive. They are
addressed in the Agile Requirements Engineering (ARE). It integrates
classic RE with Agile development processes.
With the agile requirements engineering is often referred to as
bureaucratic and unproductive current RE to be broken
Current frameworks, libraries, tools and other technical issues
dominate the attention of software development. The real Achilles heel
is the requirements engineering (RE).
What good is technically ausgefeilste system if the customer wanted
it, only 30% and of this work, only 20% the same as required?
The classic RE is often seen as bureaucratic and unproductive. Are
popular agile approaches that address but the RE is limited. The agile
requirements engineering, briefly called ARE integrates the discipline
of requirements engineering in agile Entwicklungsprozess.Anzeige
Agile practices are booming. Extreme Programming, Scrum, Lean, Kanban
are the main issues of trade publications and conferences. Even if the
names of specific methods may change, the basic agile principles are
taking their place in the sustainable development system.
Choose the appropriate requirements for each RE technology in order
to describe them. Choose for each ...
Based on the requirements for the system, this means that after an
initial overview of the product features (Big Picture), this
prioritized by business value and high-priority requirements
immediately in detail and implemented, while low-priority requests are
absorbed only when the more valuable are already underway or very
developed are advanced.
Iterative and incremental
Altogether, a procedure is iterative and incremental steps to increase
transparency and project risks to be clarified early. Iterative means
that the project is divided into fixed periods, for example 4 weeks.
These are the iterations. Incremental means that the system was
developed at the end of an iteration by one increment further.
Agile approach
Agile approach also means to get early feedback. The customer of the
project will be confronted not only with requirement descriptions and
models with a request for feedback, but also receives an executable
increment of the system (Fig. 1). This feels a lot better for him,
allowing in-depth feedback that can be directly taken into account in
subsequent iterations. So overall the work is organized as a distinct
river, produced a more continuous flow of work and the productivity
gesteigert.Anzeige
Embedded Systems
The agile practices are not only suitable for software-only projects,
but also for embedded systems with hardware aspects. The hardware has
its own requirements to the process that must be explicitly
considered. It does not prevent, tackle agility.
A frequently cited stumbling block is the short iterations of example
only three weeks' duration, which will conclude with an executable
increment. The obstacle you can out of the way by the hardware design
iterations by running longer than the software development. Suitable
multiples to have such a regular integration points, ie 6 - or 9-week
iterations in the hardware-and three-week iterations in software
development.
Interestingly, the origin of agile software processes often in product
development and production with little regard for the software (Scrum,
Kanban).