Information Technology Reference
In-Depth Information
Model Reviewer reviews the defined use cases to ensure quality in the defined
requirements.
While RUP is an iterative development model, it is not considered an agile
method. Its variant AUP (Agile Unified Process) is used as an agile method for
software development. The commonality between both models is the dependence
on use cases as the method for capturing requirements and software design.
AUP uses the same four phases as in RUP, namely, the inception, elaboration,
construction and transition phases detailed above. It also emphasizes the iteration
of these four phases to realize all the user requirements in the proposed software
product.
AUP utilizes only seven workflows instead of nine workflows of RUP. These
are, modeling, implementation, test, deployment, configuration management,
project management, and environment. The requirements workflow is merged
into the modeling phase. Architecture definition part of the analysis and design
phase is merged into the modeling phase. The detailed design part of the analysis
and design phase is merged into the implementation phase.
AUP uses two types of software release, namely the development release and
the production release. The development release is for deployment on the target
system and is used for quality control and training the end users. The production
release is the software ready for putting the system into production.
The requirements in the AUP are established utilizing the use case method in
the modeling phase. Change management happens throughout the project. The
Business Analyst takes responsibility for defining the requirements and tracing
them through the software development.
15.9 Kanban
The Kanban technique has originated in the Japanese manufacturing plants of the
Toyota Corporation. Kanban in Japanese means ''signboard/signaling device''.
This technique was utilized to achieve JIT (Just In Time) manufacturing. In high-
volume manufacturing the practice before the onset of Kanban, was used to pro-
duce the maximum number of components at each of the workstations. This has
led to a pile up of components at a few workstations that had higher capacity than
the downstream workstations. Over a period of time, the pile up was significant,
locking up scarce capital. To reduce the pile up of components at workstations, the
Kanban technique was introduced. Kanban suggests that a new batch of compo-
nents should be started if and only if the previously produced components are
picked up by the downstream workstation. Kanban has changed the concept of
''pushing'' to ''pulling''.
''Pushing'' indicates pushing components from an upstream workstation to the
downstream workstation without considering whether the downstream workstation
is ready to receive them.
Search WWH ::
Custom Search