Hello Folks I got lot of enquires about Netweaver webdynpro development methodology and any documentation on netweaver coding guidelines, best practices;etc and sincerely felt that we must kick it of on from the head to start with. Hence as a series, I am planning to provide /share some of our best net weaver based application development guidelines in a series of blogs. My main series will include 1. Guidelines& practices for netweaver – webdynpro project estimation 2. Guidelines& practices for netweaver – webdynpro coding guidelines 3. Guidelines& practices on netweaver – webdynpro project management guidelines Assumptions 1. All the above revolve around webdynpro based application development using WAS, under JDI framework and usage of EP as just the launching Pad. 2. The guidelines are best suitable for 100 % custom development of SAP netweaver based webdynpro development 3. Use of SAP RFC Function modules as back end connectivity with SAP R/3 as the core at the back end 4. Use of JDI as the development infrastructure 5. It revolves around various teams viz business team, development team, basis team…etc 6. All the IView development is custom iviews and no usage of R3 transactions on EP. My earlier blog on list of activities talk only about the webdynpro activities. GUIDELINE SERIES - PART I Guidelines& practices for netweaver webdynpro project estimation Introduction Having been on netweaver consulting for so many years exclusively on the webdynpro based project developments, we have improved / scaled on our project estimations along with the various SPs that have been out on the netweaver framework. I still recollect the days that we did the first few projects with SP 9 /10 and 11 consecutively , where when we estimated the work with SP9, and we did the development in SP10 and did the testing in SP11, it was all fun some time back !. We did not have Either JDI or did not even use EP for our launches. Most of them are still running good with many thanks to SAP for new upgrades. Now coming to the reality and the dynamism of JDI and using EP as just the launch pad, though we had some re-working on our estimation, based on our lessons learnt, we progressively improved on our estimation guidelines that we will like to share to the SAP Forum. The estimation doesn’t talk about the methodology of estimation like how we need to derive at the numbers in terms of function points or based on the legacy estimation techniques on complexity determination. This guideline is for you to prepare the ground work and to do a bottom up approach. ESTIMATION KICK OFF ! Prepare your ground for the battle The following are some key pointers. list out all the tasks involved on the project list out all the work involved for different teams identify the dependencies on the task Please note that for the above steps, we will explain in detail on my next blogs. IDENTIFICATION OF TASKS Major list of tasks for webdynpro Development to be considered for estimation DOCUMENTATION 1)Technical specification - Webdynpro / EP / JDI 2)Program specification - Webdynpro / EP 3)Test cases - unit / code walkthrough 4)RFC mapping document 5)Help manual 6)System manual Under documentation, ensure you have a split up of your efforts on complexity. It is essential to capture the efforts required for the low level design documents that are prepared by the developers based on the business requirement and high level design document. Also it’s essential to have the buffer on the help manual and the system manual prepared by the netweaver team. Our best practices where to identify individually the different business process and have the specifications for each of them which must have the list of views, components…etc BASIS TASK1)Basis - Infrastructure setup 2)System Landscape Setup 3) JCO Connection set up 4) Theme - setup - WAS 5) Preparation & creation of tracks - JDI 6) Development component creation - SCs & DCs - JDI 7) Identification of dependencies and mapping of components (DCs) - JDI 😎 Security setup for DCs - JDI 9) Transport Setup - JDI 10)Portal Configuration - setup - EP 11) Portal administration - setup -EP 12) Portal - system administration - setup - EP 13) Portal - Content administration - setup - EP Generally as per our previous experience with our projects and a major lesson learnt, the efforts required from the basis team are not generally taken in to consideration during the estimation DEVELOPMENT 1)Development Configuration set up - NWDS 2)Creation of activity- NWDS 3)Data Model Creation - Model mapping - NWDS 4)Data Model Mapping - RFC - NWDS 5)Creation of Components ( Component Controllers , Custom Controllers) 6)Iview - Lay Out Design - UI Controls creation - NWDS 7)Context Mapping - NWDS 8)Validations (coding within the component) - NWDS 9)Iview - integration - NWDS 10) unit level testing - NWDS 11) Code walkthrough - NWDS 12) activity check in - NWDS 13) activity release - NWDS 14) activity transport - Dev / TST ; JDI EP Post development) 1) Portal / webdynpro - Theme creation - Mapping 2)Portal - Content creation - Menu and configuration 3)Portal - Iview Mapping 4)Portal - Ivew configuration 5)Portal - Iview validations set up 6)Portal - security mapping 7)Portal - work flow setup INTEGRATION 1)Integration for SSO - Single Sign On & security 2)Integration with - External website - HTTP Url parameters TESTING 1)Transport &Testing 2)Integration testing 3)System testing 4)Activity transport - DEV / TST / PRD - JDI 5)Acceptance testing Still to come, OPTIMAL RESOURCE IDENTIFICATION HOW TO MAP RESOURCE WITH THE TASK AND THE DEPENDABILITY? SIMPLE PROJECT PLAN SIMPLE ESTIMATION SHEET Do watch for the next consecutive blogs for the ground work for the estimation Based on the feedback and reviews, if required, we can dwell deeper in to each of the activities and identify the priority and complexity of them.
