Academia.eduAcademia.edu

Figure 5 – uploaded by Bálint Molnár

See full PDFdownloadDownload figure
Figure 5: A Multi-dimensional model for interaction of Information Systems and Documents

Figure 5 A Multi-dimensional model for interaction of Information Systems and Documents

Related Figures (6)

interactive documents and the emphasis on Web intertaces led to the concept of modern Information Systems. Beneath Information Systems there is a set of data that delivers the required information either to the business activities or to the information processes. During analysis, the question that is investigated is as to whether what information should be kept in the system. The data and their collections exist independently from business documents that may or may not related to decision processes. The modeling of Information Systems focused on document should adhere to established practices of data and information modeling. The model should be perceivable by users at high level. The approach for modeling and analysis should be semantically powerful in order to serve as a basic model and be understandable by users. The document-centric model is unlike to the data model but they are interdependent on each other. The document model tries to gather the transformations and the results of activities to extend information on documents with new facts. Figure 1: Levels of collections related to documents
interactive documents and the emphasis on Web intertaces led to the concept of modern Information Systems. Beneath Information Systems there is a set of data that delivers the required information either to the business activities or to the information processes. During analysis, the question that is investigated is as to whether what information should be kept in the system. The data and their collections exist independently from business documents that may or may not related to decision processes. The modeling of Information Systems focused on document should adhere to established practices of data and information modeling. The model should be perceivable by users at high level. The approach for modeling and analysis should be semantically powerful in order to serve as a basic model and be understandable by users. The document-centric model is unlike to the data model but they are interdependent on each other. The document model tries to gather the transformations and the results of activities to extend information on documents with new facts. Figure 1: Levels of collections related to documents
The artifact-centric business process model uses three basic concepts: artifact classes, tasks, and busines: tules*”’. The tasks handle the artifacts, the business rules govern which tasks should be triggered and which artifact will be manipulated'*"’. Figure 2: Class Diagram for Documents at “Document Conceptual Level” within a Case Study
The artifact-centric business process model uses three basic concepts: artifact classes, tasks, and busines: tules*”’. The tasks handle the artifacts, the business rules govern which tasks should be triggered and which artifact will be manipulated'*"’. Figure 2: Class Diagram for Documents at “Document Conceptual Level” within a Case Study
To combine the previously referred approaches to model modern Information Systems, there are various proposals'*”°”', Blokdijk’s assembly of Information System Models> offers structuring principles, moreover the axiomatic design approach” can be employed for the Information Systems provides clues for both theoretic and practical modeling point of view. The concept of generalized hypergraph® seems to be a proper mathematical formalism that fits to unifving all viewpoints. perspectives. artifacts and modeling elements. Figure 3: Class Diagram for Documents Class Diagram for Documents at “Data Model Conceptual Level” within a Case Study
To combine the previously referred approaches to model modern Information Systems, there are various proposals'*”°”', Blokdijk’s assembly of Information System Models> offers structuring principles, moreover the axiomatic design approach” can be employed for the Information Systems provides clues for both theoretic and practical modeling point of view. The concept of generalized hypergraph® seems to be a proper mathematical formalism that fits to unifving all viewpoints. perspectives. artifacts and modeling elements. Figure 3: Class Diagram for Documents Class Diagram for Documents at “Data Model Conceptual Level” within a Case Study
included in documents should be traced, i.e. creating, modifying data items, establishing new relationship; the precedence analyses is an available option for tracking the impacts”. The chain of events and processes can be monitored through roles/actors and their handling of identifiable datz tems within documents. The human roles stimulate data processing activities that effects documents, consequently he data items as well that are included in the documents. The document-subdocument structure (Figure 1, Figure 2. ‘igure 3) is able to represent both the organization and the information model at the same time. Whilst the datz nodel is not structured as set of swb-data models instead it displays rather uniform configuration’ (Figure 5) 3lokdijk’s model offers a structuring approach for perceiving Information Systems. The model’s major component: re: (1) organizational model (2) information model; (3) data model; (4) process model. The process mode! rovides the composition of business activities and it is strongly coupled to the control structure. However, the date nodel is not an exact representation of the organization structure. For the reason that patterns of data model reflec’ he relevant facts about the organization but it does not map the organization structures. The document and date nodel requires a common representational method in which the services, and functions of documents, the couplec yusiness activities can be depicted in a uniform manner. Furthermore, the interrelationships between the data anc locument model can be shown as much the same way as possible. There is logic of inheritance to identify data items vithin documents. Within the document chain, data elements are inherited from the previous element of documents. Towever, the responsibility for recognizing the proper data items relates to the currently valid system role (human o1 usiness process). The previously published figure’ (Figure 5) has been extended to designate the name space o1 Jocument’s DBMS, emphasize the mutual mapping between the information related to control and business rocesses, and to pinpoint to set of models that play a crucial role in integration of enterprises and informatior ystems.
included in documents should be traced, i.e. creating, modifying data items, establishing new relationship; the precedence analyses is an available option for tracking the impacts”. The chain of events and processes can be monitored through roles/actors and their handling of identifiable datz tems within documents. The human roles stimulate data processing activities that effects documents, consequently he data items as well that are included in the documents. The document-subdocument structure (Figure 1, Figure 2. ‘igure 3) is able to represent both the organization and the information model at the same time. Whilst the datz nodel is not structured as set of swb-data models instead it displays rather uniform configuration’ (Figure 5) 3lokdijk’s model offers a structuring approach for perceiving Information Systems. The model’s major component: re: (1) organizational model (2) information model; (3) data model; (4) process model. The process mode! rovides the composition of business activities and it is strongly coupled to the control structure. However, the date nodel is not an exact representation of the organization structure. For the reason that patterns of data model reflec’ he relevant facts about the organization but it does not map the organization structures. The document and date nodel requires a common representational method in which the services, and functions of documents, the couplec yusiness activities can be depicted in a uniform manner. Furthermore, the interrelationships between the data anc locument model can be shown as much the same way as possible. There is logic of inheritance to identify data items vithin documents. Within the document chain, data elements are inherited from the previous element of documents. Towever, the responsibility for recognizing the proper data items relates to the currently valid system role (human o1 usiness process). The previously published figure’ (Figure 5) has been extended to designate the name space o1 Jocument’s DBMS, emphasize the mutual mapping between the information related to control and business rocesses, and to pinpoint to set of models that play a crucial role in integration of enterprises and informatior ystems.
Figure 6: Information Systems’ model in a document-centric approach.
Figure 6: Information Systems’ model in a document-centric approach.
A database-centric Information System model that is based on an information theory approach’ outlines a framework that describes the input, output and query processing. Figure 6 contains the Information System model indicated by the dashed red line; the previously published version’® is enhanced to express that the source code data outside of the system and the code generated by the information system towards destination are communicated through a crust consisting of documents. In computerized systems, interactive documents and Web services become visible on the source and the output side. Free documents appear at the interface/fagade level. The system roles (either human or automated system) perform variable valuation, or binding at each single variable through simple tasks. The business activities consist of tasks, a task can be composed of elementary tasks. An elementary task can be coupled to specific variables and its manipulation. The end-users who typically use information can retrieve data through documents, e.g. querying and fetching data from database and then processing the obtained responses.
A database-centric Information System model that is based on an information theory approach’ outlines a framework that describes the input, output and query processing. Figure 6 contains the Information System model indicated by the dashed red line; the previously published version’® is enhanced to express that the source code data outside of the system and the code generated by the information system towards destination are communicated through a crust consisting of documents. In computerized systems, interactive documents and Web services become visible on the source and the output side. Free documents appear at the interface/fagade level. The system roles (either human or automated system) perform variable valuation, or binding at each single variable through simple tasks. The business activities consist of tasks, a task can be composed of elementary tasks. An elementary task can be coupled to specific variables and its manipulation. The end-users who typically use information can retrieve data through documents, e.g. querying and fetching data from database and then processing the obtained responses.
Related topics:
Information SystemsService Oriented ArchitectureProcess AlgebraZachman framework
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved