A Look Behind Conceptual Modeling Constructs in Information System Analysis and Design

Information systems can be conceptualized in a number of ways. Most methodologies propose to analyze separately process and data semantics by projecting them into totally different diagram types. This system analysis and design tradition is very strong in most modeling approaches such as structured analysis as well as object-oriented design. Structural and behavioral aspects are complementary. They cannot be analyzed in isolation. Lack of a conceptual modeling approach, which can be used for verification of semantic integrity among various types of diagrams, is the cornerstone of frustration for information system architects. Inconsistency, incompleteness and ambiguity of conceptual views create difficulties in verification and validation of technical system architectures by business experts, who determine the organizational strategies. Consequently, the traditional information system methodologies are not able to bridge a communication gap among business experts and IT-system designers. Various interpretations of semantic relations in conceptual modeling approaches make the system analysis and design process more art than science. It creates difficulties to formulate comprehensible principles of decomposition and separation of concerns. Unambiguous definition of aggregation and generalization is necessary for breaking down information system functionality into coherent non-overlapping components. This article concentrates on conceptual modeling enhancements, which help to avoid semantic integrity problems in conceptualizations on various levels of abstraction. The presented conceptual modeling approach is based on a single type of diagram, which can be used for reasoning on semantic integrity between business process and data across organizational and technical system boundaries.