It is said that "programming is writing is programming." Both programming and writing involve high-level plans. Programming involves understanding the problem, creating a design, and coding. In this paper, we further explore the nature of programming based on the concept that "programming is diagramming." A diagram can be coded, and both the code and diagram approximate the conceptual (mental) form of the programmer behind both. We adopt a new diagramming technique called a thinging machine (TM) and build a TM diagram of the solution to the involved problem, which is sliced to produce program statements, much as flowcharts are converted to code. The TM introduces a simplified form with its five basic operations, which are repeated throughout the flow of events until reaching the end of the solution description. A case study is given that establishes an account through which a user can apply for a modeled job. The resulting diagram and program point to a viable approach to developing computer programs.

In computer science, models are made explicit to provide formality and a precise understanding of small, contingent "universes" (e.g., an organization), as constructed from stakeholder requirements. Conceptual modeling is a fundamental discipline in this context whose main concerns are identifying, analyzing and describing the critical concepts of a universe of discourse. In the information systems field, one of the reasons why projects fail is an inability to capture requirements in a way that can be technically used to configure a system. This problem of requirements specification is considered to have "deficiencies in theory". We apply a recently developed model called the Thinging Machine (TM) model which uniformly integrates static and dynamic modeling features to this problem of requirements specification. The object-Oriented (OO) approach to modeling, as applied in Unified Modeling Language, is by far the most applied and accepted standard in software engineering; nevertheless, new notions in the field may enhance and facilitate a supplementary understanding of the OO model itself. We aim to contribute to the field of conceptual modeling by introducing the TM model's philosophical foundation of requirements analysis. The TM model has only five generic processes of things (e.g., objects), in which genericity indicates generality, as in the generic Aristotelian concepts based on abstraction. We show the TM model's viability by applying it to a real business system.