When we started the design and information systems, generally use use cases or user stories to describe the various human or automated interactions that are required to comply with its requirements functional and nonfunctional. For years, most of these information systems have had a strong functional dependence, which do not incorporate a vision of processes, including HR and ERP systems have no mechanism to add the scale and time in which the activity should be executed, known in the jargon of IT as service agreements (SLA).
Simplifying my arguments, information systems rarely respond to processes, or a transverse view. It is very common to observe that the activities do not include features such as maximum response time or attention on a task, scaling, persistent variables for decision making, use of metrics, among others. Information systems are generally functional islands which promote loss efforts, governance and value.
need to change the way they are conceptualized and designed the information systems today. The development of an information system should start with process modeling using use cases or user stories to describe the interactions in more detail. This approach has major benefits. First consider the processes, mechanisms that are used to achieve compliance organizational goal or objective, ie the application is explicitly connected with a strategic objective and not to a specific need, which usually does not add value to the organization. Secondly, services are incorporated agreements and business rules required to be taken as a specification. Finally, the information system incorporating a vision to decision making and measurement of variables.
On this approach is necessary: \u200b\u200b
need to change the way they are conceptualized and designed the information systems today. The development of an information system should start with process modeling using use cases or user stories to describe the interactions in more detail. This approach has major benefits. First consider the processes, mechanisms that are used to achieve compliance organizational goal or objective, ie the application is explicitly connected with a strategic objective and not to a specific need, which usually does not add value to the organization. Secondly, services are incorporated agreements and business rules required to be taken as a specification. Finally, the information system incorporating a vision to decision making and measurement of variables.
On this approach is necessary: \u200b\u200b
- Identify decisions can be made based in metric measurement, indicators, critical success factors, among others.
- Identify the processes which support the information system. Model
- processes. The information system must meet the conditions established in the process. I recommend using the graphical notation BPMN 2.0.
- processes should include the establishment of service agreements to measure time and effort required.
- processes should include the establishment of business rules.
- The information system should include in its implementation model service agreements and business rules.
- Identify indicators and outcome management information system to manage. Start
- development.
From my perspective it is necessary to change the paradigm, what I call the " Information Systems Development Process Oriented ." I am currently writing about this approach using a methodology, which share with the community soon.
Greetings;
0 comments:
Post a Comment