Database Reference
In-Depth Information
Many alternate strategies were devised like CASE and prototyping; however, none were able
to cross this basic hurdle. CASE provided more rigorous environment for requirement analy-
sis and design and automated to a large extent the subsequent development of code, testing,
and documentation efforts. The increased time spent on requirement definition with the
users was envisaged to lead to systems that were closer to the users' actual requirements.
On the other hand, prototyping was designed to address the requirement capture issue by
making the users directly participate in the process of defining the requirements. This was
mainly focused on the screen and reports design because these were the elements that could
be visualized directly by the user. But none of these strategies really resolved the problem.
Packages like ERP and CRM adopted a totally different approach by providing the most
comprehensive functionality within the package. Company personnel were only expected to
pick and choose whatever was required by the company actually using the package. Thus,
ERP/CRM packages effectively short-circuited the whole issue of capturing requirements.
The traditional project life cycle consisting of analysis, design, development, testing, and
implementation was transformed to the ERP/CRM implementation life cycle consisting
merely of requirement mapping, gap analysis, configuring and customizing, testing, and
implementation. Figure 2.2
shows a comparison of efforts expended during ERP/CRM and
the traditional Software Development life cycle.
This ultimately led to the ERP revolution that we are witnessing today.
Unlike the traditional systems, the CRM software implementations, involving the
implementations of preengineered ready-to-implement application modules, are charac-
terized by
FAP
Traditional
soft tone
development
Effort
Requirement
definition
Analysis
and
design
Development
Testing
and
implementation
Operations
and
maintenance
Time period
Figure 2.2 Comparison of efforts expended during eRP and the traditional software
development life cycle.
