A technique used within the business reengineering methodology that ensures, and provides a means for, cross-functional planning and communications. It is a technique used for converting customer needs and satisfiers into quantitative terms.
You searched for: ∨derBy=RANK (∨DERBY=RANK)
492 items found
The purpose of this technique is to prepare for implementation and/or to prepare to pilot selected solution concepts, as a result of reengineering. Activity work flows are always affected by reengineering. Typically, there are procedures and/or policies that govern the current way the activity is performed in enterprises. In ord...
Applying this set of techniques involves the process of scanning the enterprise to relate the social systems present within it and to identify the possible disconnects between the systems and the desired behaviors which they were designed to reinforce. The social systems are the structure to motivate, pay, and drive people to perform a process. This analysis provides a big picture of the social systems within the organization. General categories of analysis include:
A graphic technique to summarize the results of reengineering a complex work flow that comprises a value stream or process. This technique can also be used to help examine the interaction between various resources, human and other parameters, within an organization. Opportunities for improvements in the interactions and/or breakthroughs can be highlighted.
Kiviat diagrams or charts are created to show the degree to which an organization is ready for the type of proposed changes that are a result of a reengineering project.
A technique used to identify all relevant opportunities where information technology can be applied to reengineer the value stream or redesign the business process. Technologies within the enterprise's current portfolio, as well as new emerging technologies which can be acquired, should be included.
To complete the information architecture, it is necessary to analyze the interaction of entity types and activities. Activities can be seen to either Create, Read, Update, or Delete (CRUD) at least one entity type. Entity types, in turn, need to be used by at least one activity. At the architectural level, we want to know answers to the following:
A technique used to identify all the information necessary for achieving certain goals or objectives, such as performing an activity, satisfying customer needs, or making strategic decisions. An information need is an unstructured statement that describes a type of information required by an organizational unit to enable it to meet its objectives and support its functions.
A technique used to compare and contrast the differences between the information architectures before and after redesign or reengineering.
A technique to categorize all ideas, generated in brainstorming sessions, and to identify idea sensitive areas.