project presentation eprocurement system. m.tech s16- team s03 institute of systems science table of...

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


Project Background

Application :

“Supplier Connect” – eProcurement System

Project Sponsor :

Fujitec Singapore Corpn. Ltd.


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


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 Email

• Send Email Notifications


Team Members


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.


Architecture Overview


Project Plan

AnalysisRequirements Analysis

Initiation Design DeploymentSystem Development

Quality Planning

Use Case Survey Model

RequirementsAnalysis

SoftwareArchitecture

Sequence Diagram Generation

Object SpecificationGeneration

Source Code Generation

Test ResultCompilation

Project Planning & Initiation

(PPI)

PE

RF

OR

M

Use Case Realisation Reporting

Transition Strategy

PrototypingModelling

RE

CO

RD

Project CharterProject Charter

ProjectPlan

ProjectPlan

QualityPlan

QualityPlan

User Requirement Specification

User Requirement Specification

High-levelDesign

Specification

High-levelDesign

SpecificationUser ManualUser Manual

Project ReportProject Report

ProjectSignoffProjectSignoff

Detailed Design

Specification

Detailed Design

Specification

Test DocumentsTest Documents

SourceCode

SourceCode

Functional SpecificationFunctional

Specification

Traceability MatrixTraceability Matrix

PrototypingStudy ReportPrototyping

Study Report

Change Control ManagementChange Control Management

Jan 2009 Jan 2010


Project Plan and Milestones (Phase I)


Project Plan and Milestones (Phase I)

We are here


Project Plan and Milestones (Phase II)

Early Prototyping


Project Plan and Milestones (Phase III)

Test Planning and Code Development


Project Plan and Milestones (Phase III)


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


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.


Effort and Cost Estimates

Programming Language C#

Translation Factor 25

Lines of Code = Translation Factor * FPC/1000= 25 * 423.7 * ( 1 + Breakage)

Note: (i) % Breakage = 0; It is assumed requirements will not change(ii) Also the system will not reuse any existing software

10593 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


Effort EstimateResource Man-Months

(Total)

1st Audit(Man-Months)

2nd Audit(Man-Months)

3rd Audit(Man-Months)

PM 1.92 0.17 0.65 1.10

QA 1.58 0.13 0.55 0.91

PL( Buyer Function) 2.48 0.06 0.77 1.65

PL( Supplier Function ) 2.20 0.06 0.77 1.38

PL( Warehouse Function) 1.97 0.06 0.77 1.14

PL( Interface Function) 3.01 0.16 0.93 1.92

PL( User and Notification Function)

1.85 0.07 0.76 1.02

Programmer(P1) 1.99 0.03 0.67 1.28

Programmer(P2) 2.99 0.03 0.72 2.24

Total 19.99 0.76 6.59 12.64


Effort Estimate

Resource Man-Months(Total)

1st Audit(Man-Months)

Actual(Man-Months)

% Diff

PM 1.92 0.17 0.22 130

QA 1.58 0.13 0.20 154

PL( Buyer Function) 2.48 0.06 0.23 383

PL( Supplier Function ) 2.20 0.06 0.21 350

PL( Warehouse Function) 1.97 0.06 0.22 366

PL( Interface Function) 3.01 0.16 0.32 200

PL( User & Notification Function) 1.85 0.07 0.18 257

Programmer(P1) 1.99 0.03 0.04 133

Programmer(P2) 2.99 0.03 0.22 733

Total 19.99 0.76 1.84 242


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.


THANK YOU


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.

project presentation eprocurement system. m.tech s16- team s03 institute of systems science table of...

Documents

stage of project

milestones phase iproject

business processes

new processes

result of eprocurement

business partners

code developmentproject

users fujitec users