erp e nterprise r esource p lanning every monday, 13:30 – 16:00 last updated: 31 march 2009erp –...

21
ERP ENTERPRISE RESOURCE PLANNING Every Monday, 13:30 – 16:00 Last Updated: 31 March 2009 ERP – Ir. H. Noor Hidayat, MMT. 1

Upload: garett-gravlin

Post on 01-Apr-2015

220 views

Category:

Documents


2 download

TRANSCRIPT

ERP

ENTERPRISE RESOURCE PLANNING

Every Monday, 13:30 – 16:00

Last Updated: 31 March 2009 ERP – Ir. H. Noor Hidayat, MMT. 1

ERPERPSyllabus

1. Introduction2. ERP Platform3. ERP Component4. ERP Development (Project Management Concerns)5. System Life Cycle

References:– Project Management Concerns, Chevron Texaco, 2005

Last Updated: 31 March 2009 ERP – Ir. H. Noor Hidayat, MMT. 2

ERPERPThe 4 P’s

• People — the most important element of a successful project

• Product — the software to be built• Process — the set of framework activities and

software engineering tasks to get the job done• Project — all work required to make the

product a reality

ERPERPWhat is Software?

Software is a set of items or objects that form a “configuration” that includes • programs • documents • data ...

ERPERPProject Management Concerns

staffing?

cost estimation?

project scheduling?

project monitoring?

other resources?

customer communication?

risk assessment?

product quality?

measurement?

ERPERPProject Risks

What can go wrong?What is the likelihood?What will the damage be?What can we do about it?

ERPERP

RISK

Risk Management Paradigm

control

identify

analyze

plan

track

ERPERPBuilding a Risk Table

Risk Probability Impact RMMM

RiskMitigationMonitoring

& Management

ERPERPEffort Allocation

40-50%

30-40%

• “front end” activities– customer communication– analysis– design– review and modification

• construction activities– coding or code generation

• testing and installation– unit, integration– white-box, black box– regression

15-20%

ERPERPUse Automated Tools toDerive a Timeline Chart

I.1.1 Identify need and benefits Meet with customers Identify needs and project constraints Establish product statement Milestone: product statement definedI.1.2 Define desired output/control/input (OCI) Scope keyboard functions Scope voice input functions Scope modes of interaction Scope document diagnostics Scope other WP functions Document OCI FTR: Review OCI with customer Revise OCI as required; Milestone; OCI definedI.1.3 Define the functionality/behavior Define keyboard functions Define voice input functions Decribe modes of interaction Decribe spell/grammar check Decribe other WP functions FTR: Review OCI definition with customer Revise as required Milestone: OCI defintition completeI.1.4 Isolate software elements Milestone: Software elements definedI.1.5 Research availability of existing software Reseach text editiong components Research voice input components Research file management components Research Spell/Grammar check components Milestone: Reusable components identifiedI.1.6 Define technical feasibility Evaluate voice input Evaluate grammar checking Milestone: Technical feasibility assessedI.1.7 Make quick estimate of sizeI.1.8 Create a Scope Definition Review scope document with customer Revise document as required Milestone: Scope document complete

week 1 week 2 week 3 week 4Work tasks week 5

ERPERPThe “First Law”

No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle.

Bersoff, et al, 1980

ERPERPWhat Are These Changes?

data

otherdocuments

codeTest

ProjectPlan

changes in technical requirements

changes in business requirements

changes inuser requirements

software models

ERPERPRequirements GatheringFacilitated Application Specification Techniques• Business Area Analysis• Technical Area Analysis

SoftwareEngineering

GroupCustomer

Group

ERPERPSoftware Testing

Testing is the process of exercising aprogram with the specific intent of findingerrors prior to delivery to the end user.

ERPERPWhat Testing Shows

errors

requirements conformance

performance

an indicationof quality

ERPERPWho Tests the Software?

developer independent tester

Understands the system

but, will test "gently"

and, is driven by "delivery"

Must learn about the system,

but, will attempt to break it

and, is driven by quality

ERPERPSoftware Testing

Methods

Strategies

white-boxmethods

black-box methods

ERPERPWhite-Box Testing

... our goal is to ensure that all statements and conditions have been executed at least once ...

ERPERPBlack-Box Testing

requirements

eventsinput

output

ERPERPQuestions

???

ERP

End of ERP Development

Last Updated: 31 March 2009 ERP – Ir. H. Noor Hidayat, MMT. 24