VRCC-3D+ is an implementation of a region connection calculus that qualitatively determines the spatial relation between two 3D objects in terms of connectivity and obscuration. The eight connectivity relations are conceptually the same as RCC8, but calculated in 3D rather than 2D. The fifteen obscuration relations are calculated using the projection of the 3D objects on a particular 2D plane and the distance of the objects from the viewpoint. Herein we present a smaller, more precise set of VRCC-3D+ obscuration relations that retains the qualities of being jointly exhaustive and pairwise disjoint. However, this new set of relations overcomes two problems that existed in the previous set of fifteen relations: (1) lack of a precise mathematical definition for a key predicate, InFront, and (2) lack of an intuitive mapping of converse relations.

Version control systems (VCS) are widely-used in the software industry. They provide a powerful, collaborative framework that allows software engineers to work together effectively. VCS allow users to track changes and merge ongoing work into concurrently evolving software projects. Distributed VCS such as Git, allow a great degree of flexibility, and provide powerful options for managing personal code and evolving collaborative content. Power incurs responsibility, and introducing collaborative coding and version control tools to new developers can create many challenges. Yet these tools, once mastered, are crucial skills for professional developers. In this paper, the authors introduce VCS to computer science students both in a custom environment specifically designed to support new developers and in a commercially-available native environment suitable for more experienced students. Results show that proper introduction of these powerful tools can make early exposure a positive and valued experience.

Version control systems (VCS), such as Subversion and Git, are pervasive in industry; they are invaluable tools for collaborative development that allow software engineers to track changes, monitor issues, merge work from multiple people, and manage releases. These tools are most effective when they are a part of a developer's habitual workflow. Unfortunately, the use of these powerful tools is often taught much later in a developer's educational career than other tools like programming languages or databases. Even an experienced student's first experience with version control can be unpleasant. In this paper, the authors analyze the workflow of two common Version Control Systems with different version controls (Subversion and Git) to build a common visual language for these systems (Version Control Visual Language, or VeCVL), and show that the same visual language applies to other version control systems.

No abstract

No abstract