Factors need for interactive forms by Adobe

Question

Hi All,
Could anyone tell me the factors that would influence the efforts estimation and what are steps involved in during the development of interactive forms with Adobe.
Regards,
Sid

Answer 1

Hi Sid,
there is no simple answer to this question.
Here are a few pointers on what to consider:
- Depending on what you want to do, the development environment and your familiarity with it. The choice is there (Web Dynpro for Java and ABAP, transaction SFP for print forms, Guided Procedures, Internal Service Request, printing in BI), but how well do you know your way around the environment? (Don't forget, the form is only one small aspect of your application.)
- Complexity of the form, and thus the need to script in Adobe LiveCycle Designer
- Experience of the forms developer (SAP-internally we have seen differences of several factors)
A simple interactive form can be done in 1-2 days including testing. With print forms, things become more complex with a medium-complexity form (a table, some scripting for business logic) taking about 7 days.
<b>Most importantly</b>, please take this to heart:
- A PDF form does not and cannot replace a full-fledged application. Most people don't realize that a form is in essence not a lot more than a user's view on (i.e. interface with) the system. The business logic is in the system, and should be limited in the form.
- Of an overall business process using a PDF form, at most 20% is spent on forms development. The bulk of the work is the application (usually involving some sort of workflow) surrounding the form.
Hope this helps,
Markus Meisl
SAP NetWeaver Product Management