The complexity of software-based systems has increased significantly, especially with regards to capturing requirements along with dependencies among requirements. A conceptual model is a way of thinking about and making sense of the real world s complexities. In this paper, we focused on two approaches in this context: (a) multiple models applied to the same system with simultaneous usage of dissimilar notations vs. (b) a single model that utilizes a single framework of notations. In the first approach, inconsistencies arise among models that require a great deal of painstaking discipline and coordination between them. The multiple-model notion is based on the claim that it is not possible to present all application views in a single representation, so diverse models are used, with each model representing a different view. This article advocates a second approach that utilizes a single model with multilevel (static/dynamic and behavioral) specification. To substantiate this approach s feasibility, we embrace the occurrence-only model, which comprises (a) Stoic ontology, (b) thinging machine (TM) language and (c) Lupascian logic. In this paper, we focus on TM modeling as the mechanism of single-model building. We claim that a TM can be a unifying diagrammatic language for virtually all current modeling languages. To demonstrate such a claim, we redraft almost all the diagrammatic representations in The Handbook of Requirements Modeling of the International Requirements Engineering Board. This redrafting includes context, class, activity, use case, data flow and state diagrams. The results seem to indicate that there are no difficulties in representing all views in TM.

翻译：软件系统的复杂性显著增加，尤其是在捕获需求及其依赖关系方面。概念模型是一种思考并理解现实世界复杂性的方式。本文聚焦于该背景下的两种方法：(a) 对同一系统同时使用不同表示法的多重模型，与(b) 采用单一表示法框架的单一模型。第一种方法下，模型间会因需要大量严格的规范与协调而产生不一致。多重模型概念基于一种主张，即无法在单一表示中呈现所有应用视图，因此采用多种模型，每种模型代表不同视图。本文倡导第二种方法，即使用具备多层次（静态/动态及行为）规范的单一模型。为验证该方法的可行性，我们采纳了纯事件模型，该模型包含：(a) 斯多葛本体论、(b) 事物化机器语言，以及(c) 卢帕西逻辑。本文重点研究事物化机器建模作为单一模型构建的机制。我们声称事物化机器可成为当前几乎所有建模语言的统一图示语言。为证明这一主张，我们重制了国际需求工程委员会《需求建模手册》中几乎所有的图示表示法，包括上下文图、类图、活动图、用例图、数据流图及状态图。结果表明，在事物化机器中表示所有视图不存在困难。