Mis After Midterm

MIS STRATEGY
PROF.M. K. AGRAWAL(FMS-IIRM)
3/21/2012
PLANNING
EBTERPRISE OBJECTIVE
ENTERPRISE STRATEGIES
APPRAISAL
DETERMINE THE ORG. COMPARATIVE ADVANTAGES
DETERMINE PRESENT AND POTENTIAL OPPORTUNITIES
CHOICE
CONSIDER THE STRATEGIC OPTIONS
CHOOSE THE STRATEGY
IMPLEMENTATION
DEVELOP MEDIUM AND SHORT RANGE PLANS
DEVELOP THE ORG. STRUCTURE AND CLIMATE
CONTROL
EVALUATION OF STRATEGIES AND FEED BACK
3/21/2012
Vision ..
3
The vision is the starting point of strategic framework. Where you want to be in future.
That makes a difference in society. They have a vision that
how society could be or should be in future

This vision is not they can achieve on their own. It is
something that guides in their work and which they believe, can be achieved if enough organizations share the vision and works towards it.
3/21/2012
Example of vision..
4
We strive to contribute to a society where every citizen has equal access to quality health care and is able to live in an environment which supports quality health for all.
3/21/2012
Mission:
5
Purpose of existence of your organization.
The mission contains statements how you are going
to achieve the vision statement.

A mission statement have four components: What the organization or project is? What the organization or project aims to do or achieve? Who the work is aimed at( the target group), How it does it work(what methods it uses)
3/21/2012
A mission statement is a statement of the organizations reason for being, its purpose what it wants to accomplish in the larger environment. (Kotler p.49).
3/21/2012
Goal.
7
Goals are general directions, that are not specific
enough to be measured.
Think of the word "go." It has no end.
A good example is the signature line of the Star Trek television series: Go where no one in has gone before." You can't measure it, and you probably will never know if the goals were accomplished, because once humans have gone somewhere, we've been there, and there are still other places to go since the universe is infinite and has no end.
3/21/2012
Objectives..
8
Objectives, on the other hand, are specific and
measurable.
Think of the word "object." You can touch it, it's
there, it's actual, it's finite.

A crystal-clear objective would read something like
this: "Our objective is to deliver X results by Y date at a cost of Z dollars." .

3/21/2012
Think of the goals as the treasure at the top of a stairway, and the objectives as the stairs.
3/21/2012
Establishing Objectives for Systems Development

10
Systems development objectives should be
supportive of, and aligned with, organizational goals. There are four kinds of objectives that should be considered:
Performance objectives. Cost objectives. Control objectives. Complexity objectives.
3/21/2012
Role of system analyst:

11
Due to the various responsibilities that a system analyst requires to handle, he has to be multifaceted person with skills required at various stages of the life cycle. Technical know-how of the information system
3/21/2012
12
Business knowledge Interpersonal skills As the analyst might have to develop any kind of a business system, he should be familiar with the general functioning of all kind of businesses. Such skills are required at various stages of development process for interacting with the users and extracting the requirements out of them.
Problem solving skills A system analyst should have enough problem solving skills for defining the alternate solutions to the system and also for the problems occurring at the various stages of the development process.
3/21/2012
13
Review of present system: Capabilities and shortcomings.
Specifications of system requirements..(system planning)

Survey of system userstheir information
needs.requirement analysis and specifications Alternative system concept Identify and investigate the problem and opportunities Feasibility studyrough estimates and cost, risk and ROI analysis.
In short researching, planning and recommending software and system choices

3/21/2012
14
3/21/2012
15
ORGANIZATIONAL ANALYSIS
ANALYSIS OF PRESENT SYSTEM FUNCTIONAL REQUIREMENT ANALYSIS
3/21/2012
Organizational analysis
16
No design can be made , no improvements can be
made unless we are unknown to organizational environment and related activities. The need of information must be identified.
3/21/2012
Analysis of present system

17
System decomposition concept: The process of
dividing the large systems into smaller systems is called decomposition. It helps in understanding the existing the present system. It helps to go through the organizational objectives. It helps to know that whether the system is totally feasible or not and what improvements are required
3/21/2012
Functional requirement analysis.

18
Information system design requirements, processes,
hardware and software configuration must be restructured.
3/21/2012
Assessing information needs:

19
Step 1. Identify future issues
Step 2. Develop a taxonomy Step 3. Rate the importance of information
requirements Step 4. Prepare a data collection / analysis plan
3/21/2012
Step 1. Identify future issues

