mis implemention methodology

8/22/2019 MIS Implemention Methodology

1/28

1

Management Information System


2/28

2

CHAPTER 4

MIS Planning and

Implementation


3/28

3

Outline

How to plan MIS project

System Development Life Cycle

Planning of MIS project

New methodologies

Waterfall methodology Rapid application development methodology (RAD)

Extreme Programming Methodology

ASAP: Accelerated SAP


4/28

4

SDLC

Systems Development Life Cyc le: the overall process for

developing information systems from planning and analysis throughimplementation and maintenance


5/28

5

Project planning

Set up project administration Staff project

Set goals and objectives

Acquire project resources Define metrics


6/28

6

Project staff

Project manager

Solution expertsProcess experts

Technical experts

Geography expertsChange management


7/287

Example of Project Team organization


8/288

Example of Team organization


9/289

Traditional Systems Development Life

Cycle

Detailed analysis of system using tools andtechniques to determine problem areas

Process models Data models

Phases Problem definition

Feasibility study

Systems analysis Systems design

Detailed design

Implementation

Maintenance


10/2810

Traditional Systems Development Life

Cycle, continued

Automating current system is counter-productive Inherit old problems and flaws

Provides opportunity to re-engineer current system

Create logical database design before details arerefined

Takes too much time

Uses a great deal of resources Expensive


11/28

11

New Methodologies

Waterfa ll methodo logy

Rapid appl ication development methodo logy

(RAD)

Extreme Programming Methodology

ASAP: Accelerated SAP


12/28

12

Waterfall methodology

Waterfal l methodology

a sequential, activity-

based process in whicheach phase in the SDLC

is performed sequentially

from planning through

implementation andmaintenance


13/28

13

Rapid application developmentmethodology (RAD)

Emphasizes extensive user involvement in the rapidand evolutionary construction of working prototypes ofa system to accelerate the systems developmentprocess

The prototype is an essential part of the analysisphase when using a RAD methodology Prototype a smaller-scale representation or working model

of the users requirements or a proposed design for aninformation system


14/28

14

The Prototyping Process


15/28

15

Extreme ProgrammingMethodology

Extreme prog ramm ing (XP) methodolog y breaks a project into tiny

phases, and developers cannot continue on to the next phase until the first

phase is complete


16/28

16

ASAP

Accelerated SAP (ASAP) is SAP's standard implementationmethodology. It contains the Roadmap, a step-by-step guidethat incorporates experience from many years of implementingR/3.

Accelerated SAP contains a multitude of tools, acceleratorsand useful information to assist all team members inimplementing R/3. Quality checks are incorporated at the end of

each phase to easily monitor deliverables and critical successfactors.


17/28

17

ASAP


18/28

18

Goal Setting

Define project goals & objectives

Implementation strategy1.Clarify the scope of implementation

2.Establish the project organization and

relevant committees and assign

resources

Implementation SequenceDefine sequence in project has to be

executed

TeamCore team+ project team+

consultant team

Sign OffAt the end of phase every above steps

will be documented & will be signed offwith the client

Phase 1 : Project Preparation

During this phase theteam goes through initial

planning andpreparation for SAPproject.


19/28

19

Phase 1 : Project Preparation


20/28

20

Phase 2 : Business Blueprint

SCOPE DOCUMENTThis document will consists of

questionnaire of entire business

process

AS IS1.Understanding the business Process

from the core team. 2.Based on the

input ASIS document has to be created

according to module wise

TO BE1.In this process will map the business

process in SAP based on ASIS

2.Module wise TOBE document has to

be created

GAP ANALYSIS1.The GAP b/w ASIS process & TOBE process

is called GAP analysis ie., The inputs or the

business process which cant mapped into

standard SAP will be analyzed here

2.GAP document has to be created

SIGN OFFEach process above has to be

taken sign off from client

The purpose of this phase is toachieve a common

understanding of how thecompany intends to run SAPto support their business.The result is the BusinessBlueprint, a detaileddocumentation of the resultsgathered during requirementsworkshops.



21/28

21



22/28

22

Phase 3 : Realization

BaselineMajor scope

Final ConfigurationRemaining scope

SIGN OFFEach process above has to be

taken sign off from client

The purpose of this phase is toimplement all the business

process requirements based onthe Business Blueprint. Thesystem configurationmethodology is provided in twowork packages: Baseline (majorscope); and Final configuration

(remaining scope).


23/28

23

Phase 3 : Realization


24/28

24

Unit Testing

Testing within each module

Integration TestingIntegrate testing of modules ie.,

combine testing of all the

modules

User Training

Cut over Strategylegacy system will be migrated to

SAP system.

SIGN OFF

Each process above has to betaken sign off from client

The purpose of this phase is to

complete the final preparation

(including testing, end usertraining, system management and

cutover activities) to finalize your

readiness to go live. The Final

Preparation phase also serves to

resolve all critical open issues. On

successful completion of thisphase, you are ready to run your

business in your live SAP System.

Phase 4 : Final Preparation


25/28

25

Phase 4 : Final Preparation


26/28

26

Phase 5 : Go Live & Support

Production Support

Monitor System

Transactions

Optimize Performance

Help Desk &

Competency Center

The purpose of this

phase is to move froma project-oriented,

pre-production

environment to live

production operation.


27/28

27

Phase 5 : Go Live & Support


28/28

28

ASAP Roadmap

Final

PreparationProject

Preparation Business BlueprintRealization

Setup of Local Project

Organization

Adaption of

Strategic Framework

Establish OCM

Procedures + Responsibles

Infrastructure Requirements

and Design

Early Adoption of Best

Business Practice Proceesses

Training and

Documentation Strategy

Data ManagementStandards Implementation

Data Cleansingand Data Preparation

Completion Check &

Prepare for Next Phase

General

Project Management

Local Business Blueprint

Documentation

Security Requirements

Infrastructure Planning

System Operation Stategy


Business Practice Processes

Training Planning

Data Cleansingand Data Preparation

Completion Check &

Prepare for Next Phase

OCM Organizational

Alignment + Change Analysis

General

Project Management

OCM

Training Preparation

Configuration &

Development

Unit / Process / Integration /

Business Acceptance Testing


Business Practice Processes

InfrastructureImplementation

Data Preparation & DataMigration Simulation

Completion Check &

Cutover Planning

& Preparation

Business Transition

Planning for Cutover

General

Project Management

OCM

End User Training

End User Practice in the

System

Data Migration toProduction

Infrastructure Finalization

Cutover Management

Business Simulation

Pre-Go-Live Operations

Completion Check &

Final Cutover and

Controlled Process GoLive

GoLive and

Support

General

Project Management

OCM

Project Closing

System Support

Business Support

mis implemention methodology

Documents