Examples of 'classes' of functional servers are: business object management,
data administration, event control/scheduling, knowledge management and
structure administration. It might well be clear that it is absolutely not
obligatory to design and construct all these servers in the same manner or
conforming the same principles. Behaving themselves as servers to their
clients in conformation with a pre-arranged protocol will do.
Business object management servers might very well be internally
designed conforming a data oriented approach. In that case there is
a 'local' partial data model only for the server, and the retrieve and update
functionality are disposed through the server's services.
A scheduler (event controller) is perhaps better designed and realized using an event oriented approach. Key problem here is mechanism and not
administration.
Low-structurable business objects, such as all kinds of regulations
or flexible product specifications, might best be designed using a pure
object oriented approach. In this case, the business objects to be administrated
will be specified in the server using an OO modelling tool. A fixed meta
structure is not required using this method, which influences flexibility for good.
Additionally, OO is best fit for real world modelling.
- Knowledge might best be implemented as knowledge system. This requires
an approach totally different from that of the definition of object structures.
- DeskTop Publishing functionality doesn't need to be structured, when
implementing existing DTP-software. In this case functional separation
will do.
- Finally, the integrating mechanism for the clients could be established as a user view program library.
Besides their own internal organization (structure) functional servers also
contain 'contents'.
For business object administration these contents will only be maintained in an implemented (information) system. But with all kinds of knowledge this will not be the case at all. Typical on knowledge is that it will be already there at the moment of implementation of a system.
For business object administration these contents will only be maintained in an implemented (information) system. But with all kinds of knowledge this will not be the case at all. Typical on knowledge is that it will be already there at the moment of implementation of a system.
Examples of frequently used knowledge are: knowledge on products, on
legislation, on official procedures, on the market, branch typical knowledge,
organization-type typical knowledge.
It is possible to realize implementations that do already contain any knowledge. Therefore, beside their role in implemented (information) systems, functional servers can also serve as part of reference models and consultancy supporting models.
It is possible to realize implementations that do already contain any knowledge. Therefore, beside their role in implemented (information) systems, functional servers can also serve as part of reference models and consultancy supporting models.
| < to previous page | to top of document ˆ | to next page > |
