Your SlideShare is downloading. ×
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Vidya dharan presentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Vidya dharan presentation

308

Published on

ERP & SDLC

ERP & SDLC

Published in: Career
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
308
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. AGENDA
    • ERP system and its integration
    • Choosing a particular technology on an IT project
    • Software Development Life Cycle (SDLC)
    • Queries
  • 2. ERP System
    • Enterprise Resource Planning
    • An integrated computer-based system
    • Manages internal & external resources
    • Consolidates all business operations into uniform & enterprise wide environment
  • 3. Evolution of ERP
    • Continuous innovations
    • Computers
    • MRP
    • MRP II
    • EAS
  • 4. ERP Components
    • Manufacturing
    • Operational Planning
    • Materials Management
    • Quality Management
    • Sales & Distribution
    • Human Resources
    • Maintenance Management
    • Finance
  • 5. How ERP works?
    • Eases the exchange of data
    • Unites all business practices within a single family of software modules
    • Modules run on client/server or internet architecture
    • Each modules work separately performing specific data-processing functions
    • PC’s are connected to more powerful computers that feed them data
  • 6. What’s the big deal?
    • Cuts production & inventory costs
    • Measures & account for product waste
    • Ensures required materials availability
    • Improves customer service
    • Plans & forecasts product demand
    • Improves cost allocation
  • 7. Implementation of ERP
    • Who?
    • Project leader
    • Module leaders
    • Individual team members
    • What?
    • Module selection
    • Full or partial implementation
  • 8. Implementation
    • How?
    • Study the existing system
    • Design & develop it using the new product
    • Test the new system
    • Train users on new system
    • Put it in real use
  • 9. ERP’s Performance
    • Decrease data entry
    • Centralize information for decisions
    • Decrease delivery cycle
    • Increase profit margin
    • Increase customer satisfaction
    • On time delivery
  • 10. Choosing the Technology
    • Business needs & shortlist of solutions
    • Compare using the criteria
    • Analyze the strengths & weakness
    • Implementation Cost
  • 11. Implementation Factors
    • Forecasting Economic Impact
    • Manager support
    • Technology Diffusion
    • Applications Compatibility
    • Service Support
    • Company stability
    • System Links
    • Customer satisfaction
  • 12. Vendors of ERP
    • Peoplesoft
    • SAP
    • Oracle
    • Ramco
    • Microsoft
    • SSA Global
  • 13. Software Development Life Cycle (SDLC)
    • Structure imposed on a software development
    • Activities performed at each stage of software development
  • 14. Waterfall Model
  • 15. Strengths
    • Easy to understand, easy to use
    • Provides structure to inexperienced staff
    • Sets requirements stability
    • Good for management control
    • Works well when quality is more important
  • 16. Disadvantages
    • Requirements must be known
    • Can give false impression on progress
    • Does not reflect problem-solving nature of software development
    • Integration is big issue at the end
    • Little opportunity for customer to preview the system
  • 17. When to use Waterfall model
    • Requirements are known
    • Product definition is stable
    • Technology is understood
    • New version of an existing product
    • Porting an existing product to a new platform
  • 18.
    • QUERIES
  • 19.
    • Thank You!

×