IS Week 11

This week in class we covered information based processes, information flows, and process analytics. There are two prominent ways to model information flows. Every information based process has a couple of inalienable traits: an explicit and measurable goal, specific inputs in the form of information, specific outputs in the form of new information, the use of resources, and having an effect on multiple organizational units. Data is generally modeled via Data Flow Diagrams, whereas activities are generally modeled through Flow Charts. The first thing an analyst must do when modeling a process is identify where the process begins and where it ends. If it is ever unclear how detailed a process should be, an analyst should air on the side of generality, choosing instead to refer to subprocesses that can in turn be modeled on their own. In the modeling of processes, different actors become involved. Popular actors include customers, employees, suppliers, and regulatory agencies. Process models are built so as to do one or more of the following: document a business or some other process, identify weaknesses in a process, evaluate improvements to the process, communicate business logic to the stakeholders, communicate business logic to stakeholders, aid in the automation of business processes through information systems, gain consensus amongst stakeholders, facilitate on-boarding of new employees, or meet regulatory compliance needs. If the goal is to redesign a process, first the general type of flaw that exists in the process must first be diagnosed. A process can either be inefficient, be out of date, or not exist at all. In order to model a process you must first engage in process elicitation. Process elicitation first involves observation. Once process elicitation has been done, then process visualization can be done.

https://simplicable.com/new/information-flow