Abstract The paper proposes universal conceptual modeling, conceptual modeling that strives to be as general-purpose as possible and accessible to anyone, professionals and non-experts alike. The idea of universal conceptual modeling is meant to catalyze new thinking in conceptual modeling and be used to evaluate and develop conceptual modeling solutions, such as modeling languages, approaches for requirements elicitation, or modeling tools. These modeling solutions should be usable by as many people and design agents as possible and for as many purposes as possible, aspiring to the ideals of universal conceptual modeling. We propose foundations of universal conceptual modeling in the form of six principles: flexibility, accessibility, ubiquity, minimalism, primitivism, and modularity. We then demonstrate the utility of these principles to evaluate existing conceptual modeling languages and understand conceptual modeling practices. Finally, we propose future research opportunities meant to realize the ideals of universal conceptual modeling.

One opportunity for organizations to participate in open source software (OSS) development is throughorganizations OSS(orgsOSS), a term we use to describe a group of organizations that commit resources to collectively develop OSS. This archetype of OSS development is distinct from other types that include organizations, yet is understudied. As organizations increasingly contribute to and rely on OSS as part of their strategy, understanding how they can collaborate to build software holds importance for the future of software development. This study collects a unique dataset of development tasks from a large orgsOSS project spanning over two years and seven releases. Building on existing OSS research, we explore norms with respect to collaboration, i.e., how developers assign, discuss, and complete tasks, in an orgsOSS project. Interestingly, our analysis reveals that developers in orgsOSS do not always adhere to ideals of widespread sharing and participation espoused by traditional OSS, however some developer and task characteristics helped foster these ideals. Based on these and other findings, we develop a set of propositions and associated collaboration mechanisms that are important to future orgsOSS and other similarly structured software development projects.

While many conceptual modelling grammars have been developed since the 1970s, they share the general assumption of representation by abstraction; that is, representing generalised knowledge about the similarities among phenomena in a domain (classes) rather than about domain objects (instances). This assumption largely ignores the fundamental role that instances play in the constitution of reality and in human psychology. In this paper, we argue there is a need for a grammar that explicitly recognises the primary role of instances. We examine the limitations of traditional class-based approaches to conceptual modelling, especially for modern information environments. We then explore theoretical and practical motivations for instance-based modelling, and show how such an approach can address the limitations of traditional modelling approaches. We conclude by calling for the engineering of instance-based grammars as an important direction for conceptual modelling research to address the limitations of traditional approaches, and articulate five challenges to overcome in such efforts.

Process modeling is useful during the analysis and design of systems. Prior research acknowledges both impediments to process modeling that limits its use as well as customizations that can be employed to help improve the creation of process models. However, no research to date has provided a rich examination of the linkages between perceived process modeling impediments and process modeling customizations. In order to help address this gap, we first conceptualized perceived impediments to using process models as a “lack of fit” between process modeling and another factor: 1) the role the process model is intended for; and 2) the task at hand. We conducted a case study at two large health insurance carriers to understand why the lack of fit existed and then show different types of process modeling customizations used to address the lack of fit and found a variety of “physical” and “process” customizations employed to overcome the lack of fits. We generalize our findings into propositions for future research that examinethe dynamic interaction between process models and their need to be understood by individuals during systems analysis and design.