|
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
| |||||
The subject of systems analysis and design is the information system. Many people will be familiar with terms such as information technology (I.T.) and information systems (I.S.). However, the terms are not synonymous. Think of information technology as the actual software and hardware used to build an information system. The information system itself is a more encompassing term that covers not only the technology but also the intelligent management and manipulation of business data. Additionally, information systems also involve human interaction and other non-technological factors. A business will rely on various information systems, each one designed to support and improve a specific set of day-to-day operations, or to enable business problem-solving and decision-making. | |||||
| |||||
The information system can be broken into three* main areas of concern | |||||
| |||||
| |||||
* Some experts will argue for a fourth area of concern, the communication / networking component. | |||||
| |||||
|
| |||||
 | |||||
As illustrated in the diagram above, the different yet complimentary points of view of all groups of system stakeholders, with respect to the three main areas of the system, are part of any analysis and design project. | |||||
| |||||
| |||||
The three focuses of an information system project, regardless of the size, will involve
the system stakeholders at different levels of specificity. System owners will possess a more “global” view of
the information system’s role within their business. In other words, how does this system help them achieve the
overall objectives of their organization, including maximizing profitability, decreasing risks, and serving their
customers, employees, and shareholders? System users may have similar concerns, but as their involvement with the
information system will be on a more direct day-to-day basis, these stakeholders will have expectations, requirements,
and knowledge that will be immensely important during analysis and design. What are the data requirements for the system?
How will the system handle certain processes? What will the system look like? All of these questions can be answered by
key system users, also known as user community representatives, during systems analysis and design. The designers, technicians, and
programmers who create the system will relate to it differently, with an eye toward how it operates from a nuts-and-bolts perspective.
Of course, these stakeholders must seek and rely on the direction provided by system owners and users; otherwise, the system will
fail to deliver expected results since those who create the system are usually not the ones who will rely on its operation.
Finally, those people who have a stake in supporting the system after it is completed will bring their own point of view.
