1 / 43

Petals SAP Point of Sale System

Petals SAP Point of Sale System. M.Tech. Team SE 15 (Saturday) Team 08 12-Apr-2008. Presentation Overview. Project Team Project Introduction Functional Requirements Efforts Estimation Schedule & Milestones Technical & Management Strategy Risk Analysis & Mitigation Plan Progress Report.

fisk
Download Presentation

Petals SAP Point of Sale System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Petals SAP Point of Sale System M.Tech.Team SE 15 (Saturday) Team 08 12-Apr-2008

  2. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  3. Project Team

  4. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  5. Project Introduction • The Project objective is to provide a Client based Sales system for Retail Sales that will integrate with the SAP Business One Accounting System for OBTech Asia Pacific Pte Ltd, Singapore • The current system is having the multiple problems and the client’s intention is to create a new system to take care of all those issues and provide the basic functionalities

  6. Project Introduction

  7. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  8. Functional Requirements - Scope • Development of POS system integrated with SAP B1 Accounting System • Automate the synchronization between HQ SAP B1 Database and client side Databases.

  9. Functional Requirements - 1

  10. Functional Requirements - 2

  11. Functional Requirements - 3 • Point of Sale • Store Manager • Data Transfer Service – Client • Data Transfer Service – Server

  12. FR – POS high level use cases

  13. Functional Requirements Point of Sale Maintain item Create transaction Make payment Suspend transaction Resume transaction

  14. FR - Store manager high level use cases

  15. Functional Requirements Store management View transaction Amend transaction Void entire transaction Make item requisition Generate reports Generate alert Create users

  16. FR – Data Transfer Services - 1

  17. FR - Data Transfer Services - 2

  18. FR - Data Transfer Services - 3 • Top Layer : Head Office SAP B1 • Generate and Upload text files to FTP • Push the Data from FTP Server to Client side • Download File(s) from FTP to HQ Temporary Database • Synchronize SBO Data with HO Database

  19. Data Transfer Services - 4 • Middle Layer FTP Site – Located at SAP Server • Acts a storage location for all the data files • All Stores and head office download and upload data files to this location

  20. Data Transfer Services - 5 • Bottom Layer - Outlet • Generate and Upload files to FTP • Synchronize Client Data from Downloaded SAP B1 Data

  21. Data Transfer Services - 6 • Synchronization and File Transfer Methods • Batch based replication • Text Files • FTP site acts an intermediate layer between the Head Office and different stores • 2 way replication • SBO  Head Office  Stores (Masters) • Stores  Head Office  SBO (Transactions) • Offline mode • Error logs and alerts

  22. Non-Functional Requirements • Performance • POS Response Time less than 5 seconds • Update SAP B1 Database before 9.00AM • Reliability • POS Front End 100% • Store Manager 95% • Data Transfer Service 100% • Data integrity • SAP B1 100% • Transaction Data 100% • Master Data 95%

  23. Non-Functional Requirements • Availability • No downtime between 9:00am-9:30pm • Security • FTP User ID and PWD • Login to POS • Login to Store Manager • Extensibility • Cater for business logic change • Phase 2 customization

  24. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  25. Effort Estimation - 1

  26. Effort Estimation - 2

  27. Effort Estimation - 3

  28. Function Point Diagram Vendor Data Product Item Data Customer Data Payment Data Applications Boundary Price List Header Data Store Data Price List Detail Data Reason Code Data Transaction Item Data Store Tender Data Transaction Payment Data Role data Invoice Header Data User Data Denomination Data POS Profile Data Payment Header Data Invoice Detail Data POS Terminal Data Transaction Data Store Manager Sales Person

  29. Function Point Count ITEM LOW AVERAGE HIGH TOTAL Total Degree of Influence External Input 2x3 =6 1x4 =4 54 1x6 =6 16 External Output 11x4 =44 9x5 =45 7x7 =49 138 Internal File 18x7 =126 0x10 = 0 0x15 = 0 126 Interface file 8x5 =40 0x7 = 0 0x10 = 0 40 External Inquiry 2x3 =6 0x4 = 0 0x6 = 0 6 Unadjusted Function Points = 326 Value Adjustment Factor Adjustment Factor = 0.65 + (0.01 x 54) 1.19 Adjusted Function Point Count Summary Adjusted FPC = 326* 1.19 = 388

  30. COSTAR Estimation

  31. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  32. Initial Planning Planned Milestones Project Kick off Req Modeling Analysis Modeling Prototyping Req Identification Design Modeling ISS Audit 1 URS Prototype Product UCRR (Analysis) UCRR (Req) Functional Spec Project & Quality Plan Design Modeling Executables Integration Programming Release candidate Testing UAT Detailed Design User Document Src code UAT Signoff ISS Audit 2 ISS Audit 3

  33. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  34. Project Strategies – Technical - 1 .NET Windows Forms Client/Server applications 4 executables Point of sale (Windows Forms) Store manager (Windows Forms) Data transfer client (Console) Data transfer server (Console)

  35. Project Strategies – Technical - 2 • Use Google code for Configuration Management • Prototype • User Interface • Master data download • Data transfer with SAP • Seek guidance from ISS faculty, Project Sponsor and Advisor

  36. Project Strategies – Management - 1 • Development Approach • Waterfall plus prototype development model • Rational Unified Process • Task Assignment • Assign task owners for each task. • Task owner to plan and implement task • Task owner to request for resources and for review meetings • Provide team members with visibility of all tasks using effort estimate table

  37. Project Strategies – Management - 2 • Begin detailed design after first iteration of prototyping • Divide team to 2 groups to do work in parallel • POS and Store Manager • Data transfer service • Involve user early in all key review phases • High level design • Prototype • Change user requirement

  38. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  39. Risk Analysis & Mitigation Plans • Risk 1 - Less Domain Knowledge - Mitigation Plan • Have an early substantive user interface design. • Familiarize with the existing similar systems and seek expert advice • Risk 2 - Scope too large - Mitigation Plan • Make functionality of phase 1 sufficient to use and realistic to implement. • Have a working system as early as possible

  40. Risk Analysis & Mitigation Plans • Risk 3 - Less Knowledge on SAP Tools - Mitigation Plan • Have a prototype to familiarise with SAP Tools • Risk 4 - Resource Availability - Mitigation Plan • Given Buffer Time during the project planning

  41. Presentation Overview • Project Team • Project Introduction • Functional Requirements • Efforts Estimation • Schedule & Milestones • Technical & Management Strategy • Risk Analysis & Mitigation Plan • Progress Report

  42. Initial Planning Progress Report – Current Status Project Kick off Req Modeling Analysis Modeling Req Identification ISS Audit 1 URS UCRR (Analysis) UCRR (Req) Functional Spec Project & Quality Plan Delayed by 2 days

  43. Q & A

More Related