Please enable JavaScript.

Coggle requires JavaScript to display documents.

SDLC (Difference between SDLC and ERPLC, Traditional ERP Life Cycle, SDLC…

- - - - How large the ERP system scope based on departmental or functional coverage?
      - Develop long-term vision and short-term implementation plan with top management commitment for the plan
      - Structure of the implementation team
        
        role of external consultants (time and scope)
        
        role of internal employee (SMEs, who'll provide the knowledge to business rule, input for interfaces and report designs
      - Vendor selection
        
        review vendor information
        
        choices could be narrowed by testing alternative software
        access number of items to create boundaries between vendors
      - Gap Analysis
        Compare with operational processes
      - Physical Scope
        Identify sites (addressed, geographical location, number of users
      - BPR Scope
        
        Can it be refined, replaced, or eliminated
        
        What users, departments, sites will be affected?
      - SMEs (Subject matter experts)
        BPR (Business Process Reengineering)
      - Technical Scope
        
        How much modification?
        
        What process will be utilized and customized?
      - Resource Scope - time and budget
      - Implementation Scope
        
        Which modules
        
        What modules will be connected to the existing system?
  - - - Phased: implementing new system in stages (replacing specific modules of the old system)
      - Pilot: implementing the new system in a limited area
      - Parallel: running the old and new system in parallel (ensure new system working correctly before fully transition it)
      - Big Bang: move from old system directly to the new system
- - - - create a working model of the software application to get feedback from stakeholders and make improvements
      - test the application's features
        
        make changes as needed
    - - end-users create software applications to meet their specific needs
      - user-friendly tools or platforms
        
        no coding knowledge
  - - - determine problem/opportunity
    - - analyze information and requirement need by the end user, organization and system that will be used
    - - develop specification/design for the hardware, software, product information that will satisfy the requirement by user
    - - install hardware, software
      - test & document system
      - training
    - - convert to new system
      - postimplementation review process
- - - - Emphasize Training and Change Management
      - Minimize the Type and Number of Customizations
      - Strong and Experienced Program Management
      - Solid Top Management Commitment
  - - - Phase
        
        • Testing and Delivery: Integration testing. Business and system delivery.
        
        • Configuration: Software development. Integration test planning.
        
        • Redesign: To-be Modeling. Software design and development.
        
        • Visioning and Targeting: Needs assessment. Vision and targets identified. As-is modeling.
        
        • Scoping and Planning: Project definition and scope. Project planning is initiated.
    - - Phase
        
        • Delivering Value. Measuring results and celebrating success
        
        • Success Dimension. Getting the right blend of people, skills, methods, and management in the team.
        
        • Aligned approach. Setting the right expectations that deliver both short-term and long-term value.
        
        • Reality Check. Is the organization ready for change?
        
        • Value Proposition. Does the solution make sound business sense?
  - - - Each project team knows
        
        who they will report to
        
        what is expected from them
        
        what they will be evaluated on
      - Defining roles will be PMO's responsibilities
      - Identify roles and responsibilities to ensure accountability of project
    - - Change Management Team - Provide project implementation information to key areas within organization
      - Reporting Team - Develop reporting framework and initial reports to be included in the system implentation
      - Conversion Team - Convert legacy data to new system
      - Development Team - Modify software based on goals
      - Infrastructure Team - Implement hardware and software
      - Functional Team - Knowledgeable staff from each area
- - - - example staff, or technologies
    - - Traditional ERP Life Cycle
- - - - Create and Implement
        
        Review and Monitor