The players - System Stakeholders :- Let's assume you are in a position to help build and information system. Who are the stakeholders in this system? Stakeholders for information systems can be broadly classified into the five groups shown on the left hand side of the given chart. Notice that each stakeholder group has different perspective of the same information system.
The system analyst is a unique stakeholder in this given chart. The systems analyst serves executive information as a facilitator or coach, bridging the communications gap that can naturally develop between the non-technical system owners and users and the technical system designers and builders.
All the above stakeholders have one thing is common - They are what the U.S. Department of labor calls information workers. The livelihoods of the information workers depend of decision made based on information. Today more than 60 percent of the U.S. labor force is involved in producing, distributing, and using information. Let's examine the five group of information workers in greater details.
Let's briefly examine the perspectives of each group. But before we do so, we should point out that these group actually define "role" played in systems development. In practice, any individual person may play more than one of these roles. For example, a system owner might also be a system user, Similarly, a system analyst may also be a system designer, and a system designer also be a system builder. Any combination may work.
Systems Owners:
For any information system, large of small, there will be one of more System Owners. System owners usually come from the ranks of management. For medium to large information system, system owners arc usually middle or executive managers. For the smaller systems, system owners may the middle manages or supervisors. System owners tend to be interested in the bottom line how much will the system cost? How much value or what benefits can be measured in different ways, as noted in the margin checklist.
System Users:
System user make up the vast majority of the information workers in any information system.Unlike system owners, system users tend to be less concerned with the costs and benefits of the system. Instead, as illustrated in chart, they are concerned with the die functionality the system provides to their jobs and the system's ease of learning and ease of use. Although users have become more technology-literate over the years, the primary concern is to get the job done. Consequently, decisions with most users need to be kept at the business requirements level as opposed to the technical requirements level. Much of this site is dedicated to teaching you how to effectively identify and communicate business requirements for an information system.
There are many classed of system users. Each class should be directly involved in any information system development project that affects them lets briefly examine these classes.
Stakeholders perspective of an information system.
The system analyst is a unique stakeholder in this given chart. The systems analyst serves executive information as a facilitator or coach, bridging the communications gap that can naturally develop between the non-technical system owners and users and the technical system designers and builders.
All the above stakeholders have one thing is common - They are what the U.S. Department of labor calls information workers. The livelihoods of the information workers depend of decision made based on information. Today more than 60 percent of the U.S. labor force is involved in producing, distributing, and using information. Let's examine the five group of information workers in greater details.
Let's briefly examine the perspectives of each group. But before we do so, we should point out that these group actually define "role" played in systems development. In practice, any individual person may play more than one of these roles. For example, a system owner might also be a system user, Similarly, a system analyst may also be a system designer, and a system designer also be a system builder. Any combination may work.
Systems Owners:
For any information system, large of small, there will be one of more System Owners. System owners usually come from the ranks of management. For medium to large information system, system owners arc usually middle or executive managers. For the smaller systems, system owners may the middle manages or supervisors. System owners tend to be interested in the bottom line how much will the system cost? How much value or what benefits can be measured in different ways, as noted in the margin checklist.
System Users:
System user make up the vast majority of the information workers in any information system.Unlike system owners, system users tend to be less concerned with the costs and benefits of the system. Instead, as illustrated in chart, they are concerned with the die functionality the system provides to their jobs and the system's ease of learning and ease of use. Although users have become more technology-literate over the years, the primary concern is to get the job done. Consequently, decisions with most users need to be kept at the business requirements level as opposed to the technical requirements level. Much of this site is dedicated to teaching you how to effectively identify and communicate business requirements for an information system.
There are many classed of system users. Each class should be directly involved in any information system development project that affects them lets briefly examine these classes.