A Business Model, that is elaborated to a desirable level of detail, can
very well serve as a reference when making decisions. For the Model can
of course comprise any aspect that is relevant to the decisions to be made.
Some possibilities:
Some possibilities:
- Projection on the Model of legacy systems;
- Projection on the Model of packages to be reviewed;
- Projection on the Model of the various steps in a migration strategy;
- Projection on the Model of the consequences of Business Process Redesign;
- Projection on the Model of the process parts to be computerized and the process parts not to be computerized;
- Projection on the Model of the interaction between data processing and physical streams.
Software package implementation in an organization can very well be
analized, when there are legacy systems to be kept and new functionality
to be added. An implementation strategy results from the outcomes in
the Model.
Both the system parts to be kept and the software package to be implemented,
have to be embedded in an adequate functional server supplying the
corresponding services.
When system or package options are not to be used, they are not included
as service in the embeddding server.Any overlap in projection (see above) means that overlapping information systems and software packages must be embedded in the same server (see at right).
| < to previous page | to top of document ˆ | to next page > |
