Mis After Midterm
-
Upload
shivesh-dubey -
Category
Documents
-
view
219 -
download
0
Transcript of Mis After Midterm
-
7/31/2019 Mis After Midterm
1/54
-
7/31/2019 Mis After Midterm
2/54
EBTERPRISEOBJECTIVE
ENTERPRISESTRATEGIES
DETERMINE THEORG. COMPARATIVE
ADVANTAGES
DETERMINE PRESENTAND POTENTIALOPPORTUNITIES
CONSIDER THESTRATEGIC OPTIONS
CHOOSE THESTRATEGY
DEVELOP MEDIUMAND SHORT RANGE
PLANS
DEVELOP THE ORG.STRUCTURE AND
CLIMATE
EVALUATION OFSTRATEGIES AND
FEED BACK
PLANNING
APPRAISAL
CHOICE
IMPLEMENTATION
CONTROL
3/21/20122PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
3/54
Vision ..
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 thathow society could be or should be in future
This vision is not they can achieve on their own. It issomething that guides in their work and which they believe,can be achieved if enough organizations share the visionand works towards it.
3/21/2012
3
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
4/54
Example of vision..
We strive to contributeto a society whereevery citizen hasequal access to
quality health careand is able to live in
an environmentwhich supports
quality health for all.
3/21/2012
4
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
5/54
Mission:
Purpose of existence of your organization.
The mission contains statements how you are goingto achieve the vision statement.
A mission statement have four components:What the organization or project is?What the organization or project aims to door achieve?
Who the work is aimed at( the targetgroup),How it does it work(what methods it uses)
3/21/2012
5
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
6/54
A mission statement is a statement of theorganizations reason for being, its purpose
what it wants to accomplish in the largerenvironment. (Kotler p.49).
3/21/2012
6
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
7/54
Goal.
Goals are general directions, that are not specificenough 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 goalswere accomplished, because once humans have gone somewhere,we've been there, and there are still other places to go since theuniverse is infinite and has no end.
3/21/2012
7
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
8/54
Objectives..
Objectives, on the other hand, are specific andmeasurable.
Think of the word "object." You can touch it, it'sthere, it's actual, it's finite.
A crystal-clear objective would read something likethis: "Our objective is to deliver X results by Y date ata cost of Z dollars."
.3/21/2012
8
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
9/54
Think of the goals as the treasure at
the top of a stairway, and the
objectives as the stairs.
3/21/2012
9
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
10/54
Establishing Objectives for Systems Development
Systems development objectives should besupportive of, and aligned with,organizational goals.
There are four kinds of objectives thatshould be considered: Performance objectives.
Cost objectives.
Control objectives. Complexity objectives.
3/21/2012
10
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
11/54
Role of system analyst:
Due to the various responsibilities that a systemanalyst requires to handle, he has to bemultifaceted person with skills required at various
stages of the life cycle.Technical know-how of the information system
3/21/2012
11
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
12/54
Business knowledge Interpersonal skills Problem solvingskills
As the analyst mighthave to develop anykind of a businesssystem, he should befamiliar with thegeneral functioning ofall kind of businesses.
Such skills are requiredat various stages ofdevelopment processfor interacting with theusers and extractingthe requirements out ofthem.
A system analystshould have enoughproblem solving skillsfor defining thealternate solutions tothe system and also forthe problems occurringat the various stages of
the developmentprocess.
3/21/2012
12
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
13/54
Review of present system: Capabilities and shortcomings.
Specifications of system requirements..(system planning)
Survey of system userstheir informationneeds.requirement analysis and specifications
Alternative system concept
Identify and investigate the problem and opportunities
Feasibility studyrough estimates and cost, risk and ROI
analysis.
3/21/2012
13
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
14/54
3/21/2012
14
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
15/54
ORGANIZATIONAL ANALYSIS
ANALYSIS OF PRESENT SYSTEM
FUNCTIONAL REQUIREMENT ANALYSIS
3/21/2012
15
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
16/54
Organizational analysis
No design can be made , no improvements can bemade unless we are unknown to organizationalenvironment and related activities. The need ofinformation must be identified.
3/21/2012
16
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
17/54
Analysis of present system
System decomposition concept: The process ofdividing the large systems into smaller systems iscalled decomposition.
It helps in understanding the existing the presentsystem.
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
17
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
18/54
Functional requirement analysis.
Information system design requirements, processes,hardware and software configuration must berestructured.
3/21/2012
18
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
19/54
Assessing information needs:
Step 1. Identify future issues
Step 2. Develop a taxonomy
Step 3. Rate the importance of information
requirementsStep 4. Prepare a data collection / analysis
plan
3/21/2012
19
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
20/54
Step 1. Identify future issues
A number of mechanisms can be used for anticipating strategic issues.Techniques like the Delphi, Nominal Group technique have beenused to capture the opinions of groups of experts on the likelihood thatissues 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
20
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
21/54
Step 2. Develop a taxonomy
In this step, the analysis team works with the panelto identify categories of information. The panel listsfor each issue what information will substantiallyuseful and assist in decision making. The analysisteam then categorizes these information items.
For example, cost of operations maybe important inseveral different upcoming issues.
3/21/2012
21
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
22/54
Step 3. Rate the importance ofinformation requirements
No information system can collect and analyze datato address every possible information requirement.Even if one could guarantee that the format in whichthe data were collected was appropriate to aparticular strategic issue, the cost would beprohibitive. It is imperative to establish priorities onwhat information is to be collected and analyzed.
3/21/2012
22
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
23/54
High Medium Low
Critical issues High priority issues
Low priorityissues
High priorityissues
High priorityissues
Low priorityissues
To be watchedissues
Low priorityissues
Low priorityissueslo
w
M
edium
High
Impact on business
Proba
bilityofoccurrenc
e
3/21/201223PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
24/54
Issues Weightage
Rating Total Weight agescore
Comments
Opportunities
Threats
The total weighted score indicates how well the business isresponding to current and expected factors in its external
environment.
Factorimpact
Businessresponse
Weight age(0 to 1)
Rating(5=outstanding1=po
or)
3/21/201224PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
25/54
P L A N N I N G
L I F E C Y C L E
Systems Development
3/21/2012
25
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
26/54
Systems Development Model26
Traditional: SDLC
Alternatives Prototyping
CASE-based Time-boxing
Rapid Application Development
3/21/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
27/54
Systems Lifecycle27
Investigation
Design
Building
Testing
Installation
Maintenance
Enhancement Retirement
All of these activitiescomprise systemdevelopmentand form a lifecycle
3/21/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
28/54
Traditional Software Development Lifecycle (SDLC)
28
Often called Waterfall Model
Investigation
Design
Construction
Implement
and Control
Testing
3/21/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
29/54
Definition phase..
Analysis of existing informationsystem and business activities
Problems related to current
operations and IS are identified.
A good solution is drawn in a detailedrequirement statement
Feasibility study: applicability andcost benefit analysis
3/21/2012
29
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
30/54
Construction phase
On the basis of requirement analysis, the designerdesigns the system first logically and then physicallythrough IT tools and methods. When physical designis made feasible then computer software is developedand evaluated
System design(logically flow
diagram)
Coding and physicallydevelopment
System testing
3/21/2012
30
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
31/54
Implementation phase
When business managers and IS professional aresatisfied with system, they install it.
Implementation
Cutover
It can be installed in acomplete .
phase-in
It can be installed in parallelwith operation of old system
3/21/2012
31
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
32/54
Is a type ofevolutionary 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
Prototype approach.
3/21/2012
32
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
33/54
Development of a Prototype
Prototype building
Develop and testprototype
Modify the prototype
specifications
Modified prototypeIs the user satisfied
NO YES
Documents
Engineerthe
product
STOPQuick design
Define systemobjective
Identification of
informationrequirements
IS objectives
3/21/2012
33
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
34/54
Prototyping approach.34
Identification basic system requirements
Developing initial prototype
Users role(suggestions and desired changes)
Revise and enhance prototype
Evaluation of prototype system
Construction phase
Implementation phase
Logicaldesign and
testing
3/21/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
35/54
Rapid Application Development
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
35
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
36/54
Time Box Approach36
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/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
37/54
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/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
38/54
Types of CASE tools.
3/21/2012
38
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
39/54
Rapid Application Development (RAD)
Figure 10.12 Four-Step RAD Cycle
Hybrid methodology
aspects of SDLC and
prototyping
3/21/2012
39
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
40/54
Rapid Application Development (RAD)
Joint application design (JAD) a technique inwhich a team of users and IS specialists engage inan intense and structured process in order to
minimize the total time required for gatheringinformation from multiple participants
Computer-aided software engineering (CASE) any
software tool used to automate one or more steps ofa software development methodology
3/21/2012
40
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
41/54
Rapid Application Development (RAD)
Figure 10.14 RAD Advantagesand Disadvantages
3/21/2012
41
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
42/54
End User Development42
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/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
43/54
IT Organization vs. End-User Development
43
Source of tension
How should IT respond to this? Ignore
Outlaw and drive underground
Offer assistance and consultation
IT: Usersproduce poorsystems andleave us with
maintenance
3/21/2012PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
44/54
User Acceptance
User acceptance document - a formal agreementsigned by the user that a phase of the installation or
the complete system is approved.
This is a legal document that usually removes orreduces the IS vendor from liability or responsibilityfor problems that occur after it is signed.
3/21/2012
44
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
45/54
THE MAKE-OR-BUYDECISION
Decision should be made jointly bybusiness managers and IS
professionals
Advantages of purchasing:
Cost savings
Faster speed of implementation
Disadvantages of purchasing:
Seldom exactly fits a companys needs Often forces trade-offs
3/21/2012
45
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
46/54
PURCHASING METHODOLOGY
The Purchasing Process
RFP=Request
forProposal
3/21/2012
46
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
47/54
Initiating the Purchasing Process
3/21/2012
47
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
48/54
Establish Criteria for Selection
3/21/2012
48
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
49/54
Develop and Distribute the RFP
Request for proposal (RFP) a formal documentsent to potential vendors inviting them to submit aproposal describing their software package and
how it would meet the companys needs
3/21/2012
49
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
50/54
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
Evaluate Vendor Responses to RFP and Choose Package
3/21/2012
50
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
51/54
Evaluate Vendor Responses to RFP and Choose Package
Matching Company Needswith Capabilities of the Package
3/21/2012
51
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
52/54
If no software package modifications
required:
Skip system design and building steps
Move directly to system testing Develop any necessary process changes
If software package is modified:
Consider contracting with vendor or a third
party for changes versus modifying in-house
Determine if changes are required to other
existing company systems
Construction Phase
3/21/2012
52
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
53/54
Business managers and users
IS professionals
Project manager usually a businessmanager
Software vendor personnel
Sometimes includes a third-party
implementation partner Purchasing specialists
Project Team for Purchasing Packages
3/21/2012
53
PROF.M. K. AGRAWAL(FMS-IIRM)
-
7/31/2019 Mis After Midterm
54/54
Purchasing Advantages and Disadvantages
54