20
A number of mechanisms can be used for anticipating strategic issues.
Techniques like the Delphi, Nominal Group technique have been used to capture the opinions of groups of experts on the likelihood that issues will occur.
Identify weaknesses in existing system operation,
literature reviews, and observing the environment, penal research,
focus group research, survey, can also be helpful.
3/21/2012
Step 2. Develop a taxonomy

21
In this step, the analysis team works with the panel
to identify categories of information. The panel lists for each issue what information will substantially useful and assist in decision making. The analysis team then categorizes these information items. For example, cost of operations maybe important in several different upcoming issues.
3/21/2012
Step 3. Rate the importance of information requirements

22
No information system can collect and analyze data
to address every possible information requirement. Even if one could guarantee that the format in which the data were collected was appropriate to a particular strategic issue, the cost would be prohibitive. It is imperative to establish priorities on what information is to be collected and analyzed.
3/21/2012
Impact on business
Probability of occurrence
High Medium
High priority issues
Low
Low priority issues
High Medium
Critical issues
Low priority issues
low
To be watched issues
23
Low priority issues
Low priority issues

3/21/2012
Issues
Weight age
Rating
Total Weight age score
Comments
Opportunities
Threats
Weight age(0 to 1) Factor impact Business response
Rating(5=outs tanding1=po or)

The total weighted score indicates how well the business is responding to current and expected factors in its external PROF.M. K. AGRAWAL(FMS-IIRM) environment. 24 3/21/2012
Systems Development
25
PLANNING LIFECYCLE
3/21/2012
Systems Development Model

26
Traditional: SDLC
Alternatives Prototyping CASE-based Time-boxing Rapid Application Development
3/21/2012
Systems Lifecycle
27
Investigation
Design
Building Testing
Installation Maintenance
Enhancement Retirement
All of these activities comprise system development and form a lifecycle
3/21/2012
Traditional Software Development Lifecycle (SDLC)

28
Often called Waterfall Model

Investigation Design
Construction
Testing
Implement and Control

3/21/2012
Definition phase..
29
Analysis of existing information system and business activities Problems related to current operations and IS are identified.
A good solution is drawn in a detailed requirement statement Feasibility study: applicability and cost benefit analysis
3/21/2012
Construction phase
30
On the basis of requirement analysis, the designer
designs the system first logically and then physically through IT tools and methods. When physical design is made feasible then computer software is developed and evaluated
System design (logically flow diagram)
Coding and physically development
System testing
3/21/2012
Implementation phase
31
When business managers and IS professional are
satisfied with system, they install it.

Implementation
Cutover
phase-in
It can be installed in a complete .

It can be installed in parallel with operation of old system

3/21/2012
Prototype approach.
32
Is a type of evolutionary development process

Input and output screens developed for users to test as part of requirements definition First-of-a-series a completely operational prototype used as a pilot
Selected features only some essential features included in prototype, more added later
3/21/2012
Development of a Prototype
33
IS objectives Modified prototype Is the user satisfied
Identification of information requirements

Define system objective
Modify the prototype specifications
NO
YES
Develop and test prototype
Documents
Quick design
Prototype building
STOP
Engineer the product

3/21/2012
Prototyping approach.
34
Identification basic system requirements Developing initial prototype Users role(suggestions and desired changes) Revise and enhance prototype
Logical design and testing
Evaluation of prototype system
Construction phase Implementation phase
3/21/2012
Rapid Application Development

35
Goal is to produce a system in less than a year

Trendy term for many of these alternative methods
used is some combination:

CASE JAD Prototyping Time Boxing
3/21/2012
Time Box Approach

36
Identify objectives Create project team Set time period (say for 6 weeks)
Team cycles through all phases of lifecycle very quickly.

Fast development tools very useful
3/21/2012
CASE Tools..
37
Computer Aided Software Engineering Toolsets to speed software development and improve quality Upper CASE Focus on investigation, analysis and logical design
Lower CASE Design, code generation and testing

Integrated CASE include both
3/21/2012
Types of CASE tools.

38
3/21/2012
Rapid Application Development (RAD)

39
Hybrid methodology aspects of SDLC and prototyping
Figure 10.12 Four-Step RAD Cycle
3/21/2012

40
Joint application design (JAD) a technique in which a team of users and IS specialists engage in an intense and structured process in order to minimize the total time required for gathering information from multiple participants
Computer-aided software engineering (CASE) any software tool used to automate one or more steps of a software development methodology
3/21/2012

41
Figure 10.14 RAD Advantages and Disadvantages
3/21/2012
End User Development

42
Easy-to-use tools encourage end-user development
So does IT department resource constraints

Advantages Good knowledge of business needs Control of resources and priorities Disadvantages Lack of technical expertise Lack of planning
3/21/2012
IT Organization vs. End-User Development

