Overview of System Analysis

Going through what ‘System Analysis’ is about, lets have a quick definition of it.

The Study of a business problem domain to recommend improvements and specify the business requirements and priorities for the solution.

System analysis helps to provide the team the better understanding of the problem domains that is needed to be focused on it. Here the research is to be made of what works and find if there is any solution that works even better that existing one. As we know that working with the system users, there requires the clear business requirements and expectations that needs to be developed. One more thing that affects the system analysis is ‘Business drivers’. Completion of analysis, leads in need to update of many deliverables produced earlier, during system initiation. But this reveals many ideas and the revision of the project goals and also the business scope. The idea leads us to know whether the project is small or too big. It also gives us the ideas of the schedule and budget. And after all this the feasibility itself becomes clear. If the project is feasible then the project can be continued else it can be cancelled.

We all know that the project managers, system analysts and system users are the primary stakeholders in the system analysis.

Stakeholders, The Players of an Information System

When we come to the designing of the information system, a term often make us think; Who are Stakeholders? so let us define this with the formal definition and it goes like this.

Any person who has interests in an existing or proposed information system. Stakeholders may include both technical and non-technical workers. They also may be the internal ones or may be the external one.

So I think the idea of ‘Who are stakeholders?’ has come to the mind. In building the information system the system owners, system users, system designers, system builders and all of the above system analysts and the project managers all these are commonly known as the stakeholders. Whatever their roles in an organization are it doesn’t matter, all the thing common in them are that, they are information workers. Let us explore a little deep to the stakeholders:

  • System Owners
  • System Users
    • Internal System Users
      • Clerical and Service workers
      • Technical and professional staffs
      • Supervisors, Middle managers and executive managers
    • External System User
      • Customers
      • Suppliers
      • Partners
      • Employees
  • System Designers
    • Database Administrators
    • Network Architects
    • Web Architects
    • Graphics Artists
    • Security Experts
    • Technology specialists
  • System Builders
    • Application programmers
    • System programmers
    • Databases Programmers
    • Network Administrators
    • Security Administrators
    • Webmasters
    • Software Integrators
  • System Analysts