Agile development ultimately driven by the suitable state of
the art technique to ensure the holistic objective is met by simply aligning
with the Organization structure, goal and process. Agile development is very much associated with
requirement capturing using “User story” template for better alignment. But
there are many cases where requirement is being captured using Use Case
template, Story Point and Model driven Architecture.
Out of many ways of capturing requirement and defining
acceptance criteria, MDE / MDA proves to have advantage over other mechanism
due to below reasons.
1.
User Story – Aligns very well with business
requirement and business value, but technically bring lot of challenges to
handle change request, version control, and effort estimation. Effort estimation
using story point has been always ambiguous with a degree of accuracy varying
from +/- 30% and this figure in effect introduces 60 % risk to project timeline
and cost.
2.
Use Case – This technique is not very often used
with agile development using scrum, but there are many projects, which kick
start using Use Case document. This technique of requirement capture is subject
textual description of all functional, behavioral, non-functional and system
requirement, which always brings in understanding gap between the customer and
developer. And also this technique brings in all challenges such as change
management, version control and effort estimation.
3.
MDA / MDE – This technique has been used but
very rarely in Agile development for digital services and it proves to be much
more reliable and overcome many short coming identifying through user story and
use case template for requirement capturing. The major advantage was observed with
the viewing of business requirement, implementation, effort estimation and
version control.
MDE / MDA tools are
available today which transform the business model to database in SQL or NoSQL
format, generate specs for Soap, REST and many other technologies. The tools
are capable of capturing non-functional, behavioral and functional requirement and
combine them to Database, API and connectors for realization of business
requirement. This mechanism brings in lot of advantage over other technique.
However it is open debate and discussion.
Your feedback and comments on advantage and disadvantages of
various techniques are welcome.
No comments:
Post a Comment