Project Presentation eProcurement System. M.TECH S16- Team S03 Institute of Systems Science Table of Content Project Background Project Requirement User.

Slides:

Advertisements

Similar presentations

Content Management Portal Final Presentation Team SE16 – 7S 16 January, 2010.

Advertisements

Project Management with VIVA PPM Tool (Project Portfolio Management)

Calyxinfo Walking through Calyx Info The Organisation.

Requirements Specification and Management

Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.

Tutorial 9 Lanjun Zhou SEEM Outline Introduction to Assignment Phase 4 Transition to the new System (Chapter 13) – Making the transition to the.

GAI Proprietary Information

Lecture 13 Revision IMS Systems Analysis and Design.

Managing the Information Technology Resource Jerry N. Luftman

APPLICATION DEVELOPMENT BY SYED ADNAN ALI.

Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.

The Project Charter The most Important and Powerful Document to use for Initiating, Controlling and Preparing a Project in order to ensure Project Quality.

Chapter 3: The Project Management Process Groups

Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.

SAP Purchasing Prepared by Lavanya.M. Purchasing The R/3 System consists of a number of components that are completely integrated with one another. This.

S R S S ystem R equirements S pecification Specifying the Specifications.

IS&T Project Management: How to Engage the Customer September 27, 2005.

Project Management and Scheduling

 ]project-opem[ 2008, Title / Speaker / 1 ]project-open[ Open Source Enterprise Business Application Project Invoicing using ]project-open[ Version: 0.5.

© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.

 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”

S/W Project Management

Volunteer Management System Presented by Team SE18-08S.

Managing Projects using Oracle Project Management (PJT) & SPREADSHEETS Neeraj Garg Vice President, Client Services.

Requirements Walk-through

An EDI Testing Strategy Rosemary B. Abell Director, National HIPAA Practice Keane, Inc. HIPAA Summit IV April 24-26, 2002.

Master Data for SCM (1) Master Data in Demand Planning & Fulfillment Processes EGN 5346 Logistics Engineering (MSEM, Professional) Fall, 2013.

EProcurement. Transaction: ME41 Create RFQ Transaction: ME41 Assign Vendor The following button invites vendor to participate in the bid.

End HomeWelcome! The Software Development Process.

Project Management Practices Vesa Tenhunen University of Eastern Finland LUMA Centre

Volunteer Management System Presented by Team SE18-08S.

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

WEBINAR Presentation for Fleet Coordinators October 3, 2006.

Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.

Project Life Cycle.

Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.

Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.

Petals SAP Point of Sale System M.Tech. Team SE 15 (Saturday) Team Aug-2008.

© Mahindra Satyam 2009 Configuration Management QMS Training.

Petals SAP Point Of Sale System Third Project Presentation M.Tech Team SE 15 (Saturday) Team Jan-2009.

Agenda  Project Overview  Project Goal & Scope  Estimates  Deadline  Project Environment  Delivery Plan  Project Plan  Team Structure  Risk Analysis.

Project Background WWW Cargo Pte Ltd (Project Sponsor) is a privately owned company offering a one-stop total logistics package. At the moment, the.

Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.

Petals SAP Point Of Sale System Second Project Presentation M.Tech Team SE 15 (Saturday) Team Aug-2008.

SE 464: Industrial Information systems Most Images and inform. used in these slides are SAP © Not to be used for other than educational purposes Systems.

Petals SAP Point Of Sale System Second Project Presentation M.Tech Team SE 15 (Saturday) Team Aug-2008.

The information contained in this document is highly confidential and privileged. No part of this document may be copied or circulated without express.

Team SHARP February 10,  Sponsor ◦ Dr. Will Tracz  Faculty Coach ◦ Robert Kuehl  Members ◦ Samuel Goshen ◦ Leo Torbochkin ◦ Dan Edenhofer ◦ Dominic.

IS2210: Systems Analysis and Systems Design and Change Twitter:

Kansas State University Purchasing Contracts Management System (KSU – PCMS) Presentation 1 Date : 14 th October 2010 By Arthi Subramanian CIS 895 – MSE.

Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.

NEM201 Week 4 Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative.

1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.

T Project Review Muuntaja I1 Iteration

SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.

SCG PAPER: SAP By: Panidda P./ Narinthip W./ Pabhabwich S.

Purchase Order Creation Manually or automatically With or without reference to other documents Data Documents: Purchase requisition, Purchase order, RFQ,

ECE2799 Project Management Prof. Mazumder Prof. Bitar Updated 3/18/2016.

6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.

Project Based on fictitious Coffee Roasting CompanyCoffee Roasting Company Automatic Order Processing System – –Process “projected” Accept order from customer.

MM - Purchasing.

IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.

STOCK TRADING SIMULATION SYSTEM

Systems Implementation,

Description of Revision

An EDI Testing Strategy

Chapter 1 (pages 4-9); Overview of SDLC

Executive Project Kickoff

{Project Name} Organizational Chart, Roles and Responsibilities

Presentation transcript:

Project Presentation eProcurement System

M.TECH S16- Team S03 Institute of Systems Science Table of Content Project Background Project Requirement User Requirements Overview Team Members Development and Technical Strategy Architecture Overview Project Plan Quality Plans Effort and Cost Estimates Project Risks

M.TECH S16- Team S03 Institute of Systems Science Project Background Application : “Supplier Connect” – eProcurement System Project Sponsor : Fujitec Singapore Corpn. Ltd.

M.TECH S16- Team S03 Institute of Systems Science Project Requirement – Current Process Receive Deliveries/Shipping Advice Send Goods Rejection Info Warehouse Supplier PO Acknowledgement for new and revision PO Delivery Expediting Ack. Delivery Status New Delivery Schedules, Quantity and order Status Buyer Sending Documents - PO, Contracts, RFQ Delivery Expediting Informing about revision/ amendments in PO Create RFQ Receiving Acknowledgement from Supplier Information System – Purchase Status Sending info for expediting of orders and delivery schedules

M.TECH S16- Team S03 Institute of Systems Science User Requirements Overview Acceptance of PO Acknowledgement Expediting Delivery Maintain New Delivery Schedule Create RFQ PO Acknowledgement Purchase Contract Acknowledgement PO Amendment Acknowledgement Provide Promise Date for Expediting Delivery Maintain Delivery Advice Provide Quotation to RFQ Acknowledge Delivery Advice Monitor Goods Rejections Interface PO Interface Purchase Contract Interface Vendor Master Interface PO History Stock Inventory for Materials Materials Requirements Planning Details User Registration Assign Roles Change Password Reset Password Re-activate Users Create Admin Profile Process Transactions for Send Notifications

M.TECH S16- Team S03 Institute of Systems Science Team Members

M.TECH S16- Team S03 Institute of Systems Science Development and Technical Strategy Adopt proven RUP process for the development Prototype key functions to understand business processes and technical complexities Leverage on existing technologies already implemented in Fujitec (e.g. SAP) Emphasize on Quality Reviews at every stage of project.

M.TECH S16- Team S03 Institute of Systems Science Architecture Overview

M.TECH S16- Team S03 Institute of Systems Science Project Plan AnalysisRequirements Analysis InitiationDesignDeploymentSystem Development Quality Planning Use Case Survey Model Requirements Analysis Software Architecture Sequence Diagram Generation Object Specification Generation Source Code Generation Test Result Compilation Project Planning & Initiation (PPI) PERFORM Use Case Realisation Reporting Transition Strategy Prototyping Modelling RECORD Project Charter Project Plan Project Plan Quality Plan Quality Plan User Requirement Specification High-level Design Specification High-level Design Specification User Manual Project Report Project Signoff Project Signoff Detailed Design Specification Detailed Design Specification Test Documents Source Code Source Code Functional Specification Traceability Matrix Prototyping Study Report Prototyping Study Report Change Control Management Jan 2009 Jan 2010

M.TECH S16- Team S03 Institute of Systems Science Project Plan and Milestones (Phase I)

M.TECH S16- Team S03 Institute of Systems Science Project Plan and Milestones (Phase I) We are here

M.TECH S16- Team S03 Institute of Systems Science Project Plan and Milestones (Phase II) Early Prototyping

M.TECH S16- Team S03 Institute of Systems Science Project Plan and Milestones (Phase III) Test Planning and Code Development

M.TECH S16- Team S03 Institute of Systems Science Project Plan and Milestones (Phase III)

M.TECH S16- Team S03 Institute of Systems Science Quality Plan Plan Quality Plan Project Plan URS Team Organization Document Control Do Project Deliverables Systematic Filing of Documents Check Internal & External Reviews Effort Reports Progress Reports Unit Testing System Testing Acceptance Testing Act Corrective Actions Change Control

M.TECH S16- Team S03 Institute of Systems Science Progress Review The Project team meets regularly to:  Review of Project Schedule  Review Change Controls initiated  Review new Risks identified & Mitigation action  Review of Project deliverables  Review of Resource allocation Customer Meetings  Project team members are in contact with customer Requirements Gathering Change Control Schedule All meetings are recorded as Minutes of Meeting (MOM) and task will be assigned based on this.

M.TECH S16- Team S03 Institute of Systems Science Effort and Cost Estimates Programming LanguageC# Translation Factor25 Lines of Code = Translation Factor * FPC/1000 = 25 * * ( 1 + Breakage) Note: (i) % Breakage = 0; It is assumed requirements will not change (ii) Also the system will not reuse any existing software SLOC Development Effort =18.6 man-mths (2.3 man-mths/pax) Schedule =19.9 months Cost (Development) =$ 98.4K Cost (Hardware and Software) =$ 15K Total Cost =$ 113.4K

M.TECH S16- Team S03 Institute of Systems Science Effort Estimate ResourceMan-Months (Total) 1 st Audit (Man-Months) 2 nd Audit (Man-Months) 3 rd Audit (Man- Months) PM QA PL( Buyer Function) PL( Supplier Function ) PL( Warehouse Function) PL( Interface Function) PL( User and Notification Function) Programmer(P1) Programmer(P2) Total

M.TECH S16- Team S03 Institute of Systems Science Effort Estimate ResourceMan-Months (Total) 1 st Audit (Man-Months) Actual (Man-Months) % Diff PM QA PL( Buyer Function) PL( Supplier Function ) PL( Warehouse Function) PL( Interface Function) PL( User & Notification Function) Programmer(P1) Programmer(P2) Total

M.TECH S16- Team S03 Institute of Systems Science Project Risks Change in Business Processes affecting users  Fujitec users and its business partners i.e. suppliers, that may be resistant to the new processes as a result of eProcurement System. Complexity of Requirements  We may not have fully understood the business processes. Interfaces  Technical complexity in the development of interfaces between SAP Material Management Module and eProcurement System.

M.TECH S16- Team S03 Institute of Systems Science THANK YOU

M.TECH S16- Team S03 Institute of Systems Science Audit Findings Place a file directory for all documents at the beginning of the documentation file. Foler structure should have location to store testing results. Observation Logical modules may not be the best way to organize the system. Replace Work Instruction Form with Minutes of Meeting for work assignment. Update Ghant Chart every month. Record and document internal reviews.