Beruflich Dokumente
Kultur Dokumente
Table1. Description
of BSPStudySteps
Table1. (continued)
Table2. Some
Characteristicsof Different Methodologies
Methodology Impact Focus Defines Automated
or Data Support
Alignment Architecture
BusinessSystems Primarily
Planning Alignment Data Yes No
Strategic Systems Primarily
Planning Alignment Data Yes Yes
Information Primarily
Engineering Alignment Data Yes Yes
Method/1 Alignment Projects No No
Critical Success Decision
Factors CanBe Both Information No No
CustomerResource
Life Cycle Impact Customers No No
Value Chain Internal
Analysis Impact Operations No No
Table3. TheProblems
Problem ProblemStatement Source
Code
Resources for Implementing the Methodology
R1 Thesize of the planningteamis verylarge. Vacca, 1983
R2 It is difficult to find a teamleaderwhomeetsthecriteria specified Vacca, 1983
by the methodology.
R3 It is difficult to find teammembers whomeetthe criteria specified Vacca, 1983
by the methodology.
R4 Thesuccessof the methodology is greatly dependent on the team Zachma~,1982
leader.
R5 Manysupportpersonnelare required for data gatheringand Rockart,1979
analysisduringthe study.
R6 Theplanningexercisetakesverylong. Bowman,et al., 1983
R7 Theplanningexerciseis very expensive. Moskowitz,1986
R8 Thedocumentation doesnot adequatelydescribethe stepsthat Zachman,1982
shouldbe followed for implementing the methodology,
R9 Themethodology lacks sufficient computersupport. Zachman,1982
R10 Adequate externalconsultantsupportis not availablefor Zachman,1982
implementingthe methodology.
Rll Themethodology is not basedon anytheoretical framework. Zachman,1982
R12 Theplanninghorizonconsideredby the methodology is McLeanand Soden,
inappropriate. 1977
R13 It is difficult to convincetop management to approve the Vacca, 1983
methodology.
R14 Themethodology makesinappropriate assumptions about Yadav,1983
organizationstructure.
R15 Themethodology makesinappropriate assumptions about Yadav,1983
organizationsize.
PlanningProcessSpecified by the Methodology
P1 Themethodology fails to take into accountorganizational King, 1978
goalsandstrategies,
P2 Themethodology fails to assessthe current information Schwartz,1970
systemsapplicationsportfolio.
P3 Themethodology fails to analyzethe currentstrengthsand King, 1984
weaknesses of the IS department.
P4 Themethodology fails to takeinto accountlegal and King, 1984
environmentalissues,
P5 Themethodology fails to assessthe external technological King, 1984
environment.
P6 Themethodology fails to assessthe organization’scompetitive King, 1984
environment.
P7 Themethodology fails to takeinto accountissuesrelated to Zachman,1982
plan implementation.
P8 Themethodology fails to takeinto accountchanges in the
organizationduringSISP.
P9 Themethodology doesnot sufficiently involveusers. Kay,et al., 1980
P10 Managersfind it difficult to answer questionsspecifiedby Boyntonand Zmud,
the methodology. 1984
Pll The methodology requires too muchtop management Bowman, et al., 1983
involvement.
P12 Themethodology requires too muchuser involvement. Boyntonand Zmud,
1984
P13 Theplanningprocedure is rigid. Zachman,1982
P14 Themethodology doesnot sufficiently involvetop Kay, etal.,1980
management.
Table3. (continued)
Outputof the PlanningMethodology
O1 SISPoutputfails to providea statement of organizational McLeanand Soden,
objectivesfor the IS department. 1977
02 SISPoutputfails to designatespecific newsteeringcommittees.
03 SISPoutputfails to identify specificnewprojects. McLeanand Soden,
1977
04 SISPout ~utfails to determine a uniformbasisfor prioritizing King, 1978
projects.
O5 SISPout )ut falls to determine an overalldataarchitecture Zachman,1982
for theorganization.
O6 SISPout )ut fails to providepriorities for developing specific Zachman,1982
databases.
07 SISPout ~utfails to sufficiently address theneedfor Data Sullivan, 1985
Administration in the organization.
O8 SISPout )ut fails to includeanoverall organizational hardware McLeanand Soden,
plan. 1977
09 SISPout )ut fails to includeanoverall organizational data Sullivan, 1985
communications plan.
O10 SISPoutputfails to outline changes in the reportingrelationships
in the IS department.
Oll SISPoutputfails to includean overall personnel andtraining McLeanand Soden,
plan for the IS department. 1977
O12 SISPoutputfalls to includeanoverallfinancialplanfor the McLeanand Soden,
IS department. 1977
O13 SISPoutputfails to sufficiently address the role of a King, 1984
permanent IS planninggroup.
O14 Theoutputplansare not flexible enough to takeinto account McLeanand Soden,
unanticipate.dchanges in the organizationandits environment. 1977
O15 Theoutputis not in accordance with the expectations of top Gi11,1981
management.
O16 Implementing the projectsandthe dataarchitectureidentified Zachman,1982
in the SISPoutputrequiressubstantialfurther analysis.
O17 It is difficult to securetop management commitment for Gill, 1981
implementing the plan.
O18 Theexperiencesfromimplementing the methodology are not Zachman,1982
sufficiently transferable acrossdivisions.
O19 Thefinal outputdocument is not veryuseful. King, 1984
020 TheSISPoutputdoesnot captureall the informationthat Gi11,1981
wasdeveloped duringthe study.
Table6. OverallSatisfaction
Average Satisfied Neutral Dissatisfied
The Methodology 3.55 54% 23% 23%
The ResourcesRequired 3.02 38% 24% 38%
TheMethodology’sProcess 3.68 48% 17% 25%
TheMethodology’sOutput 3.38 55% 17% 28%
CarryingOutthe Plan 2.53 32% 15% 53%
MISQuarterly~September1988 461