1 determining the high-level direction of information systems part 2

41
1 Determining the High-level Direction of Information Systems Part 2

Upload: joel-phelps

Post on 20-Jan-2016

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1 Determining the High-level Direction of Information Systems Part 2

1

Determining the High-level

Direction of Information

Systems

Part 2

Page 2: 1 Determining the High-level Direction of Information Systems Part 2

2

Computing ArchitectureComputing Architecture

Looking at the IS mission, objectives, and goals, you can determine what technical requirements (computing architecture) are necessary to meet the IS objectives.

Page 3: 1 Determining the High-level Direction of Information Systems Part 2

3

IS Objectives and Computing Architecture

IS Objectives and Computing Architecture

Page 4: 1 Determining the High-level Direction of Information Systems Part 2

4

A Detailed Description of The Computing

Architecture

A Detailed Description of The Computing

Architecture 5.23

Page 5: 1 Determining the High-level Direction of Information Systems Part 2

5

Page 6: 1 Determining the High-level Direction of Information Systems Part 2

6

Page 7: 1 Determining the High-level Direction of Information Systems Part 2

7

Page 8: 1 Determining the High-level Direction of Information Systems Part 2

8

Page 9: 1 Determining the High-level Direction of Information Systems Part 2

9

Page 10: 1 Determining the High-level Direction of Information Systems Part 2

10

Information ArchitectureInformation Architecture

For an organization with various locations, the question is often raised as to:

* what information resides at each site,

* what information is necessary at a corporate level, and

* what information must be shared across sites.

Page 11: 1 Determining the High-level Direction of Information Systems Part 2

11

Table 5.1

Page 12: 1 Determining the High-level Direction of Information Systems Part 2

12

Table 5.1

Page 13: 1 Determining the High-level Direction of Information Systems Part 2

13

Table 5.1

Page 14: 1 Determining the High-level Direction of Information Systems Part 2

14

CRUD CriteriaCRUD Criteria

You can further clarify Table 5.1 with:

C = CreateR = ReplaceU = UpdateD = Delete

Page 15: 1 Determining the High-level Direction of Information Systems Part 2

15

Policies and Responsibilities

Policies and Responsibilities

You need to identify IS’s policies and responsibilities.

Having policies and responsibilities w ell documented can save hours of frus

tration for both users and IS personnel.

Be sure to update this information fre quently and provide all users with con venient access to it.

Page 16: 1 Determining the High-level Direction of Information Systems Part 2

16

Find out Policies and Responsibilities

Find out Policies and Responsibilities

What is the standard PC hardware that ISU supports ?

What is the standard PC software that ISU supports ?

Who is responsible for budgeting acquisition of PCs ? To whom does the PC belong?

Who is responsible for ensuring optimum pricing on PC hardware and software ?

Who is responsible for budgeting PC software ?

Page 17: 1 Determining the High-level Direction of Information Systems Part 2

17

Find out Policies and Responsibilities

Find out Policies and Responsibilities

How does the organization manage PC retirement and who is responsible ? What methods do you utilize for PC disposal ?

What standards does the organization follow for user - developed PC applications ?

What is the company policy regarding PC games and Internet access ?

Page 18: 1 Determining the High-level Direction of Information Systems Part 2

18

Find out Policies and Responsibilities

Find out Policies and Responsibilities

Who is responsible for organizing and funding PC training ?

What is the responsibility of any remote sites of ISU ? And what is the responsibility of the central ISU ?

What is the responsibility of the users and ISU for new business applications or projects ?

Page 19: 1 Determining the High-level Direction of Information Systems Part 2

19

Annual ObjectivesAnnual Objectives

Clearly state what ISU will do and will not do in the coming year so that everyone has common expectations.

This is done through agreed-upon and prioritized annual objectives.

ISSC is the one doing the prioritization process.

Page 20: 1 Determining the High-level Direction of Information Systems Part 2

20

Annual ObjectivesAnnual Objectives

Complete the prioritization only for projects above a certain level of effort or cost.

* This hard level should be done by ISSC.

Small projects can be handled by ISU itself.

Page 21: 1 Determining the High-level Direction of Information Systems Part 2

21

Different Prioritization Processes

Different Prioritization Processes

Prioritization by business objective.

Prioritization by forced ranking. Prioritization by performance

impact criteria.

Page 22: 1 Determining the High-level Direction of Information Systems Part 2

22

Prioritizing by Business Objective

Prioritizing by Business Objective

A) List the business objectives. (Identified i n Phase 1 : Conceptual Business Level)

B) Ranktheimportanceofeachbusinessobjectiveon a scal e of 5t o 15, wi t h 15bei ng t h emost i mpor t ant .

C) Listal l I S pr oj ect s.

*If the list is too long, have ISSC identify a - nyl owpr i or i t y pr oj ect s t hat wi l l not be prioritizedand j ust l i st t he pr oj ect s t o be pr i oritized.

Page 23: 1 Determining the High-level Direction of Information Systems Part 2

23

Prioritizing by Business Objective

Prioritizing by Business Objective

D) Identify the impact (1-10) each project will have on the business objectives.

E) Multiply the impact with the business objective importance and total the score for each project.

F) List projects in descending total score for a prioritized list of projects.

Page 24: 1 Determining the High-level Direction of Information Systems Part 2

24

Prioritizing by Forced Ranking

