Skip to Content
avatar image
Former Member


what is SDLC?what we do in it?what is the difference between ASAP methdology and SDLC?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

7 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 24, 2007 at 09:00 AM

    SDLC is Software Development Life Cycle which is used for any IT project.

    ASAP is SAP standard methodology for any SAP implementation project.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2007 at 09:02 AM


    Welcome to SDN the Software development life cycle which you follow in your orgn during the development of objects

    the steps of it are

    Fun Specs/Technical specs

    Fun spce review/tech spec Review


    code walk through

    unit testing




    ASAP methodology

    It would be helpful to go through the help document of ASAP Methodology.

    The following information may clarify some doubts/requirements you have.

    ASAP is Accelerated SAP, a methodology being used to complete an SAP implementation from End to End. Means, it has five phases and starts with

    1) Project Preparation : where the SAP consultants try to understand the AS IS business process of the industry for which implementation is being done. The hardware and software requirements are analysed. Infact all the basic preparation is done at this stage.

    2) Blue Print : After the AS IS study is made a TO BE process is evolved where in the client business is put in technically as to how it would be like in SAP. Blue is a binding between the implementor and Client. So, there is a sign off from the client on what is going to be done.

    3) Realization : Here the blue print is configured on the system. For some processes where SAP cannot do as it is,like when there is a difference between AS IS and TO BE called a GAP , we use developers(ABAP) . The functional guys give the functional spec based on which the ABAP'rs prepare technical specs and fulfill the object ( may be reports, user exits, enhancements and so on). Also the unit and integration testing is done here.

    4) Final Preparation : Here the enduser, core user training is completed on how he has to use the sap system. Master data uploads into the production server. In a way the system is getting for going live. And just before the go live date the data that needs to be put into sap is fixed and the remaining transactions of the business are recorded may be in a flat file or sometimes they are taken off so that upto date data in the production server is maintainted.

    5) Go Live and Support : Here finally the SAP system goes live and followed by some support as agreed upon in the service level agreements.

    you can go thru the following links

    Look at the below link

    <b>Reward points for useful Answers</b>



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2007 at 09:02 AM


    SDLC-Software Development LifeCycle.

    ASAP-Accelerated SAP.

    ASAP is a Methodology used to accelerate the implementation and it has different stages like

    Project Preparation

    Blue Print


    Final Preparation

    Go Live

    Please check this link for more details

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2007 at 09:04 AM


    System Development Life Cycle (SDLC) is the process of developing information systems through investigation, analysis, design, implementation and maintenance. SDLC is also known as information systems development or application development. SDLC is a systems approach to problem solving and is made up of several phases, each comprised of multiple steps:

    - The software concept - identifies and defines a need for the new system

    - A requirements analysis - analyzes the information needs of the end users

    - The architectural design - creates a blueprint for the design with the necessary specifications for the hardware, software, people and data resources

    - Coding and debugging - creates and programs the final system

    - System testing - evaluates the system's actual functionality in relation to expected or intended functionality

    For additional information, please check this links.,10801,71151,00.html


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2007 at 09:11 AM


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2007 at 09:12 AM

    Software Process

    ESS Quality Management System maps the Software Development Life Cycle phases of its projects through two process methodologies, namely:

    Classical Waterfall Methodology

    In the traditional Waterfall Methodology, the different phases are sequenced as in figure given below.






    Each of the phases has defined entry and exit criteria. Phase transition is triggered through management decision point by signing off phase-end deliverables. This methodology is best suited when the requirements are frozen upfront and they are well documented without any ambiguity.

    Iterative and Incremental Development Methodology

    Iterative and Incremental Development is a project development and management methodology, which allows for iterative project development and periodic progress measurement. This development methodology is derived from the well documented "helix / iterative" software engineering models.

    The entire project cycle is sub-divided into vertical segments, called "slices" wherein each slice is a deliverable. Each slice is developed in isolation using the “waterfall model”. Developers will analyze, design, code and test in a tight loop.

    Slice partitioning is done up-front, with the selection criteria being:

    • The slices are vertical i.e. they are not sub-systems.

    • Slices cut across as much of the functionality of the system as possible, being tangible sets of functionality that allow the user to get a look and feel.

    • Slices represent features. In case of schedule slippages, certain functionality releases may be differed. • Slices are executable and demonstrable.

    • A slice typically will take a few weeks to complete.

    This allows a tangible part of the project to be complete at the end of a slice. Complete testing is carried out in each iteration. The deliverables for each of the slices include an executable that meets the functionality, associated analysis and design documentation and test results.

    This methodology facilitates better risk management, better control on the project schedule through better monitoring and early corrective actions and better requirements management in an incremental mode.

    This methodology facilitates requirement evolution during the development as well as helps in managing larger projects.

    What is ASAP?

    ASAP: Accelerated Systems Application and Products in Data Processing

    All implementation projects have the the following phases:

    Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.

    As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.

    Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.

    To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you

    will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.

    Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.

    Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.

    Integration testing:

    Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.

    Go live preparation

    Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.

    Read ASAP methodology for more details you will understand better.


    ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.

    1. Project preperation - consists of identifying team members and developing strategy as how to go.

    2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.

    Consists of detailed documentaion

    3. Realization -The purpose of this phase is to implement all the business and process requirements based on the

    Business Blueprint.

    4 Final Preparation - The purpose of this phase is to complete testing, end-user training,

    5 Go Live and Support

    All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc



    <b>*reward for useful answers*</b>

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 23, 2014 at 06:07 AM

    ASAP is Based on the Document Follow .

    ASAP is specially using in SAP only.

    and compare to SDLC is using in other Technology in Like , Android , Ios , Java ..

    all are following this SDLC steps

    but in case of SAP we are Following only ASAP Methodology .

    I hope so this information Helpful for you.

    - Thnx

    Jatin Chauhan

    BI - BO Consultant

    Add comment
    10|10000 characters needed characters exceeded