<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Development Methodology: urgent in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210988#M765496</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this PDF document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://hosteddocs.ittoolbox.com/CM021805.pdf" target="test_blank"&gt;http://hosteddocs.ittoolbox.com/CM021805.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also check this too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a32662d9-0b01-0010-a588-ccd23adfbc39" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a32662d9-0b01-0010-a588-ccd23adfbc39&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Maha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 22 Dec 2007 23:25:01 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-22T23:25:01Z</dc:date>
    <item>
      <title>Development Methodology: urgent</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210987#M765495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is development methodology in sap development.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Dec 2007 15:56:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210987#M765495</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-22T15:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Development Methodology: urgent</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210988#M765496</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this PDF document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://hosteddocs.ittoolbox.com/CM021805.pdf" target="test_blank"&gt;http://hosteddocs.ittoolbox.com/CM021805.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also check this too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a32662d9-0b01-0010-a588-ccd23adfbc39" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a32662d9-0b01-0010-a588-ccd23adfbc39&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Maha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Dec 2007 23:25:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210988#M765496</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-22T23:25:01Z</dc:date>
    </item>
    <item>
      <title>Re: Development Methodology: urgent</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210989#M765497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Mahalakshmi. But I think my question is not answered completely.I want an answer to the quetion " what  development methodology u follow ". Will the be any name for the methodologies we follow.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Dec 2007 10:49:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210989#M765497</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-23T10:49:38Z</dc:date>
    </item>
    <item>
      <title>Re: Development Methodology: urgent</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210990#M765498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;ASAP methodology&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;AcceleratedSAP&lt;/STRONG&gt; (i.e. ASAP) methodology/roadmap is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. ASAP is widely used for SAP Business Suite (SAP ERP, SAP CRM, SAP SCM, SAP PLM, SAP SRM), SAP xApps, SAP NetWeaver and SAP Solutions for Mobile Business among many other solutions. The methodology covers the necessary project management, the configuration of business processes, testing and training aspects as well as technical implementation activities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to ensure central data access, the ASAP roadmap and tools have become a standard component in SAP Solution Manager (service.sap.com/solutionmanager) - the implementation and operations platform. In addition, ASAP is available for browsing and offline use on Service Market Place. From tool perspective, the SAP Solution Manager implementation function is the successor to the ASAP tools, hence some tools such as the Implementation Assistant, Q&amp;amp;Adb, and the Master Lists are replaced by Solution Manager Implementation Function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ASAP Roadmap&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Use&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The ASAP Roadmap provides the methodology for implementing and continuously optimizing&lt;/P&gt;&lt;P&gt;your SAP software. It divides the implementation process into five phases and offers detailed&lt;/P&gt;&lt;P&gt;Project Plans to assist you (in Microsoft Project format). The documentation stored at each level&lt;/P&gt;&lt;P&gt;of the Roadmap tree structure contains recommendations on implementing your SAP software&lt;/P&gt;&lt;P&gt;and links to helpful tools and accelerators.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Purpose&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you install the Implementation Assistant you can choose from several Roadmap types and&lt;/P&gt;&lt;P&gt;flavors. You can select one of the following flavors:&lt;/P&gt;&lt;P&gt;&amp;#149; R/3 - Implementation and Continuous Improvement&lt;/P&gt;&lt;P&gt;&amp;#149; APO - Advanced Planner &amp;amp; Optimizer&lt;/P&gt;&lt;P&gt;&amp;#149; BW - Business Information Warehouse&lt;/P&gt;&lt;P&gt;&amp;#149; B2B - Business to Business&lt;/P&gt;&lt;P&gt;&amp;#149; CRM - Customer Relationship Management&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Features&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Implementation of SAP software covers the following phases:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. Project Preparation&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In this phase you plan your project and lay the foundations for successful implementation. It&lt;/P&gt;&lt;P&gt;is at this stage that you make the strategic decisions crucial to your project:&lt;/P&gt;&lt;P&gt;&amp;amp;#8722; Define your project goals and objectives&lt;/P&gt;&lt;P&gt;&amp;amp;#8722; Clarify the scope of your implementation&lt;/P&gt;&lt;P&gt;&amp;amp;#8722; Define your project schedule, budget plan, and implementation sequence&lt;/P&gt;&lt;P&gt;&amp;amp;#8722; Establish the project organization and relevant committees and assign resources&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. Business Blueprint&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In this phase you create a blueprint, which documents your enterprise&amp;#146;s requirements and&lt;/P&gt;&lt;P&gt;establishes how your business processes and organizational structure are to be represented&lt;/P&gt;&lt;P&gt;in SAP software. You also refine the original project goals and objectives and revise the&lt;/P&gt;&lt;P&gt;overall project schedule in this phase.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Realization&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In this phase, you configure the requirements contained in the Business Blueprint. Baseline&lt;/P&gt;&lt;P&gt;configuration (major scope) is followed by final configuration (remaining scope), which can&lt;/P&gt;&lt;P&gt;consist of up to four cycles. Other key focal areas of this phase are conducting integration&lt;/P&gt;&lt;P&gt;tests and drawing up end user documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;4. Final Preparation&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In this phase you complete your preparations, including testing, end user training, system&lt;/P&gt;&lt;P&gt;management, and cutover activities. You also need to resolve all open issues in this phase.&lt;/P&gt;&lt;P&gt;At this stage you need to ensure that all the prerequisites for your system to go live have&lt;/P&gt;&lt;P&gt;been fulfilled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;5. Go Live &amp;amp; Support&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In this phase you move from a pre-production environment to the live system. The most&lt;/P&gt;&lt;P&gt;important elements include setting up production support, monitoring system transactions,&lt;/P&gt;&lt;P&gt;and optimizing overall system performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After your system has gone live, you can use a separate Roadmap with six work&lt;/P&gt;&lt;P&gt;packages, in order to optimize your R/3 System continuously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These &lt;STRONG&gt;phases&lt;/STRONG&gt; are the main milestones for implementing SAP software. Each phase has:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149; Work packages, which consist of activities, for which project teams are responsible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149; Activities, which consist of tasks, which are processed by one or more team members.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149; Tasks, which are carried out by a project team member. You can also access the How-to&lt;/P&gt;&lt;P&gt;sections and accelerators at this level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also check this AcceleratedSAP document.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/SVASAP.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/SVASAP.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Maha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Dec 2007 18:35:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210990#M765498</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-24T18:35:35Z</dc:date>
    </item>
    <item>
      <title>Re: Development Methodology: urgent</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210991#M765499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Development Methodology in SAP is called as ASAP Methodology:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It has the following procedure:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Project Preparation:&lt;/P&gt;&lt;P&gt;The first step in ASAP is Project Preparation. In this step the Functional Consultant will analyse the business process and define the system for SAP and will give the time line for the project. The Manpower required and the budgets are also considered in this step.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blue Print Preparation:&lt;/P&gt;&lt;P&gt;This is second step in ASAP Methodology. In this step the Project Preparation scenarios are finalised. A out line of the Project is given in this step.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Realisation:&lt;/P&gt;&lt;P&gt;In this step actual development is taken place. The ABAPer is responsible for this step.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Testing:&lt;/P&gt;&lt;P&gt;In this step the development done by the abaper is being tested. This is the area where the Unit Test Document is prepared (i.e. Positive Testing and Negative Testing).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GO live and Support:&lt;/P&gt;&lt;P&gt;This is the final stage where the project is running in the live environment. In this step the bugs if any that are found in the go live procedure are fixed and the project will be considered as support project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Dec 2007 04:33:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/development-methodology-urgent/m-p/3210991#M765499</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-25T04:33:13Z</dc:date>
    </item>
  </channel>
</rss>

