Database Reference
In-Depth Information
defined, but for most part, this was not adequate for customizing SAP quickly. For typical SAP
implementation teams, locating hundreds of these parameters correctly, completely, in a proper
sequence, and also in a timely manner was an intractable problem. Rather than a systematic
process, it was more of an experience in discovery, and the number of parameters to be identi-
fied and defined was simply overwhelming. To be on the safe side, typical project teams were
always on the defensive, invariably confirming and reconfirming every small aspect (although
this did not guarantee avoiding missing something) before proceeding further in the effort, and
all this simply added to a large time frame for completing the project. And, along the way, the
benefit of using the departmental store model of computerization was being lost completely (see
Chapter 2, Section 2.1.9 “CRM Represents the New Department Store Model of Implementing
Computerized Systems”).
The obvious remedy was to address the following two issues for achieving faster SAP
implementations:
1. Enable bridging the gap between the know-how of the to-be-mapped company processes
and/or requirements, on one hand, and the functionality provided by SAP that was configu-
rable in SAP through IMG, on the other
2. Quick transfer of know-how, expertise, and experience to newer implementation teams on
experience gained from numerous earlier implementations
As was seen earlier in this topic, repository-oriented systems like SAP is in continuation with the
tradition of computer-aided software engineering (CASE) environments. By the same token, the
later point truly corresponds to a computer-aided software implementation (CASI) environment,
which we consider next.
13.1.1.2 Computer-Aided Software Implementation (CASI)
AcceleratedSAP is a classic illustration of CASI environment that assists in speeding up the imple-
mentation effort based on expertise and experience gained from thousands of past SAP implemen-
tation projects and will continue the same in the future to improve its performance further. There
are two aspects to a CASI: one is CASE and the other is intelligent assistance.
Traditionally, implementing software application systems was constituted of familiar phases
like feasibility analysis, requirements analysis, effort estimation, project plan, design, develop-
ment, testing, integration, documentation, training, data uploads, interfaces, and, finally, cutover
to production. Right from the inception of the computerization activity, there have been efforts
toward employing computerized systems to aid in this effort at different stages. There has been
the usual profusion of software applications addressing the requirements of the various phases of
the Software Development Life Cycle (SDLC). Among these program generators, screen painters,
report painters, prototyping, and automated/assisted testing tools to assist in the software develop-
ment have been the most common ones. But there have been solutions for every phase in SDLC.
Many of these environments also embodied the corresponding methodologies for speeding up
the effort at respective phases of SDLC. Some of these environments or accelerators also became
generic that made them adaptable to any methodology deployed for a particular project rather
than being confined to specific methodologies including analysis, system design, data modeling,
and database design. The history of computerization in the last century has been littered with
numerous examples of such environments that, many a time, have followed differing standards
and have been incompatible with each other.
