Prototyping in SAP

[Former Member]

Can some body throw some light on Prototyping in general.

And also wrt SAP Prototyping.

For any XI consultant, what will be Prototyping Tasks.

Any links, Pdfs would help me.

Thank you,

-Naveen.

[Former Member]

Hi Naveen,

Prototyping is the process of building a model of a system. In terms of an information system, prototypes are employed to help system designers build an information system that intuitive and easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis phase of the systems development life cycle.

During the requirements determination portion of the systems analysis phase, system analysts gather information about the organization's current procedures and business processes related the proposed information system. In addition, they study the current information system, if there is one, and conduct user interviews and collect documentation. This helps the analysts develop an initial set of system requirements.

Prototyping can augment this process because it converts these basic, yet sometimes intangible, specifications into a tangible but limited working model of the desired information system. The user feedback gained from developing a physical system that the users can touch and see facilitates an evaluative response that the analyst can employ to modify existing requirements as well as developing new ones.

Prototyping comes in many forms - from low tech sketches or paper screens(Pictive) from which users and developers can paste controls and objects, to high tech operational systems using CASE (computer-aided software engineering) or fourth generation languages and everywhere in between. Many organizations use multiple prototyping tools. For example, some will use paper in the initial analysis to facilitate concrete user feedback and then later develop an operational prototype using fourth generation languages, such as Visual Basic, during the design stage.

And if your question is why we do prototyping....Here are the reasons for the same.

- Reduces development costs.

- Requires user involvement.

- Developers receive quantifiable user feedback.

- Facilitates system implementation since users know

what to expect.

- Results in higher user satisfaction.

- Exposes developers to potential future system

enhancements.

To know more about SAP Prototyping, Go through these links.

http://www.thespot4sap.com/Articles/Critical_Success_Factors.asp

http://www.sapdesignguild.org/resources/prototypes.asp

<a href="http://www.scmexpertonline.com/archive/Volume_04_(2006)/Issue_06_(July)/V4I6A1.cfm?session=">SAP’s Best Practices to Ease Prototyping and Implementation</a>

http://72.14.235.104/search?q=cache:EFrEkbwcQucJ:www.cbp.gov/linkhandler/cgov/toolbox/about/moderniz...SAPPrototyping&hl=en&gl=in&ct=clnk&cd=1

And also go through these links for the specific info you needed...

http://hosteddocs.ittoolbox.com/SAP%20Data%20Migration%20Using%20XI.pdf

http://www.ids-scheer.com/international/english/products/sap_netweaver_cooperation/31078

/people/marian.harris/blog/2005/06/23/need-to-get-a-sap-netweaver-component-implemented-quickly-try-sap-best-practices

http://www.devbistro.com/resumes/jlive1975

I hope it helps...

Regards,

Abhy