Prioritizing by Forced Ranking

A) List all IS projects (Cut low - priority projects by ISSC).

B) Go through a forced ranking process by comparing the first project with the second, the first project with the third, fourth, and so on through the entire list to find out the project with highest ranking. Then compare the second project with the third,

fourth, fifth, and so on to find out the project with second highest ranking.

The projects with highest ranking will bubble up on the top.

Page 25: 1 Determining the High-level Direction of Information Systems Part 2

25

Prioritizing by Performance Impact

Criteria

Prioritizing by Performance Impact

CriteriaA) Identify performance impact criteria,

such as:* impact on customers* impact on quality of

service/product* impact on reduction of business

costs* impact on employees* impact on the speed of the process

Page 26: 1 Determining the High-level Direction of Information Systems Part 2

26

Prioritizing by Performance Impact

Criteria

Prioritizing by Performance Impact

CriteriaB) Rank the importance of the

performance impacts (0-10). This number will become the project multiplier.

C) List all IS projects.D) Through ISSC, agree on the impact

an IS project will have on each of the performance impact criteria. Rate that impact on a scale of 0-10.

Page 27: 1 Determining the High-level Direction of Information Systems Part 2

27

Prioritizing by Performance Impact

Criteria

Prioritizing by Performance Impact

CriteriaE) Multiply the project multiplier

in B with the rating for the project in D. Add up the total points for a project score.

F) List the projects in descending score order for a prioritized list of projects.

Page 28: 1 Determining the High-level Direction of Information Systems Part 2

28

IS Service Architecture IS Service Architecture

Service architecture is the blueprint that specifies which IS processes (งานอะไรบ้�าง) and what kinds of people are required to support the business systems and computing architecture.

The service architecture should include: processes, people, organization,

culture, technology, metrics.

Page 29: 1 Determining the High-level Direction of Information Systems Part 2

29

Service ArchitectureService Architecture Processes : Major functions of ISU. People : H iring, skill development, and co

mpensation practices. Organization : Internal structure of ISU. Culture : Values/beliefs held within ISU. Technology : Characteristics of impleme

nted and supported technology. Metrics : Methods of providing and ensuri

ng quality.

Page 30: 1 Determining the High-level Direction of Information Systems Part 2

30

PeoplePeople

Business Area Experts* Specialization by business processes* Specialized knowledge of business systems that support those business processes* General knowledge of technology

Page 31: 1 Determining the High-level Direction of Information Systems Part 2

31

PeoplePeople

Application Experts* Specialization by type of business system* Specialized knowledge of business systems capabilities, operations, and supporting tools* General knowledge of technology and business processes

Page 32: 1 Determining the High-level Direction of Information Systems Part 2

32

PeoplePeople

Technology Experts* Specialization by technology component* Specialized knowledge of technology component capabilities, operations, and supporting tools* General knowledge of business systems and business processes

Page 33: 1 Determining the High-level Direction of Information Systems Part 2

33

ProcessesProcesses

Projects* Deployment of new systems* Substantial additions to existing system capabilities* Substantial revisions to existing system capabilities

Page 34: 1 Determining the High-level Direction of Information Systems Part 2

34

ProcessesProcesses

Enhancements* Minor revisions to existing system capabilities* Minor additions to existing system capabilities

Page 35: 1 Determining the High-level Direction of Information Systems Part 2

35

ProcessesProcesses

Support* Operations* Maintenance* Troubleshooting* Consulting

Page 36: 1 Determining the High-level Direction of Information Systems Part 2

36

Questions that May Help Improve ISU

Questions that May Help Improve ISU

Is ISU providing all the IS functions that are necessary? Are users providing support that ISU should?

Are the IS processes efficient? Are user inquiries handled quickly and efficiently? Are user satisfied with the support? Why or why not?

Page 37: 1 Determining the High-level Direction of Information Systems Part 2

37

Questions that May Help Improve ISU

Questions that May Help Improve ISU

Are you hiring people with the skill set you require? Are you providing the proper development/learning for employees? Can employees cross into other areas of Information Systems and obtain cross-training?

What has been the turnover within ISU? What have been some of the reasons for leaving?

Page 38: 1 Determining the High-level Direction of Information Systems Part 2

38

Questions that May Help Improve ISU

Questions that May Help Improve ISU

Are compensation policies aligned with market demands? Have you had significant turnover due to salaries?

Is the organization structured efficiently? Do you have the functions you will need in the future? Do job descriptions and titles accurately depict the functions that are needed today as well as in the future?

Page 39: 1 Determining the High-level Direction of Information Systems Part 2

39

Questions that May Help Improve ISU

Questions that May Help Improve ISU

Aret he val ues r efl ect ed t hr ough daily decisions?

Doest he or gani zat i on under st and the direction?

How do you measure ISU’s effici ency and effectiveness?

Page 40: 1 Determining the High-level Direction of Information Systems Part 2

40

Plan ContentsPlan Contents

VII. Information Systems DirectionA. MissionB. VisionC. Strategic ObjectivesD. StrategiesE. Information Systems and the Business GoalsF. Computing Architecture

Page 41: 1 Determining the High-level Direction of Information Systems Part 2

41

Plan ContentsPlan Contents

G. Information ArchitectureH. Policies and ResponsibilitiesI. Information Systems Annual ObjectivesJ . Service Architecture