gap analysis

[Former Member]

Hi,

pls help give me explanation for ,

what is gap analysis .

[Former Member]

Gap Analysis

The gap analysis is the analysis on what the differences between actual system are and what the customer want to develop

[Former Member]

GAP Analysis

A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.

In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.

Actual gap analysis is time consuming and it plays vital role in blue print stage.

Thanks

Jaya

reward, if its useful.

[Former Member]

While implementing the SAP to one company they use ASAP Methodologies to implement it has 5 steps .

1: project preparation .

2: Business blue Print .

3: Realization .

4: Final preparation .

5: Golive .

in Business blue print they give AS IS and TOBE that means what are the different requirements are to be made to reach the customer requirement that is called Gap analysys

[Former Member]

I'm not sure whether you're completely right. According to ASAP, Gap analysis focuses on identification of "any requirements that cannot be accomplished by standard content or the standard portal platform features". I.e., the gap consists between functionality of the Standard Software Package (e.g. SAP R/3 or ERP 2005) and original customer requirements. It doesn't mean the gap between AS IS and TO BE.

As already said, you can close a gap by individual software components (Development Requirements) or by a workaround. Gaps you can close by simple customizing are no gaps in the meaning of ASAP.

For further information see ASAP Roadmap DG 2.6.5 Development Requirements (especially 2.6.5.10 Gap Analysis).