Petri nets: an introduction
A comparative evaluation of system development methods
Proc. of the IFIP WG 8.1 working conference on Information systems design methodologies: improving the practice
Can the field of MIS be disciplined?
Communications of the ACM
Comparing representations with relational and EER models
Communications of the ACM
An Ontological Model of an Information System
IEEE Transactions on Software Engineering
Communications of the ACM - Special issue on analysis and modeling in software development
A reappraisal of structured analysis: design in an organizational context
ACM Transactions on Information Systems (TOIS)
A unified model of software and data decomposition
ICIS '91 Proceedings of the twelfth international conference on Information systems
Process innovation: reengineering work through information technology
Process innovation: reengineering work through information technology
Reengineering: business change of mythic proportions?
MIS Quarterly
An overview of workflow management: from process modeling to workflow automation infrastructure
Distributed and Parallel Databases - Special issue on software support for work flow management
Information systems development and data modeling: conceptual and philosophical foundations
Information systems development and data modeling: conceptual and philosophical foundations
Anchoring data quality dimensions in ontological foundations
Communications of the ACM
IBM Systems Journal
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Petri Net Theory and the Modeling of Systems
Petri Net Theory and the Modeling of Systems
Aris-Business Process Frameworks
Aris-Business Process Frameworks
Business Process Engineering
Aris--Business Process Modeling
Aris--Business Process Modeling
Information Systems Methodologies; A Framework for Understanding, 2nd Ed.
Information Systems Methodologies; A Framework for Understanding, 2nd Ed.
Object-Oriented Meta Modelling
OOER '95 Proceedings of the 14th International Conference on Object-Oriented and Entity-Relationship Modelling
Petri Net Based Certification of Event-Driven Process Chains
ICATPN '98 Proceedings of the 19th International Conference on Application and Theory of Petri Nets
A Paradigmatic Analysis Contrasting Information Systems Development Approaches and Methodologies
Information Systems Research
SAP R/3 Business Blueprint - The Complete Video Course
SAP R/3 Business Blueprint - The Complete Video Course
A new approach to business processes
IBM Systems Journal
Design Principles for Application Integration
CAiSE '00 Proceedings of the 12th International Conference on Advanced Information Systems Engineering
Guidelines of Business Process Modeling
Business Process Management, Models, Techniques, and Empirical Studies
Comparing the control-flow of EPC and petri net from the end-user perspective
BPM'05 Proceedings of the 3rd international conference on Business Process Management
| Hi-index | 0.00 |
Process modelling has gained prominence in the information systems modelling area due to its focus on business processes and its usefulness in different business improvement methodologies. However, process modelling techniques are not without their criticisms. This paper proposes and uses the Bunge-Wand-Weber (BWW) representation model to analyse the four views - process, data, function, and organisation - provided in the Architecture of Integrated Information Systems (ARIS) popularised by Scheer [39, 40, 41]. The BWW representation model attempts to provide a theoretical base on which to evaluate and thus contribute to the improvement of information systems modelling techniques. The analysis conducted in this paper prompts some propositions. Among others, it confirms that the process view alone is not sufficient to model all the real-world constructs required. However, even when considering all four views in combination, problems may arise in representing all potentially required business rules, and specifying the scope and boundaries of the system under consideration, and employing a "top-down" approach to analysis and design.