Example of Business Case and my analysis of a web Project Requirement or Small web application: cost, benefit, process, roles, description, etc All data are ficticious

1. Web Project Description Example Stock Counter Document version: v1.3 IBM Confidential © 2006 IBM Corporation Author: Victor Pairazamán Date: 27 May 2009

2. Document owner and revision history V. 1.3 Quotation process removed for minimize the project. Added Manager in charge of the project Victor Pairazamán 10/27/06 V 1.2 Process Presentation Updated with WW sugestions Victor Pairazamán 10/25/06 V 1.1 Process Agreed between TeleSales webSales & enablement Teams Victor Pairazamán 10/19/06 V 1.0 Completed all slides for Stock Counter – Draft Version Victor Pairazamán 10/13/06 Change Description Author Date (mm/dd/yyyy) Revision History Victor Pairazaman Document Owner Name Role

3. e-solution project team ibm.com IBM Confidential © 2005 IBM Corporation Other project team members LA Websales mngr. Mariano Basso Web Local Manager Order Validation / Tracking Martha Lenis, Andrea J Diaz e-solution Teleweb ibm.com Web Sales MX Alejandra Soberón e-solution owner TBD. Ilaria Gorla Alejandra Soberon, Andrei Oman, TBD Name Dayly Content operation e-solution admin Support on the developing activities Supporter Validate the e-solution e-solution local approver Develop the e-solution and all the next steps e-solution modeller/s Responsibility Role Coordinator / Business Case / . LA Requirement Analyst and Prioritization Victor Pairazamán e-solution Requirement analyst Wireframe creation / Navigation / translation coordinator Matías Frank E-solution Wireframes and details Support and consultant in the project implementation Vania Zanella Global Business Developer Luciana Cardoso/ Name Project Lead, sizing, Status e-solution Project Manager Responsibility Role xSeries, GARS Brand ( if multi brand please list all of them identifying the most relevant ) Mexico ( pilot ) Country Stock Counter e-solution name

5. e-solution details (Ficticious Numbers) ** Open e-solutions have to be intended under very strict rules. In case of open e-solutions, it has to be clearly stated the number of users accessing the tool. If not stated the PDD will be rejected. Data Privacy review is carefully performed for open e-solutions. Open e-solutions might use a subset of WSE functions (no reports, no workflow,...). Mixed e-solutions (open for some users and pwd protected for others) must be implemented on separate DBs. N/A F2F revenue (M$) 15 BO documents estimation (including # records to be imported and/or # documents to be created) 60 % of current level ( less complaints ) Customer satisfaction contribution (% increase) 1M OI Contribution – Value (M$) 900 in a Q Number of expected transactions N/A N/A 350K N/A 900 30 % productiv. 3 hrs by transaction 4 3000 sessions in a Q (33 in a day ) Year 1 (mandatory) Year 2 (opt.) Optional : in case of usage of attachments please estimate MAX size of the total number of attachments BP revenue (M$) Tele revenue (M$) Web revenue (M$) Contract value (M$) OI Contribution – Number of leads generated Productivity increase (hours saved/month) Number of internal users ( PRIVATE ) Number of external users ( OPEN ) Year 3 (opt.) To be intercepted by a strategic corporate application To be intercepted by the WSE Websphere Project based (Tactical) Value Internet w3 Open** Closed (password protected) Mid November 2006 X X X X e-solution type (tick the most appropriate with an X) e-solution look & feel (tick the most appropriate with an X) Planned date of intercept Planned sunset date e-solution validity (tick the most appropriate with an X) Planned Live Date