43
Source of tension
IT: Users produce poor systems and leave us with maintenance
How should IT respond to this? Ignore Outlaw and drive underground Offer assistance and consultation
3/21/2012
User Acceptance
44
User acceptance document - a formal agreement signed by the user that a phase of the installation or the complete system is approved.
This is a legal document that usually removes or reduces the IS vendor from liability or responsibility for problems that occur after it is signed.
3/21/2012
THE MAKE-OR-BUY DECISION 45

Decision should be made jointly by business managers and IS professionals Advantages of purchasing:
Cost savings Faster speed of implementation Seldom exactly fits a companys needs Often forces trade-offs
Disadvantages of purchasing:

3/21/2012
PURCHASING METHODOLOGY
46
RFP= Request for Proposal
The Purchasing Process

3/21/2012
Initiating the Purchasing Process

47
3/21/2012
Establish Criteria for Selection

48
3/21/2012
Develop and Distribute the RFP

49
Request for proposal (RFP) a formal document sent to potential vendors inviting them to submit a proposal describing their software package and how it would meet the companys needs
3/21/2012
Evaluate Vendor Responses to RFP and Choose Package

50
Evaluation steps:

Review vendors responses from RFPs Request demonstrations of leading packages Request references from users of software packages in other companies Assess how well package capabilities satisfy companys needs Understand extent of any additional development efforts or costs to tailor software Make decision
3/21/2012
Evaluate Vendor Responses to RFP and Choose Package

51
Matching Company Needs with Capabilities of the Package

3/21/2012
Construction Phase
52
If no software package modifications required:

Skip system design and building steps Move directly to system testing Develop any necessary process changes Consider contracting with vendor or a third party for changes versus modifying in-house Determine if changes are required to other existing company systems
3/21/2012
If software package is modified:

Project Team for Purchasing Packages

53
Business managers and users IS professionals Project manager usually a business manager Software vendor personnel Sometimes includes a third-party implementation partner Purchasing specialists
3/21/2012
Purchasing Advantages and Disadvantages

54
3/21/2012

Mis After Midterm

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mis After Midterm

Uploaded by

Copyright:

Available Formats

MIS STRATEGY

DETERMINE THE ORG. COMPARATIVE ADVANTAGES

DETERMINE PRESENT AND POTENTIAL OPPORTUNITIES

CONSIDER THE STRATEGIC OPTIONS

CHOOSE THE STRATEGY

DEVELOP MEDIUM AND SHORT RANGE PLANS

DEVELOP THE ORG. STRUCTURE AND CLIMATE

EVALUATION OF STRATEGIES AND FEED BACK

That makes a difference in society. They have a vision that

how society could be or should be in future

Purpose of existence of your organization.

The mission contains statements how you are going

to achieve the vision statement.

Goals are general directions, that are not specific

Objectives, on the other hand, are specific and

there, it's actual, it's finite.

this: "Our objective is to deliver X results by Y date at a cost of Z dollars." .

Establishing Objectives for Systems Development

Systems development objectives should be

Performance objectives. Cost objectives. Control objectives. Complexity objectives.

Role of system analyst:

Review of present system: Capabilities and shortcomings.

Specifications of system requirements..(system planning)

In short researching, planning and recommending software and system choices

ANALYSIS OF PRESENT SYSTEM FUNCTIONAL REQUIREMENT ANALYSIS

No design can be made , no improvements can be

Analysis of present system

System decomposition concept: The process of

Functional requirement analysis.

Information system design requirements, processes,

hardware and software configuration must be restructured.

Assessing information needs:

Step 1. Identify future issues

Step 2. Develop a taxonomy Step 3. Rate the importance of information

requirements Step 4. Prepare a data collection / analysis plan

Step 1. Identify future issues

A number of mechanisms can be used for anticipating strategic issues.

focus group research, survey, can also be helpful.

Step 2. Develop a taxonomy

In this step, the analysis team works with the panel

Step 3. Rate the importance of information requirements

No information system can collect and analyze data

High priority issues

High priority issues

Low priority issues

Low priority issues

Low priority issues

Total Weight age score

Weight age(0 to 1) Factor impact Business response

Rating(5=outs tanding1=po or)

Systems Development Model

Alternatives Prototyping CASE-based Time-boxing Rapid Application Development

All of these activities comprise system development and form a lifecycle

Traditional Software Development Lifecycle (SDLC)

Often called Waterfall Model

Implement and Control

On the basis of requirement analysis, the designer

Coding and physically development

When business managers and IS professional are

satisfied with system, they install it.

It can be installed in a complete .

It can be installed in parallel with operation of old system

Is a type of evolutionary development process